Philips Hue Hub all of a sudden is "not detected on LAN"

[RuCAS]

Yesterday night out of nowhere, my Philips Hue Hub (2nd GEN) all of a sudden had a red symbol in the top right corner in iCUE.
Hover my mouse over it and it says "This device is not detected on LAN". Running the Setup Wizard in iCUE does absolutely nothing when I press the centre button on my Hub. Usually this is instant but nope the progress bar just keeps going until it times out.

It was working just fine before hand (and always has for the last 1-2 years), because around 7:15pm when I first turned on my PC, my Hue lights changed exactly as they should when my default profile is loaded once iCUE launches. My PC remained on, and a couple hours later (maybe even less), is when it all of a sudden became not detected on LAN???

Nothing was changed on my PC or my network during this time, so I am not sure why it is not seeing my Hub now. My Hub is 100% online and it has the exact same static IP address assigned that it always has (and so does my PC). My PC and my Hub are both directly connected to my router via ethernet and are literally 1 IP address away from each other. My Hue Hub/PC tower/Router are all side by side on my desk lol.

I can access my Hub no problem either via the Philips Hue app on my phone connected to the same router (wirelessy), or with any Alexa in my house, or even directly within my web browser on my PC. I can also see the Hub as a connected device when I login to my router...so I know that it is online and accessible.

- I am currently on the latest iCUE build v4.22.203 and even tried last night reinstalling this same version using the repair option, but it did not fix the issue.

- When I first installed v4.22.203 back at the end of March 2022, I did it via direct downloading the installer file, and a FULLY clean install (not via update within iCUE). I say fully clean install meaning that I followed all the steps outlined by Corsair here: https://help.corsair.com/hc/en-us/articles/360025166712-Perform-a-clean-reinstallation-of-the-Corsair-Utility-Engine-iCUE- . Everything has been working just fine the past 3 weeks since doing this. [*the only reason I even did a clean install a few weeks ago was due to all of my created keyboard macros in a specific profile were not working at all...so it was nothing related to anything Philips Hue as I have never had any issues with it*]

- I have also tried factory resetting my Philips Hue Hub (and all of my Hue lights) from scratch, but this also has not fixed the issue of not being able to re-link my Hub in iCUE. It still says This device is not detected on LAN.

- I have tried backing up my config.cuecfg file elsewhere first, and then deleting it and letting iCUE create a fresh one. Did not fix the issue so I just copied the original file back.

- I see in the release notes of v4.22.203 they made a change to Philips Hue, so maybe is this just a random bug in this version? https://forum.corsair.com/release-notes/icue/422203-r21/

I am trying to avoid having to do another clean install of iCUE and/or of an earlier version, because of all my profiles and settings required to be exported/imported doing so is a PITA. Even more so, if doing this didn't even fix the issue anyways.

Any help or suggestions would be greatly appreciated! Sorry for the long post, but I wanted to be thorough in order to avoid any of the typical scripted responses from customer support :^)

[Trakth0r]

I have exactly the same problem. Literally to the word.
Everything was working fine more than a year previously with ICUE v3 and later with v4. Today (only discovered it today) I saw the red icon on the Hue bridge in ICUE saying "This device is not detected on LAN"

I checked for updates for ICUE and there was an updated to the v4.22.203 which I have performed, but this didn't fix the problem. Hue bridge is v2.1 and is still working fine with my phone apps, Hue sync PC app, etc.

I've uninstalled all PC apps related to Philips Hue, restarted router/PC/Hue bridge, re-plugged all the LAN cables, still the device can't be detected on the network by ICUE. Tried the pairing in ICUE again, but when prompted to press the Hue bridge button it is not detected and the process times out.

I have tried also some steps from this post regarding config.cuecfg and <value name="PhilipsHueSerialId"></value> settings but with no luck.

 

[Aoxomoxoa]

Exact same problem here too.  Since my initial install of my Philips Hub and for the last for the last 5 months I've had zero problems setting up or using the Hue hub and lights with iCue.  After the latest update however it seems to have stopped working.  I also cannot get it to link up again.

My hub is still working with the Philips Hue app for android, with the Philips Hue Sync PC program, with MSI Center, and with my Google and Alexa voice assistants.  Nothing seems to be wrong with the hub itself.

Corsair added better support for my MSI motherboard and I was exited to try it out...unfortunately I also lost functionality with the same update so I still can't control all the lights in my room with one button.  Sadface.

I'm hoping corsair will get on this soon as I can only assume there's a problem with the latest version 4.22.203.

 

[Aoxomoxoa]

It appears intermittent.  Out of nowhere my Hue bulbs suddenly changed color to match my current profile.  Then I changed a few more profiles and it was all working.  Was....  Then it stopped working again after about 5-10 minutes.

[Corsair LandLubber]

If you haven't done so already, please create a ticket via our support page. We can then take a closer look at this issue.

[Trakth0r]

9 hours ago, Corsair LandLubber said:

If you haven't done so already, please create a ticket via our support page. We can then take a closer look at this issue.

Support ticket Id #2005243348 created

[Aoxomoxoa]

I submitted a ticket too.  I had to reference some hardware in order to submit a ticket so I referenced my most recent Corsair product purchase, my mouse, although it isn't really a mouse problem at all.   #2005243821

Assigned to Jose P.

[RuCAS]

Just an update to my initial posting...

I tried doing a clean install using v4.22.203 (was the latest at the time), and still the same issue.

Also tried doing another clean install, but this time using the previous version (v4.21.173), still the same issue so I just reinstalled v4.22.203 back on.

What I have noticed though, is if I disable the Philips Plugin in the iCUE settings, and a few PC boots later if I enable the plugin back on, my Hue Hub is detected once again. But unforunately this does not last long at all. Sometimes 5-10 mins, sometimes a bit longer, before it becomes not detected on LAN again. I've been monitoring my network and my Hub is definitely not going offline at all.

I see v4.23.137 was just released today, but no mention of anything Philips Hue related so I doubt it has been fixed yet.

Guess I will also open a ticket now to help get this resolved for us all.

[Aoxomoxoa]

Here's an interesting thing...  Yesterday morning at 3:07 AM PST iCue rediscovered my Hue Hub for just a few minutes.  During that time I could control my my motherboard headers and philips hue.  Today at exactly 3:07 AM again iCue started to briefly control my Hue Hub.

I'll watch for it again tomorrow morning....So Weird....

[Trakth0r]

1 hour ago, Aoxomoxoa said:

Here's an interesting thing...  Yesterday morning at 3:07 AM PST iCue rediscovered my Hue Hub for just a few minutes.  During that time I could control my my motherboard headers and philips hue.  Today at exactly 3:07 AM again iCue started to briefly control my Hue Hub.

I'll watch for it again tomorrow morning....So Weird....

Well. I've created support ticket to Corsair. They have asked me to completely uninstall iCue, clear all folders manually and remove Windows registry entries for Corsair SW.

Then they asked me to install older version of iCue v4.20.169 and see if the Hue bridge is working. After clean install the Hue bridge was working for around 30 seconds and then stopped working again.

I've performed update to latest version of iCue again.

I just booted my PC and went directly to iCue and saw Hue connected again and after couple of seconds it disconnected again.

[RuCAS]

Yeah I also have already tried everything that all of you have.

It first happened to me on April 20th. My PC was off the entire day while at work and didn't turn it on until around 7pm-ish and all was fine. Was left idle for a while and later that evening is when I first noticed the issue. Only thing that changed on my PC that day was a Microsoft Defender Security Intelligence Update version 1.363.716.0 (shown in the pic linked below).

Unfortunately these updates can't be removed/uninstalled like how normal Windows Updates can be, but that day I did also try disabling Windows Defender entirely and any firewalls etc., to see if that was maybe the conflict but it didn't make any difference doing so.

I suspect it may possibly have something to do with this update though...

https://imgur.com/a/pcGSQsG

[Trakth0r]

I'm waiting for the newest reply to my support ticket. Meanwhile there was a new iCue v4.23.137 released, but as suspected this did not fix the issue.

Upon searching on google I've found some interesting things that I've also put to the support ticket for Corsair to investigate.

There is 7 days old post on the Homey forum about Hue and that Philips (or the Signify company behind Hue) introduced some "rate limits"
https://community.homey.app/t/philips-hue-broken-on-5-5-8-update/62857/1

Also here
https://developers.meethue.com/terms-of-use-and-conditions/
"6. API Calls. For purposes of service stability and user experience of the Philips Hue ecosystem, Signify limits the number of remote API calls. The limit is currently set to a total of 50000 calls per day. If you exceed these limits, Signify may (without notice) at its sole discretion throttle your activity or revoke your access to the Hue remote API. You will not attempt to circumvent such limitations. If you want to increase the limit, you should contact Signify and Signify may in its sole discretion approve or reject the request."
But this version of Terms&Conditions is from: 02 June 2021

Don't know if this may be somehow connected since I have absolutely no idea how Hue and iCue interaction works.

And lastly from November 12, 2021; https://developers.meethue.com/new-hue-api/
"As per today, we deprecate UPnP as a local bridge discovery method, scheduled to be disabled in Q2 2022. Please use the recommended discovery methods mDNS and discovery.meethue.com which are supported since January 2018"

There are 2 behaviors occurring when pairing the Hue bridge in iCue that I've observed.

1. The process goes OK, but the connection is lost immediately or after few seconds. This is my video of the event: https://youtu.be/40RSszQpsec
2. The process never finishes and timeouts.

[Rigi_RBLX]

So weird. I just got philips hue yesterday and i couldnt connect it to icue. Its the same like you video Trak.

[Aoxomoxoa]

Rate limits sounds about right.  If I close iCue for a few minutes then start it up again, the Hue Hub is detected and working again for about a minute.

[pburgess22]

Have the same issue here myself. It connected fine the first time round and then very quickly stopped working. Now if I try and add the Hue Hub to another machine it wont even let me connect at all. 

[RuCAS]

Corsair responded on April 27th to my support ticket. They said they have reached out to their iCUE specialist regarding this issue and I made them aware of this thread as well.
There is nothing us users can do as the issue is clearly on their end of things. Probably is best to just disable the Philips Hue plugin in iCUE settings for now, until they release an update with a fix for this. 

[Setiri]

This is so frustrating, I was dealing with this issue myself.  Today I decided (for a few reasons) to do a full partition deletion, creation, reinstall of Windows 11 and everything.  So it doesn't get any more of a clean install than this.  Fired up iCue, set all my fans/lights up, and turned on Philips Hue.  Ran the wizard, pushed the button on the Hue hub, it found it instantly and was working.  FINALLY!  30 seconds later as I'm about to change the color of my Hue desk lights aaaand... same exact thing as before.  I do not believe it's me or any of my equipment and that RuCAS is correct in that it's on the Corsair side of things.  Corsair, please get this fixed.  I put a lot of money into my setup and you guys, and I'd appreciate y'all putting some resource fixing this feature.

[Trakth0r]

Hello, Corsair already knows where the issue is and will be solved in one of the next 4.24.xx updates.

[Aoxomoxoa]

Looks like the fix is in.....so far so good.

THANK YOU CORSAIR!!!!  YOU ROCK!!!

[RuCAS]

Yeah they may have "fixed" the Hub connection issues, however they definitely broke the way the lights are configured.

Now that you can only set the lighting effects by "Entertainment Areas", I haven't found a way yet to set different colours to different light bulbs.

I went into my Hue app and made an area for each bulb, thinking I could then set a different layer to each bulb in iCUE but nope!!...the "Quick Lighting" is horrible. Only lets you set 1 colour/effect layer to 1 area at a time, and if you have more than 1 layer it behaves very strangely when you try to unselect an area (it automatically just applies the layer to other areas even after you have already deselected them all previously).

So basically now, you can only set 1 colour or 1 effect to all of your bulbs and no longer can set bulbs/strips to their own individual colour/effect 😞

[Corsair Notepad]

5 minutes ago, RuCAS said:

Yeah they may have "fixed" the Hub connection issues, however they definitely broke the way the lights are configured.

Now that you can only set the lighting effects by "Entertainment Areas", I haven't found a way yet to set different colours to different light bulbs.

I went into my Hue app and made an area for each bulb, thinking I could then set a different layer to each bulb in iCUE but nope!!...the "Quick Lighting" is horrible. Only lets you set 1 colour/effect layer to 1 area at a time, and if you have more than 1 layer it behaves very strangely when you try to unselect an area (it automatically just applies the layer to other areas even after you have already deselected them all previously).

So basically now, you can only set 1 colour or 1 effect to all of your bulbs and no longer can set bulbs/strips to their own individual colour/effect 😞

That is due to the API limitations set by Philips.

[RuCAS]

12 minutes ago, Corsair Notepad said:

That is due to the API limitations set by Philips.

Yes I read the release notes before downloading/installing the latest version and was aware of the API limiting to Entertainment Areas.

Just seems odd that if you have multiple areas, you can't individually assign each different entertainment area, and is only 1 area at a time or nothing at all.

The HUE app still lets you assign colours/effects to individual areas or bulbs for that matter, but I guess they must not use their own API.

[Corsair Notepad]

6 minutes ago, RuCAS said:

Yes I read the release notes before downloading/installing the latest version and was aware of the API limiting to Entertainment Areas.

Just seems odd that if you have multiple areas, you can't individually assign each different entertainment area, and is only 1 area at a time or nothing at all.

The HUE app still lets you assign colours/effects to individual areas or bulbs for that matter, but I guess they must not use their own API.

The Philips Hue API limits third-party software apps to control over the entertainment areas only. If you are not happy with that limitation then you will need to contact Philips directly.

[Setiri]

Thank you so much for fixing this.  I know it seems small but this means a lot to me with my desk layout, all the Corsair lighting and the 2 Hue Play lights I have backing the desk's lighting.  It does seem a little limited now but I'll make it work, at least it's up and running again.

[Corsair Notepad]

On 5/29/2022 at 7:24 PM, Setiri said:

Thank you so much for fixing this.  I know it seems small but this means a lot to me with my desk layout, all the Corsair lighting and the 2 Hue Play lights I have backing the desk's lighting.  It does seem a little limited now but I'll make it work, at least it's up and running again.

Unfortunately Philips made the decision to limit third-party applications, such as iCUE, to only having control over Entertainment Zones setup in the Philips Hue app going forward with their new API.