search

Foddy / node-red-contrib-huemagic

Philips Hue node to control bridges, lights, groups, motion sensors, temperature sensors and Lux sensors using Node-RED.
https://flows.nodered.org/node/node-red-contrib-huemagic
Apache License 2.0
201 stars 67 forks source link

Sorry. Your selected Hue Bridge is invalid [object: Object] #143 - still a problem after 4.0.2 update #265

Open HonestJohn61 opened 2 years ago

HonestJohn61 commented 2 years ago

Describe the bug Setting up a new Hue Bridge connection succeeds in getting a API key but is then unable to connect

Please complete the following information:

Foddy commented 2 years ago

Can you please share the logs of your Node-RED instance?

HonestJohn61 commented 2 years ago

Thanks for such a quick response. Here's the log from yesterday. I updated to 4.0.2 at 17.10. After that failed to work, I tried various things including uninstalling through the Palette manager (17:30), restarting Node-RED and reinstalling again (17:31). I think the key information lies between 17:33:57 and 17:35:41. If there's anything else I can provide please let me know.

node-RED log.csv

Foddy commented 2 years ago

Okay, there seems to be a general problem with your OpenSSL installation/version. Do you use a different / custom port?

This is what happens, when HueMagic tries to connect to the Hue bridge: Error: write EPROTO 140708609617224:error:1408F10B:SSL routines:ssl3_get_record:wrong version

I would recommend to install Node-RED via docker and try it again. Otherwise you could google the error message and maybe fix this issue on your instance. It seems like this problem is not caused by the HueMagic library.

HonestJohn61 commented 2 years ago

Hi, Thanks for the response.

I saw the error you've highlighted, but what about the errors I highlighted that precede this error - are they relevant? But I ask this without understanding what any of them mean!

I'm surprised at your suggestion because I've been running Node-RED under Docker for many months now without issue until adding Huemagic. The installation under Docker is completely standard: I used nodered/node-red:latest from the Docker Hub registry and launched without making any customisation.

HonestJohn61 commented 2 years ago

I'm also a little confused as to why the HueMagic node can communicate with the Hue Hub to obtain a API logon key but then fail to complete the process. Is the first part of the process insecure, and then the connection becomes secure?

Foddy commented 2 years ago

Sorry for my late response. Regarding to your question, yes, it is indeed the case that requesting a new key in the bridge configuration is currently done via the v1 API endpoint and http only.

That is because the new CLIP/v2 API by Philips is still not 100% finished – like this feature (or at least not documented officially right now).

Can you please make sure, that you have the latest (stable) Philips Hue Bridge firmware installed? I am also running Node-RED inside the official docker container with HueMagic installed and can’t reproduce this error.

HonestJohn61 commented 2 years ago

Hi, Thanks for the reply. Yes, the Hue app reports that the Hue has the latest software - 1.49.1949107040 on a BSB002 device.

I'm casting round here for anything that might be relevant, but two things to mention.

Firstly the server that Docker/Node-RED runs on also runs an openHAB instance (in another Docker container) that has a connection to the Hue hub (which works fine) - but might running two connections from the same network IP cause a problem?

Secondly, the Node-RED Docker container has a Host network configuration (as does the openHAB one) but that shouldn't matter should it?

nixilb commented 1 year ago

Same pb.Hue magic finds the Hub (the IP address) but unable to connect to it later. Image There is no network pb to access the Hue gateway Image