Phil G

Hello, I am not sure what to expect from this NS. After installation, I have a single node reporting 11 parameters. Interesting, but I'm wondering if I'm missing the intended functionality. I'm not sure of the value of knowing that I have 37 Insteon, 17 Z-Wave nodes, or 376,242 error log entries. I learn a lot from browsing these forums and occasionally find something new and interesting to incorporate. Just discovered the occupancy servers last week after 10 years of playing around with this system. BTW, I appreciate the trial license option. Suggest that you put this information into the description on the NS Store.

RE: changing Hue bridge ip / static Good idea but still no success. Only getting 1 node. I set the bridge with a new and static ip, then logged in to Hue's site (meethue.com) to verify that the bridge successfully registered with its new ip since the NS tries to find it there. Speaking of that, I what the NS is passing to Hue in order to discover the bridge ip? Here are some log excerpts: hue:connect: Saved bridges information is not found hue:connect: No bridge configuration found, trying discovery... INFO phue:connect: Attempting to connect to the bridge... INFO phue:connect: Error opening config file, will attempt bridge registration INFO interface:_message: Successfully set key = notices 2022-06-03 14:49:50,347 Thread-1 udi_interface INFO phue:get_ip_address: Connecting to discovery.meethue.com/ 2022-06-03 14:49:50,392 Thread-1 udi_interface ERROR hue:connect: Cannot find Hue Bridge Then it tries to connect to this ip, below, but times out, my LAN range is 10.0 so this is an invalid ip: ERROR phue:request: POST Request to 192.168.1.2/api timed out Looks like a lot of python errors too, regarding failed communications. I don't know how to connect with the dev since the PG3 store links to the Hue dev site. I guess I could create a dev account and try to track him down but it's a free app, so not much motivation to solve this. I think I'll try a factory reset on the bridge next. Thanks for your help, Phil

Thank you for the reply. I discovered that the Hue NS is still installed and connected on PG2 to my old ISY. Don't know how I managed mess this up, but now I need to figure out how to delete the PG2 NS that is showing 'connected' to an ISY that is now sitting unpowered on my spares shelf. Very surprising, because I remember deleting all node servers on PG2 before moving over to Polisy and PG3.

Some cool new buttons with 5.4.4: Let's try that BIOS upgrade, right? Yikes! Recommendations??

Jason, I seem to be having the same issue. Did you find a solution? I only see 1 node, huebridge, on both the IoP and the PG3. I have tried StangMan's directions. Also tried 'add all nodes' from the Node Servers > Configure drop-down, and the 'Re-Discover Bulbs' button for the IoP Hue node. Thanks in advance for any help.

I assume everyone on this thread talking about Hue lighting is using the Polisy and not the Polyglot Cloud? I can't find a Hue NS in the cloud store.