Closed barns102 closed 4 years ago
We recently moved away from NGINX. Our images do set the permissions on the node binary. To fix this, set the server port to 3000 +.
We are going to make the default a higher port and only changer this for our pre-built images.
@resgroupmsr not the same issue this guy is having.
Please open a new issue. Anyway we are working on a fix for this in version 3.2.2. Will be out soon.
3.2.2 is published to NPM. It may take a few hours to show up.
I have been able to update to 3.2.2, but I still don’t see any accessories under the accessories tab, @mkellsy what am I doing wrong?
This is the only error (is it an error) showing up in the logs: 03/05/2020, 8:34:49 am [Broadlink RM] Broadlink RM won't detect device failures due to a permissions issues with "net-ping".
To fix:
Broadcom may be having issues
sudo setcap cap_net_raw+ep /usr/local/bin/node
You may also need to add the hoobs binary too
sudo setcap cap_net_raw+ep /usr/local/lib/node_modules/@hoobs/hoobs/bin/hoobs
@mkellsy This is what I got
Typos, sorry I am very busy, typing too fast.
/use -> /usr
Broadcom may be having issues
sudo setcap cap_net_raw+ep /usr/local/bin/node
You may also need to add the hoobs binary too
sudo setcap cap_net_raw+ep /usr/local/lib/node_modules/@hoobs/hoobs/bin/hoobs
@mkellsy So I have run those commands, and restarted, and the Broadlink error is no longer showing, but I still can’t see my accessories in the accessory tab.
@mkellsy Does this have something to do with the port ranges?
no
It's hard to say. Do the accessories show up in HomeKit?
@mkellsy Yeah they do show up in HomeKit, just not HOOBS UI.
Is this something I should get over, I just struggle when things don’t work as they should!!
FYI, I absolutely love HOOBS, it has transformed home automation for me.
Thanks for your help.
I think we might not have those accessories defined in HOOBS. It it is a TV type, we don't have that yet.
@mkellsy I have several accessories, TPLink sockets, Ring Doorbell, Panasonic TV, Mijia Cameras, Nest Protect, as well as the broadlink RM.
None of them show up.
I will need to investigate that. Make a system backup and a download your logs. Then email them to me mkellsy@hoobs.org
Config Screen -> Backup - System
@barns102 is the issue solved? if not reopen and provide more info
Hi, @BobbySlope no this issue is not resolved. I have already updated to 3.2.3 and yet I still don’t have any accessories showing in the HOOBS UI. My log is not reporting any errors.
did u sent the backup to @mkellsy ?
@BobbySlope. I tried to, but my email said the size of the file exceeds to limit. I will investigate this further.
Description A clear and concise description of what the bug is. On the HOOBS UI under the accessories tab I can’t see any accessories.
Version Please include the version of HOOBS you are using. 3.2.1
Did you upgrade Please let us know if you upgraded from a previous version.
Pervious version If you upgraded, please let us know your previous version. 3.2.0 Did you orginally upgrade to HOOBS 3 from HOOBS 2.1.1? Did you perform an upgrade from HOOBS 2.1.1? Some things are different.
What device are you using? Please let us know the device you are running HOOBS on.
If this is a custom install, what's your operating system? Please let us know what operating system and version you are using. Ex. Fedora 30 or macOS Catalina. Raspberry Pi List your plugins Please include a list of the plugins you are using. We need to be able to find it on NPM. If the plugin is no published, please include a link to the repository. Ring Broadlink RM TPLink Smarthome PanasonicTV Camera FFMPEG Mijia Camera
Post your config This can be found in the interface, Configuration -> Advanced or you can get it via SSH
cat ~/.hoobs/etc/config.json
Post your log You can get the log from the intercafe. This is in the Log section.
Additional context Add any other context about the problem here. The only error that has come up in the logs is the following: 02/05/2020, 10:37:52 am [Broadlink RM] Broadlink RM won't detect device failures due to a permissions issues with "net-ping".
To fix:
Run "which node" to determine your node path. Run "sudo setcap cap_net_raw+ep /path/to/node". Note: Replacing /path/to/node with the path you found in the first step. 02/05/2020, 10:37:52 am [Broadlink RM] Sky Toggle getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] TV Toggle getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] Soundbar Toggle getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] Sky Power getSwitchState: true 02/05/2020, 10:37:52 am [Broadlink RM] TV Power getSwitchState: true 02/05/2020, 10:37:52 am [Broadlink RM] Vol. Up getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] Sky and ChromeCast getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] Apple Tv getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] Netflix getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] Vol. Down getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] Sky Select getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] Chrome Cast Select getSwitchState: false 02/05/2020, 10:37:52 am [Broadlink RM] TV Mute getSwitchState: false