DualBandAid Posted December 28, 2023 Posted December 28, 2023 I have an EISY. I was able to get my Hue bulbs into the system. All was well. Then things got a little weird with one Hue device. I tried to delete the offending Hue device but couldn't. THEN!!!!... I had a grand idea that if I UNGROUPED the Hue bulbs, I could delete the errant Hue device. That worked. But then I couldn't group the devices again. So like an idiot, I tried to delete everything from the system. I deleted the Hue from the EISY; I went into Polyglot and deleted Hue there. Then I tried to reinstall. So that worked. But it appears that the only thing showing in the EISY is the Hub. There is an option to Rediscover Bulbs in the EISY. That does nothing. Also, jumping back, when I install the Hue back into Polyglot, it told me to hit the hue hub buttong and restart within 30 seconds. I did that. Nothing worked. I have tried many combinations of deleting and reinstalling and vomitting in my mouth in despair. Any thoughts?
Solution Geddy Posted January 3 Solution Posted January 3 @DualBandAid Did you attempt to directly connect bulbs to the eisy? Best I've seen is to simply use the Hue plugin (formerly Node Server) and control items that way. It's possible that the Hue Hub changed IP addresses in your network. Do you (or did you) have an IP reservation in the DHCP settings on the router? If the hub changed IP address during this the eisy is looking for it at the old address. You will need to hardcode the current IP in for the bridge. From the plugin "more info" config page: Quote bridges - this should be set to the list of Hue bridges if you have multiple you would like to be able to control, for example: ["10.0.1.1","10.0.2.1"] Make sure you include the square brackets [ ] and quotes around the IP address. I had an issue with the IP address changing when I first set it up and PG2 had a rough time getting the bridge connected again. When I setup PG3 I had a reservation made and haven't had to hard code the bridge. Make sure you've got all the lights in the bridge before you connect to it. Also, if any devices are on outlets that can turn them off (making them unreachable to the Hue Bridge) be sure to have them powered ON or at least "reachable" when you begin the linking process.
DualBandAid Posted January 4 Author Posted January 4 I will dig in and check everything when I'm home. I didn't realize I could connect all my bulbs DIRECTLY to the EISY - without using a hub - if that's what you mean. Is that what you mean? I'm not sure all my old bulbs could do that - nor do I know how. But one thing I want to add. I added a second hub, and that works find. I hit the button on the hub and restarted the node, and the outside lights were all recognized. Also, fwiw, I had no DHCP reservations nor did I tweak anything on my router/switch/modem at all. It's all off the shelf.
Geddy Posted January 5 Posted January 5 21 hours ago, DualBandAid said: I didn't realize I could connect all my bulbs DIRECTLY to the EISY - without using a hub - if that's what you mean. Is that what you mean? No, just some have attempted to make a direct connection since with Zigbee there might be a link available, but for Hue I think the only/best method is still through the Hue Hub/Bridge. 21 hours ago, DualBandAid said: I added a second hub, and that works find. Fine? Yes, if you added a second hub that had not been in the system at all it probably added correctly. Sounds like the first one changed IP address and the plugin is looking for it at the old IP. That's where you need to hard code it in the settings in the dashboard for the plugin. 21 hours ago, DualBandAid said: Also, fwiw, I had no DHCP reservations nor did I tweak anything on my router/switch/modem at all. It's all off the shelf. That's fine, until the IP changes. The plugin information used to (I haven't looked at it lately) encourage an IP reservation so this exact issue didn't happen. It's probably wise to set a DHCP reservation for that 2nd hub since it's connected and working correctly. For the first hub you'll either need to force it back to the old IP (if you know what it was) or hard code it and hopefully discover it in the plugin.
DualBandAid Posted January 6 Author Posted January 6 I took your advice and also followed this link: https://github.com/exking/udi-hue-pg3/blob/master/README.md And added this to the mix which basically reiterated what you said: Quote Sometimes automatic bridge IP address discovery fails, in that case - you can specify Bridge IP address in a custom parameter ip for the NodeServer using Polyglot's frontend interface. It wasn't particularly specific but I put << IP >> in the key paramenter and then I put my IP address, in brackets like you said. It transformed to this, I guess (I just looked at it) and all is well now. Question though on the new hub which is working fine. Should I just do an IP reservation? Or should I do an IP reservation and specifically tell the Hue node what that IP is? Also, is there a difference here between a DHCP reservation and an IP reservation? Thanks for all the help!
Geddy Posted January 6 Posted January 6 1 hour ago, DualBandAid said: Should I just do an IP reservation? Yes 1 hour ago, DualBandAid said: Also, is there a difference here between a DHCP reservation and an IP reservation? If on the router, no. It means the same (generally speaking). At the router level typically in the DHCP settings is the IP reservation option. Just depends on your equipment. Glad you got it working!
DualBandAid Posted January 6 Author Posted January 6 It's kinda amazing all this network stuff is still being sorted out, requiring this kind of detailed fine-tuning. Then again, it's kinda amazing any of this works at all. (Though maybe the problem is, this whole Hue node thing is kinda a kludge - and should just shut up and be grateful it even exists in the first place)
Recommended Posts