Elko ESH 316 Endevender RF - device support request

[Knodd]

This is the battery operated wireless remote for the 316GLED RF requested here: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2497

Phoscon will not find it but it shows up in deCONZ after pairing. I can bind it to a light to turn on/off and dim but cannot bind to groups.

Device

• Product name: Elko ESH 316 Endevender RF
• Manufacturer: ELKO
• Model identifier: ElkoDimmerRemoteZHA
• Device type : Please remove all unrelated device types.
  • Remote
  • Switch

Screenshots

Basic cluster

Node info

[WTell]

I would be happy to help with testing with my ESH 316 remotes. In my experience, binding is hit-or-miss, and some remotes refuse to show up in deCONZ at all.

[SwoopX]

I guess I can give it a look within the next days. It would really help if anybody could compile the plugin then for testing.

[WTell]

@SwoopX I would love to help in any way I can, as long as I get a little bit of guidance on the way!

The product in question here is described by the manufacturer on https://proff.elko.no/316-endevender/category2990.html .

The battery operated remote mentioned above is meant to work in conjunction with an in-wall mounted dimmer that features the same design. The dimmer is called Elko ESH 316GLED dimmer RF, and is described on https://proff.elko.no/smart-316gled/category2968.html .

I have with success been able to add the in-wall dimmers to my ZigBee network, and they show up as Lights in deCONZ and Phoscon. They works reasonably well. They are have model ElkoDimmerZHA, and vendor either Heiman or ELKO depending on what hardware version it is and when it was manufactured. It seems reasonable to add support for the ElkoDimmerZHA along with the ElkoDimmerRemoteZHA that @Knodd mentioned above. Should I add the requested screenshots for the ElkoDimmerZHA in this thread, or should I start a separate thread?

Edit: My mind is a mess, I see that the dimmer was requested on #2497 , but that it was marked as stale. Any chance in reviving it?

[WTell]

@Knodd What is your experience with the ElkoDimmerRemoteZHA in your ZigBee network? My experience is that they sometimes seem to "forget" their bindings, or fall deeply asleep requiring me to jiggle them a bit before they do anything. I also have a few devices that seem to refuse to be part of my network. What devices are you binding them to?

[SwoopX]

Ok, so I guess I got everything ready for a test. Someone who doesn't run HA, but deconz on a bare Raspbian can give it a try. It requires the "deconz-dev" package to be installed. Just in case, I'd recommend to make a backup in Phoscon ;)

Steps should be as follows:

sudo systemctl stop deconz
sudo systemctl stop deconz-gui
git clone --branch elko https://github.com/SwoopX/deconz-rest-plugin.git elko
cd elko
qmake && make -j2
mkdir .local/share/dresden-elektronik/deCONZ/devices/
cp button_maps.json .local/share/dresden-elektronik/deCONZ/devices/
sudo cp /usr/share/deCONZ/plugins/libde_rest_plugin.so /usr/share/deCONZ
sudo cp ../libde_rest_plugin.so /usr/share/deCONZ/plugins

[WTell]

@SwoopX Installing! Will report back.

[WTell]

@SwoopX Compiled seemingly successfully, but I'm stuck just after compilation. I'm sorry to be a newbie in this area – I have little experience with qmake and make tools.

I'm assuming that mkdir .local/share/dresden-elektronik/deCONZ/devices/ should be mkdir ~/.local/share/dresden-elektronik/deCONZ/devices/ (is this correct?).

However, button_maps.json does not exist anywhere in the new elko directory. There only one I can find is at /usr/share/deCONZ/devices/button_maps.json, but this file is dated September 26. Where should I be able to find button_maps.json?

For the second-to-last line, /usr/share/deCONZ/plugins/libde_rest_plugin.so is also still dated September 26, does it make sense to copy this file to /usr/share/deCONZ?

The last line still assumes that I'm in the newly created elko folder, which would mean that it actually executes sudo cp elko/../libde_rest_plugin.so. Does this make sense? I created the elko folder in my home folder, was this wrong on my part?

[SwoopX]

I'm assuming that mkdir .local/share/dresden-elektronik/deCONZ/devices/ should be mkdir ~/.local/share/dresden-elektronik/deCONZ/devices/ (is this correct?).

Yes, indeed

For the second-to-last line, /usr/share/deCONZ/plugins/libde_rest_plugin.so is also still dated September 26, does it make sense to copy this file to /usr/share/deCONZ?

The compiled plugin is from today or yesterday. The intention here is to preserve the originally installed plugin so it can be restored after testing or when needed.

