node-red-contrib-huemagic
node-red-contrib-huemagic copied to clipboard
Foddy
Hue motion sensor and dimmer switch not working
Hello,
As a very new Hue- and quite new node-red user I encountered a problem: the huemagic does not seem to be able to connect to my Hue Motion sensor through the bridge. The motion sensor works with native android app(s), both Philips' own and third party apps. There I can see all the movements, trigger scenes and access brightness and temperature information.
In node-red, everythin else works and the connection is established into my Hue bride, but when ever I try to connect motion sensor it just won't succeed.
The motion detector -node can find the sensor and it's name automatically with the search function, but thats it. If I try to push the node, or send a status message into it, I get following error:
"The sensor in not yet available. Please wait until HueMagic has established a connection with the bridge or check whether the resource ID in the configuration is valid."
Is there a known bug or way to fix this? Device seems to work but node's cannot connect into it. Same thing goes with the dimmer switch: should it be working with the 'button' node? It is not found at all.
Please complete the following information:
- Node-RED version: v2.1.6
- NodeJS version: v12.22.5
- Device running Node-RED: Raspberry Pi
Additional context Add any other context about the problem here.
This issue is very real. No error messages here but ever since updating to the latest version a couple of days ago, all motion sensors and smart buttons stopped working. Very annoying as my home automation heavily relies on HueMagic 😞
Update; I've downgraded to 4.2.1 and now everything works as expected again.
If it helps, I uninstalled and reinstalled, re-paired the hue bridge API and its all working ok now, fingers crossed
** update, a few hrs later ** its stopped again :-(
This issue is very real. No error messages here but ever since updating to the latest version a couple of days ago, all motion sensors and smart buttons stopped working. Very annoying as my home automation heavily relies on HueMagic 😞
Update; I've downgraded to 4.2.1 and now everything works as expected again.
@rvanbaalen sorry for the simple question, but I do not know - how did you downgrade within Node Red?
This issue is very real. No error messages here but ever since updating to the latest version a couple of days ago, all motion sensors and smart buttons stopped working. Very annoying as my home automation heavily relies on HueMagic 😞
Update; I've downgraded to 4.2.1 and now everything works as expected again.
@rvanbaalen sorry for the simple question, but I do not know - how did you downgrade within Node Red?
Not sure what your level of experience is but this is what I did:
SSH into the device running NodeRED
Go to ~/.node-red
Remove the addon npm uninstall nodered-contrib-huemagic
Install the old version
npm install [email protected]
All this without going to NodeRED in between.
Here experiencing issues with the Hue Button (only node I use). For me, this issue is looking like this issue; https://github.com/Foddy/node-red-contrib-huemagic/issues/227#issuecomment-1100605098 The node works for ~5 minutes, and then the button-node does stop working.
The issue above is fixed since version 4 but maybe the issue is still related?
For now trying to downgrade to 4.2.1. Not at home right now, so I will test later if the Button will work after downgrading. I will update this comment if I tried the button.
update downgraded, works fine with 4.2.1
me2, hue-magic was working for YEARS w/o problems/issues untill 4.2.2 dimmer isn't recognized from time to time and status of lights/groups as well believe me, i turn on/off a separate light in my kitchen under the cabinets with hue-magic -->> shelly 1pm, that was working 100% untill 4.2.2 conclusion: 4.2.1 AND GOOD btw, the correct command in my case is: npm install node-red[email protected]
This issue is very real. No error messages here but ever since updating to the latest version a couple of days ago, all motion sensors and smart buttons stopped working. Very annoying as my home automation heavily relies on HueMagic 😞
Update; I've downgraded to 4.2.1 and now everything works as expected again.
@rvanbaalen sorry for the simple question, but I do not know - how did you downgrade within Node Red?
Not sure what your level of experience is but this is what I did:
SSH into the device running NodeRED
Go to
~/.node-redRemove the addon
npm uninstall nodered-contrib-huemagicInstall the old version
npm install [email protected]All this without going to NodeRED in between.
Thanks this fix my issue! I was getting insane from debugging everything....
For Docker:
docker exec -it nodered_containername /bin/bash
cd /data
npm uninstall nodered-contrib-huemagic
npm install [email protected]
downgrade, still has issues with button switches and motion sensors
After my downgrade I left the system alone without any more changes for a day, then just like magic it all works flawless again, weird but i'm glad it works 😊 hoping a fix for this issue is soon implemented so i can continue updating
Same problem here. I wonder when an update is available? I try to remove the 4.2.2 file but I cannot locate the folder on my raspberrypi openhab2 system. So has anyone an idea? /usr/lib/node_modules/node-red/node-red_modules --> is this the correct one? When I use the ls command: I see a whole bunch of files? --> no idea
This issue is very real. No error messages here but ever since updating to the latest version a couple of days ago, all motion sensors and smart buttons stopped working. Very annoying as my home automation heavily relies on HueMagic 😞
Update; I've downgraded to 4.2.1 and now everything works as expected again.
I have the exact same problem. The Version 4.2.2 does not work, 4.2.1 is OK. unfortunately the new version 4.2.2 does not work for me. The motion function is disturbed.
I have two Philis Hue Motion sensors and switch with each of them a KNX lamp. The function msg.payload.motion does not provide correct values anymore. After restarting the node, the function returns once or twice the correct value (true / false) but stops the operation at some point, without error message. Then it reports no motion at all although the sensor works correctly.
In version 4.2.1 (I deleted the module and installed it against the old version) everything works again without any change.
The problem cost me 2 days, why is not corrected ??? It is ka apparently known for 2-3 months.
Apparently the 4.2.2 can not be used, and all users download this broken version.
This is very annoying and not nice of the support team.
👎
