search

lopelex / node-red-contrib-harmony

Node-RED integration for Harmony hub
MIT License
13 stars 6 forks source link

hubs scan find only philips hue bridge hubs #24

Open eh03 opened 3 years ago

eh03 commented 3 years ago

hi, iam running nodered on windows, and iam experiencing some crush time to time; i have to restart node red manually. after some investigation i found that nodered close always with these messages:

... 21 Oct 04:06:32 - [info] HarmonyWS close (192.168.1.111) 21 Oct 04:06:35 - [info] HarmonyWS open (192.168.1.111) 21 Oct 05:23:35 - [info] HarmonyWS close (192.168.1.111) 21 Oct 05:23:56 - [red] Uncaught Exception: 21 Oct 05:23:56 - Error: connect ETIMEDOUT 192.168.1.111:8088 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1159:16)

192.168.1.111 is the ip address of my harmony hub.

after that i tryed to reconfigure the ip in nodered, but when iam in configuration searching for hubs, it does not show 192.168.1.111, but it shows me other 2 ip address, my 2 philips hue hub. it could be some sort of conflict?

asilva54 commented 3 years ago

I am also getting this, i randomly wake up and node-red cannot find any of my hubs.

When i check the harmony app on my phone, the hubs show up fine (not "cloud")

zygi79 commented 2 years ago

Hello, it seems that there is not much update work going on here. I also have the issue, that in case my Harmony Hub shows the red light for a longer time I get the uncaught exception shown above leading to a shutdown of Node Red. The Hub list was never showing me the IP of my Harmony Hub additionally, I always had to add it manually.