If you are outside the US, ST may be offering up their own Edge driver. If this happens, the only way around it is to run discovery again without deleting theirs. Once THIS driver find the hub, you can delete their devices.
You also need to press the button on the Hue hub during discovery. You can verify the driver by checking the version in the ‘Driver’ section of the device menu.
@klkler88 and @Dienzora As stated in the original post, changes made outside of ST will not sync up in real time yet. There is a feature being added to the Edge stack to support this. Once it is available, it will be added here as well.
It sounds like you aren’t using this driver. This driver will import the Hue Hub and Rooms/Zones by default. Only rooms and zones support scenes. If lights were imported by default, then you are using the ST driver. I would verify that you have this driver installed by look at your ST hub device and going into the ‘Driver’ menu. If it is there, and ST is giving you their driver, you may need to run discovery a second time, and press the Hue hub pairing a second time as well. If that still doesn’t work, you can send me your driver logs in DM and I will take a look.
Changes outside of ST are not currently syncing up live. Please see the known issues in the original post and the last few comments before yours. We are waiting on ST to release some stuff. ST also doesn’t let us change names via code as far as I know. If you change it in the Hue app, you have to do the same in ST.
If you have multiple rooms turning on, then you probably have some other automation setup in ST. If you are using Zones, it is also possible that the zones overlap. That is up to you though.
The only link is in the original post. The invitation links and hub enrollment process are not specific to the driver. That is all managed by ST after the link is created. What is the issue?
There is at least one user that was unable to find the Hue hub on their network during device discovery. The Hue hub would not respond to discovery broadcasts due to network filtering within the Eero router. This filtering was setup through HomeKit, and prevents Hue from interacting outside of the Apple ecosystem. This has to be modified from inside HomeKit to open things up for Hue. Please see this article for details and refer to the section on “Granular HomeKit Security”
Does this enable matter pairing or is it still using Standard LAN? I’d like to see a matter edge driver for the hue Bridge as it just doesn’t work without a driver.
Just uses the LAN. There aren’t any benefits to switching to Matter once you have a LAN connection. Matter just makes pairing easier for users and standardizes device interactions. Once you have gone to the point of installing custom Edge drivers, you have already jumped over the reason for matter existing.
I used to connect hue bridge to SmartThings hub using LAN method. After I installed edge driver, both stock and this, I deleted hue bridge from smartthings app and tried to reconnect. But no matter what do I do, “scan nearby” or by brand, the hue bridge simply won’t use the edge driver but added as previous LAN devices. There is no driver when click the three dot menu, no setting in hue bridge. All lights were found together with the bridge and added as LAN devices as before.