Add support for OSRAM Lightify 'Switch Mini' and 'Switch 4x' remotes

[olicooper]

Added support for the Osram Switch Mini+ and Osram 4x Button in collaboration with @Smanar

Switch Mini

• Up short / long press
• Middle (0) short / long press
• Down short / long press
• Battery reporting

4x Button

• Upper-left short / long press
• Upper-right short / long press
• Lower-left short / long press
• Lower-right short / long press
• Battery reporting

resolves #294
resolves #374
resolves #1893
resolves #2082
resolves #2763

[YKO-de]

I just tried it with a switch 4x. Mine delivers a different modelid.

[olicooper]

Very interesting, is this an old version of the Osram 4x Button then? The date code says 2016 possibly? I can fix this. Does the MAC address start with 0x000D6F? Just want to make sure we are targeting the correct one.

[YKO-de]

The switch is definitely old. The version is e.1.2.0CK. Which version do you have? I did not find an OTAU to update. Yes the mac starts with the vendor code 000D6F.

[olicooper]

I think the model number will always stay the same so an update won't change it. I don't actually have this switch, we've been talking to other people to get it configured. I do have the 3 button remote though.

I have added support for that model, so hopefully this will now work for you if you recompile the code. If the button mappings or configuration are different then we might have to revert these changes and work on another solution.

Would you be able to test all the button mappings and tell me what buttonevent outputs you get? for example:

Upper-left short press: 1002
Upper-left long press: 1001
Upper-left long press release: 1003

P.s. you will need to remove the switch from deconz and un-pair it before trying again.. see this link for unpairing. It just ensures that the binding process is done properly. Oh and You will need to add the switch via Phoscon as a "sensor" (the "other" option).

[YKO-de]

short press and long press are mixed up. But only for the top left button. The other keys work correctly.

• Upper-left short press: 1001

• Upper-left long press: 1002

• Upper-left long press release: 1003

• Upper-right short press: 1002

• Upper-right long press: 1001

• Upper-right long press release: 1003

But I also have the problem that not every time I press a key a command comes up.

[olicooper]

Thank you for that! I have updated the mapping for the button, if I understand correctly it should be okay now after recompiling :)

But I also have the problem that not every time I press a key a command comes up.

I can't explain this, I will have to ask @Smanar for feedback on this but we will probably need to look at the logs to understand this better. If all the button mappings are good, you will see the events appear in the log as you press them (if you tail -f the log output) for example: UL short press see this for the button mappings. It could be that the API is not updating, but the logs should always have all events in them.

[YKO-de]

The left side now works correctly. On the right side I only have short press events at the moment.

[olicooper]

Good news! I'm glad the left side now works.

So the issue with the right side could be because the button is an older version or it could be something else. We will definitely need logs to understand what is happening. We will probably also need other people with this button to tell us if they are getting the same results so we know if we are breaking it for other people or not.
Are you able to provide logs for us? Have a read of this issue #374 (comment), I have added some comments about getting logs from deconz if you don't know how.

[Smanar]

But I also have the problem that not every time I press a key a command comes up.

You haven't this problem with the original Gateway ?

[YKO-de]

I got the ConBee II.
At the moment I have no long press events on the right side. I'm trying to get the log right now.

[YKO-de]

ep02 has the same error

Is that enough or do you need more information?

[olicooper]

Yeah this is good.. So these are the events that I see in your logs:

15:44:49:379 button 1002 UL short press
15:45:09:087 no button handler for: Switch-LIGHTIFY ep: 0x02 cl: 0x0300 cmd: 0x01 pl[0]: 0x01
15:45:12:155 no button handler for: Switch-LIGHTIFY ep: 0x02 cl: 0x0300 cmd: 0x47 pl[0]: 0x00
15:45:31:144 button 2002 UR short press
15:52:59:756 button 1002 UL short press
15:53:21:798 button 1001 UL long press
15:53:54:507 no button handler for: Switch-LIGHTIFY ep: 0x02 cl: 0x0300 cmd: 0x01 pl[0]: 0x01 # duplicate
15:53:56:382 no button handler for: Switch-LIGHTIFY ep: 0x02 cl: 0x0300 cmd: 0x47 pl[0]: 0x00 # duplicate
15:54:29:162 no button handler for: Switch-LIGHTIFY ep: 0x04 cl: 0x0300 cmd: 0x01 pl[0]: 0x03
15:54:42:065 no button handler for: Switch-LIGHTIFY ep: 0x04 cl: 0x0300 cmd: 0x47 pl[0]: 0x00
15:57:06:436 no button handler for: Switch-LIGHTIFY ep: 0x02 cl: 0x0300 cmd: 0x01 pl[0]: 0x01 # duplicate
15:57:07:772 no button handler for: Switch-LIGHTIFY ep: 0x02 cl: 0x0300 cmd: 0x47 pl[0]: 0x00 # duplicate

I've added #duplicate to the entries which are the same. Could you tell me what order you pressed the buttons and whether they are short or long presses?

[YKO-de]

20200612.log

• top-left short, long
• bottom-left short, long
• top-right short, long
• bottom-right short, long

[andi78]

I see the osram switch mini in deconZ app but not as device in web app. DId i made something wrong?

6:59:30:239 button 2002 Down short press 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0006 on endpoint 0x01 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0006 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0008 on endpoint 0x01 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0008 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0300 on endpoint 0x01 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0300 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0006 on endpoint 0x02 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0006 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0008 on endpoint 0x02 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0008 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0300 on endpoint 0x02 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0300 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0006 on endpoint 0x03 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0006 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0008 on endpoint 0x03 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0008 16:59:30:239 0x000D6F001417D8C3 [Lightify Switch Mini] create binding for client cluster 0x0300 on endpoint 0x03 16:59:30:239 discard double entry in binding queue (size: 9) for for 0x000D6F001417D8C3, cluster 0x0300 16:59:31:179 Mgmt_Lqi_req zdpSeq: 241 to 0x7CB03EAA0A049EB3 start index 0 16:59:31:206 ZDP status = 0x00 -> SUCCESS 16:59:31:206 ZDP Mgmt_Lqi_rsp zdpSeq: 241 from 0x7CB03EAA0A049EB3 total: 1, startIndex: 0, listCount: 1 16:59:31:206 * neighbor: 0x00212EFFFF05AD7B (0x0000), LQI: 74, relation: 0x00 rxOnWHenIdle: 1 16:59:31:230 CTRL skip polling while permit join is set 16:59:32:232 CTRL skip polling while permit join is set 16:59:33:232 CTRL skip polling while permit join is set 16:59:33:579 Mgmt_Lqi_req zdpSeq: 243 to 0x00212EFFFF05AD7B start index 0 16:59:33:594 ZDP status = 0x00 -> SUCCESS 16:59:33:594 ZDP Mgmt_Lqi_rsp zdpSeq: 243 from 0x00212EFFFF05AD7B total: 5, startIndex: 0, listCount: 2 16:59:33:594 * neighbor: 0x7CB03EAA0A049EB3 (0xFB75), LQI: 231, relation: 0x02 rxOnWHenIdle: 1

[YKO-de]

@andi78 You're not doing anything wrong. They're working on integrating the switches now.

Please ask questions about the web app under the repository phoscon-app-beta.

[olicooper]

@Smanar according to @YKO-de's logs these should be the correct bindings...

static const Sensor::ButtonMap osram4ButRemoteMap[] = {
    // mode               ep    cluster cmd   param    button                                       name
    // Button upper-left
    { Sensor::ModeScenes, 0x01, 0x0006, 0x01, 0x00,    S_BUTTON_1 + S_BUTTON_ACTION_SHORT_RELEASED, "UL short press" },
    { Sensor::ModeScenes, 0x01, 0x0008, 0x05, 0x00,    S_BUTTON_1 + S_BUTTON_ACTION_HOLD,           "UL long press" },
    { Sensor::ModeScenes, 0x01, 0x0008, 0x03, 0x00,    S_BUTTON_1 + S_BUTTON_ACTION_LONG_RELEASED,  "UL long release" },
    // Button upper-right
    { Sensor::ModeScenes, 0x02, 0x0300, 0x4C, 0x01,    S_BUTTON_2 + S_BUTTON_ACTION_SHORT_RELEASED, "UR short press" },
    { Sensor::ModeScenes, 0x02, 0x0300, 0x01, 0x01,    S_BUTTON_2 + S_BUTTON_ACTION_HOLD,           "UR long press" },
    { Sensor::ModeScenes, 0x02, 0x0300, 0x47, 0x00,    S_BUTTON_2 + S_BUTTON_ACTION_LONG_RELEASED,  "UR long release" },
    // Button lower-left 
    { Sensor::ModeScenes, 0x03, 0x0006, 0x00, 0x00,    S_BUTTON_3 + S_BUTTON_ACTION_SHORT_RELEASED, "LL short press" },
    { Sensor::ModeScenes, 0x03, 0x0008, 0x01, 0x01,    S_BUTTON_3 + S_BUTTON_ACTION_HOLD,           "LL long press" },
    { Sensor::ModeScenes, 0x03, 0x0008, 0x03, 0x01,    S_BUTTON_3 + S_BUTTON_ACTION_LONG_RELEASED,  "LL long release" },
    // Button lower-right 
    { Sensor::ModeScenes, 0x04, 0x0300, 0x4C, 0x03,    S_BUTTON_4 + S_BUTTON_ACTION_SHORT_RELEASED, "LR short press" },
    { Sensor::ModeScenes, 0x04, 0x0300, 0x01, 0x03,    S_BUTTON_4 + S_BUTTON_ACTION_HOLD,           "LR long press" },
    { Sensor::ModeScenes, 0x04, 0x0300, 0x47, 0x00,    S_BUTTON_4 + S_BUTTON_ACTION_LONG_RELEASED,  "LR long release" },
    // end
    { Sensor::ModeNone,             0x00, 0x0000, 0x00, 0,    0,                                           nullptr }
};

But this is an old version of the device which could have different bindings. Should I update these bindings on the PR for testing?

Also, @andi78 We won't be able to get the button to show in Phoscon because we don't have access to the code. What we have done is told the core deCONZ system how to talk to these new devices. dresden-elektronik will need to update their Phoscon app to allow you to see them on the UI. It looks like you have paired the button okay though so you should see the button working in the API (see this guide and also this API guide)

[Smanar]

Yes, I think Osram make their remote compatible, so I don't think they change the command.
And there is @pollierer that have recent device and know the procedure to test it.

Else we just need to make 2 table, will be easy the 2 device have different name.

But better if someone can make some test before you make the PR. For the 3 buttons switch we have remake the table at least 6 / 7 time ^^.

[YKO-de]

@olicooper You're welcome to do that. I don't get to test it until Tuesday. I can't do it now.

[olicooper]

So I will try to get the changes up on my old repo for testing instead then. Just need to merge all the other updates first. I'll try to do it soon.

[pollierer]

uh much to read.. I will Check the thread on monday evening and geht back to it!

[olicooper]

@pollierer Yeah there was quite a few things happening today! We didn't want to update the code on this PR without testing first, so I copied the changes to my old repository: https://github.com/olicooper/deconz-rest-plugin-old/commits/smanar-osram-switch

If you build from that repository then you will be able to see if the button mappings are all working properly now. That's all that needs testing at this point, it looks like everything else is working. You probably don't need to read anything else.

[grayve]

Hello this is coming from this website https://www.ledvance.com/consumer/smart/faq/faq-for-smart-zigbee-products/index.jsp

5.2.2. HOW CAN I USE THE SMART+ ZIGBEE SWITCH TO CONTROL OTHER SMART+ ZIGBEE PRODUCTS WITHOUT THE USE OF A SMART HOME SYSTEM (VIA TOUCHLINK)?
a) Use Touchlink with SMART+ Switch:

1. Plug in the SMART+ Zigbee product you want to connect to the SMART+ Switch and wait 20 seconds. Only one product is able to pair within one Touchlink cycle.
2. Hold the SMART+ Switch 1-5 cm away from the respective SMART+ Zigbee product.
   Please be aware that some SMART+ Zigbee luminaires have a separate control unit between the power supply and the luminaire itself. For Touchlink pairing hold the SMART+ Switch within 1-5 cm distance to the control unit.
3. Press and hold the left and right lower buttons for up to 10 seconds. The status LED of the SMART+ Switch will blink blue several times. Release the buttons immediately when the status LED stops blinking and constantly shines blue.
4. The pairing was successful if the status LED blinks blue again and the corresponding SMART+ Zigbee product blinks once. When the pairing failed the status LED blinks red, if so, please start over with step 2.

indeed on the next chapter I can see:
5.2.4. HOW CAN SMART+ ZIGBEE SWITCHES BE CONNECTED TO A COMPATIBLE SYSTEM?
a) Setting a SMART+ Switch into pairing mode:

