Give it a try and see what turns up in the logs
I did a delete/re-add of the device, and I deleted the DTH I had and pasted in your current one. I loaded the Advanced Button Controller Smartapp, and used it to configure the device. At first I set it to a normal behavior controlling a bulb Iâve been using by my desk to test. I set Btn1: push = on, hold = brighten. Btn2: push = off, hold = dim. I set Btn3 & btn4 to mimic 1&2, but they do not function, and report nothing in the logs.
Just to see what would happen, I changed the SmartApp config so Btn1 push would turn the light off, and Btn 2 would turn it on. This worked, sort of. If I press Btn1 when the bulb is already off, it starts to come on, then turns off. If I press Btn2 when the bulb is already on, it starts to turn off, then comes back on. Itâs like thereâs built-in functionality, and SmartApp is only partially overriding that functionality.
Then for another test, I switched the app settings to control a different bulb. When I did, it still controlled the test bulb AND the other one that I changed it to. I double-checked to make sure I didnât accidentally leave the test bulb checked (which I hadnât). When I changed the config back to the test bulb, it worked (and no longer controlled the second bulb). This one is definitely gonna need some more testing to understand whatâs going on.
Any advice/suggestions for my next round of testing?
Did you reset the switch before adding it? The switch is intended by the manufacturer to control bulbs directly, and this is what it does out of the box. I would guess it controls the bulb without you seeing anything in the logs because it is sending the message not to the hub but to the bulb. Confusingly, mine did both initially i.e. controlled the bulb and sent the messages to the hub, yet I had not set up any smartapp. This was because before adding the switch to smartthings I had previously configured it to control that bulb in the lightify app. If the bulb is being turned on and off at the same time it sounds exactly like this situation, i.e. the switch is sending âonâ messages to both the bulb and hub, and your smartapp is then sending and âoffâ command to the bulb.
It sounds like it is working on he ST side but it is hard to tell whilst it is still configured to control directly, and not sure if youâre saying buttons 3 and 4 still donât work. I still think you should check that the handler is working first - without any smartapp configured. You should see the tiles on the device page update when you press and hold the buttons, without bulbs coming on and off.
If I remember correctly the reset is done by holding the bottom 2 buttons for some length of time. I did that, but maybe not long enough. I didnât confirm that it no longer controlled any lights, before loading the new DTH & Smartapp, so youâre probably right.
Correct, buttons 3 & 4 still arenât doing anything. The LED on the remote lights up green like it thinks itâs doing something, but thereâs no activity in any of the SmartThings logs.
Iâll try getting it actually reset, and kill the smartapp tonight and see what happens.
So I did a reset, and verified that it no longer controlled anything. Then I deleted the device from SmartThings, then readded it. After adding it, I set the type in the IDE to âOSRAM 4 Button Switchâ, which should set it up with your DTH.
At this point, it seems to be controlling a couple (seemingly random) bulbs. Button 1&2 are on and off for my test bulb, as well as 1 other bulb that Iâm pretty sure Iâve never set it to control. Buttons 3 & 4 still do nothing. Is there anything in your DTH that would assign it some default mappings that would explain the fact that itâs controlling 2 devices w/o a Smartapp configuration?
On the âRight Nowâ page in the SmartThings app, pressing B1 changes that square to show âonâ, holding sets it to âlevel upâ, release after hold changes it to âlevel stopâ. B2 press shows âoffâ, hold=âlevel downâ & release=âlevel stopâ. B3 & B4 just have a â0â that never changes.
Iâm new to groovy and to the SmartThings codes, so forgive my ignorance, but looking through your DTH, I noticed you have the following:
fingerprint profileId: "0104", deviceId: "0810", inClusters: "0000, 0001, 0020, 1000, FD00", outClusters: "0003, 0004, 0005, 0006, 0008, 0019, 0300, 1000", manufacturer: "OSRAM", model: "Switch 4x EU-LIGHTIFY", deviceJoinName: "OSRAM 4x Switch (EU)"
fingerprint profileId: "0104", deviceId: "0810", inClusters: "0000, 1000, 0020, 1000, FD00", outClusters: "0003, 0004, 0005, 0006, 0008, 0019, 0300, 1000", manufacturer: "OSRAM", model: "Switch 4x LIGHTIFY", deviceJoinName: "OSRAM 4x Switch (US)"
I have Model: Switch 4x-LIGHTIFY and my fingerprint is:
01 0104 0810 02 05 0000 0001 0020 1000 FD00 08 0003 0004 0005 0006 0008 0019 0300 1000
âŠwhich matches the inClusters numbers for the Switch 4x EU-LIGHTIFY model in your DTH. Am I misunderstanding, or should the inClusters string be â0000, 0001, 0020, 1000, FD00â for both EU & non-EU?
UPDATE: I tried changing updating my DTH with inClusters: â0000, 0001, 0020, 1000, FD00â, and it doesnât seem to have made any difference. I did not delete/reconnect it tho, is that necessary to get it to see changes in the DTH?
Same fingerprint for my US switch. I also update the DTH to use my fingerprint, but it did not help. There are still no messages sent to the hub when 3/4 are pressed.
Hi Iâve just bought one of these switches hoping to get it working with my smartthings hub but I canât seem to get it paired with the hub. Iâve tried removing the battery several times but nothing happens when I try to add it as a thing in ST. How did you guys all manage to at least do that?
Cheers
I am trying to look into this as well, but I cannot see anything for buttons3/4
I am in the same boat. Any updates on this? Mine will only register as a âthingâ, and I can change it to a zigbee switch, but it just turns off and on other zigbee lights. 1 and 2 are the only buttons that have and events show up in the log. I have the US version of FCC ID:2AJRH-LDV740099
model: Switch 4x-LIGHTIFY
application: 01
manufacturer: OSRAM
endpointId: 01
Raw Description 01 0104 0810 02 05 0000 0001 0020 1000 FD00 08 0003 0004 0005 0006 0008 0019 0300 1000
8:54:49 PM: info Button 1 released (action: level stop)
8:54:49 PM: debug message data: []
8:54:49 PM: debug message command: 3
8:54:49 PM: debug message endpoint: 1
8:54:49 PM: debug message cluster: 8
8:54:49 PM: debug Parsing 'catchall: 0104 0008 01 FF 0100 04 71DF 01 00 0000 03 00 '
8:54:46 PM: info Button 1 held (action: level up)
8:54:46 PM: debug message data: [0, 38]
8:54:46 PM: debug message command: 5
8:54:46 PM: debug message endpoint: 1
8:54:46 PM: debug message cluster: 8
8:54:46 PM: debug Parsing 'catchall: 0104 0008 01 FF 0100 04 71DF 01 00 0000 05 00 0026â
8:54:44 PM: info Button 1 pushed (action: on)
8:54:44 PM: debug message data: []
8:54:44 PM: debug message command: 1
8:54:44 PM: debug message endpoint: 1
8:54:44 PM: debug message cluster: 6
8:54:44 PM: debug Parsing 'catchall: 0104 0006 01 FF 0100 04 71DF 01 00 0000 01 00 '
8:54:39 PM: info Button 2 released (action: level stop)
8:54:39 PM: debug message data: []
8:54:39 PM: debug message command: 3
8:54:39 PM: debug message endpoint: 3
8:54:39 PM: debug message cluster: 8
8:54:39 PM: debug Parsing 'catchall: 0104 0008 03 FF 0100 04 71DF 01 00 0000 03 00 '
8:54:38 PM: info Button 2 held (action: level down)
8:54:38 PM: debug message data: [1, 38]
8:54:38 PM: debug message command: 1
8:54:38 PM: debug message endpoint: 3
8:54:38 PM: debug message cluster: 8
8:54:38 PM: debug Parsing 'catchall: 0104 0008 03 FF 0100 04 71DF 01 00 0000 01 00 0126â
8:54:30 PM: info Button 1 released (action: level stop)
8:54:30 PM: debug message data: []
8:54:30 PM: debug message command: 3
8:54:30 PM: debug message endpoint: 1
8:54:30 PM: debug message cluster: 8
8:54:30 PM: debug Parsing 'catchall: 0104 0008 01 FF 0100 04 71DF 01 00 0000 03 00 '
8:54:25 PM: info Button 1 held (action: level up)
8:54:25 PM: debug message data: [0, 38]
8:54:25 PM: debug message command: 5
8:54:25 PM: debug message endpoint: 1
8:54:25 PM: debug message cluster: 8
8:54:25 PM: debug Parsing 'catchall: 0104 0008 01 FF 0100 04 71DF 01 00 0000 05 00 0026â
8:54:16 PM: info Button 2 released (action: level stop)
8:54:16 PM: debug message data: []
8:54:16 PM: debug message command: 3
8:54:16 PM: debug message endpoint: 3
8:54:16 PM: debug message cluster: 8
8:54:16 PM: debug Parsing 'catchall: 0104 0008 03 FF 0100 04 71DF 01 00 0000 03 00 '
8:54:16 PM: info Button 2 held (action: level down)
8:54:16 PM: debug message data: [1, 38]
8:54:16 PM: debug message command: 1
8:54:16 PM: debug message endpoint: 3
8:54:16 PM: debug message cluster: 8
8:54:16 PM: debug Parsing 'catchall: 0104 0008 03 FF 0100 04 71DF 01 00 0000 01 00 0126â
8:54:17 PM: info Button 1 pushed (action: on)
8:54:17 PM: debug message data: []
8:54:17 PM: debug message command: 1
8:54:17 PM: debug message endpoint: 1
8:54:17 PM: debug message cluster: 6
8:54:17 PM: debug Parsing 'catchall: 0104 0006 01 FF 0100 04 71DF 01 00 0000 01 00 '
8:54:10 PM: info Button 2 pushed (action: off)
8:54:10 PM: debug message data: []
8:54:10 PM: debug message command: 0
8:54:10 PM: debug message endpoint: 3
8:54:10 PM: debug message cluster: 6
8:54:10 PM: debug Parsing 'catchall: 0104 0006 03 FF 0100 04 71DF 01 00 0000 00 00 '
8:54:05 PM: info Button 1 pushed (action: on)
8:54:05 PM: debug message data: []
8:54:05 PM: debug message command: 1
8:54:05 PM: debug message endpoint: 1
8:54:05 PM: debug message cluster: 6
8:54:05 PM: debug Parsing 'catchall: 0104 0006 01 FF 0100 04 71DF 01 00 0000 01 00 â
I am having the same issues. I have loaded Andyâs device handler, but am unable to get the hub/app to see the switch. I have removed the battery and set it into pairing mode a number of times with the hub a few feet away, but it never gets discovered.
May I join in here? I have two of these purchased from Amazon. I was misled by some reviews that said it pairs with ST, but now realize that the reviews were talking about other product âvariantsâ on that page.
I have loaded the DTH in the IDE, but Iâm not even getting a pairing (does it require the DTH to get that far? Iâm stoopid here). The little booklet and Sylvania support say they donât know how to put it into pairing mode, alhough âresetâ is holding upper left/lower right for 10 seconds. In this thread, it is mentioned to hold lower left/upper right instead. And to top it off, the booklet says that pairing mode is indicated by flashing blue. BLUE! so far Iâve seen this thing do green and orange, never a blue.
And one last question ⊠I loaded the DTH in the IDE, but I donât know what a Binder is. I mean ⊠I have the code ⊠just donât know where it goes.
Thanks for any help!
I returned mine Osram Lightify 4 Button Switch. The best be bet if you want multiple buttons that I found was the Aeotec By Aeon Labs ZW130-A WallMote Quad which I found on Ebay. Works great and the device handler and the app that runs it is pretty good. You can button press, hold, and you can even fade up and down. The Osram Lightify 4 Button Switch seems to be great if you have the European version, but not if you have the US version, as the firmware is different for the zigbee.
I gave up and returned mine as well. Thanks for the recommendation.
Apologies for absence, real life took over. So looking at Scott_Hâs post I guess the fingerprint is actually the same for the 2 devices (previously he posted his was reporting a fingerprint with some missing inClusters). I have updated the handler to reduce confusion. Youâd have to re-add the device for it to show up but I donât think it would make a functional difference anyway).
I suspect the reason some are having issues with buttons 3 and 4 is because the different firmware shipped in US and EU units causes them to simply behave differently. If you are seeing no events at all in the logs then I donât think thereâs much we can do as it is not sending anything to smartthings for those outClusters. We would need to analyse and reverse engineer the method that Osram use to configure the switch in their native app I suspect. Not even having a device or hardware necessary to sniff ZigBee packets (or the time) this isnât something I can do.
Just succeeded in getting smartthings to see this switch, but had to chenge the model to âSwitch 4x EU-Lightifyâ in Andyâs code as Iâm in the UK, which is still part of Europe. However, Iâm getting no response from button 4. Nothing in the logs or the event list. Strangely it worked on a previous attempt, when I was getting the broadcast effect from button 1, so Iâm sure the button is physically OK. Any ideas?
I notice this thread has been quitet since February, so I may be posting in the wrong place.
Did you try a reset?
It comes down to the firmware. If it doesnât match as we al found it is a no go.
Got this to work, eventually, after a couple of resets. Iâm now trying to implement a dimming function using webcore. However, all the examples I can find assume that an event is sent when the button is released. I can see that in the smartthings logs, but not in webcore. Not sure whether this is an issue with the DTH or with webcore.
In the function âgetBatteryResultâ the âdescriptionTextâ contains ${result.value}, which should be ${value}, I believe. In any case, this change seems to fix the âbatteryâ reporting problem.
Thanks I updated it on GitHub