I really appreciate that SmartThings is acknowledge the problem and is working on a solution. Still scary though, that this hasn’t been caught in some QA.
Could we get some kind of timeline on this?
Great news that you’ve been able to recreate. If the fix is challenging, could some if us get on a firmware with reduced polling or an adjustable value? I’m really getting serious flack from the WAF especially as we had guests round and the whole lighting system was going crazy. Seriously embarrassing. 
It’s so bad that my smartthings experiment might have to come to an abrupt end if I cannot stabilise this.
2 Likes
You’re right again, of course.
Just a thought, if it’s all local then do we know what’s preventing rules in smart lighting app using hue lights from running locally?
1 Like
First post in the forums and I’m glad i’m not the only one experiencing problems with the ST / Hue integration. I have had issues over the past couple of weeks where the Hue Hub appears offline in the ST app, but i can control lights through the Hue app. Only way to correct was to reboot the ST hub. Since the latest updates there has been a noticeable delay in the lights responding to commands from ST, whether through a routine or smartapp. I have 1 Tap connected, and a total of 11 bulbs / lightstrips. Glad to hear a fix might be on the way 
2 Likes
I’ve killed ST, removed my Smart Apps and the link to Hue and the lights are now instant! When can we expect a fix for this?
I’ve preordered my hue PIR sensors for 4th October 2016. I can’t have this happening when I have young kids relying on auto-sensing lights at night.
It’s just a waiting game now and hope they fix it.
1 Like
It’s not all local, but it’s local messaging to the hue bridge and code running in the SmartThings cloud. Nothing running in the Phillips cloud.
I don’t know why a SmartLights automation that includes a Phillips hue bulb has to run in the SmartThings cloud rather than local in the current architecture. But it seems like that’s true for anything which isn’t a zwave or zigbee device. Maybe the message management is just too complex for the hub software as currently designed?
2 Likes
It’s a shame, if it were all local maybe we’d see faster responses even when it’s working normally.
2 Likes
How does harmony to hue achieve an almost instant status then? Also without effecting the user experience? I just did another test, I unplugged my ST hub from my network, opened the hue app on my wifes phone and the harmony app on mine. Turnng on a light on either results in a status update of 1-2 sec from either app. Now throw ST back on the network doing the same test and the status update is taking 10-12 sec. This is very annoying that its effecting my direct harmony to hue integration. I specifically set those two up together to get instant control of my living room lamps with my harmony remote. Now that is all lost and my WAF is going down. My wife absolutely loves using the remote to set the lamps when she watching tv, reading, using the computer, etc. Hope you guys get this resolved ASAP.
Some of us like me are getting 10 second response at best. Most of the time it gets congested so badly I’m getting nothing even from the hue app.
The harmony app does show what lights are on and also their brightness. Thats what my test was about, using each of the apps and watching the light status update.
1 Like
I may be mistaken, but I thought what it is showing you is the last request from harmony. If you made a change some other way, like turning the Phillips hue bulb off with a tap switch or echo does it also update immediately in the Harmony app?
OK, I’m probably just wrong then. I thought it showed you the status of the last request it sent to hue, but not the actual Hue status if the Hues had been controlled by some other means.
But I guess the harmony/Phillips integration is just more efficient.
Thanks for the correction. I pulled my post above since obviously it was just wrong. 
I think they got better over time. Just tested turning off via Hue app and Harmony updated the state almost instantly…
1 Like
Yes, harmony seems to manage it effortlessly. I remember testing them side by side and it pulled the updates from hue as fast as smartthings did when a change was made in hue.
Whatever philips apparently did in their last firmware update, it did not impact the harmony integration at all.
I am not seeing any issues on my end between ST and hue. But I didn’t have issues with hue before ST update either…
Probably local to local… just saying…
1 Like
Hey everyone, if people that are willing could try to self-publish the Hue Connect SmartApp with the changes from this PR to verify that normal operation is restored that would be very helpful! In my testing, this seems to have been the root cause for the increased latency when combined with the new hue bridge firmware (very strange symptoms for the problem)…
While sniffing network traffic I spotted that the HTTP request headers being sent to the hue did not appear to have the correct line endings. The Hue bridge was still responding but these malformed requests seem to have been causing issues.
Assuming this is the problem, we should be able to provide a fix for the published SmartApp quickly. I had initially feared a change to the hub firmware might be required which is a bit more involved to release.
EDIT: Just a note, switching to a custom app to test this could be pretty painful (have to remove existing things connected through hub, readd them, …). If you don’t want that hassle (and you probably don’t), I recommend that you wait until we confirm the fix and are able to update the published SA. If you have a spare bridge around, the testing would be appreciated.
10 Likes
Thank you very much for the update. 
Already been through the pain of reinstating lights and rules, not something to be taken likely. So will unfortunately have to pass and wait.
Eagerly looking forward to seeing what the results of this are as I left smartthing disconnected for 8 hours today to regain control of my lights.
1 Like