Hue Hub Connected But No Hue Bulbs Added to System

[UD2)17rrh]

Hi.  Bringing back an issue I had some time ago but did not resolve.  

EISY and Polygot 3 show that the Hue install was successful.  That is, I see a green "connected" status in Polygot.  However I do not see any Hue devices added when I review my admin console. I tried a reboot of the system along with several attempts with "re-discover bulbs". 

Any thoughts?  Anything obvious I am missing?

Many thanks.

[dbwarner5]

@UD2)17rrh If the Plug-in is installed and running, and nothing is showing in the AC, then we need to start with checking to see if the PI has the light bulbs and is connecting to your Hue Hub first.

Open PGX and then hit Details on the Hue. 

Then hit Nodes. Is there anything listed? 

You should see all of your bulbs AND your Hue Hub. 

Is just the Hub showing? and if so does it say for the State (ST) a value of 1 for true. See below. 

 

If not, then it hasn't connected with your hub correctly. Here are the instructions from the README for the HUE.

Once installed - push the button on the Hue Bridge and add NodeServer into Polyglot, that will allow it to pair with the Bridge. 

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. 

Notes

Poly assumes that Bridge IP address never change, so it is recommended that you create an IP address reservation for the Hue Bridge on your router.

If you do see your hub but no lights, or if your Hub is not connected, then you may want to uninstall the Plug-in and then re-install it and try again. Follow any prompts upon installation to press the Hue button. 

However if you DO SEE your lights and hub listed then it's a problem between the PGX and EISY and linking into the AC. 

If that is the case, be sure to close your AC, then go to the HUE log in PGX and change it DEBUG and then stop the Plugin and then  restart it. Open up the AC and see if it shows. If not, download the log and post it. 

As a side note, in the AC, everything will be grouped under the Hue Hub. So be sure to expand it to look for your lights.  You can right click and ungroup them if that is the case and they will show in the tree.

An easy way to look for your Hue hub is to click on MyLighting and then click on the column labeled Address. Then scroll down to the node server number. In my case below it's loaded in slot 3 so it is easy to find that way. 

[UD2)17rrh]

Thanks for the reply @dbwarner5.  So I see the Hub just as the screenshot above shows (yes, State (ST) is a value of 1).

But no Hue bulbs.

I removed the plug-in and reinstalled it.  As above, everything looks good (ST = 1) but still no bulbs.

[dbwarner5]

Ok. Then let’s eliminate one more step backwards. 
 

are the bulbs showing up in the Phillips hue app?  Meaning are the bulbs themselves connected to the hub? 
 

we need to verify that before we work on why the plug in , which is connected to your hub,  doesn’t have the bulbs. 
 

thanks 

[oberkc]

Shot in the dark....unlikely, I suspect...but is it possible that you have installed the Hue "Emulator" rather than the Hue 

[UD2)17rrh]

@dbwarner5 yes, my Hue iOS app sees all my Hue bulbs and accessories.

 

@oberkc Yes, Hue installed and not the emulator.

 

Thanks for helping.

[dbwarner5]

So progress. We have now narrowed it to the plug in. 
 

One  more thing to try: 

1) while you have the plug in open and looking at the nodes, unplug your hue hub. 
 

The plug in should change to state 0. 
 

plug the hub back in and it should change back to 1 

just want to be sure it’s actually seeing your hub.

 You may have to restart the plug in for the state to change. 
 

but before you do that can you change the log to debug?

then after it runs for a bit , download the log file and post it 

 

thanks 

[dbwarner5]

Just curios, what are the names of your lights in the hue hub / app? 
 

 

[UD2)17rrh]

Thanks.  Here is the log:

2025-01-18 12:30:54.604 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-01-18 12:30:54.606 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-01-18 12:30:54.606 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-01-18 12:31:09.615 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-01-18 12:31:09.616 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-01-18 12:31:09.616 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-01-18 12:31:24.622 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-01-18 12:31:24.622 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-01-18 12:31:24.622 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-01-18 12:31:39.631 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-01-18 12:31:39.631 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-01-18 12:31:39.632 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-01-18 12:31:41.796 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message longPoll
2025-01-18 12:31:41.796 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING longPoll
2025-01-18 12:31:41.796 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS longPoll message {} from Polyglot
2025-01-18 12:31:54.641 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-01-18 12:31:54.641 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-01-18 12:31:54.642 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-01-18 12:32:09.647 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-01-18 12:32:09.647 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-01-18 12:32:09.647 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-01-18 12:32:24.653 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-01-18 12:32:24.653 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-01-18 12:32:24.653 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-01-18 12:32:39.657 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-01-18 12:32:39.657 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-01-18 12:32:39.658 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-01-18 12:32:41.800 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message longPoll
2025-01-18 12:32:41.801 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING longPoll
2025-01-18 12:32:41.801 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS longPoll message {} from Polyglot
 

[UD2)17rrh]

3 hours ago, dbwarner5 said:

One  more thing to try: 

1) while you have the plug in open and looking at the nodes, unplug your hue hub. 
 

The plug in should change to state 0. 
 

plug the hub back in and it should change back to 1 

just want to be sure it’s actually seeing your hub.

 You may have to restart the plug in for the state to change. 

The state did not change to 0 when I unplugged my Hue hub.

[dbwarner5]

@UD2)17rrh thanks. 

