You mean that if you turn the dimmer all the way down it doesn’t turn off in the ST app? Is it on but at 0%? The driver get the on/off state from Hue, not the dimmer values. What does Hue say in the Hue app?
Hue app says off. But ST will stay on if it was turned on in ST using this driver. I’ve actually also just noticed the dimmers aren’t getting status updates in ST when using this driver.
I hope I’m explaining this right…
The only way I can get smartthing’s to update is to pull down to do a refresh. It isn’t happening on its own anymore.
If the the app control in ST works, you are connected to the Hue hub. If you aren’t getting updates back from Hue (sounds like it), there are a few things:
- Hue has a limited number of integrations allowed (3 or 4). If you are over that, it won’t allow the callbacks
- Your router or internet provided hardware may be blocking those connections, only allowing the basic local http. This is unlikely since you said it was working, but could be the issue if you updated your network.
If neither of those sounds correct, I would restart ST first and see if that works. It causes the ST firmware to restart along with the drivers. It’s possible the socket stack in the firmware has an issue. If that doesn’t work, I would then restart Hue. They typically don’t have issues though.
Didn’t know about the limit.
But I did try reboot the hub last night and it still didn’t seem to work.. but it seems to be ok now. So I don’t know what it was in the end. At least it’s ok again. I was worried an update might have broken it.
So, after a power outage it’s back to not getting call backs.. none of the dimmer switches register..
It’s been awhile now, waiting worked before. I don’t know. Is it a bad idea to just, remove the driver and start again? How can I check if I’m at that limit? If I was at the limit it wouldn’t have come back at all right?
I’m sorry for being stupid.
Sounds like they changed something in their tech stack with the latest firmware. This is the second report like this. If you are able to grab logs, I’d appreciate it.
I did a relink. It wasn’t something I’d thought of before because it was already saying linked and I didn’t think it would work.
If you still need logs can you tell me how to get the right logs you need?
### Capturing Logs for a Specific Edge Driver (SmartThings CLI Method)
Requires computer on same Wi-Fi as Hub. First setup ~10-15 min.
1. **Install CLI**
Releases · SmartThingsCommunity/smartthings-cli · GitHub
Test: `smartthings --version`
2. **Log in** (one-time)
smartthings login
3. **Get Hub IP**
App: Settings → Hub → Details (e.g. 192.168.1.XX).
Same network required.
4. **Capture logs**
All drivers (easy)
smartthings edge:drivers:logcat --all --hub-address 192.168.1.XX
5. **Trigger issue** → reproduce while command runs.
6. **Save**
Stop with Ctrl+C, copy output to file.
Or auto-save:
smartthings edge:drivers:logcat --all --hub-address 192.168.1.XX > my_logs.txt
Got to be honest.. I’m a bit nervous to break it again after relinking fixed it. Do I need to try break it again?
Rookie here. I have noticed that changes made to Hue device status (on/off etc) made in the Hue or iOS Home app are not reliably reflected in SmartThings. I am using the standard Hue integration. If I go back to the integration and refresh is it sorts the issue, but this is happening randomly and the issue might be resolved for several days before recurring. Seems related to the 0.59 firmware update that I got last week. @Itati Is this known about? I have submitted a support case via the SmartThings app just now.
I can’t offer much insight into the standard ST driver other than to say that if it is also having this dropout issue, the cause is probably in the ST firmware itself. It also lines up with them recently updating their hub.
I plan to dig through their updates and see if any of them looks like it could be the culprit.
No. If you are happy, I’d leave it be. If it happens again, you’re fine to grab logs at that point. I don’t need to see the “trigger” for something like this. Whatever error you were getting would likely stay in the logs well after it started.
Hey Hue folks — I’m Back!
I’m officially back and planning to bring this driver to the next level with a full production build.
Quick update:
- Moving support to GitHub soon for better collaboration & issue tracking
- Planning premium features in the queue: camera motion sensors, using bulb groups as motion zones, doorbell events, support for new buttons/switches
- These aren’t locked in yet — just items that will be up for community voting once sponsorship tiers launch (Basecamp, Pathfinder, Summit)
Beta invites are still open — if you’re still using the beta or want in, grab one here:
Existing beta users — please sign up too!
This is super important to me: I want to reward you for your early support and feedback. Signing up (and/or sponsoring early if you’d like) lets me reach you directly with updates, new betas, priority access to features, and future tier details. Without your email, I can’t make sure you’re included in those rewards or stay in the loop as things roll out.
Full vision & roadmap details coming in a new top-level post soon.
Thanks for all the feedback over the years — it’s what shaped everything so far.
Let’s do this — see you on the site!
BlueYeti
Quick follow-up now that I’m back 
Thanks to the early supporters who’ve signed up already on the new link. I’d love to keep the momentum going and reach the hundreds or thousands that I know are enjoying the current driver. SmartThings doesn’t give developers a way to know the true impact of their work, and that’s one of the things I hope to remedy with this revival.
The new testing and deployment infrastructure is underway, and automated testing will be a persistent goal of this driver — part of the very first production release. Once that’s solid, I’ll queue up possible features for community consideration:
- Motion Groups: Group motion sensors together for treating zones as a single entity
- Cameras (Motion Sensor): Motion sensor only for now (video feed still not available)
- Hue Pro Motion Zones: Use existing lights as motion sensors that cast a net to track motion. This is my personal favorite so far
- Doorbell Buttons: Use doorbell events as triggers for other automations (e.g., muting the stereo or alerting your phone)
- Additional lighting effects to expand the existing library
I’d love to see this project become truly community driven and involve everyone who’s enjoyed the driver over the past 2 years. Please sign up at the site below so I can make sure you’re in the loop for the next phase (when the current beta retires):
I’ll be rolling out details on sponsorship levels and perks soon. In the meantime, any help is appreciated — this is a passion project, and every little bit helps move things faster.
Until the community setup is live, please drop your feature wish list here — I’ll preload them when voting goes live!
I am having issues with random lights turning on and off. It’s impacting mostly Hue but not exclusively. Would running the ST Hue integration and this 3rd party driver impact things? Running both has been fine for a while but I can’t figure out what’s causing the random on/off which started 2 days ago.
I can’t think of a reason that running both would be an issue. You mentioned “mostly” Hue. You have other non-Hue lights randomly turning on/off as well? Are you using a smart app or anything that has hidden automations?
What is in the stock driver that you are still using that has you running two of them?
I don’t use Automations in Hue and only use them in ST. I also disabled many of the rules in ST in case something was causing it.
For the Stock, no features so perhaps I should just unlink it to remove that factor.
History in ST doesn’t show any rules that would be causing it either.
I removed the stock driver and 3 of the hue rooms are still having the issue. I started running CLI to see if I see anything but nothing immediately returns when one of them turns on. Any other suggestions for tracking down the source?
I don’t remember where I saw it but I recently read a thread on here where someone one saying Alexa was connected to their setup with a feature called “hunches”. From what I gather, it sounded like an AI driven thing that was turning on lights in a “smart” way. Have anything like that?
I saw that while googling and I disabled it. I also went in and removed any Alexa groups as this driver as rendered them pointless. I was really hoping CLI would show something promising but it just shows that something turned on the room. The hunt continues….
THat’s actually a hint. If it only shows that it turned on, with no trigger, then it tells you that the ON command came from outside the driver. Feel free to DM me a log if you want