I’m not able to program the Hue dimmer switch (v1) when connecting Hue via Matter. It does work when connecting with the normal integration. Is this just me, or everyone?
What do you mean exactly by “program”? The device does not appear in SmartThings? The number of buttons shown is incorrect? The pressed events are not there to create automations?
For the “regular” integration/connection, four buttons are presented, as well as the battery life of the switch - and I am able to create routines for both pressed and held actions.
For the matter integration, it just says “Status Connected” in a big blue box at the top, cant do anything with it.
I see, that happens with my bridged Tapo S200B since they are not exposed as “buttons” (Generic Switch in Matter terms) so the Matter driver uses the matter-thing profile which has nothing more than the status.
Could be the same situation (and then there’s nothing you can do) or could be a problem with the Matter switch driver that needs a reconfiguration (that’s going to be tricky since you would need to change the driver to something else and then go back).
Edit: With the SmartThings CLI you can run smartthings edge:drivers:switch -I and switch your button to another driver, for instance the old Matter Button. Then change back to Matter Switch and that will force a reconfiguration.
1 Like
Thanks! Its using the smartthings driver for Matter switch devices - this seems to be a bug in that driver.
Hopefully @Vaishnavi_Devi ,@Itati or someone else from their team can help here! Ive granted support access as requested.
Did you try the switching back and forth to Matter Switch driver in the edit?
There’s always the possibility that this specific Hue dimmer is not bridged as a button, you should be able to see that in the logcat when switching drivers but I understand that’s a bit cumbersome if you’ve never used the CLI tool.
I guess since this is offtopic they could split the issue to its own thread and leave alone this one which is for LAN driver.
Thanks for the continued help! <3
The way I understood this thread, is that they have added Philips Hue 4-button remotes to be controlled in SmartThings, and are asking us to report any issues. I’m doing that!
Pressing “select different driver” results in “No results found”, so I’m unable to switch drivers back and forth unfortunately. I’m just a regular user, so CLI and looking in logcats is a bit too much 
- I just want it to work OOTB
Yeah, but this thread is for the LAN driver, not for the Matter driver, they’re different integrations 
Can you check a thing in the advanced website? Go to your device, then in the Summary section at the end there’s a Raw JSON, click the View button. A whole lot of text will appear, search for deviceTypeId and see if any of those lines starting with deviceTypeId is "deviceTypeId": 15
If there are no lines with 15 it means the Hue bridge is not exposing the dimmer as a button to Matter and SmartThings can’t really do anything about that. If there are lines with 15 (there should be four), then it’s a Matter driver issue.
Ahh, thanks. The original post stated that the device was supported through both LAN and Matter integrations, so I misunderstood.
I checked the raw JSON, and four lines do indeed have “deviceTypeId”: 15. If this is then a Matter driver issue, where is the correct place to report?
Let’s tag @nayelyz too, although you already tagged staff before.
Maybe it’s even an old issue already fixed, the problem with stock Matter drivers is that they only configure things once when they’re added and only update things when the driver is switched (hence my previous suggestion with the CLI command). So, if it was added time ago but was incorrectly recognized, it will stay that way.
Hi @fredrile
The engineering team mentioned that your Matter integration issue is likely due to Hue Bridges marking the device as unreachable.
We’re adding some additional robustness in a future firmware release to handle this better.
In the meantime, the issue should be resolved by removing the device and re-adding it in the Hue app.
Now you have the official answer which is, unsurprisingly, removing the device from the Hue bridge and adding it again. That indeed fixes many things in SmartThings as discussed earlier since stock drivers only configure devices when they are added or the driver is switched.
Mind removing the button from the Hue app will make it disappear from all your platforms and integrations so you will have to configure the button again in every platform.
Out of curiosity, before you go ahead, can you check again in the advanced website Summary of the device if the “Device Profile” is “matter-thing” or not? If it’s matter-thing I’m 99.9% sure the driver switch with the CLI mentioned before would fix it without having to reinstall anything, especially since the status is “Connected” so it is reachable (otherwise should say Offline) and the device types were correct so the profile can be correctly mapped.
3 Likes