1. Make sure the battery of your SMART+ Switch is properly inserted. You might have to remove the battery protection strips.
2. Simultaneously press and hold the lower left and upper right button. The status LED should continuously blink blue while holding the buttons.
3. Release the buttons after 3 seconds. The status LED should give a short sequence of blue flashes and then stop blinking.
4. Within 30 seconds your SMART+ Switch should appear in your smart home system.

So indeed it's the wrong process

[Smanar]

ha yep, it s like for ikea (4 short press or one long press), the first one is to link remote<>bulb and the second remote<>netowrk

Someone can confirm me the 4 buttons is this one ?

On his side He have only green LED.

[larslorenz]

Hi,

there is also another one of the 4 buttons grey switches. This one has a full height line in the middle and something like a small break or antenna.. My one of this kind has also a blue led in the middle. But I can connect this switch on the same way (press upper right and lower left for a moment).
Right now I m able to connect a smart switch mini and a smart switch 4 button. I can see them in deconz but how can I configure them now? Is there any working way or do we have to wait for a phoscon integration (is there maybe something in the pipe?).

thanks for help

[olicooper]

Adding the button

1. Make sure the button is not already added to deconz. If it is then it will need to be properly removed from deconz before proceeding (see 'Removing an existing button' note below)
2. Go to Phoscon web app, then Sensors > Add new sensor > Other
3. Put the button in pairing mode
   • Lightify Switch 4x: Press the upper-right and lower-left buttons at the same time for around 3-5 seconds (until the blue light flashes quickly 3 times to indicate it has paired)
   • Lightify Switch Mini: Press the up and center buttons at the same time for around 3-5 seconds (until the blue light flashes quickly 3 times to indicate it has paired)
4. Wait for the phoscon app to say "sensor added"

Pairing with a light

This can be done in home assistant using automations (see this for help) OR directly in the OLD phoscon app by adding the relevant lights to the same group as the button. You can access the old app via http://<ip-address>/login.html or Phoscon App > help > Open Old WebApp

Removing an existing button

1. Go to the phoscon API (not the deconz GUI). Read the REST API guide for more info
2. Find the ids for the sensors you need to delete GET /sensors
3. Delete the sensors DELETE /sensors/

[larslorenz]

Hi,

I had tried to delete the switches from the deconzGUI. My way was reset them, and than delete it. After that tasks the buttons where still visible in the deConz GUI but without the small colored lines which shows the connections.
After a reboot and a second attempt to delete them they where not showed up again.
So afterwards I did a new reconnect like I write yesterday. But I did this in the switches area of phoscon not at sensors (maybe german translation issue?). Deconz found the switches very fast and connect them. But this is the last state they are connected but only switch all lights.
If i use a get request to the deconz api like get/.../sensors I only get the predefined daylight sensor, no other sensors which I maybe can delete via the API way. At the end I can see in the rest api everything as aspected except of the switches. do i do something wrong?

[grayve]

For information for those a little bit limited like me (no joke)

You can add device using phoscon pairing but you will not see them in this interface. You have to open the VNC interface where you'll find them.
Once done you can use the deconz_event listening inside Home Assistant to get the id and event number to use it inside your automation.
Quiet simple at the end if you don't expect to see them in the phoscon interface and only in the VNC one.

[olicooper]

@larslorenz You can't delete the device on the deCONZ GUI because it doesn't actually delete it at all. My short guide states that you need to delete it through the Phoscon API. It was a good idea to reboot after deleting it though as this will power-cycle the conbee/raspbee which is why it didn't come back for you after rebooting.

After you pair the button you should see it when you do GEt /sensors. If you do not see it then it hasn't paired correctly.

But I did this in the switches area of phoscon not at sensors

You should add a 'Sensor' not a 'Switch'

@grayve is correct, you will not see the button in Phoscon until drezden-elecktronik update the Phoscon GUI, but you can still use the button through the Phoscon API until then.

[Smanar]

@larslorenz if you can see the device in deconz but not in the API, and make inclusion using phoscon

Can you give us the model id of the device ? Basic cluster 0x0000 in the table, you probably need to wake up the switch and press the "read" button in same time.

[larslorenz]

@larslorenz if you can see the device in deconz but not in the API, and make inclusion using phoscon

Can you give us the model id of the device ? Basic cluster 0x0000 in the table, you probably need to wake up the switch and press the "read" button in same time.

First I have tzo say sorry, I did againb a check and see that I just had the deconz v .05.78. So I allready installed the v 5.79 but didnt make checks right now. I will do it today later, and give you more informations afterwards.

thanks & greets

[larslorenz]

Hi,

so I tried again some steps. Right now I have surly the ..5.79 prerelease, but also here there is no way to delete the old paired devices with the api. I dont can find them there anywhere, and right now it also doesnt works to delete them from the deconz gui side.
One point is I m very early in a testing phase to change over to deconz conbee etc so its no problem for me to factory rset something. So What can I do to really get rid of that old paired devices? And how can I help you with more infos.

greets

[larslorenz]

Hi,

I try now to connect one switch which I never had connected before. I now use the sensor connection in phoscon, and see the working pairing in deconz gui. Direct special was that right now I get a real name from the device not the before typical kryptic names. Also I see the new group in the old webapp and can configure it like you suggest (put a light in the same group).
So now it controls - like it was planned - only one bulb on the right side buttons.
I see it in deconz-gui with right name.
I see it also in an api call to endpoint sensors.
I did not see the old paired switches in the API call so I m not able to delete them properly.
I see the old paired buttons in deconz gui.
Also if I do a request to .../api/apikey/ I searched for fitting entries but there is nothing.

My questions:
Is there a way to use/configure the other buttons of the switch?
Why do I have to connect the switch as a sensor, and did that make any problems in the future (maybe it will be future possible to connect it as a switch)?
Is there any other way to get the needed ID to delete the old switches properly?
In phoscon beta there are a lot new switches possible (a new nav point switches (beta)) but sincs now there is no place for osram/ledvance switches. Do you guys have any info about a possible integration in phoscon soon?
Can I help you with something like any information I can read out with deconz gui or stuff like thatß

thanks in advance..

[olicooper]

I see the old paired buttons in deconz gui

I think you can safely delete these in the deconz gui, you can identify the new entries by pressing a button and watching for the blinking blue/green LED on the deconz gui.

Is there a way to use/configure the other buttons of the switch?

If you want to control the individual buttons then you will have to use HomeAssistant instead of adding the light to the same group as the button like you currently have it configured.

Why do I have to connect the switch as a sensor

It is just how I have managed to get it to work properly. You shouldn't have any issues but I can't be 100% sure. I haven't had any for 2+ months

Is there any other way to get the needed ID to delete the old switches properly?

Don't worry about deleting the old entries as it is working for you now. Deleting the old entries just ensures the device is paired properly rather than using an old configuration.

Do you guys have any info about a possible integration in phoscon soon?

We are not drezden developers so I don't have any timeline for you. You'd have to ask them directly somehow (maybe using discord?)

Can I help you with something like any information

If the buttons are working as expected (not switching all lights etc.) then everything should be fine. Which buttons have you connected - 2 x Switch Mini + 1 x Switch 4x ? You can find out the model numbers in the deconz gui if you need to.

So now it controls - like it was planned - only one bulb on the right side buttons

Do all 4 buttons work or just the right side?

[larslorenz]

I think you can safely delete these in the deconz gui, you can identify the new entries by pressing a button and watching for the blinking blue/green LED on the deconz gui.

I can delete them but they are directly reappearing

If you want to control the individual buttons then you will have to use HomeAssistant instead of adding the light to the same group as the button like you currently have it configured.

I m using fhem maybe there is a was also do get it done?

Is there any other way to get the needed ID to delete the old switches properly?

Sadly I m not able to reconnect the devices which I used before for trying. I m was only able to connect a new never used before one.

We are not drezden developers so I don't have any timeline for you. You'd have to ask them directly somehow (maybe using discord?)

Okay thanks I will do... BUT right after I wrote the last post I see that the button now appears in the pwabeta as a sensor but properly named as a osram switch.. But I was only able to rename the sensor in the phoscon pwabeta.

If the buttons are working as expected (not switching all lights etc.) then everything should be fine. Which buttons have you connected - 2 x Switch Mini + 1 x Switch 4x ? You can find out the model numbers in the deconz gui if you need to.

