New device support request: Bitron remote control 902010/23

[nikolauzi11]

Hi, I would like to ask to support the Bitron remote control 902010/23.

Thanks!

[SwoopX]

Hm, it feels like something is missing there. Can you try to re-pair while pushing the buttons randomly?

[nikolauzi11]

Something seems to be wrong with my device. I tried to re-pair, but now the endpoint menu button is gone. I think, I'll send it back and get back to you as soon as I have a new one.

[ebaauw]

deCONZ hasn't read the Node Descriptor and/or Simple Descriptor. Use the other menu button to read them. Make sure to wake the remote during read.

[nikolauzi11]

It reads reads the node descriptor and the power descriptor, but I don't get the second menu button.
Sorry, I'm just getting started on deconz.

[SwoopX]

You might wanna give that procedure a try: #2052 (comment)

In your case (for bullet 1), reset the remote accordingly.

[nikolauzi11]

I got it paired up again after I reset it. But the same attributes are always read as in my first post.
Unfortunately SwoopX's method did not work either. It did not bind after inserting battery, only after pressing button 2 for 10s as usual.

[SwoopX]

Can you try pushing a button and immediately reading the simple descriptors in deconz GUI? It's under the 1st menu button you previously mentioned.

[nikolauzi11]

Sorry for the late answer, I have reinstalled my environment in an lxc container with gui, so it is no longer necessary to plug the conbee stick back and forth
I tried that, but the attributes look the same as before.
How exactly can I see that the simple descriptors were read successfully?

[SwoopX]

I guess sniffing the zigbee traffic would give the required answers...

[nikolauzi11]

I'm afraid I'm not up to it.
I'd like to donate the remote to one of the developers.

[ebaauw]

I'd like to donate the remote to one of the developers.

I'll be happy to take a look at the remote, but it seems simple enough to support without sniffing.

I tried that, but the attributes look the same as before.

This looks to be a standard wireless controller, that sends On/Off and Level Control commands directly to (a group of) light(s). It uses a ZHA endpoint, so it probably won't select a group on factory reset. You want to bind the client On/Off and Level Control clusters to a group. Then add a light to that group, and the remote should control the light. You might also want to bind the server Power Configuration cluster to the coordinator, and setup attribute reporting for Battery Percentage Remaining. Double check that it's reported in 0.5%.

If you whitelist the remote, the deCONZ REST API plugin should log the commands the remote sends to the group on the various button actions. This should be enough to create a buttonMap. Setting up the group and client cluster bindings has been done for many other switches and remotes (e.g. the IKEA Trådfri On/Off switch).

[nikolauzi11]

I'll be happy to take a look at the remote, but it seems simple enough to support without sniffing.

I would be happy to support the project, so I would like to send you the remote control.
How can I get the address, because there are no PMs on Github

[ebaauw]

Please send me an email, or DM me on the homebridge Slack, https://homebridge-slackin.glitch.me/.

Note that I'm not associated with dresden elektronik, so I can only support the remote in the REST API plugin (and, of course, in homebridge-hue). Phoscon isn't open source, so only dresden can add support in the web app.

[ebaauw]

Received the device, thanks @nikolauzi11.

From the figure on the Quick Start Guide, you need to hold button 2 to reset the device. It took a good 10 seconds of holding, but after that it immediately paired with deCONZ. I bound the On/Off and Level Control clusters to a group and indeed, can control the lights in the group.

The switch sends the following on pressing a button.

button	command	direction	size	transitiontime
1	Step (with On/Off)	Up	10	0xFFFF
2	On
3	Off
4	Step (with On/Off)	Down	10	0xFFFF

No double press, release, hold, or anything fancy. Will be supported by buttonevent values 1002, 2002, 3002, and 4002.

It doesn't report battery status nor voltage, despite the Power Configuration cluster. It does seem to report the battery level through the Power descriptor, though. deCONZ shows the battery at 2/3rd, but Wireshark doesn't seem to like the value. I would need to check the ZigBee documentation for the exact meaning of the field. Also, the CR2032 battery is disposable, not rechargeable.

IEEE 802.15.4 Data, Dst: 0x0000, Src: 0xc301
ZigBee Network Layer Data, Dst: 0x0000, Src: 0xf893
ZigBee Application Support Layer Data, Dst Endpt: 0, Src Endpt: 0
ZigBee Device Profile, Power Descriptor Response, Nwk Addr: 0xf893, Status: Success
    Sequence Number: 239
    Status: Success (0)
    Nwk Addr of Interest: 0xf893
    Power Descriptor: 0x8221
        .... .... .... 0001 = Mode: Receiver Periodically On (1)
        .... .... ...0 .... = Available AC Power: False
        .... .... ..1. .... = Available Rechargeable Battery: True
        .... .... .0.. .... = Available Disposeable Battery: False
        .... ...0 .... .... = Using AC Power: False
        .... ..1. .... .... = Using Rechargeable Battery: True
        .... .0.. .... .... = Using Disposeable Battery: False
        1000 .... .... .... = Level: Unknown (8)

[ebaauw]

Ah, it does support attribute reporting on the battery Alarm Mask. That should be enough to support state.lowbattery.