Namron 4512719 no longer able to Add

On 2.28.0
This used to work.
Trying to add a 2ch/4button Namron switch (a few years old).


Tried to wake up switch several times. Blue dot on icon blinks when pressing keys.

Also note Switch 39, it is a 4ch/8 button Namron 4512703, has a DDF, but not marked as a DDF in the icon.?
image

Any tricks I could try?

Hi, this is a deconz issue, not phoscon

Please open a bug report on GitHub.

Hello, and for information, you are not using a DDF, and the one on your picture have a “draft” status, it’s an auto generated one, this device probably don’t have one.

Edit:
After a check both device already have a DDF, there is something bad somewhere

You need to have this one deconz-rest-plugin/devices/sunricher/4button_switch.json at master · dresden-elektronik/deconz-rest-plugin · GitHub and not the one with a “Draft” Status.

Sorry, could you move it please?

I can not. GitHub is another platform

Changed labels.
Will make a github issue.

1 Like

Can it be that the 4512719 has a double space in the manufacturer name and the 4512703 is not yet covered by any DDF?

Will take some weeks. No longer at that site, and no 4512719 where I’m currently at.
Take it the GitHub gatekeeper will be asking for logs, so …

Follow up.
Turns out the Sunricher vendor 's Namron manufacturer have released, for the similar HW device 4512719 two Firmware with different manufacturer names.

Firmware 2.5.3_r21 presents manufacturername = "NAMRON AS" (note one space between N & A)
Firmware 2.5.3_r20 presents manufacturername = "NAMRON  AS" (note two spaces between N & A)

In the /usr/share/deConz/devices/sunricher/4button_switch.json DDF, only the first manufacturer with the one space is defined.

This was spotted early by Swoop, but apparently the work flow for DDFs is DIY based, so in order to fix it one must clone the repo, learn and edit the DDF content and then fork and create a Pull Request. So for first timers this takes a while.
Remember the definition of an expert; One that has done every conceivable mistake within a very narrow field of expertise. :slight_smile:

Anyway, PR is out there now, and for those who encounter this before it is merged, have a look at: