Unplugging Hue Bridge Crashes Node-Red #237
Labels
Comments
|
Same here, its not only unplugging. Its when in my case the raspberry loses the ethernet connection (due to restart of the router which I do on a nightly basis), HueJay creates a crash; |
|
Same here. |
|
So what I did as a hack to prevent this error is editing Transport.js in the Huejay module. Put a 'Return false;' at the latest catch to prevent the error being thrown. It works fine now. I might suggest a patch for Huemagic to have a try/catch in the Huejay call. See hack in Transport.js below (I know its terrible). |
Foddy
added a commit
that referenced
this issue
Jan 9, 2022
> **Attention!** HueMagic v4 + has been almost completely rewritten under the hood and requires at least the (square-shaped) Philips Hue Bridge firmware 1948086000+ from November 1st, 2021 ([Upgrade instructions](https://www.lighting.philips.com/content/B2C/en_US/microsites/meethue/marketing-catalog/huewireless_ca/support/security-advisory/general/where-and-how-can-i-update-my-hue-system-with-the-latest-software.html)) and Node-RED v1 + ([Upgrade instructions](https://nodered.org/docs/getting-started/local#upgrading-node-red)). If you are upgrading from a previous HueMagic version to the v4, you will have to reconfigure (not completely rebuild) all nodes by clicking them and selecting the appropriate device from the list. This also applies to nodes / functions that are operated in universal mode, as the numeric identifiers of the latest Philips Hue API version have been replaced in UUIDs. The nodes "Hue Switch", "Hue Button" & "Hue Tap" have been replaced in v4 by the universal and uniform node "Hue Buttons", which works with all button / switch devices that are connected to the Hue Bridge (please note here also the new API in the documentation). The request and return objects of the individual nodes are largely compatible with older HueMagic versions - with the exception of the nodes "Hue Bridge", "Hue Buttons", "Hue Scene" & "Hue Group". These need to be adjusted in the v4. Make sure that you meet the minimum technical requirements and have a quiet minute for the migration before upgrading to the v4. * HueMagic speaks now directly with the bridge without any submodules *(huejay dependency removed)* * Migrated to the newest CLIP/v2 API version from the Philips Hue bridge * Nodes are now updated via push notifications (SSE) from the bridge instead of periodic polling * Instant "current status" queries on each node with no loading time * "Hue Buttons" node supports all new Philips Hue buttons/switches (e.g. Dimmer Switch v2, Hue Wall Switch…) * All nodes provide additional property information in the output (check docs) * New universal node "Hue Buttons" replaces the following nodes: "Hue Switch", "Hue Button", "Hue Tap" * New "updated" object for all nodes, which only contains the properties that have been updated since the last state * New configuration option to suppress first message after node initialization (for all nodes) * New gradient color setting for compatible light sources (in "Hue Light node) * New inject button for almost all nodes, which triggers the current status of a node * New "universal mode" support for "Hue Rule" nodes * New SVG-version of each node icon for higher quality rendering in the Node-RED UI * New and full featured examples for each node right inside Node-RED * New color mix feature in "Hue Light" nodes with the ability to mix the current light color with another * New automatic brightness support based on the current time for "Hue Light" & "Hue Group" nodes * New "Superhero", "Neon City" & "Christmas" (for next year, sorry) animations in "Hue Magic" node * The custom alert effect on "Hue Light" & "Hue Group" nodes can now also be configured in brightness * All nodes will now also forward the last command that has been applied ([#249](#249)) * "Hue Temperature" & "Hue Brightness" nodes can now also be activated & deactivated * "Hue Light" & "Hue Group" nodes can now also receive XY color settings * "Hue Light" & "Hue Group" can now also receive a named color temperature setting * "Hue Light" & "Hue Group" nodes can now receive future brightness states in "turned off" mode ([#244](#244)) * Automatic light temperature setting outputs now values from 153 (coldest) to 500 (warmest) * Automatic color correction based on the light´s capabilities for more accurate color settings * Optimized node editor configuration UI to better match the current Node-RED´s UI * The option for "automatic firmware updates" on the bridge moved to the bridge configuration node * "Hue Group" node does no longer contain the "msg.info.model" & "msg.info.class" property * Fixed timeout connection issues to the bridge * Fixed an issue with non stopping custom animations ([#222](#222)), ([#224](#224)) & ([#226](#226)) (thx) * Node-RED will no longer crash if there is no active connection to the bridge ([#237](#237)) * Fixed an issue that prevented the light / group from not reporting its own status when queried & node events were deactivated ([#248](#248)) * Fixed an issue with nodes in universal mode ([#245](#245)) * A possible attack target has been fixed ([#217](#217)) * Moved away from "moment.js" to "Day.js" for date/time formatting inside the nodes * Updated README and help section on each node * Updated dependencies to the latest version
|
Fixed with v4 |
|
For me the problem persists, on network loss, Node-red crashes, I have the following in the logs: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When I unplug the power or the ethernet to my hue bridge, shortly thereafter node-red crashes, restarts, crashes, repeat. I've searched the issues section here, but couldn't find anything I recognized as relevant.
Flow to Reproduce
I don't have any specific flows. As far as I know, my flows are great - things have been working really well. Recently I got the idea that I should place my 2 Hue Bridges on smart switches, in case I ever wanted to reboot them / cut their power I wouldn't have to pull out furniture. When playing with cutting their power, I noticed it completely took down node-red and put it in a restart loop until the hue bridge is available again. I've tried playing with the poll interval in the settings - placing it really high, but doesn't seem to make much of a difference. I have a lot of flows sending commands to the 2 hubs - they all seem to work well as long as the bridge is available.
Expected behavior
If I lose a hub, either by me unplugging it or it dying, or even a network failure, I'm hoping to keep it from taking down all of node-red.
Screenshots
None
Please complete the following information:
Additional context
I don't really need to cut power to the hue bridges - they are pretty stable. But I'm concerned now that if one of them dies or loses network it will break node-red.
The text was updated successfully, but these errors were encountered: