node-red-contrib-huemagic: Repeat commands make "executing command" status getting stuck
Describe the bug When sending the command to set a bulb to the same state that it already has the “executing command” status gets stuck
Flow to Reproduce
[{"id":"5b4e2a7dc2c82fd5","type":"hue-light","z":"d6bf57b796e15a50","name":"Bulb 1","colornamer":true,"skipevents":false,"initevents":false,"x":800,"y":160,"wires":[[]]},{"id":"7fc82b42658a7e2d","type":"inject","z":"d6bf57b796e15a50","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"{\"brightness\":50, \"color\":\"green\"}","payloadType":"json","x":550,"y":160,"wires":[["5b4e2a7dc2c82fd5","5b4e2a7dc2c82fd5"]]}]
(You’ll have to set to your own Hue Hub + Bulb obviously 😉 )
To reproduce click on “inject” multiple times.
Expected behavior Node should return to “turned on 50%” or “turned off” or something like that status message if no change has to happen.
Screenshots
Please complete the following information:
- Node-RED version: v2.2.0
- NodeJS version: v14.18.2
- Device running Node-RED: Unraid on Intel® Core™ i5-10600 CPU via Docker
Additional context Nope
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 1
- Comments: 19 (1 by maintainers)
This is absolutely awful, and I cannot believe this bug isn’t getting fixed.
Here it actually gets stuck - as in, the lights are not getting switched anymore. And that’s with one single hue bulb. All it takes is turning on and off the light a few times, and then the room stays dark until nodered gets redeployed.
Obviously I have to toss out huemagic right then and there. The lights have to work, no ifs and buts. I replaced the huemagic node with an MQTT node sending the command to FHEM, which then executes it - and it works perfectly, so it’s not like there’s anything wrong with the flow.
OK, no solution from @BlaM so the node is gone for me. Lights are too important for that shitty programmed node.
Same problem here, this was a great node but is now worthless 😦
Same here. Annoying. Same bug is described there: https://github.com/Foddy/node-red-contrib-huemagic/issues/345
Same problem here: Node-RED v2.1.4 with Huemagic 4.2.2 This is a very serious issue and I am surprised it does not receive more attention.