Aw Man… I thought I was on to something. I can’t use the “ZigBee Thing Mc” driver because there is no driver option. And the Simple Device Info Viewer doesn’t show a model field.
I still believe the “finger print” for the ZigBee button is wrong because there is no other Osram Lightify 2 button switch.
I guess I need to figure out how to find the model and maybe make my own driver if I want this to work.
Thank you for the timely responses.
The driver option does not appear in the menu or does it not show the zigbee thing Mc driver as compatible?
If not appears the driver option then is using a DTH and can see the fingerprints in IDE
The driver option does not show in the menu. It is also listed as DTH in the simple device info viewer.
It’s fairly common for a device which has the same model number on the box and looks exactly the same physically to be sold with multiple different fingerprints for different reasons. Usually they represent different firmware levels, but it can also be an OEM issue. Or just a matter of being sold in different distribution channels or regions. You can find several examples in the forum of devices that have multiple possible fingerprints, but since the fingerprint needs to match exactly, the drivers need to be updated for each.
Also…as it happens there are multiple Osram lightify 2 button switches manufactured, but they are sold in different regions, so most individual users will only know of one.
You make some good points, but I am familiar with both switches, but one is described as a “switch mini” while the one I have is sold as a 2 button dimming switch.
But you are right. The identical looking device sold under the same name could have a different model. I just need to figure out what that is.
So I installed the Smartthings CLI and pulled the device information for my Dimming Switches that isn’t “fingerprinting” to the beta driver Zigbee Button. Below is the info that was pulled.
name": “OSRAM Lightify Dimming Switch”,
“label”: “Living Dimming Switch”,
“deviceManufacturerCode”: “OSRAM”,
“manufacturerName”: “SmartThings”,
“deviceModel”: “LIGHTIFY Dimming Switch”,
My plan was to create my own duplicate Zigbee Button Driver with the correct “fingerprint” information. Based on what you said above, my device should already be matched to the Zigbee button from the Smartthings Beta Channel, but it is not. It’s just showing as DTH.
2 out of my 3 switches work, but none of them fingerprints correctly. They all show as DTH. The only difference with the 1 that doesn’t work is that I removed and re-added it thinking that it would match a driver and it didn’t.
Unless SmartThings should be the manufacturer in the driver for it to fingerprint correctly.
Your device match with stock zigbee button driver fingerprints and must works fine
- id: OSRAM/LIGHTIFY Dimming Switch
deviceLabel: OSRAM Button
manufacturer: OSRAM
model: LIGHTIFY Dimming Switch
deviceProfileName: two-buttons-battery-holdTime
Try the steps in the following post. Do all 10 steps, including checking the IDE after removing the device. (Some people have found that a ghost remains that won’t go away until they delete it through the IDE. It doesn’t show up in the CLI listings, but it’s still enough to derail a new pairing.)
FAQ: I have no idea what Edge is. Is that a new developer tool? (2022) - #3 by JDRoberts
Is the deviceProfileName a part of the fingerprint? If so that could be the problem. By looking at the fingerprint for my other devices that have a driver, the profile name for the button would be RemoteController. This seems to be the section that matches the deviceprofileName
“categories”: [
{
“name”: “RemoteController”,
“categoryType”: “manufacturer”
}
<
I thought IDE was shutdown? Is there someway to still access it and the custom DTHs?
I have done everything in the 10 steps except Checking IDE, because I cant. Still Doesn’t work
you can probably still get to the IDE on the day of this posting at the following URL, but it is expected to go away soon. However, a lot of the functionality has been shut off. You can’t edit existing custom DTH‘s or add them, but you may be able to delete one or delete a device.
They keep changing the functionality without announcement, so I can’t promise what you’ll find when you get there, but this is what you can try.
Only manufacturer and model are need match to pair device
manufacturer: OSRAM
model: LIGHTIFY Dimming Switch
This is the profile assigned to work, (capabilities supported) by device in edge drivers.
For DTH is different in IDE. Please forgot IDE to check edge drivers.
Install driver Zigbee Button from smartthing Beta channel in your Hub
https://api.smartthings.com/invitation-web/accept?id=450930c1-02a6-43d8-adaa-4cbc51027956
If your devices not pair with the edge driver then could be need delete DTH
Yes. This is exactly what I needed to do. I deleted the DTH from IDE, then the Edge driver paired automatically the next time I added the device.
I was under the impression that IDE was shut down because all my smart apps stopped working. I had no idea I could still access it and couldn’t understand why several of my devices were listed as DTH if IDE was taken down
Thank You so much.
I have a 73743 that I used with the old DTH as a simple two button device (it was the only device handler that allowed me to monitor the battery life as well as use the buttons and it worked very well).
I have changed it over to the SmartThings Drivers (Beta) Zigbee Button and am regretting it.
The tile in the app shows me the battery status of the device but when I press either of the buttons on the device I get (to borrow the lyric from “Page One” by Lemon Jelly) Nothing!
I have excised its presence from the IDE and tried re-adding it several times.
Am I missing something?
I would check with @Mariano_Colmenarejo on whether his Zigbee button Edge driver would work for you. He’s Mr Zigbee for Edge 
I’m sorry, I don’t handle the zigbee buttons well and I only have driver for the single smartthings button
That seems fair enough.
Thanks.
However, if I uninstall the Beta driver and revert to standard Smartthings, I get the same result. In fact, the device controller in the app is so similar to Mariano’s that I suspect SmartThings just copied his code.
Is that the case?
The driver detects both buttons but does not repsond to presses.
I should apologise that I didn’t update this thread. The device automagically started working and I was getting on with it quite nicely.
However, within the last couple of days it has reverted to its old troublesome ways. The button flashes its orange light when I press a button but the driver panel in the app does not reflect any button presses and any associated activities fail to respond.
I don’t know if it’s related but I have had same smart bulbs randomly go ‘offline’ in the app. The strange thing is that they still respond in automations and scenes, so I don’t touch them. Is something wrong with the SmartThings platform that its becoming so flaky?