I did start over and reconnect it from scratch. It’s an issue with the Aeotec hub only for some reason.
Hi, @slgalvin
If you’ve confirmed you have everything ok for the connection, we’ll report this issue. To do so, we need your help with the following:
- Delete the currently discovered devices since they are not working correctly.
- Then, set up the SmartThings CLI on your PC (here are the instructions)
If you need further help with that, please let us know and share which OS your PC has to provide detailed instructions. - Once you have the CLI ready, you need to open the driver logs using the command below:
smartthings edge:drivers:logcat
- Once the connection is open, you need to retry the discovery process so the events are shown there.
- After the process is finished, copy those logs into a file and send it to build@smartthings.com along with the description of what happened this time you made the discovery and what was expected
- Simultaneously, after finishing the discovery process, send the Hub logs to compare what happened in the driver to the events registered in the Hub to see if there’s an error shown.
- In the Advanced Users app, enter the “Hubs” section
- Enter the corresponding Hub and click on “Dump Hub logs”
- Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
- You’ll get a green box at the top confirming the Hub logs were requested.
- Finally, Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it in the same email of the file of #5
- Enable support access to your account:
- Go to the SmartThings Web (my.smartthings.com)
- Log in to your Samsung Account
- Select Menu (⋮) and choose Settings
- Toggle on Account Data Access
- Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
All done, just sent through the logs and enabled account access.
I guess it’s time to try the unofficial edge driver. Support confirmed the new edge driver only supports globes and not sockets, how ridiculous that we get migrated to this wonderful new platform and lose functionality, after I got the hue bridge to actually pair properly with the Aeotec hub. I’m lucky my wifi hub still uses the old DTH so I can stick with that if I want to and continue to control the globes and sockets like I have always done. It’s so disappointing we get forced to take steps back like this. Why fix what isn’t broken
As much as I agree that you should use my driver instead, I think support misled you. I’ve looked at their code and it should be supported. However, I’d still make the switch 
1 Like
It’s been working fairly well until recently when the app is now frequently missing switch events - most often switch off and for some bulbs more than others.
That bulb cant be directly controlled from the app when the on/off status is wrong but running a routine or using some other app seems to correct the status. Removing and re-adding the device also corrects the status but hasnt fixed the issue.
This is a little similar to Sonos where the app stops processing events.
Is there still is any working fix for this issue that could be done rather easily without “coding skills”? Or what are currently the options to make SmartThings app able to control again the Hue lights?
Since the start of June, I have had no control of Hue lights (except some few random bulps) via SmartThings app which makes also the automations regarding lights useless. I have send few times some data what SmartThings people have asked for me, but still they have not been able to fix the issue in more than 4 months.
They have said maybe dozens of times that they will “ping the engineering team”, but so far the engineering team have not been able do in practice anything to solve the problem! I’m wondering if they have even properly looked into it…
As a “non-coding person” it is hard for me to understand how it can be that difficult to fix the mistake that happened in the beginning of June. It is also hard to understand, if this problem only appears to me. I believe there are a lot of people in the same situation even though they are not here asking for help.
Four months is tooo long time!
Please help me to fix this annoying problem!
1 Like
welcome
what happens with practice is that it works normally in the Hue application, I can see motion detection there. After resetting the product, I add it to the Smart Thing application, then it updates, but then it does not update the status data. It seems to me that there is something with the data transfer of the Philips and Samsung cloud services. This error has existed since Friday
Apps are the most up-to-date software on devices
Hue motion sensors: SML003/ software: 2.53.6
Hue center: BSB002 1.61.1961076030
Smart Things center: Aeotec Firmware: 00005000010
Synchronization: Connected services
In practice, almost nothing has been working for three days, as many protocols - including the alarm system - would rely on data from the Hue motion sensors. My built ecosystem has completely collapsed
I added to the smartthings web
Csaba Móricz
1 Like
Well, two days ago the issue came back for me. I was still on the Alpha Driver, which was the one that fixed it for me last year.
My Hue lights stopped working after the Alpha Driver got updated to this version:
2024-05-30T21:57:12.048704523
So I installed the Beta Driver instead and my Hue lights started working again. This is the Beta Driver version:
2024-04-30T18:30:55.669282462
The Beta driver got updated today and my Hue lights stopped working again.
This is the new Beta driver version number:
2024-06-03T20:15:13.938365842
I tried reinstalling the Alpha driver, but it is still the version that stopped working on May 30th (2024-05-30T21:57:12.048704523)
Could this be the same issue as last year’s, @nayelyz ?
Any help would be appreciated.
1 Like
@ordigas Are you able to provide edge driver live logs and hubcore logs? I’ve been trying to reproduce this issue myself using the following steps:
- Sideload the driver using a personal channel on the Alpha version from before the update
- Onboard all of my Hue lights
- Update the driver to the Alpha version
When I do so, my existing lights continue to work. So anything additional you can provide to help me find the root cause would be greatly appreciated, since I can’t reproduce it myself 
1 Like
Hi, @ordigas
Aside from the info that Doug mentioned, could you enable support access to your account, please?
- Confirm the email account registered in the forum is the same one you use for SmartThings. If not, please share it with me over DM
- Enable support access to your account:
- Go to the SmartThings Web (my.smartthings.com)
- Log in to your Samsung Account
- Select Menu (⋮) and choose Settings
- Toggle on Account Data Access
- Select the time period and confirm - In this step, please select “Until turned off”, once the team finishes, we’ll let you know so you can disable it again.
In case you have questions about how to get the driver and hub logs, you can expand the options below to see the steps
Here are the steps to get the driver logs:
- For this, you need to set up the ST CLI and run the command below:
smartthings edge:drivers:logcat
- The CLI will prompt you to select from which hub and driver you want to listen to events
- Then, send commands to the devices so their logs get registered there
- Copy those logs in a file and share it with us, you can send it to build@smartthings.com.
Here are the steps to get the hubcore logs:
After replicating the issue of sending commands that the devices don’t respond to, follow these steps:
- In the Advanced Users app, enter the “Hubs” section
- Enter the corresponding Hub and click on “Dump Hub logs”
- Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
- You’ll get a green box at the top confirming the Hub logs were requested
Hello @doug.stephen and @nayelyz . Thanks for the quick response.
I’ve enabled support access to my account.
I’ve also requested the Hub logs and sent a text file with the Philips Hue Edge Driver Logs to build@smartthings.com
Thanks.
1 Like
Hi, @ordigas, thank you, I have access now, but I couldn’t find your email with the text file.
I’ll send you a message using the email you registered here and you can reply to me there, this is to avoid the email not being received for some reason.
1 Like
Hi, @ordigas
Following up, the engineering team didn’t find a specific issue so, they enabled more logging for the driver, and, we need you to check the following, please:
- In the main device (the hue bridge), please pull down the screen to refresh to see if it helps
- If step #1 isn’t successful, please run the commands/actions that don’t work for you and let us know the details of what you try to do but fails.
For example:
I try to turn on the device “lamp 1” but it stays loading and get a “network error”.
We would need the names of those devices that fail to get their ID and see their details and the corresponding logs, please.
Hello, @nayelyz
Thanks for the follow up.
The issue persists.
I pulled down the screen in the hue bridge page to refresh it and it didn’t help.
Basically, none of my Hue Lights work if I try to control them using SmartThings, either trough the App or trough Routines (the Hue Bridge is connected to SmartThings via LAN). They do work if I control them using the Hue App or Alexa (which is connected to Hue using the corresponding Skill). Once I turn them on or off this way, SmartThings do update and show the correct status of the device.
Almost all of my Hue Lights are part of a Routine with a corresponding Motion Sensor. So if I walk into a room, movement is detected and lights should turn on. And they should turn off after 5 minutes of no motion detected. Those routines are currently not working. The Motion Sensors are detecting movement, but the lights do not respond.
And with the SmartThings App, if I try to turn on or off any Hue Light, it stays loading and I get a network error.
To give a specific example, I just tried to turn on “Foco Tele” and “Foco Baño Visitas” using the SmartThings App, but in both cases it appeared as loading and after 25 seconds I got the following message saying there was a network or server error: “Se produjo un error de la red o el servidor. Inténtelo de nuevo más tarde.”
So, none of the Hue Lights you can see in the logs I sent you are working. None of the logged actions resulted in a Hue Light turning on or off.
As I said before, after the issue was solved last year with the Alpha Driver, everything was working fine until the driver updated to 2024-05-30T21:57:12.048704523. Then I switched to the Beta Driver and things started working again immediately, but a couple of days later the Beta Driver got updated to 2024-06-03T20:15:13.938365842 and the issue came back.
Today I realized that both Drivers got updated two days ago, but neither fixed the issue for me (Beta: 2024-06-11T18:23:27.106273219. Alpha: 2024-06-11T01:02:00.173048092)
Thanks again for your support.
Hi, @ordigas
Thank you for the information, I shared it with the team and they’ll take a look at the info collected. We’ll let you know once we have an update.
2 Likes
Hi, @ordigas
Following up, the engineering team mentioned they need to compare the information from the driver in the default channel and the one that has the issue.
So, please help us by following these steps:
- Installing the driver of the link I shared above (From the default channel)
- Send new commands to the devices to. confirm it works again.
- Then, go back to the previous driver and make sure the devices stopped working
- Immediately after, pleaae submit the hub logs so the team can get the info of those changes.
- In the Advanced Users app, enter the “Hubs” section
- Enter the corresponding Hub and click on “Dump Hub logs”
- Confirm the process by clicking on “Dump Hub logs” again in the pop-up.
- You’ll get a green box at the top confirming the Hub logs were requested.
Please let us know once you’re done.
1 Like
Just to clarify…
My understanding Is that users should not try to switch from one edge driver to another for LAN or Wi-Fi devices because the security key will not be correctly managed (these devices don’t have the same kind of device IDs as Zigbee and Z wave). So we have always told people that if they want to change from one driver to another for devices like the Hue Bridge, they have to delete the device from their account and then re-add it. Otherwise, the new driver will not work correctly.
In contrast, LAN devices typically exchange a security key when they are first added to your account and trying to switch to a new driver may make that device non-functional. Devices in this category include the hue bridge and Sonos.
Of course, this means that any routines they had with those devices will have to be rebuilt, which is annoying, but I don’t think there’s a workaround for the security key issue, is there? 
Hello, @nayelyz
I installed the Driver from the Default Channel and my Hue Lights started working again.
Then I reinstalled the Driver from the Alpha Channel and the Hue Devices stopped working once more.
After that, I submitted the Hub Logs from the Advanced Users App.
Should I stick with the Alpha Driver for now, while you do more tests? Or can I just switch to the Default Driver to get my lights working again?
Thanks!