Phil G

FWIW, I'm having the same issues. I installed the NS today for the first time. The bridge node is listed, but no devices. No "discover devices" button. Hope this gets fixed, I was hoping for an easier integration with Somfy.

@Michel Kohanim, regarding Hue NS wish list, I would like to see support for effects. I am putting in some Gradient Light Strips that have some interesting effects available from the Hue app but the only effect available from the console is a color loop.

@RJ K, If it helps, this is my PG3 configuration: Also, log in to your "meethue" account and see if the "python_hue" app is listed:

@JacktheRipper, I'm having the same issue. Were you able to resolve it? I'm accessing the ISY remotely, using Launcher, win 10, fresh java install. I sometimes get a DHCP error from the ISY when I launch the admin console, but not always. Otherwise it always fails about 80-90% of the way in. Same results on 2 different computers, 1 Mac and 1 win10.

I am hopeful that UDI's approach to incentivizing NS development results in a paid NS version. I have some Hue strip lights on order now and plan to use much more in the future. I didn't stop to think about the fact that the current NS may not recognize these lights. oops. @Bumbershoot, do you have any indications that the current version is being revised by anyone?

I don’t have any suggestions. The current NS is great as far as I’m concerned. The configuration notes in PG3 are misleading (the ip key seems useless) and they are insufficient for this user who doesn’t know how to wade into the dev environment and search the developer’s notes. I don’t mean to sound critical. The NS is free, after all, which is why I suggested throwing some money at it when I couldn’t figure out how to resolve the ip problem.

Just do it after it grabs an initial IP address; reserve that address. If you don't, then you need to use the 'bridges' key and the ["x.x.x.x"] parameter format.

Thank you @Geddy and @bpwwer! I added the 'bridges' key, ip (formatted correctly), and restarted the NS. All the Hue lights popped up in the ISY w/o even a restart on the admin console.

The Hue NS doesn't update the Hue hub ip if it changes for whatever reason. It probably doesn't have anything to do with PG3 vs PG2, but I don't know how to evaluate that. The problem surfaced for me when all of my LAN ip's changed for an unrelated reason around the time I was moving from 994i/PG2 to Polisy/PG3. However, @Geddy and @bpwwer have found a way to force the NS to look for the hub at it's new ip: This solution worked for me.

The Hue NS quit working when I moved from PG2 to PG3. I believe the root cause was a concurrent LAN ip range change from 192.168.xxx to the 10.0.xxx. That change was unrelated to home automation but seems to have uncovered a problem that several others have noticed. The PG3 NS cannot find the Hue bridge if you make any router changes. I forced the Eero router back to the 192.168.xxx range, factory reset the Hue hub, verified that meethue.com is communicating with the hub, and then reinstalled the PG3 NS. Same outcome, a Hue node does appear is IoP, but no lighting nodes. The log files show that the NS is not finding the bridge. Using the 'ip' parameter does not help. Some files are missing with the new NS install on PG3, for example: FileNotFoundError: [Errno 2] No such file or directory: '/var/polyglot/.python_hue' 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 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 Getting a lot of python errors too, regarding failed communications. I put in a ticket, but we didn't get anywhere and it's not really UDI's problem, I guess. Any thoughts about what to try next? I don't know how to connect with the developer since the PG3 store links to the Hue dev site.

Is there any developer out there willing to update the Hue Hub NS? There seems to be a few of us here in PG3 world are not able to access nodes any more since PG2 went away. I'd be willing to support the effort financially. I'm guessing it might sell a few licenses on PG3 to offset costs.

@RJ K any success with your ticket? I also submitted one, but Michel wasn’t able to help out on this. My Eero router switched the LAN to 10.0… from 192.168… a few months ago (I probably caused that while trying to fix an HP printer problem) and I'm wondering if that may have created a problem. Any chance you have same situation?

No python in there now, but thanks for the suggestion.

I juggled ISY vs Insteon hub also, many years ago. I think it was because I thought I wanted HomeKit / iPhone control. Then I realized that looking for my phone, opening an app, finding the device, was much more work than just flipping a switch on a wall. The automation aspect was never a contest between the two, I just thought that I wanted a way to turn on a light while sitting on my couch. Dumb.

I recall needing to email my UUID to UDI sales so they could add it to the portal. Nothing magic about it.

Trying to stay optimistic! ? Those must be extremely old. I believe you but I don't recall ever seeing ISY marketed by Smarthome/Insteon.

Buy Now: https://www.insteon.com/isy-994i Looks like a new day is dawning!

Thank you, sir. I’ve been running a 994i for a long time and never knew about the node limits. Learned something new. Thanks again for the trial license.

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.

Thanks for that information. I had no idea. Some of the commenters here probably don't realize the affect they can have with the constant 'Insteon is dying' posts. Casual hobbyists like me can read one or two threads like that and get scared off investing any more in our 994/Insteon system, assuming that the world is coming to an end. I'm building a small retirement home and was worried about using Insteon because of the PLM issues. I feel safer about making that decision now and will definitely be buying a few PLMs when they get back in stock.

I wonder if anyone has kicked around the idea of crowd funding a bulk PLM rebuild. Sounds like there must be hundreds of dead candidates. Someone in this forum came up with a BOM for a rebuild using better capacitors and was successful, I think.