[New device request] Osram Smart+ mini switch #2763
Comments
NicolasBoulanger
changed the title
|
Hello. There is so much issue about it Some people say it's working, some other not. And I don't see the problem, I m missing something ? This device is detected in deconz ? I don't see it in supported device on the code, you have it as light or sensor ? Can you show me the device JSON pls ? You want to use it for your roller shutter ? But how it work ATM, I m seeing only 3 button on the device and according to the cluster it can make on/off+ level control + color control, seriously ??? Edit: Button 1 short press: All ON |
|
its not really working, i cannot see remote in switch category on deconz software i use it with: long press up: open desktop window cover my second remote, i use it for garden light which json logs you need ? which command? 15:52:24:069 APS-DATA.indication srcAddr: 0x532a, srcEp: 0x02 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 215, rssi: -6715:52:24:069 APS-DATA.indication srcAddr: 0x532a, srcEp: 0x02 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 215, rssi: -67 15:54:00:255 APS-DATA.indication srcAddr: 0x50b9, srcEp: 0x02 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 215, rssi: -67 thanks ! |
|
Ok so you are using it with zigbee broadcast (or group) command ? Are you using an home assistant application with deconz ? HASS openhab or other ? (and have an API key ?) |
|
i'm using unicast: default configuration in deconz docker version all in bridged network, managed by my unifi router |
|
if can help |
|
Ok so I think this device is not in deconz at all. It will be something I will ask again soon, so to see your device in deconz API, you can use this kind of url Now I can try make a ZHAswitch for this device, so you will have a value for all fonctions (IDK how much yet). But if you want to make "direct connexion" between your shutter and the remote, not sure if it will work. You can make try using phoscon. But if you want a buttonevent value like for ikea remote to use it with nodered, I think it will be possible. But it's strange no one have already do it ^^, I think there is a trap I haven't see yet. |
|
ok i'll check with the api |
|
i think this is the action for remote switch? |
You can get the API key by locking up the gateway and run a Rest client, or Curl: |
yes i have my key :) |
|
Ok so I have started Smanar@55ecd9a But I have some problems for the table sensor. Have you an Unix machine 32 bit to compile the code and make tries ? The procedure is explained here > https://github.com/dresden-elektronik/deconz-rest-plugin at "Install deCONZ development package (optional, Linux only)" You just need to change the step 1 by The new code will include the device, you will probably have some issue with braodcast command (some bulbs in your network will react to the remote). You will have a new sensor, a ZHAswitch with "bouttonevent" field. If you enable the deconz log (like in your second post) you will see something like
Everytime you press a button (for the missing one, but I think only 2 will work) |
|
I've tried this and it's working. I installed Smanars patch and started a search for new switches in Phoscon. I see the switch in Deconz and in the logs: 13:11:05:886 0x00124B0014B71F47 onOff 0 --> 1 |
|
But to make it working I need all button value, I have some problem to guesss them (3 mode / 4 cluster/ 3 endpoint .....), and it's easier with debug. |
|
@bphermansson can you did it ? you have this device too ? |
|
I can make explanation if you need @NicolasBoulanger ? |
|
I have the Osram remote that is black in rubber. It has three button, large and small arrow and a circle. The output I get from Deconz is noisy and I only see one of the buttons, the small arrow. It gives this on a short press: |
|
I think I have values from zigbee2mqtt @NicolasBoulanger give a link for that #2763 (comment) But it's realy faster using debug ^^. I will try better tommorow But I don't understand why you have only the small arrow and not the big, I can understand for the "O" but the arrow ...
Cluster metring ? I will try to make better using this mapping |
|
And I m stupid. Better to check working values before the no working one ^^. Pls can you check in the json (or somewhere else) the "buttonevent" value, if the value is "none" I m totaly wrong, if you have something like X00Y I have at least 1 good value in my table. |
|
So I have used this message So now I m using 1 endpoint by button, but always cluster 0006 and command 0x0A. |
|
is good for you with these logs ? 11:55:47:312 no button map for: SML001 ep: 0x02 cl: 0x0406 cmd: 0x0A pl[0]: 000 |
|
Bas luck, RWL021 is a philips dimmer and SML001 is a HUE motion sensor ^^. And now I m looking better, I have based my table on
But It's not the good device too 0x00124B0014B71F47 is not in the good MAC range adress. The log I need will contain "no button handler for: Lightify Switch mini" (not sure for typo). |
|
No-one can compile the code and give me some logs ? |
|
Maybe later tonight I can give it a try. |
|
Some new findings. Now I see my switch as 0x75B7 in Deconz. It's a Osram Lightify Switch Mini. Pushing the circle gives: 07:57:23:092 APS-DATA.indication srcAddr: 0x75b7, srcEp: 0x03 dstAddrMode: 2, profile: 0x0104, cluster: 0x0008, lqi: 167, rssi: -70 (and my Hue lamp switches on) Pushing the large arrow: 08:01:20:906 APS-DATA.indication srcAddr: 0x75b7, srcEp: 0x01 dstAddrMode: 2, profile: 0x0104, cluster: 0x0006, lqi: 151, rssi: -72 The small arrow: |
Did you try long press on both buttons? |
|
Hello, what is the MAC adress of your osram remote ? Because perhaps the line
is for the device 0x00124B0014B71F47 PSMP5 And this one is already on the table https://github.com/Smanar/deconz-rest-plugin/blob/master/sensor.cpp#L146 Can you share the complete log ? |
|
|
|
But phoscon is closed source. |
|
Sorry, I didn't mean to say The button reports battery level on cluster As you have said before, I think reporting on
I've also seen these:
Update: I wonder if the read problems are because we don't push the sensor fingerprint in These are the logs: One last thing.. The middle button event seems to take longer to appear/update on the API than the other two buttons. Do you know why that might be? I disabled the 'suprise' button mapping to test but it didn't make it any quicker. |
|
No you are right, and I have checked on other project it s 0x20 for sure. We don't make
But we make
so at final it's same. For me the problem can come from you can try other values, on z2m they are using 300, 3600, 0. (reportableChange8bit = 0xFF for disabled) 2 - Or just the device don' use reporting but the pooling cluster, I have exactly same problem for legrand switch, it's the code you are using ^^ But this code work for legrand because this device make a device announce every time you press the button, not sure osram do same. With this code it's possible the value will be updated only 1 time. For the middle button, have you take a look on log in same time, to see wich one action is delayed ? Its perhaps normal and coming from the hardware ? |
|
Right, I messed around with the reporting attributes and can't explain why changing intervals sorted it, but I configured Maybe making the min interval shorter means we get a report before the device goes in to deep sleep? I'm not convinced it is fixed so I'm going to test again to ensure it wasn't accidental etc. What do you think is in this payload? Update: Related links: |
|
Ha, you have cleaned the code ? |
|
I've started a pull request... I had to create a new fork because the master branch was a mess and GitHub still don't allow multiple forks... my old forked-repo is still there as a mirror though. I'm currently testing that pull request so should be done soon. I can create another PR if there are bugs found but I don't think there are. Let me know if there is anything wrong etc. and I'll fix it 👍 Ideally I would have the double press working too but its probably not going to be easy so I think its better if this is added later too. |
|
Yep, it s better ^^, because so much tries. I think it will be ok for the 3 buttons remote. And I think it can be usefull to bind only the usefull cluster for exemple only the 0008 and 0006 or only the 0300. Because without that it can make 3 * 6 = 18 binds. But you are right, even not perfect, the PR will be usefull, at least for some returns. |
|
I had a look at the binds for the 4 button and one of them is on the comissioning cluster
Yes, I think it would be better. zigbee2mqtt has this: Koenkk/zigbee-herdsman-converters@7756df8#diff-6c9a6acf22f90d1c6e524d9f3c5c1745R1347-R1353 Not sure how you do this though. Also, the battery updates are working 👍 |
|
IDK, perhaps they are not usefull, and I don't find the device on other project. And you are right, hard to that with the actual code, If I have time tommorow, I will try to make something without too much ugly hacks. Happy for battery, because I haven't more idea for it :) |
|
I'm considering making the battery updates every |
|
I m agree with you, make it every hour is useless. If you make code change on the branch you have make the PR, the modification will be used too on this github. But I realy don't think it's something usefull, there is no devices that use that, because you just need some time to have the value, the device make lot of requests during inclusion, better to remove the useless one. |
|
BTW, I have started something. Not sure it will be usefull, so it's just a prototype Smanar@8986adf Not compiled/ Not tested, so don't spend too much time on it. But with this code, you can choose the endpoint, the group and the cluster like in Z2M, and it s compatible with old code. The return will be "false" so I think you will have an error message but the binding will work. |
|
I have tested your prototype code and its working. There were a few compile issues and I updated it a bit too so check out my latest commit for the changes. olicooper/deconz-rest-plugin-old@c525343 The first cluster binding task starts at This is the first binding task: Still no broadcasting with this new code and all bindings are still present so this solution will work 👍
|
|
I have already do an update since, but the last is not tested ^^. But on bad branch, will correct tommorow And In my mind, I prefer remove the "return ret" on line 2576 (and all the code before. Like this the code can be compatible for old and new binding mode. If you are using the new one srcEndpoints.size() will be = 0, so so all the "if loop" will be skipped and the code will continue normally at line 2768. But like you idk if theses changes can be used in your PR, for me it's usefull for some other device, we realy miss a simple bind fonction. And I have set only the last bind able to change the ret value, it will work like before the modification, and I m not sure it will be usefull to check all command, it s just a binding list, if 1 succed, all other will do same. |
Yes that's a good point, I will use your code for the next version. The reason I copied the code was to be 100% sure it wasn't going to execute anything else for the test. I knew it probably wouldn't though 😊
I think we need to ask the main developers about it maybe? I would probably submit another PR with this added function, then update the code later on to use this so that it is all kept clean and separate. Maybe this won't work for the development of that other device you are working on though? It would be nice to speak directly with the main devs though, maybe they will add it straight in without a PR? Happy to test it soon. Good work! |
|
Don't worry for that, my modification don't impact the rest of the deconz code. In the worst sistuation it's your device that will not work, no impact for others devices. And the code just take 10/20 lines. And PR take somes days to be validated, so hard to wait beetween 2 of them, it's for that you can see some PR used for 5/6devices or more. |
|
Hi Smanar, I noticed one small issue when I bound a light to the button in the old UI, the center (0) button sets the color back to default but it doesn't make the light go to 100% like it should. I've added some new code to bind one of the missing button handlers and it works again but could you double check that this implementation is okay? olicooper/deconz-rest-plugin-old@7d2c24b |
|
Lol, don't worry, I trust you, you know the code for this device as good than me, and you have the device to make test and not me. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Thanks for your hard work ! 🎉 |
|
Hello, I have switched from the not-anymore-supported Osram Lightify gateway to Phoscon on Raspberry Pi 2 with RaspBee II from Dresden-Elektronik. As I was able to pair the grey and blue Osram SMART+ Switch Mini (AC0251 600NJ | x 1718 and AC0251 700NJ | x 1718), I thought I could put them to use as well. They appear (besides a normal-sized Osram SMART+ Switch) in Phoscon under switches. However, when I try to connect them in a group, they are not offered, i.e. do not appear in that selection screen at all; only the normal-sized switch is there. So it seems that Phoscon adds them as switches but cannot use them in groups to apply them to certain lights/plugs etc. for whatever reason. Now do these mini switches work for you in Phoscon? How can you apply them to existing groups? I have no experience yet with deconz and logs etc., so I do not yet know how I can provide some logs, but I am willing to learn. :) Thanks for your kind help and hints! |
|
Hi, I don't think phoscon support thoses switches, for me the better is using third application. |
|
What is so different with the mini switch in comparison to the normal-sized switch? If logs or sniffed traffic of the mini switch helps, I could try to provide such, but would need a little help how to accomplish this. I think that I have everything that is needed, except the knowledge how to start. ;) |
|
The problem is the API have nothing to see with phoscon. If your device is the 3 button device, this one use native zigbee command, so you can use group feature in the "old web app", it will be direct connexion, without using deconz/phoscon/API. But I don't remember what will be the 3 used command with this remote (and you will be not able to change them) |
|
Thank you so much, I will look there. It is indeed the 3 buttons switch (available in different rubber colours). And I just now realise that my comments might be off-topic here, sorry. |
Hello,
i bought 2 zigbee osram mini switch, i made a pull request to make it working on zigbee2mqtt, but now i use conbee :)
i have 1 blue and 1 white
i like these remotes for my roller shutter
https://www.amazon.fr/dp/B074PYT9R4/ref=twister_B07MVNX6V6?_encoding=UTF8&psc=1
the device is detected in deconz but can only switch on and off all lights
here screenshot of the 2 remote (maybe different)
if you need more informations tell me :)
thanks !
Blue:
White:
The text was updated successfully, but these errors were encountered: