Support for Luzense devices #1509
Comments
|
Check this page? https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support But do they support even Zigbee? Did not find any info on this |
|
Yes they are ZigBee, the only info I have is here: https://www.unilamp.no/produkt/zig-b-veggbrytere/ These remotes are meant to be used with some "acutators" to dim traditional lights and make them smart. The great thing about them is that they fit directly into the 55mm frames from Elko in Norway. I am trying to chase the importer to find out who they buy their products from and see if they have more detailed product documentation. This is bought from a sub supplier (whitelabled) and rebranded for the Nordic market. I will see if I can get more information and share when I get it. |
|
Here is another one of the same source, but with another brand name. |
|
I think this might be the source: https://sunricher.en.alibaba.com/product/60812056361-0/Sunricher_wireless_Zigbee_3_0_single_color_keypad_smart_switch.html |
|
The only information I got from the producer is this. I could send them another question to get more information if you could help me formulate something. I think this is not detailed enough. They only state that they are "ZigBee certified" but still we are not able to join the switch to the gateway. |
|
They look like the iCasa switches: https://www.amazon.de/iCasa-Pulse-8S-ZigBee-Keypad/dp/B07L2SLY29 Looks like these are branded version of Sunricher OEM products. http://www.sunricher.com/zigbee-series/zigbee-remotes.html @ebaauw added supported for iCasa switches in 2.05.58. https://github.com/dresden-elektronik/deconz-rest-plugin/releases/tag/V2_05_58 |
|
Can you please provide some screenshots of the Basic cluster with the model identifier as described in: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support Perhaps due the branding these are different from the iCasa model identifiers and need to be added. |
But with different labels on the buttons, suggesting different commands (level control and multiple on/off instead of scene recall). |
|
@ebaauw could you share the pairing steps for the iCasa switch? Following the documentation on the luzense does not work. It never pairs. If it is fact the same hardware perhaps I could reset it and pair the same way. |
|
I didn’t have to do anything special, see #1124. I would try the usual remedies against the pairing-battery-powered-devices blues:
If the device has different firmware with a different Model Identifier, it needs to be whitelisted, before the REST resources will be created. Please provide the info from: https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Request-Device-Support. |
|
Loking at the manual, you need to follow steps 6 (Factory Reset Manually) and 3 (Zigbee Network Pairing through Coordinator or Hub). While looking similar, they seem to have different firmware from the iCasa Pulse keypads, with a slighly different reset and pairing sequence (see manuals at http://www.icasa.io/downloads/). Also the iCasa have additional output clusters, not mentioned in the Luzense manual: Groups, Scenes, ZLL Commissioning. To be seen if that's an omission in the manual or really the case, though. The battery power monitor function (under 15) looks interesting. I haven't seen anything like this on the iCasa Pulse switches, and had to resort to polling the battery power. The Pulse 8S seems to report battery when pressing S1 and S2 simultaneously, but the Pulse 4S doesn't. The Pulse 2 only has On and Off buttons... |
|
Bloody hell, all three seem to report battery slightly under every 4 hours. I totally missed that when integrating these. |
|
|
|
|
|
I think I got them working kindof. The first one is a four button, the last one is a 8 button. The GUI in phoscon does not recoginize that the device is joined, but I find them on the VNC.
|
|
Node info 8 button device: Node info 4 button device: |
|
Can you please double-check the Model Identifier in the Basic cluster of each of the switches? I hope they use a different value of each type, or it will be very hard to distinguish them. Can you also please manually read all the attributes (double click an attribute for the popup window, press a key on the switch, and press Read in the popup window)? I'm particularly interested in the SW Build ID. The 8-button switch is exactly what I expected: four switch endpoints, one for each row. I suspect the switch sends Level Control commands when holding the buttons, and On/Off commands when pressing/releasing them, just like the iCasa Pulse switches. We need to double-check which commands, to expose the right The 4-button switch is a bit puzzling. I suspect it doesn't send anything different for pressing vs holding the On and Off buttons. I wonder if it does something on press of the Dim Down and Dim Up buttons. Can you run deCONZ with The |
|
Correct identifier for 8 button switch, seems I did it wrong first time :)
|
It appears these keypads report battery percentage periodically after all, slightly under every four hours. see #1509 (comment) and #1124.
|
Not sure I 100% understand what you ask me to do with regards to reading but I have now double clicked all the lines from the screenshot above and clicked read to get more info. Then I get the following:
Also I changed the options to be like this (running on hassio / home assistant): I tried setting the debug_aps to 2 but then I get an error. So I changed it to 1 for now. Hope that gives you what you need. I tried pushing all 4 buttons (this is the 4 button one) and get the following output. Is this what you are looking for? |
|
Hello again, is there someone I could send these switches to for inclusion? Right now I just have them lying in a box and I think they could be very useful and affordable. I think these switches are the same as this: I could send them to whomever wants to try and include them in Deconz :D |
I'm afraid that's hassio not supporting a value of 2 here.
Unfortunately, no. We need the payload of the message (the
I'll be happy to have a look at them. |
|
Great @ebaauw. Send me an email on stian at barmen dot nu and we can arrange the details. :) |
|
Would be really nice if these switches will be included/ supported. I ordered them including the raspbee with the assumption due to the compatibility with Philips Hue (according to some other fora) they would work out of the box. Thanks for all the work so far... If I can deliver some debugging output let me know, I will be more than happy to share and get these switches to work. |
|
I received the switches by mail today, thanks @corvy. Indeed, they're very similar to the iCasa pulse switches (the 8-button switch even has the same firmware image). They did flip the position of the On and Off buttons, though, so I had to create new button maps. The eight-button switch is straightforward: four On and four Off buttons, each pair controlling a separate group. The buttons support press/release, hold, and release after hold, sending the usual On, Off, Move up (with on/off), Move down (with on/off), and Stop (with on/off) commands. So that leads to {
"config": {
"battery": 100,
"group": "11009",
"on": true,
"reachable": true
},
"ep": 1,
"etag": "4f739c696f64633242a08209e44daf83",
"manufacturername": "Sunricher",
"mode": 1,
"modelid": "ZG2833K8_EU05",
"name": "ZG2833K8_EU05 11",
"state": {
"buttonevent": 1002,
"lastupdated": "2019-09-11T20:07:55"
},
"swversion": "2.2.3_r11",
"type": "ZHASwitch",
"uniqueid": "00:0d:6f:00:0f:95:0e:e0-01-1000"
}{
"config": {
"battery": 100,
"group": "11010",
"on": true,
"reachable": true
},
"ep": 2,
"etag": "4f739c696f64633242a08209e44daf83",
"manufacturername": "Sunricher",
"mode": 1,
"modelid": "ZG2833K8_EU05",
"name": "ZG2833K8_EU05 12",
"state": {
"buttonevent": 3002,
"lastupdated": "2019-09-11T19:48:59"
},
"swversion": "2.2.3_r11",
"type": "ZHASwitch",
"uniqueid": "00:0d:6f:00:0f:95:0e:e0-02-1000"
}{
"config": {
"battery": 100,
"group": "11011",
"on": true,
"reachable": true
},
"ep": 3,
"etag": "4f739c696f64633242a08209e44daf83",
"manufacturername": "Sunricher",
"mode": 1,
"modelid": "ZG2833K8_EU05",
"name": "ZG2833K8_EU05 13",
"state": {
"buttonevent": 5002,
"lastupdated": "2019-09-11T19:49:00"
},
"swversion": "2.2.3_r11",
"type": "ZHASwitch",
"uniqueid": "00:0d:6f:00:0f:95:0e:e0-03-1000"
}{
"config": {
"battery": 100,
"group": "11012",
"on": true,
"reachable": true
},
"ep": 4,
"etag": "4f739c696f64633242a08209e44daf83",
"manufacturername": "Sunricher",
"mode": 1,
"modelid": "ZG2833K8_EU05",
"name": "ZG2833K8_EU05 14",
"state": {
"buttonevent": 7002,
"lastupdated": "2019-09-11T19:49:00"
},
"swversion": "2.2.3_r11",
"type": "ZHASwitch",
"uniqueid": "00:0d:6f:00:0f:95:0e:e0-04-1000"
}The four-button CCT switch is somewhat a-typical. The On and Off buttons only support press/release (On and Off commands). The Dim button only supports hold and release after hold (alternating between Move up (with on/off), Stop (with on/off) and Move down (with on/off), Stop (with on/off). The C/W button supports press/release, hold, and release after hold. On press/release, it sends Move to color temparature, cycling through five different {
"config": {
"battery": null,
"group": "22529",
"on": true,
"reachable": true
},
"ep": 1,
"etag": "9993867cdcae5b3c73c05f4bcaaa07c0",
"manufacturername": "Sunricher",
"mode": 1,
"modelid": "ZGRC-KEY-002",
"name": "ZGRC-KEY-002 10",
"state": {
"buttonevent": 1002,
"lastupdated": "2019-09-11T20:08:30"
},
"swversion": "2.2.3_r11",
"type": "ZHASwitch",
"uniqueid": "00:0d:6f:00:0f:95:0e:9c-01-1000"
}@manup there's some unholy |
|
I found a way with the single switch. It works fine now controlling 4 lights. I could configure the group in the wireless light control interface but the 8 button one only shows in VNC and not in the wireless light control. Can I edit the config.group directly somehow? Do you have a step-by-step way to do it in REST API? I have a REST API plugin but I am seriously on deep water there... Here is the one-zone one (4 button) working fine: |
Did the REST API plugin create the (four) resources for it (one for each button pair/endpoint)? It should also have created four groups (one for each resource). That might actually confuse the old web app - not sure.
I don't think you can. It's updated when the REST API plugin sees a group command from the corresponding endpoint. To change the group, use the GUI to create a binding to a different group in the GUI. |
|
Thanks for responding @ebaauw No only the 4 button one created one group. The 8 button (four groups) did not show up in the APWeb interface. In VNC I can see all four just fine like this:
In the Web API I get these groups. The bottom left one is the 4-button one, just renamed it. The 4 zone, 8 button one, does not show up. I have also connected over REST API with a REST client. Did a GET towards http://localhost:40850/api//groups and got this response: Is there any way I could debug this further? |
|
Looks like the REST API plugin didn’t create anything for the 8-button switch. Could you open the network from the old web app (settings tab) and then in the GUI read the Basic cluster of the switch? The label in the node should change as the REST resources are created. |
|
Yes I can try this tonight. I am not at home right now and I need to push the buttons to wake the switch up. But just to be clear on what you want me to do.
Potentially I would need to repeat for each of the four switches I guess? |
|
Yes and no, you should not have to repeat for each endpoint. If you have multiple switches, you might have to do that for each switch. Tip: set the Duration on the web app to 10 min, so you have some more time to wake the switch(es) and read the Basic cluster(s). |
|
It worked :) I had to repeat the "read" for each switch a few times before I got them all into groups. But in the end it worked! |
|
Another quick question for you @ebaauw. The 4 button one have no way to dim up-down for the lights assosciated. It will only turn on-off. But when I listen to deconz_events I can see when I hold in the on or off button it will fire a new event every half-a-second with a new ID. The events look like this:
Here I held the first button (top left) for about 2-3 seconds. You can see the ID changes underways, and also the event changes from 1002 to the occational 1003 (to indicate that it is being held?). Is it any way to make it so that when you hold the button the lights actually gets brighter and brither or dimmer and dimmer? |
|
Looks like the binding from the client Level Control cluster to the group hasn’t been setup. For each of the four endpoints, it should be to the same group as the client OnOff cluster. Are you on deCONZ v2.05.70? I think that version has serious issues with pairing devices. I haven’t tried .71 yet. |
|
Yes I am on .70. I will update and try again. 👍 |
|
Updated to .71 one but still it does not dim up and down. How should I attack this? Do I need to remove the remote and add it again? |
|
Should be enough just to reset the switch/dimmer and re-pair it. |
|
Thanks again @ebaauw. I have tried reset and pairing twice but still the dimming does not work. I get the groups, can pair the lamps and everything but long-press does not work. I only see it in deconz_event log. I have also tried in VNC to read the cluster-info. If you have any ideas I would be happy to try them out :) |
|
The switch sends a Move (with on/off) command, when holding the button. That part works, because deCONZ sees this as it creates the button events. What type of lights did you add to the group? Do they accept the Move (with on/off) command? Could you check in the deCONZ GUI, in the Cluster Info panel of the Level Control cluster of one of those lights, that they actually react to this command? Note that the REST API creates a x002 button event when pressing/releasing the button; a x001 when holding the button, and a x003 when releasing the button after holding it. I double-checked .71 with my iCasa switches. Still had pairing issues with one of them (the other two worked fine), in that deCONZ wouldn't read the Simple Descriptor(s) while the network was open (so the right drop-down circle for the endpoints/clusters wouldn't appear). After fixing that (and for the other two) the groups and bindings were created alright. Of course these switches only have one endpoint. Did you force the switch awake during the entire pairing process by repeatedly pressing one of its buttons? If the lights react to the Move (with on/off) command, most likely the switch doesn't send the command to the corresponding group, but to group 0x0000 instead. In that case, the binding from the client Level Control cluster (on the switch) to the group hasn't been setup. Kinda weird, as the binding from the client OnOff cluster has been setup correctly (or the lights in the group wouldn't react to the press/release). You can set up the binding manually in the Bind Dropbox panel in the GUI. |
|
Thanks again for your time and effort @ebaauw :) I have GU10 Philips Hue second generation for two button pairs and two IKEA lamps, E27 for the two others. All of which dimmed fine with the 4 button switch. I tried to check the Level Control on one of the buttons but there is nothing. Is this related?
|
|
Now I found the Bind Dropbox 👯♂ But I cannot understand how I enable the binding. I read somewhere that I could pull the 008 (Level Control) from the switch onto the bind dropbox, but how do I add the group?
|
|
Select the radio button and enter the group ID (in hex) in the field.
Good. The four-button CCT switch sends the same commands for dimming as the eight-button switch.
No, this is a client cluster (grey), which simply has nothing to show. See #2077 (comment) and the Wiki. |
|
Ok just tried this. Took the first part of the switch and dragged the Level Control cluster onto the source, now it looks like this:
What do I pull onto destination? Do I select one lamp in the group? Or how do I find the group ID? |
|
That's looking good, so far. You need to select the Group radio button and enter the group ID. This is listed as So e.g. for my iCasa switch, group 60929 (0xee01) corresponds to endpoint 0x01 ( |
|
Almost there :P
I think this should work. Found the group ID in the API Web interface in the URL and also in the REST client but when I bind I get a timeout. Could that be why it did not work by itself when joining? |
Make sure to press a button to wake the switch. |
|
Got it paired now, stupid to forget to press a button. 😂 But still no dimming. The first group/switch is the top pair on the remote right? |
|
Yes. Not sure why it doesn’t work. Could you double-check that Could try and bind the Level Control cluster endpoint to a different group, and check that |
|
Thanks for the suggestions, let me play a bit with it and get back to you 👌 |
|
I found the solution 💃 I checked the battery level on the remote and found it to be low. I noticed since the remote seemed sluggish. Replaced the battery, re-paired it and now it all just works. Dimming and all! Thanks for the unlimited patience @ebaauw |
|
Hey @PrimaryInc you can close this issue. Solved by Mr @ebaauw 👍 |
|
Hi, after a search i found your issue with many informations but not enough for me :( |
Hi,
I've been testing a 2 luzense switches, but not been able to pair them,
As far as I know thy are not supported in deconz at the moment.
What information can I provide for support?
The text was updated successfully, but these errors were encountered: