Unused Tap chrashes nodered #246
Comments
|
My Node-RED within Home Assistant is doing the same thing except that I was using Tap switches before this issue arrived. I have two HUE tap switches and a HUE smart button switch as input nodes. These are not configured with the HUE application (on IOS and that executes in the HUE Bridge) and are used only in Node-RED. They stopped working a few days ago. The Node-RED log file shows that activation of any switch on either of the two tap switches generates an uncaught exception error HUE version (reported from IOS app) 3.48.0 (11197) Node-RED log
|
|
Fixed in v4 |
|
Thanks for the update but this bug's symptoms remains in v4. HUE version (reported from IOS app) 3.48.0 (11197) LOG: Add-on: Node-RED Add-on version: 10.3.1 Please, share the above information when looking for help [cont-init.d] 00-banner.sh: exited 0. |
|
Can you please try it again with the v4.0.2 and report if this fixed the issue? I unfortunately don't own any Hue Taps so I can't test it on my own :S … |
|
Hi Foddy,
Thanks for the v4.0.2 update.
I have applied this and tested again with two tap switches and a button without any HUE Buttons nodes in use (just lights and the bridge).
I am pleased to confirm Node-Red’s log file is no longer reporting exception traps (it reports no response to button presses from any of my HUE switches).
However, another issue appears to have arrived with some lamps working okay from Node-Red but others are hanging with a status of “executing command…”.
The attached screen shot was taken several minutes after the command was issued – all lights should have been turned on with similar light settings.
The log file shows a status code 503 for the two lights that are in the hung state.
10 Jan 20:49:31 - [info] Starting flows
10 Jan 20:49:31 - [info] [hue-bridge:Philips hue] Initializing the bridge…
10 Jan 20:49:31 - [info] Started flows
10 Jan 20:49:31 - [info] [hue-bridge:Philips hue] Connected to bridge
10 Jan 20:49:32 - [info] [hue-bridge:Philips hue] Process ressources…
10 Jan 20:49:32 - [info] [hue-bridge:Philips hue] Initial emit of ressource states…
10 Jan 20:49:33 - [info] [hue-bridge:Philips hue] Keeping nodes up-to-date…
10 Jan 20:49:33 - [info] [hue-bridge:Philips hue] Subscribing to bridge events…
10 Jan 20:49:33 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates…
10 Jan 20:49:36 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Jan 20:49:36 - [info] [server:Home Assistant] Connected to http://supervisor/core
10 Jan 20:50:14 - [error] [hue-light:Backroom] Error: Request failed with status code 503
10 Jan 20:50:14 - [error] [hue-light:Kitchen Bench] Error: Request failed with status code 503
10 Jan 20:51:01 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates…
10 Jan 20:54:34 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates…
The following screen capture shows the configuration of one of the faulty lamps. All lamps are configured this way, even the ones thar are working okay. When you open the edit dialogue the light is always listed as the long HEX string, then you remap it to the correct name and then save it. If you open it again the HEX string reappears. I don’t care about the HEX strings (as such) because I rarely change these settings BUT it might indicate some scrambling of the lights in the bridge database?
Okay, so I then added a HUE Button configured as a tap switch and confirmed it is now generating events that are being seen within Node-RED and not crashing it – but the issue with the hanging lamps remains.
I deleted one of the lamp nodes and re-added it from the library and it generated the same result.
So, the issue with the traps appears to have gone but a new issue has appeared in its place.
Thanks for your support of this great library.
I’m happy to assist with any button testing you need (as you don’t actually have any HUE buttons). 😊
regards,
Greg Belcher
From: Foddy ***@***.***>
Sent: Monday, 10 January 2022 19:23
To: Foddy/node-red-contrib-huemagic ***@***.***>
Cc: isaac-the-newt ***@***.***>; Comment ***@***.***>
Subject: Re: [Foddy/node-red-contrib-huemagic] Unused Tap chrashes nodered (#246)
Can you please try it again with the v4.0.2 and report if this fixed the issue? I unfortunately don't own any Hue Taps so I can't test it on my own :S …
—
Reply to this email directly, <#246 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AWY7QE7TUMKXADUE7GWBFODUVKJPZANCNFSM5DSQPOJA> unsubscribe.
Triage notifications on the go with GitHub Mobile for <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> iOS or <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> Android.
You are receiving this because you commented. <https://github.com/notifications/beacon/AWY7QEYZOONS3U4GLPVJRWDUVKJPZA5CNFSM5DSQPOJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHQPIQGY.gif> Message ID: ***@***.***>
|
|
PS – the log file has “resource” and “resources” misspelt.
There is only one “s” in the middle of the word.
regards,
Greg Belcher
From: Greg Belcher ***@***.***>
Sent: Monday, 10 January 2022 21:42
To: 'Foddy/node-red-contrib-huemagic' ***@***.***>; 'Foddy/node-red-contrib-huemagic' ***@***.***>
Cc: 'Comment' ***@***.***>
Subject: RE: [Foddy/node-red-contrib-huemagic] Unused Tap crashes nodered (#246)
Hi Foddy,
Thanks for the v4.0.2 update.
I have applied this and tested again with two tap switches and a button without any HUE Buttons nodes in use (just lights and the bridge).
I am pleased to confirm Node-Red’s log file is no longer reporting exception traps (it reports no response to button presses from any of my HUE switches).
However, another issue appears to have arrived with some lamps working okay from Node-Red but others are hanging with a status of “executing command…”.
The attached screen shot was taken several minutes after the command was issued – all lights should have been turned on with similar light settings.
The log file shows a status code 503 for the two lights that are in the hung state.
10 Jan 20:49:31 - [info] Starting flows
10 Jan 20:49:31 - [info] [hue-bridge:Philips hue] Initializing the bridge…
10 Jan 20:49:31 - [info] Started flows
10 Jan 20:49:31 - [info] [hue-bridge:Philips hue] Connected to bridge
10 Jan 20:49:32 - [info] [hue-bridge:Philips hue] Process ressources…
10 Jan 20:49:32 - [info] [hue-bridge:Philips hue] Initial emit of ressource states…
10 Jan 20:49:33 - [info] [hue-bridge:Philips hue] Keeping nodes up-to-date…
10 Jan 20:49:33 - [info] [hue-bridge:Philips hue] Subscribing to bridge events…
10 Jan 20:49:33 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates…
10 Jan 20:49:36 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Jan 20:49:36 - [info] [server:Home Assistant] Connected to http://supervisor/core
10 Jan 20:50:14 - [error] [hue-light:Backroom] Error: Request failed with status code 503
10 Jan 20:50:14 - [error] [hue-light:Kitchen Bench] Error: Request failed with status code 503
10 Jan 20:51:01 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates…
10 Jan 20:54:34 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates…
The following screen capture shows the configuration of one of the faulty lamps. All lamps are configured this way, even the ones thar are working okay. When you open the edit dialogue the light is always listed as the long HEX string, then you remap it to the correct name and then save it. If you open it again the HEX string reappears. I don’t care about the HEX strings (as such) because I rarely change these settings BUT it might indicate some scrambling of the lights in the bridge database?
Okay, so I then added a HUE Button configured as a tap switch and confirmed it is now generating events that are being seen within Node-RED and not crashing it – but the issue with the hanging lamps remains.
I deleted one of the lamp nodes and re-added it from the library and it generated the same result.
So, the issue with the traps appears to have gone but a new issue has appeared in its place.
Thanks for your support of this great library.
I’m happy to assist with any button testing you need (as you don’t actually have any HUE buttons). 😊
regards,
Greg Belcher
From: Foddy ***@***.***>
Sent: Monday, 10 January 2022 19:23
To: Foddy/node-red-contrib-huemagic ***@***.***>
Cc: isaac-the-newt ***@***.***>; Comment ***@***.***>
Subject: Re: [Foddy/node-red-contrib-huemagic] Unused Tap chrashes nodered (#246)
Can you please try it again with the v4.0.2 and report if this fixed the issue? I unfortunately don't own any Hue Taps so I can't test it on my own :S …
—
Reply to this email directly, <#246 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AWY7QE7TUMKXADUE7GWBFODUVKJPZANCNFSM5DSQPOJA> unsubscribe.
Triage notifications on the go with GitHub Mobile for <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> iOS or <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> Android.
You are receiving this because you commented. <https://github.com/notifications/beacon/AWY7QEYZOONS3U4GLPVJRWDUVKJPZA5CNFSM5DSQPOJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHQPIQGY.gif> Message ID: ***@***.***>
|
|
This update is checking for new firmware updates for the HUE bridge every five minutes. 11 Jan 00:23:10 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates… |
|
This is not a correct behaviour. You can deactivate the automatic firmware updates for now in the bridge configuration. HueMagic should normally check for updates every 3h... I will take a look at this issue |
* Fixed an issue with the bridge config node checking for updates too frequently ([#246](#246 (comment))) * Fixed an issue with multiple bridges configured
|
Hi Foddy,
Updated to HueMagic Version 4.0.4 and the firmware update check has reverted to every 3 hours – thanks.
16 Jan 14:39:21 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates…
16 Jan 17:39:21 - [info] [hue-bridge:Philips hue] Checking for Hue Bridge firmware updates…
16 Jan 18:00:20 - [error] [hue-light:Backroom] Error: Request failed with status code 503
16 Jan 18:00:20 - [error] [hue-light:Kitchen Bench] Error: Request failed with status code 503
Can you say what an error status code 503 represents?
This comes from the same two HUE lights; all other (seven) lights work fine.
The same two lights work fine using the HUE app on IOS.
I’ve deleted and re-added these two lights in Node-RED and the same error results.
Thanks.
regards,
Greg Belcher
From: Foddy ***@***.***>
Sent: Tuesday, 11 January 2022 18:52
To: Foddy/node-red-contrib-huemagic ***@***.***>
Cc: isaac-the-newt ***@***.***>; Comment ***@***.***>
Subject: Re: [Foddy/node-red-contrib-huemagic] Unused Tap chrashes nodered (#246)
This is not a correct behaviour. Zhou can deactivate the automatic firmware updates for now in the bridge configuration.
HueMagic should normally check for updates every 3h... I will take a look at this issue
—
Reply to this email directly, <#246 (comment)> view it on GitHub, or <https://github.com/notifications/unsubscribe-auth/AWY7QE2ECSHOI2OLKUL4ZJ3UVPORBANCNFSM5DSQPOJA> unsubscribe.
Triage notifications on the go with GitHub Mobile for <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> iOS or <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> Android.
You are receiving this because you commented. <https://github.com/notifications/beacon/AWY7QE7E6PY3X6OA4OB62QDUVPORBA5CNFSM5DSQPOJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHQXIECA.gif> Message ID: ***@***.***>
|
|
Hi Foddy,
Updated Node-RED on Home Assistant to 2.2 this morning and HueMagic is crashing on start.
This just loops continually. I will be rolling back my upgrade but captured this snippet from the log file before doing so.
1 Feb 09:37:40 - [info] [hue-bridge:Philips hue] Keeping nodes up-to-date…
1 Feb 09:37:40 - [info] [hue-bridge:Philips hue] Subscribing to bridge events…
1 Feb 09:37:40 - [red] Uncaught Exception:
1 Feb 09:37:40 - [error] TypeError: Cannot read properties of undefined (reading 'length')
at new HueBridgeMessage (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/utils/messages.js:17:61)
at HueBridge.get (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge-config.js:306:23)
at /config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge.js:84:30
at EventEmitter.<anonymous> (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge-config.js:556:7)
at EventEmitter.emit (node:events:390:28)
at HueBridge.pushUpdatedState (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge-config.js:275:16)
at Timeout._onTimeout (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge-config.js:177:13)
at listOnTimeout (node:internal/timers:557:17)
at processTimers (node:internal/timers:500:7)
[09:37:40] INFO: Starting Node-RED...
start
node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
2022/02/01 09:37:42 [error] 552#552: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "192.168.0.100:8123"
1 Feb 09:37:42 - [info]
Welcome to Node-RED
===================
regards,
Greg Belcher
|
|
Hi Foddy,
Rolling back didn’t solve this issue.
I’ve had to disable the HUE Bridge node and re-deploy the configuration to stop Node-RED from crashing.
HueMagic is at Version 4.1.0
regards,
Greg Belcher
From: Greg Belcher ***@***.***>
Sent: Tuesday, 1 February 2022 09:46
To: 'Foddy/node-red-contrib-huemagic' ***@***.***>; 'Foddy/node-red-contrib-huemagic' ***@***.***>
Cc: 'Comment' ***@***.***>
Subject: Node-Red 2.2 HueMagic crashing on start
Hi Foddy,
Updated Node-RED on Home Assistant to 2.2 this morning and HueMagic is crashing on start.
This just loops continually. I will be rolling back my upgrade but captured this snippet from the log file before doing so.
1 Feb 09:37:40 - [info] [hue-bridge:Philips hue] Keeping nodes up-to-date…
1 Feb 09:37:40 - [info] [hue-bridge:Philips hue] Subscribing to bridge events…
1 Feb 09:37:40 - [red] Uncaught Exception:
1 Feb 09:37:40 - [error] TypeError: Cannot read properties of undefined (reading 'length')
at new HueBridgeMessage (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/utils/messages.js:17:61)
at HueBridge.get (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge-config.js:306:23)
at /config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge.js:84:30
at EventEmitter.<anonymous> (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge-config.js:556:7)
at EventEmitter.emit (node:events:390:28)
at HueBridge.pushUpdatedState (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge-config.js:275:16)
at Timeout._onTimeout (/config/node-red/node_modules/node-red-contrib-huemagic/huemagic/hue-bridge-config.js:177:13)
at listOnTimeout (node:internal/timers:557:17)
at processTimers (node:internal/timers:500:7)
[09:37:40] INFO: Starting Node-RED...
start
node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
2022/02/01 09:37:42 [error] 552#552: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "192.168.0.100:8123"
1 Feb 09:37:42 - [info]
Welcome to Node-RED
===================
regards,
Greg Belcher
|
Describe the bug
When I hit a Button on a Tap bordered crashes
Flow to Reproduce
I don't use my Taps in any flow
Expected behavior
Nothing. No crash
Please complete the following information:
Additional context
The text was updated successfully, but these errors were encountered: