If you cannot control these unreachable bulbs even in the hue app then there’s nothing smartthings can do about it and would only be a Hue problem.The fix from smartthings is the capability to operate bulbs which are labelled as unreachable which still work in hue.
With every update philips are basically making it difficult for any manufacturer to be compatible without being part of their friends of Hue programme. My view is they will not out and out block access like they did before (bad PR) but just make subtle changes to make you want to abandon unofficial devices.
Basically, I think it’s inevitable that things will get worse with every hue bridge update rather than better.
While all of this was happening I switched to a v2 hub without the Aug update and hue worked great… as soon as the ST hub got the latest update the issues started again. I agree this clearly is a ST~Hue issue, but the ST Aug update isn’t innocent in this.
I’m personally migrating to Lutron more and more… and using ST to manage sensors only , but other apps to manage lighting…
My Smartthings have had almost daily problems since the update to the hub firmware on the 15th August.
The most frequent problems have been with my Philips Hue’s.
The status page; http://status.smartthings.com/# says "Update - Changes to the Hue integration have improved control of bulbs marked as “Unreachable”. We continue to work to address incorrect state reporting from “Unreachable” lights.
Sep 30, 21:12 EDT"
This is the latest update on what has been an ongoing problem for me since early August.
I find it hard to blame the Hues because they work perfectly on their own or with Alexa, it’s only when I add my Smartthings hub that the Hues become unreachable.
I’m really disappointed with Smartthings.
I’m going on two weeks communicating with support daily about the same problem. I can control my Hue bulbs with any other integration except smart things. Make sure you send an email to support@smartthings.com. Hopefully the more people telling them about this, the higher priority it will be on their list.
I am seeing a bunch of issues with Hue over the last couple of days. Tonight already have seen 3 or 4 failures where 4 of 5 lights came on when commanded via ST. Didnt have live logging up so cant tell the issue. But tonight for the last 3 hours or so I’ve seen this happen at least 3 or 4 times here in my house. All Hue connected. All show online and connected… but still part of the lights didnt come on.
And now my app is just sitting here spinning. Not opening. @Aaron seems like there is an issue if you ask me… My app isnt even opening @slagle@Tyler . Just dead in the water… and its been so smooth for a while… the ST way…
While watching live logging saw timeouts for controlling hue, saw java errors here and there. This is using all stock apps and device handlers. Hue connect app, with all my automation done though SmartLighting.
Getting 500’s for multiple places within the site…
Oh No! Something Went Wrong!
Error
500: Internal Server Error
URI
/device/list
Reference Id
95875e90-5f5b-4fe5-b2d9-14b60593d523
Date
Fri Oct 14 02:48:59 UTC 2016
Execution of my kitchen light automation was sub 1000ms up until 10-11. After that we have a high of 8500ms with what looks like I’d call it an average of 5000ms… for a simple ‘on with motion’ with smartlighting app, controlling Hue connected bulbs.
Same delay here. It’s so bad that it seems to affect my Hue Dimmers too. The automatic lights using Smartthings motion sensor seems to have problems as well. It’s weird because if I open the app on my iPhone, the delay gets better and events that didn’t happen will happen all at once once the Smartthings app is opened on my phone.