Sorry for the continued trouble. I actually just unplugged my Hue Hub as well. No change. So wonder if the plug in is  going directly to the Hue Server, once it connects with the Hub the first time. Was worth a test.

So lets continue with some basics... what software versions  are you  on for both the Eisy and PGX?

I think the latest is 3.3.17 for pgx and 5.8.4 for Eisy. Hit Upgrade packages in the Admin console and wait until it updates to the latest versions if you are not there.

Once updated, you may want to try and again, uninstall and reinstall the Hue Plug in..when you do this, does it ask you to push the button on your hub? 

If so, and it still doesn't work, I saw in some of the other Hue posts that stop/ starting of the plugin a few times may be necessary to get all the lights in. In a different Plug in, there was an issues once of special characters used in the name of the devices which the plugin couldn't handle.  Just throwing out some more ideas to try.

Lastly, I have also noticed with PGX that if you are in the screen and restart the plug in, it wont show the Nodes, until you go back to the Dashboard of PGx and then back into the Plug in. 

Lastly, can you change the log to Error and after a few tries of restarting, download it? 

Thanks.

 

[UD2)17rrh]

Thanks @dbwarner5 for your help.  Currently running PG3x v 3.2.27.  IoX running 5.8.4. It has been for a while.  I previously did delete the plug in and reinstall.  I did not get the request though to press the button on my hub.  I also tried starting and stopping the plug in.  No success at this time.

Here is a portion of the error log...thanks again.

 

2025-01-18 22:16:33.799 MainThread udi_interface.interface WARNING interface:start: No node server version specified. Using deprecated server.json version

2025-01-18 22:16:33.800 Interface udi_interface.interface INFO interface:_startMqtt: Using SSL cert: 0021b9026579_3.cert key: 0021b9026579_3.key ca: /usr/local/etc/ssl/certs/ud.ca.cert

2025-01-18 22:16:33.800 MainThread udi_interface.interface WARNING interface:db_getNodeDrivers: huebridge not found in database.

2025-01-18 22:16:33.800 MainThread udi_interface.interface INFO interface:addNode: Adding node Hue(huebridge) [None]

2025-01-18 22:16:33.800 MainThread udi_interface INFO hue:__init__: Started Hue Protocol

2025-01-18 22:16:33.801 Interface udi_interface.interface INFO interface:_startMqtt: MQTT keepalive is 300 seconds.

2025-01-18 22:16:33.850 MQTT udi_interface.interface INFO interface:_connect: MQTT Connected with Reason code: Success

2025-01-18 22:16:33.850 MQTT udi_interface.interface INFO interface:_connect: MQTT Subscribing to topic: udi/pg3/ns/clients/00:21:b9:02:65:79_3 - MID: 2 Result: 0

2025-01-18 22:16:33.892 MQTT udi_interface.interface INFO interface:_subscribe: MQTT Subscribed Successfully for Message ID: 2. Reason codes: ['Granted QoS 0']

2025-01-18 22:16:33.975 Thread-2 (parameter_handler) udi_interface INFO hue:connect: Saved bridges information is not found

2025-01-18 22:16:33.975 Thread-2 (parameter_handler) udi_interface INFO hue:connect: No bridge configuration found, trying discovery...

2025-01-18 22:16:33.976 Thread-2 (parameter_handler) udi_interface INFO phue:connect: Attempting to connect to the bridge...

2025-01-18 22:16:33.976 Thread-2 (parameter_handler) udi_interface INFO phue:connect: Error opening config file, will attempt bridge registration

2025-01-18 22:16:34.008 Thread-2 (parameter_handler) udi_interface INFO phue:get_ip_address: Connecting to discovery.meethue.com/

2025-01-18 22:16:34.055 Thread-2 (parameter_handler) udi_interface ERROR hue:connect: IP Address OK. Node Server not registered.

[firstone]

10 hours ago, UD2)17rrh said:

2025-01-18 22:16:34.055 Thread-2 (parameter_handler) udi_interface ERROR hue:connect: IP Address OK. Node Server not registered.

When you see this, you should usually see the notice on dashboard saying "Please press the button on the Hue Bridge(s) and restart the node server within 30 seconds". If you're not getting a notice there would be something wrong on pg3 side. But either way, try to do it.

[dbwarner5]

A few other things you may want to try:

1) delete and re-install, but pick a different slot number

2) per the directions, if you know your hub IP, you can add it:

 

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. 

3) following Firstone's thoughts, he indicates pressing the hub button and THEN restarting the plugin.

 

After that, I am out of ideas!!  

 

[dbwarner5]

@UD2)17rrh Just thought of one other possibility>. Is your Eisy on Wifi?   If so, I found with a different plug in, that the Eisy makes its own Subnet on your LAN when connected via wifi, which wont allow it to find your Hue hub. 

If you can add the IP address of your Hue hub into the Plugin, this may solve the issue.

If not, if you can temporarily connect your eisy via ethernet (which will require a reboot), and try the plug in, this will at least  identify what the problem is. 

Good luck. 

[UD2)17rrh]

Thank-you @dbwarner5 and @firstone for your help.

So I am afraid to say (aka embarrassed) that this was operator error on my part.  I pressed the Hue Hub button and immediately restarted the plug-in.  Within a few seconds everything populated.

Thank-so much for your help.  I also see all my Hue bulbs in my admin console, and I am happy to start programming.

 

[dbwarner5]

YEA!!!  the directions aren't clear about that, so no problem. 

Glad it worked out because I was out of ideas!

cheers.