The last line still assumes that I'm in the newly created elko folder, which would mean that it actually executes sudo cp elko/../libde_rest_plugin.so. Does this make sense? I created the elko folder in my home folder, was this wrong on my part?

You should be still in the elko directory, so "../XYZ" is fine as the compiled plugin is one directory up.

[WTell]

I'm assuming that mkdir .local/share/dresden-elektronik/deCONZ/devices/ should be mkdir ~/.local/share/dresden-elektronik/deCONZ/devices/ (is this correct?).

Yes, indeed

Thank you.

For the second-to-last line, /usr/share/deCONZ/plugins/libde_rest_plugin.so is also still dated September 26, does it make sense to copy this file to /usr/share/deCONZ?

The compiled plugin is from today or yesterday. The intention here is to preserve the originally installed plugin so it can be restored after testing or when needed.

I understand. I'll make sure I make a copy.

The last line still assumes that I'm in the newly created elko folder, which would mean that it actually executes sudo cp elko/../libde_rest_plugin.so. Does this make sense? I created the elko folder in my home folder, was this wrong on my part?

You should be still in the elko directory, so "../XYZ" is fine as the compiled plugin is one directory up.

I had so far failed to notice libde_rest_plugin.so appearing a level above elko/. PEBKAC.

cp button_maps.json ~/.local/share/dresden-elektronik/deCONZ/devices/ still makes no sense, though, as there is no new button_maps.json anywhere. In fact, the only place I can find this in my entire file system is at /usr/share/deCONZ/devices/button_maps.json. What am I missing? Am I supposed to issue cp /usr/share/deCONZ/devices/button_maps.json ~/.local/share/dresden-elektronik/deCONZ/devices/?

[SwoopX]

Ah, forgot about the maps, sorry. That won't be necessary as the code still uses the "old" approach

[SwoopX]

Any news?

[WTell]

@SwoopX I'm having trouble paring my devices, but I believe it's a lower level Zigbee issue so I'll give it a bit more time (some of my devices simply don't appear in either Phoscon or the fat GUI).

[SwoopX]

All good, just let me know when there's any news.

[oywino]

Hi @SwoopX Sorry for my late arrival. Was this device eventually added - or not ? Mine shows up in deConz and in Phoscon, but I'm uncertain how to bind it to a light (or even better; a group). I tried to bind it, but it failed. Event though it is visible in Phoscon, it cannot be added to a group. The REST-API post looks like this:

{
    "config": {
        "group": "9",
        "on": true,
        "reachable": true
    },
    "ep": 1,
    "etag": "8f3ff2b123697e66f702c8ce7e2685fa",
    "lastseen": "2021-01-24T19:10Z",
    "manufacturername": "ELKO",
    "mode": 1,
    "modelid": "ElkoDimmerRemoteZHA",
    "name": "ElkoDimmerRemoteZHA 8",
    "state": {
        "buttonevent": null,
        "lastupdated": "none"
    },
    "swversion": "0.0.1",
    "type": "ZHASwitch",
    "uniqueid": "00:0d:6f:00:0c:b0:8b:cc-01-0006"
}

Any help is appreciated

[SwoopX]

You need to do that via the old webapp, there you can directly bind lights to a switch.

If you want to have button events to be emitted, you'd need to get me some certain messages from the deconz debug log.

[Knodd]

I was able to link it with the bind box in deCONZ but not in the old webapp. Mine never showed up in Phoscon, how did you link it @oywino ? I started a search for switch in Phoscon and when I got an error saying "could not connect" or somethin I checked deCONZ and found it. Linking in deCONZ seems to be maximum 3 lights (level control and on-off) and then I get binding table full

[oywino]

Hi @SwoopX and thanks for getting back to me. So, I followed your advice and in the old web app, the Elko switch/Dimmer shows up as a "group" on its own. Binding a light to it by adding it to this "group" worked fine - apparently, but the switch isn't able to control the light.

I'd love to give you info from the deConz log, but i'm afraid I do not know what you mean by "some certain messages" ? Can you be more specific?

[oywino]

@Knodd Are you using the same Elko switch/dimmer as I am? Mine is the one Elko calls "Endevender" (ESH RS16 316GLED). This is the one that runs on two CR2032 batteries (No Mains).

[Knodd]

@oywino yes thats the one. The normal 316 ESH showed up as a light in Phoscon, but the "endevender" does not show up

edit: I deleted the node from deCONZ and reconnected and now it shows up in deCONZ and the old web app but not in Phoscon. I get the same result, I can add lights to the group but nothing happens when I push the switch. I read somewhere this switch does not support group commands, could that be the problem @SwoopX ?

[oywino]

Mine shows up in Phoscon like this:

[oywino]

When I added a light to the switch (using the old Web App), this is what I got in the log (INFO):

22:48:02:777 delay sending request 169 dt 0 ms to 0xCCCCCCFFFEC2E48A, ep: 0x01 cluster: 0x0003 onAir: 1
22:48:02:783 group 10 member 1
22:48:04:624 Add to group response for light 1. Status:0x00, capacity: 254
22:48:06:782 ZCL attribute report 0xCCCCCCFFFEC2E48A for cluster: 0x0008, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
22:48:20:180 ZCL attribute report 0xCCCCCCFFFEC2E48A for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
22:48:20:217 ZCL attribute report 0xCCCCCCFFFEC2E48A for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 
22:48:27:258 Current channel 11
22:48:27:268 Device TTL 5160 s flags: 0x7
22:48:43:743 skip binding for attribute reporting of ep: 0x00 cluster 0x1000 (end-device might sleep)

(As this switch is battery powered, I always click and dim rapidly to try to keep it awake during binding.)

[WTell]

@Knodd @oywino Is this the first time your are adding the the Elko ESH 316 Endevender RF to your network? I've got around twelve of these added, with various degrees of success.

First of all, they are notoriously dependent on having an extremely potent power source – I've found that some CR2032 3V cells are simply not up to the task, even when brand new. Some brand new cells measuring in at 3.15 V is not enough, and I've had to dig around for ones clocking in above this (they are rare!) to get the device to pair successfully to the network. (This was using the GUI to add the device, before the update in #3409 that @SwoopX links to above).

Secondly, the devices are really bad at paying attention and caching up. I've had to try multiple times to get them to bind, and most importantly, I tend to be more successful when I keep the device awake by pressing the "button"-button on the PCB every two seconds while performing the binding and repeatedly up to ten seconds afterwards. Give this a chance and see what you get!

[SwoopX]

You guys should look out for those kind of messages messages coming from your switch:

[INFO] - No button map for: eTRV0100 endpoint: 0x01 cluster: 0x000A command: 0x0A payload[0]: 000

[Knodd]

Like this @SwoopX ? I created at binding to deCONZ Toggle on/off:

Dim up:

Dim down:

[SwoopX]

Yes, exactly. I'd assume those were short presses only. You should also check if there's further possibilities (bouble press, long press). Please take note that especially the long press most likely fires consecutive events, so you should ensure to look for them as well.

[SwoopX]

Meanwhile, based on the information above so far, that would be the additions to button_maps.json, which you can basically do your selfes. The below contains the new map till the end of the file and the map above (you need to be very thorough with the brackets)

        },
        "lidlMap": {
            "vendor": "LIDL Livarno Lux",
            "doc": "LIDL / Livarno Lux Remote Control (_TYZB01_bngwdjsr)",
            "modelids": ["HG06323"],
            "map": [
                [1, "0x01", "ONOFF", "ON", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", "On"],
                [1, "0x01", "ONOFF", "LIDL", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", "On (0)"],
                [1, "0x01", "ONOFF", "LIDL", "1", "S_BUTTON_1", "S_BUTTON_ACTION_DOUBLE_PRESS", "On (1)"],
                [1, "0x01", "ONOFF", "LIDL", "2", "S_BUTTON_1", "S_BUTTON_ACTION_TREBLE_PRESS", "On (2)"],
                [1, "0x01", "ONOFF", "LIDL", "3", "S_BUTTON_1", "S_BUTTON_ACTION_QUADRUPLE_PRESS", "On (3)"],
                [1, "0x01", "LEVEL_CONTROL", "STEP", "0", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "DimUp Press"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE", "0", "S_BUTTON_2", "S_BUTTON_ACTION_HOLD", "DimUp Hold"],
                [1, "0x01", "LEVEL_CONTROL", "STOP", "0", "S_BUTTON_2", "S_BUTTON_ACTION_LONG_RELEASED", "DimUp Release"],
                [1, "0x01", "LEVEL_CONTROL", "STEP", "1", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "DimDown Press"],
                [1, "0x01", "LEVEL_CONTROL", "MOVE", "1", "S_BUTTON_3", "S_BUTTON_ACTION_HOLD", "DimDown Hold"],
                [1, "0x01", "LEVEL_CONTROL", "STOP", "1", "S_BUTTON_3", "S_BUTTON_ACTION_LONG_RELEASED", "DimDown Release"],
                [1, "0x01", "ONOFF", "OFF", "0", "S_BUTTON_4", "S_BUTTON_ACTION_SHORT_RELEASED", "Off"]
            ]

        },
        "elkoMap": {
            "vendor": "ELKO",
            "doc": "Elko ESH 316 Endevender RF",
            "modelids": ["ElkoDimmerRemoteZHA"],
            "map": [
                [1, "0x01", "ONOFF", "TOGGLE", "0", "S_BUTTON_1", "S_BUTTON_ACTION_SHORT_RELEASED", "On"],
                [1, "0x01", "LEVEL_CONTROL", "STEP", "0", "S_BUTTON_2", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim up"],
                [1, "0x01", "LEVEL_CONTROL", "STEP", "1", "S_BUTTON_3", "S_BUTTON_ACTION_SHORT_RELEASED", "Dim down"]
            ]

        }
    }
}

[Knodd]

Thanks @SwoopX The toggle was a short press, this is a rotary dimmer wheel so a long press normally triggers the same action as a short press The dim action is turning the rotary wheel and is fired multiple times during dimming so turning x degrees fires x/(device sesitivity) events

where can we find button_maps.json? I have HA with deCONZ installed in docker on a NUC with Debian an s search for the file in usr/share/hassio where my HA installation is gives no result

[SwoopX]

I'm afraid I can't really help you with that file, since I don't run HA. On a bare Linux, it is to be found in /usr/share/deCONZ/devices

[Knodd]

I found it in the docker containers under /var/lib/docker/overlay2 by searching for folder "deconz"

Toggle works great, and the log shows "[INFO] - Button 1002 On ElkoDimmerRemoteZHA"

Dimming seems to be expecting single button pushes and not continuous dimming with a rotary wheel. I can only get it to dim one step and the next events are ignored

11:02:31:040 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 11:02:31:076 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 11:02:31:155 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 11:02:31:198 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 11:02:31:220 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 11:02:31:256 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 11:02:31:279 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 11:02:31:299 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 11:02:32:199 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 11:02:32:218 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 11:02:32:238 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 11:02:32:377 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 11:02:32:402 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 11:02:32:415 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA

We might need to tweak the dimming, but this switch just got a lot more useful!

[SwoopX]

Seems we're getting there. However, I'd expect to also see some STOP commands or anything alike... If not, than it's gonna be tough.

Please double check if there's literally any further info message from the device.

[Knodd]

I double checked and the are no stop messages. Also there are no attribute reports like when toggling, is that normal?

The dimmer has a potensiometer that clicks every x degrees when turning. Is seems one dim buttonevent is sent for every click.

13:32:31:822 [INFO] - Button 1002 On ElkoDimmerRemoteZHA 13:32:31:932 ZCL attribute report 0x000D6FFFFE4C9350 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 13:32:31:949 ZCL attribute report 0x000D6FFFFE4CBF1C for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 13:32:31:001 ZCL attribute report 0x000D6FFFFE53A920 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 13:32:32:007 ZCL attribute report 0x000D6FFFFE4C91E5 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 13:32:34:867 [INFO] - Button 1002 On ElkoDimmerRemoteZHA 13:32:34:969 ZCL attribute report 0x000D6FFFFE4C9350 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 13:32:34:984 ZCL attribute report 0x000D6FFFFE53A920 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 13:32:35:039 ZCL attribute report 0x000D6FFFFE4C91E5 for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 13:32:35:044 ZCL attribute report 0x000D6FFFFE4CBF1C for cluster: 0x0006, ep: 0x01, frame control: 0x08, mfcode: 0x0000 13:32:37:080 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:112 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:154 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:219 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:273 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:304 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:339 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:363 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:410 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:420 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:451 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:469 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:501 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:516 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:540 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:551 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:562 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:566 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:590 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:603 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:620 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:37:637 [INFO] - Button 2002 Dim up ElkoDimmerRemoteZHA 13:32:38:732 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:38:755 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:38:761 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:38:778 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:38:875 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:38:886 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:38:895 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:38:908 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:38:980 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:39:014 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:39:116 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:39:137 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:39:240 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA 13:32:39:374 [INFO] - Button 3002 Dim down ElkoDimmerRemoteZHA

[SwoopX]

Also there are no attribute reports like when toggling, is that normal?

That depends on the reacting devices if they support reporting on the level control cluster as well or need to be polled. I'm not too familiar with lights, since I barely have any, but I'd expect to seem some reports.

It would now be interesting to see which command is send unicast and which broadcast. On the broadcast, there should be additional messages, so I'd assume it is unicast. That would in turn also mean the lights don't get dimmed?

Anyway, I planned to polish the debug output a bit to get some additional information. Maybe there's also something hidden for the Dim commands we currently don't see in the debug output (and potentially useful).

[Knodd]

Let me know what I can do to help with debugging!

I've tested a bit and the lights don't seem to change brightness when dimming so maybe we need a different button mapping?

[oywino]

@Knodd - you seem far ahead of me now. Did you have to change to new batteries to get it kicking - like @WTell suggested ? Mine is visible in both Phoscon as well as deConz, but a GET at the REST-API reveals absolutely nothing whether I turn or click. It just says "buttonevent": null Could you give me som guidance to get going?

[Knodd]

@oywino I didn't change the batteries and I can still not see it in Phoscon. What I did was use the deCONZ GUI and create a binding between both cluster 6 and 8 and the deCONZ node with the switch as source and deCONZ as destination. That makes the switch send the button events to deCONZ.

If you have not used the binding box in deCONZ before this is how to do it: Click "open web gui" and choose "deCONZ"

Under Panels menu, check "Bind Dropbox"

Click and drag cluster "0006 on/off" of the dimmer remote to source Click and drag from the top of the configurator (I renamed it deCONZ) to destination

Important: Before you press "Bind", press the "push button" on the elko dimmer (the little white one under the rotary wheel), this wakes the button so it's not in sleep mode.

Now press "bind" and make sure it says "success", if not then try again.

Then you need to Click and drag cluster "0008 Level control" to source and press bind again.

After this the button events for toggle and dim will be sent to deCONZ

[oywino]

Hi, binding it to Conbee II (deconz) persistantly resulted in failure: timout I deleted and repaired the dimmer several times but to no avail. I also replaced the batteries. However, binding it an IKEA Leptiter light was immediately successful and I could use it to control the light easily. But of course, that binding was the same as "TouchLink" The signals passes directly between the dimmer and the light, bypassing the coordinator (Conbee II). Looking at your dialog with @SwoopX, I get the impression that a modification of the button_maps.json was done (?) Did you have to do that to get it to work?

[Knodd]

Did you wake the switch before binding?

Touchlink is how I've been using it so far, but the binding table is very small (6 spots) so you can only control 3 lights with on/off and dimming. I have several up/down wall lamps with IKEA bulbs so that's 1,5 lamp for 1 dimmer :-)

After binding to deconz i got this in the log:

After editing button_maps, on/off worked for the group created in "old web app" but dimming is not working

[oywino]

Did you edit the button map before or after binding it to the coordinator (Conbee II) ?

[Knodd]

After, but I don't think it matters

[oywino]

Can you see what firmware version your dimmer has ?

[WTell]

Touchlink is how I've been using it so far, but the binding table is very small (6 spots) so you can only control 3 lights with on/off and dimming.

Do you know how to clear the binding table? I have one remote that I can't seem to be able to add, and I believe that it might be because the binding table is full – but it doesn't seem to be bound to anything but one lamp.

[Knodd]

software 0.0.14, I got a file to update from Elko so it should be the latest. I never found out how to clear the binding table when I didn't know what binding to unbind so I used "delete node" in the deconz gui and then repaired it

[oywino]

After playing around with it and attempting several binds, I eventually got an error message binding table: full Then I just removed the batteries and held the little switch for 10 seconds and re-inserted the batteries again and I could continue to experiment with binding. So my impression is that this did empty the table - but I'm not sure. I haven't had that error message again.

[Knodd]

Great tip. Did you not have to pair it again? I've been googling for hours how to factory restore this thing before I found out I could delete it and pair again

[oywino]

Could you post the update file? My SW version is 0.0.1

[Knodd]

Here it is, you have to extract the .bin file to a micro SD card. MAKE SURE THE CARD IS FORMATTED TO FAT32 and not FAT, or the switch dies... ELKDF001.zip edit: just in case anybody finds this later. This is for the battery switch only, not the mains connected ESH 316

[oywino]

No, I did not have to pair it again. The touchlink connection works directly without the need for coordinator assistance. It actually never disappeared from deConz at all. This is typical for all ZigBee devices I have ever used. Even if I leave them unused for month at a time, they are online as soon as they get power (batteries or mains). Never needed to re-pair anything. Thanks for the file 👍

[oywino]

According to Elko docs, there are two different update files; One for the "Endevender SW" and the other is for the "ZigBee radio FW" The update procedure is somewhat different. Do you now which one you sent me?

[Knodd]

this is the "Endevender SW"

[Knodd]

Just remembered I also updated the zigbee FW a few months ago. Found it here, on the bottom of the page: https://www.elko.se/support/programvara/