I have connected working and clean: 1 Osram 4 Buttons; Before the update I had connected one smart switch mini and one of this special osram 4 button switches https://preview.redd.it/h3pwps0q9wa31.jpg?width=1500&format=pjpg&auto=webp&s=7473f78688f48a3797601565b746ba9f32dfcaa3
both of them im not able to connect them clean now. and this are the ones I can not find in the api and cannot delete them. I give it a try and did a research in my zll.db but also there I didnt find anything (maybe a neighbour table problem?)

Do all 4 buttons work or just the right side?

Sorry it was the left side, but only the left side works for the configured group.

thx

[Smanar]

To delete device you can too use command line (but take care, not reversible)

curl -X DELETE http://192.168.1.1:80/api/AZ7844FG44/sensors/7

It delete the sensor 7 in the API, but not in deconz.

[larslorenz]

It delete the sensor 7 in the API, but not in deconz.

sadly I m not able to see the old sensors in the api, so I can not figure out which ID I have to delete. There is only the standard virtual time "sensor" and now the one newly paired 4switch button...

Is there A way to reset everything in deconz so I can start from the scratch?

[Smanar]

Yep, you can delete the zll.db file.
But if you can see it in sensor list, it mean you have already delete it, no ?
You have the full list using the url
http://IP:PORT/api/KEY/sensors

[letszb]

The Lightify / Smart+ Switch is already fully functional in the Phoscon App. Only the specific icon is currently not available. Add the switch via "others".

[Chris-LZ]

WOW!!! :-) :-) Really great, Thanks to you guys to implement the switches! (y)

Unfortunately I'm not able to connect my 4-Button Lightify - Switches :-(
Maybe I do somethting wrong? (I have the ConBee2 USB-Stick, connected to a Raspi4B with normal Raspbian running (Desktop Version).
Could you guys please give me a hint what I'm doing wrong?

I connect them like to the OSRAM gateway.

This is what I do:

• reset the switch (hold upper left and down right button for about 10 sec, until it blinks green)
• in phoscon, I add a new "others" switch
• I press and hold the upper right and down left buttons for about 3 sec, until it blinks blue.

In the phoscon app happens nothing :-/ after a few minutes it says the the connection failed.
But in the deconzGUI I can see a new device showing up, but with a generic name (I guess thats the adress of the switch). So it seems like its connected - somehow.
When I press one of the 4 buttons on the lightify switch, ALL lamps connected to deConz are switched on and off.
But I cant configure something, because the switch isn't displayed in phoscon :-(

[Edit: I also did an upgrade to latest firmware (deCONZ_ConBeeII_0x26660700) and the phoscon app "deconz-latest-beta" according to that official manual: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Update-deCONZ-manually#update-in-raspbian ]

Do you guys got it up and running? THANK YOU VERY MUCH FOR YOUR HELP in advance!! :-)

[Smanar]

Hello, what is the model id of the device ? (visible in deconz, cluster 0x0000, you probalby need to press "read" and make the device awake in same time to have values)

[Chris-LZ]

Hello, what is the model id of the device ? (visible in deconz, cluster 0x0000, you probalby need to press "read" and make the device awake in same time to have values)

Thank you Smanar for your help :-)
This is what I can see:

And its displayed like:

Sorry for being stupid, I'm not that firm with deConz yet :-(

[Smanar]

The IEEE is a good one, but not the Manufacture code.
But your device is not correctly inluded in deconz, it miss the second circle on the node.

2 things you can try (and first delete the node in deconz to be sure)

• Remake the inclusion procedure, but just after the blink, use the switch every seconds to penvent it fall asleep.
• If it appear again in deconz, use the first circle to enable the second one (use availables commands when press the first circle, but you need to awake the device again whith using it in same time)

[Chris-LZ]

The IEEE is a good one, but not the Manufacture code.
But your device is not correctly inluded in deconz, it miss the second circle on the node.

2 things you can try (and first delete the node in deconz to be sure)

* Remake the inclusion procedure, but just after the blink, use the switch every seconds to penvent it fall asleep.

* If it appear again in deconz, use the first circle to enable the second one (use availables commands when press the first circle, but you need to awake the device again whith using it in same time)

YEEEAHHH!!!!! :-) great! Exactly that was the issue! THANKS A LOT, mate!! (y)
It looks like that the switch is going to sleep after the first circle. By keeping it awake with button press every secound, it does the 2nd circle and then it gets detected correctly.
Super! :-)

[hchchchc2]

The Lightify / Smart+ Switch is already fully functional in the Phoscon App. Only the specific icon is currently not available. Add the switch via "others".

Hi,
i already did it this way using the 4-Button Ledvance Smart+ Switch but without success.
The Software i'm using:

iobroker 4.1.11
deConz Version:1.3.11
Conbee II Stick on Raspberry Pi 4
2.09.01 / 12/23/2020
26660700

I tried to connect as Sensor and as Switch but both don't work.
The switch hast AB37186|x1319 Ledvance Smart+ Switch writte on the Backside.

Should it work in that configuration ?
Did i do something wrong ?
I really appreciate your help ;-)
Thanks and BR/Chris

[mo8Zomo0]

Is there any trick to pair like the Switch 4x to the current deconz / conbee II.
I am running the docker image and it is using channel 25.

docker images|grep deco
marthoc/deconz                       latest    e45c6747d34e   5 days ago      643MB

deconz    | [marthoc/deconz] Current deCONZ version: 2.13.01
deconz    | 02:15:19:137 Device firmware version 0x26680700 ConBee II
deconz    | 02:15:19:183 Current channel 25
deconz    | 02:15:21:634 GW firmware version is up to date: 0x26680700

Other devices have less issues (I think the Aqara Door sensor was also a bit resistant).

What would the right procedure be?

I am selecting on the webinterface switches > add new switch > other
(btw, there is a "ready" button which seems to be greyed out)

Then I am trying to press (tried different combinations, either just one or both and reversed the order).

left bottom+right top (hold 3sec) = blue blinking = pairing
left top, right bottom (hold 10 sec) = green blinking = reset

I tried it close by the conbee, or further away where it should be located. No change, no pairing.

Any tip what I might do wrong here?

I managed to add such a switch to a hue bridge 2, from what I recall that was also a lot of pain.
Interesting enough this turns on or off all devices connected to the hue bridge, or when pressing
the top right button long, puts the hue bulbs in a color cycling mode, but thats just a side note ;-)

[olicooper]

I don't have the 4 button switch, but I think that the pairing process has been mentioned before on this issue or one of the related issues. For my 3 button remote I think I went to "add sensor" rather than "add switch" but it was a long time ago now since I last did this so I can't remember exactly what I did. I think you are correct about holding multiple buttons down though. You may have to open up the deconz GUI to check if it has been added already but the pairing process failed part-way through so it didn't appear on the web UI? Details on deleting devices has been mentioned here before too if you need to do that. And I believe there is a guide on accessing the deconz GUI through docker somewhere too. Sorry I can't help you more.

[dicer]

Check the GUI. For me the pairing worked but it does not show up in the web interface, just in the network view in the other UI. You can then use it with the API.

[mo8Zomo0]

@olicooper / @dicer

thank you for the feedback. I now tried to add it as a sensor (and also via the lamp dialog) but no success.
I have and had the gui open and can not identify anything popping up of the switch in the graph or in the log when
trying to pair it or resetting it. :-/
Maybe I am just unlucky.

[KoljaHenckel]

HI all,
I have an osram smart+ switch mini (https://www.amazon.de/Ledvance-SMART-Switch-Fernbedienung-ZigBee/)
Using latest version on Home Assistant(6.6 -- core-2021.11.2 -- supervisor-2021.10.8) and deCONZ Addon (6.10.0 ).
Phozconz interface does not find it to connect, and deCONZ does not show it afterwards.
Any suggestions what to do? Or anyone got this button really running?

[Mimiix]

@KoljaHenckel I usggest to post on the forums :)

It won't show in Phoscon probably, as they need to add support themselves.

[Florian-Schmidt]

HI all,
I have an osram smart+ switch mini (https://www.amazon.de/Ledvance-SMART-Switch-Fernbedienung-ZigBee/)
Using latest version on Home Assistant(6.6 -- core-2021.11.2 -- supervisor-2021.10.8) and deCONZ Addon (6.10.0 ).
Phozconz interface does not find it to connect, and deCONZ does not show it afterwards.
Any suggestions what to do? Or anyone got this button really running?

@KoljaHenckel I guess it won't work in your first tries. I also needed multiple tries to get them recognized by Phoscon. Try to reset the switch and afterwards to connect again. Not sure but out of my mind reset should be arrow up and arrow down at the same time until there's an LED signal on the switch.