mauricedominic / node-red-contrib-huemagic

Philips Hue node to control bridges, lights, groups, motion sensors, temperature sensors and Lux sensors using Node-RED.
https://flows.nodered.org/node/node-red-contrib-huemagic-fork
Apache License 2.0
18 stars 2 forks source link

[Bug]: Hue Button stops sending messages #21

Open cmaoling opened 8 months ago

cmaoling commented 8 months ago

Node-Red-Contrib-Huemagic-Fork Version

4.2.8

Node JS Version

18.19.0

NPM Version

10.2.5

Node-Red Version

3.1.3

Operating System

Docker version 24.0.2, build cb74dfc

What happened?

Hue Button stops sending messages on the output after some/random time. Hue bridge is responsive in Node-Red so connection in general seems to be there...

How to reproduce?

I do not know.

Expected behavior:

Hue Button should issue messages while node-red is running.

Additional comments?

Additional comments here, if any.

Relevant log output

Let me know, what to provide. I am stuck on debugging this. Thx
groenerik commented 8 months ago

I noticed exactly the same thing happened to me as well. When pressing the physical Hue button the object doesn't output an event anymore. Last week I did some routine maintenance to my RPI setup. I updated the system. In Node-Red I updated all outdated packages.

When pressing the button of the object in the Node-Red interface the output shows status information: {"reachable":true, "connectionStatus":"connected", "button":false, "action":false, "updated":"2024-01-15T12:12:48+01:00"}

Output from the Hue Bridge node: {"id":"XXXXXXXXXXXXXXXX", "name":"Hue Bridge", "factoryNew":false, "replacesBridgeId":false, "dataStoreVersion":"165", "starterKitId":false, "softwareVersion":"1962097030", "apiVersion":"1.62.0", "zigbeeChannel":20, "macAddress":"XX:XX:XX:XX:XX:XX", "ipAddress":"192.168.112.155", "dhcpEnabled":true, "netmask":"255.255.255.128", "gateway":"192.168.112.190", "proxyAddress":false, "proxyPort":0, "utcTime":"2024-01-15T11:12:46", "timeZone":"Europe/Amsterdam", "localTime":"2024-01-15T12:12:46", "portalServicesEnabled":true, "portalConnected":"disconnected", "linkButtonEnabled":false, "touchlinkEnabled":false, "autoUpdatesEnabled":true, "users":[****], "updated":"2024-01-15T12:12:48+01:00", "model":{"id":"BSB002", "manufacturer":"Philips", "name":"Hue v2"}}

Node-Red-Contrib-Huemagic-Fork Version 4.2.8

NPM Version 8.19.4

Node JS Verion v16.20.2

Node-red Version: v3.02

System: RPI3B+

The current Hue firmware was released on 4 January, so that could also have broken something.


Update: I got it working again, which was (to be honost) more luck than wisdom. I tried to update NPM, NodeJS and Node-Red.

I got NPM to latest version, but then NodeJS could not be updated because my v16 was not compatible with the newest NPM.

Then I followed these instructions:

sudo apt update

sudo apt full-upgrade

sudo apt remove node

sudo apt remove nodejs

sudo apt install nodejs

reboot

and it worked again!

cmaoling commented 5 months ago

@groenerik thanks for the insight. Apologies got distracted for some time and had no time to follow up. So after your updates, which nodejs, node and npm do you have? Is this still functional....

In general I use node-red in a docker-based environment and pull currently "latest-18" from https://hub.docker.com/r/nodered/node-red/tags So I would like to avoid updating packaged w/in... I updated through the container image and now have: node v18.20.1 NPM 10.5.2 Node-Red 3.1.9

groenerik commented 5 months ago

Running the following versions here, all stable:

Node-Red-Contrib-Huemagic-Fork: v4.2.8 NPM Version: 10.5.0 Node JS Verion: V18.20.0 Node-red Version: v3.1.3 System: RPI3B+

cmaoling commented 5 months ago

Not on my side. Button nonfunctional this morning again.. Works after redeploy of node-red flow. :/