New firmware 14/3/22 1950111030 gives an HTTP 500 error

[Travelbacon]

Describe the bug
Since the update to 1950111030 for the HueBridge, the nodes to activate a scene give a HTTP 500 error and the node remains in status "Executing command forever". I noticed this on my current Raspberry Pi running Node Red. I installed a fresh version NodeRed and HueMagic on a different Pi. I Connected the Bridge to Huemagic and made a simple flow with an injection and a scene. This had the same result.

All the other nodes are working fine. And Apple Home Kit for instance is running fine with scenes.

Flow to Reproduce
Any setup with a scene in it.

Expected behavior
To activate the requested scene.

Screenshots

Log report
15 Mar 20:10:21 - [info] [hue-bridge:Philips hue] Connected to bridge
15 Mar 20:10:22 - [info] [hue-bridge:Philips hue] Processing bridge resources…
15 Mar 20:10:23 - [info] [hue-bridge:Philips hue] Initial emit of resource states…
15 Mar 20:10:26 - [info] [hue-bridge:Philips hue] Keeping nodes up-to-date…
15 Mar 20:10:26 - [info] [hue-bridge:Philips hue] Subscribing to bridge events…
15 Mar 20:10:34 - [error] [hue-scene:Helder] Error: Request failed with status code 500

Please complete the following information:

• Node-RED version: 2.2.2
• NodeJS version: 14.19.0
• Device running Node-RED: 2 Raspberry Pis with Raspbian

And of course I've rebooted the Hue Bridge. ;)

[MrTeal]

Same for me indeed. Scenes give a 500 in the logs and stay on executing command:
16 Mar 08:27:35 - [info] [hue-bridge:Philips hue] Connected to bridge
16 Mar 08:27:37 - [info] [hue-bridge:Philips hue] Processing bridge resources…
16 Mar 08:27:37 - [info] [hue-bridge:Philips hue] Initial emit of resource states…
16 Mar 08:27:38 - [info] [hue-bridge:Philips hue] Keeping nodes up-to-date…
16 Mar 08:27:38 - [info] [hue-bridge:Philips hue] Subscribing to bridge events…
16 Mar 08:28:06 - [error] [hue-scene:Sterrenlicht sterk] Error: Request failed with status code 500

[Kedarebwyn]

This issue is indeed related to the latest firmware, which seems to have activated a new version of the API used on the Philips Hue Bridge.

A temporary workaround, until @Foddy can fix the issue permanently is to locally change the file 'hue-scene.js'. Specifically the line:

node-red-contrib-huemagic/huemagic/hue-scene.js

Line 90 in 7a0d17d

patchObject["recall"] = { status: "active" };

to this:
patchObject["recall"] = { action: "active" };

[Travelbacon]

I can confirm this patch.
Thank you for this quick solution!

[AndreTzerra]

Indeed, after changing the line it's working again!
Thanks for sharing.

[MrMiracles]

This issue is indeed related to the latest firmware, which seems to have activated a new version of the API used on the Philips Hue Bridge.

A temporary workaround, until @Foddy can fix the issue permanently is to locally change the file 'hue-scene.js'. Specifically the line:

node-red-contrib-huemagic/huemagic/hue-scene.js

Line 90 in 7a0d17d

patchObject["recall"] = { status: "active" };

to this: patchObject["recall"] = { action: "active" };

Thanks, that works for me too!

[xtazy]

Another issue is for the 'group' node, which is not outputing a status anymore

[moeb98]

+1… and this is very annoying since a lot of my flows are relying on that. Any idea about a root cause and resolutions here?

[dongennl]

same, 3 bathrooms are in the dark most of the time now or the lights stay on indefinitely. Does anyone have a pull request ready? This seems very urgent.

[dongennl]

it works, I'll try and do a pull

[dafi87]

Are you sure your PR doesn't break it for people with the old firmware?
Also, it doesn't fix the issue with group nodes not sending out events anymore.

[dongennl]

hi, no, I have no way to test on older firmware; just trying to help those who's rooms are dark.
If anyone else is able to test backward compatibility or make the code conditional on firmware version that would be very welcome, I do not know how to do those things.

[TurboKanne]

This issue is indeed related to the latest firmware, which seems to have activated a new version of the API used on the Philips Hue Bridge.

A temporary workaround, until @Foddy can fix the issue permanently is to locally change the file 'hue-scene.js'. Specifically the line:

node-red-contrib-huemagic/huemagic/hue-scene.js

Line 90 in 7a0d17d

patchObject["recall"] = { status: "active" };

to this: patchObject["recall"] = { action: "active" };

Nice, after deleting a lot of flows, deleting rooms and scenes in the bridge i stumpled upon this ... and this seems to help as a workaround. Thanks. Starting to re-built the settings in Hue App, Bridge and Home Assistant Node-Red :-( and :-)