I am using a HueSwitch-Node in hue magic. The switch itself is configured and functioning within the hue bridge. The switch can turn lights on and off.
Now, I want to use the switch in Node-red.
BUT the switch node does not throw (send) messages to a debug-node. So far, it's the same as in this Tread. https://discourse.nodered.org/t/i-have-a-problem-with-the-hue-switch/8235
But in difference to this trade I haven´t also any messages under the switch.
It is the same behavior for the motion sensors. Lights can be easily controlled and the status is updated.
v0.20.8 in node red menue
node -v 10.16.3
2.0.2 HueMagic
What I have tried by now is:
- reboot raspberry
- Uninstall / Install hue magic
- Hue Bridge removed and reintegrated
Unfortunately without success. Can someone help me there?
Is it possibly related to the update to 2.0.2? However, I have previously removed two hue bridges that were not in use. I just do not know how I can proceed now.
Maybe someone in my log will see an indication of the problem.
It's weird that the log keeps repeating itself.
pi@raspberrypi:~ $ node-red-log
Welcome to Node-RED
===================
8 Oct 20:08:23 - [info] Node-RED version: v1.0.1
8 Oct 20:08:23 - [info] Node.js version: v10.16.3
8 Oct 20:08:23 - [info] Linux 4.19.66-v7+ arm LE
8 Oct 20:08:24 - [info] Loading palette nodes
8 Oct 20:08:26 - [info] Settings file : /home/pi/.node-red/settings.js
8 Oct 20:08:27 - [info] Context store : 'default' [module=memory]
8 Oct 20:08:27 - [info] User directory : /home/pi/.node-red
8 Oct 20:08:27 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Oct 20:08:27 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
8 Oct 20:08:27 - [info] Creating new flow file
8 Oct 20:08:27 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
8 Oct 20:08:27 - [info] Starting flows
8 Oct 20:08:27 - [info] Started flows
8 Oct 20:08:27 - [error] Unable to listen on http://127.0.0.1:1880/
8 Oct 20:08:27 - [error] Error: port in use
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
8 Oct 20:08:29 - [info]
Welcome to Node-RED
===================
8 Oct 20:08:29 - [info] Node-RED version: v1.0.1
8 Oct 20:08:29 - [info] Node.js version: v10.16.3
8 Oct 20:08:29 - [info] Linux 4.19.66-v7+ arm LE
8 Oct 20:08:30 - [info] Loading palette nodes
8 Oct 20:08:33 - [info] Settings file : /home/pi/.node-red/settings.js
8 Oct 20:08:33 - [info] Context store : 'default' [module=memory]
8 Oct 20:08:33 - [info] User directory : /home/pi/.node-red
8 Oct 20:08:33 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Oct 20:08:33 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
8 Oct 20:08:33 - [info] Creating new flow file
8 Oct 20:08:33 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
8 Oct 20:08:33 - [info] Starting flows
8 Oct 20:08:33 - [info] Started flows
8 Oct 20:08:33 - [error] Unable to listen on http://127.0.0.1:1880/
8 Oct 20:08:33 - [error] Error: port in use
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
8 Oct 20:08:36 - [info]
Welcome to Node-RED
===================
8 Oct 20:08:36 - [info] Node-RED version: v1.0.1
8 Oct 20:08:36 - [info] Node.js version: v10.16.3
8 Oct 20:08:36 - [info] Linux 4.19.66-v7+ arm LE
8 Oct 20:08:37 - [info] Loading palette nodes
8 Oct 20:08:40 - [info] Settings file : /home/pi/.node-red/settings.js
8 Oct 20:08:40 - [info] Context store : 'default' [module=memory]
8 Oct 20:08:40 - [info] User directory : /home/pi/.node-red
8 Oct 20:08:40 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Oct 20:08:40 - [info] Flows file : /home/pi/.node-red/flows_raspberrypi.json
8 Oct 20:08:40 - [info] Creating new flow file
8 Oct 20:08:40 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
8 Oct 20:08:40 - [info] Starting flows
8 Oct 20:08:40 - [info] Started flows
8 Oct 20:08:40 - [error] Unable to listen on http://127.0.0.1:1880/
8 Oct 20:08:40 - [error] Error: port in use
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
8 Oct 20:08:43 - [info]
Welcome to Node-RED
===================
8 Oct 20:08:43 - [info] Node-RED version: v1.0.1
8 Oct 20:08:43 - [info] Node.js version: v10.16.3
8 Oct 20:08:43 - [info] Linux 4.19.66-v7+ arm LE
Looks like you already have an instance running as the port is in use.
Many thanks for the answer. Is it possible that a second instance is started via iobroker? Is it basically possible that the sensor values in hue magic are not updated because of two running instances? The status of the lights is updating strangely.
