NodOn SIN-2-2-01 repeater

[shilga]

Hello,

I am using the NodOn SIN-2-2-01 which uses the EEP D2-01-12. The module has an option of acting as a repeater which I would like to activate. I know this is a non-standard addition to the EEP. But I need to send this message only one time. I sadly have no real idea there to start to achieve this with enoceanmqtt. Any idea?

How can I use a different profile description for just this one device? If I change my EEP config XML it's used for all d2-01-12 devices.

In Openhab there was an option for it: https://github.com/fruggy83/openocean/blob/master/src/main/java/org/openhab/binding/enocean/internal/eep/D2_01/D2_01_12_NodON.java

There is also some documentation: https://www.enocean-alliance.org/wp-content/uploads/2017/10/NodOn-SIN-2-2-0x-UserGuide-170731-EN-interactive.pdf

[ChristopheHD]

Hello,
I think the best way to implement it is to create a model configuration called nodon/repeater which will be able to be used by all Nodon devices which supports this function.
My worry is that this function is using a specific type of telegram (MSC) which I don't know if they are supported by the current enocean library.

[ChristopheHD]

Furthermore, these MSC are not documented, so I don't know if we can retrieve the actual repeater value.

[shilga]

It looks like OpenEnoceon also just supported setting this value. I will look into MSC messges. And maybe I will write Nodon if they can provide some documentation about it.

[ChristopheHD]

I tried this mapping:

nodon:
   repeater:
      device_config:
        - rorg: "0xD1"
          func: "0x01"
          type: "0x12"
          command: ""
          channel: ""
          log_learn: ""
          direction: ""
          answer: ""
      entities:
         - component: "select"
           name: "repeater_level"
           config:
               command_topic: "d1/req"
               command_template:: >-
                  {% if value == "1" %}
                  {"raw_data":"00:46:08:01","send":"clear+raw_data"}
                  {% elif value == "2" %}
                  {"raw_data":"00:46:08:02","send":"clear+raw_data"}
                  {% else %}
                  {"raw_data":"00:46:08:00","send":"clear+raw_data"}
                  {% endif %}
               entity_category: "config"
               icon: "mdi:repeat"
               options:
                  - "0"
                  - "1"
                  - "2"

Good point: repeater level can be selected in the same HA device

Bad point: the addon is receiving the payload 1 or 2 instead of the raw_data that must be sent.

I will keep working on it another day.

[shilga]

Is there any other useful MSC command in this guide ? We don't need the guide, we need the informations inside. If there is other useful MSC command in this guide, maybe we can try to implement them so everyone can use them.

there are commands to receive repeater status, Configuration for state after power cut, night-mode and auto off timer. But the last three are actually VLD commands. Not sure what to make out of that. I need to check if they are defined in the Enocean spec. I'll just list everything here as in the manual:

Output 1 ON – VLD : 01 00 64
Output 1 OFF – VLD : 01 00 00
Output 2 ON – VLD : 01 01 64
Output 2 OFF – VLD : 01 01 00
Output 1 & 2 ON – VLD : 01 1E 64
Output 1 & 2 OFF – VLD : 01 1E 00
Local Control Enable – VLD : 02 20 00 20
Local Control Disabled – VLD : 02 00 00 20
Day mode – VLD : 02 20 00 20
Night Mode – VLD : 02 20 00 A0
ON state after power cut– VLD : 12 20 00 10
OFF state after power cut– VLD : 12 20 00 00

Previous state after power cut– VLD : 02 20 00 20
Disable repeater – MSC : 46 00 08 00 00
Repeater Level 1 – MSC : 46 00 08 01 01
Repeater Level 2 – MSC : 46 00 08 01 02
Repeater status – MSC : 00 46 09
Actuator status – VLD : 03 01
Auto OFF Timer – VLD : 0B XX YY YY 00 00 00 XX : channel to apply the Auto OFF Timer YY YY : hex value (from 1s to 65535s avec un pas de 0,1 sec => pour 10 secondes : convertir 100 en hex)

But I'm not sure if we can trust all of those messages as the repeater config is seemingly wrong. But it's strange as the manufacturer id (0x46 for Nodon) should be in the first byte according to specification.

[ChristopheHD]

VLD telegrams are already part of the EEP specifications so they won't be useful, but if we can make the repeater status working it would be really great!

[shilga]

For some reason I'm unable to find the equipment profile for D2-01 anymore. I'm unsure if things like the night mode or timer are part of it. Did they remove those from the Enocean Alliance site?

[ChristopheHD]

You mean this file ? https://tools.enocean-alliance.org/EEPViewer/profiles/D2/01/12/D2-01-12.pdf

[shilga]

I now definitely have a repeater here. I placed the receiver in a place it does not have good reception and all the telegrams are shown as repeated. Only if I moved with the rocker switch next to the receiver I saw non repeated messages. You see in in the bit 0 of status.

Not sure why it is not able to show the original and the repeated message. But that might be how the USB300 stick works. It only displays the message one time with the best signal.

[shilga]

oh wow. That is already something.

I had also some check. This will eventually call RadioPacket.create() on the underlying library right? That one right now does not support MSC as you pointed out. So it needs to be added there too, right?

[ChristopheHD]

Indeed, that needs a modification of at least the enocean library and maybe the mqtt mapping. I will have a look because I'm also interested in such feature.

[shilga]

From library side it might need an additional function to create the packet from what I see. The MSC message does not really have func and type fields.

[ChristopheHD]

Nodon repeater configuration will be added in the next release. I rewrote the MSC support in the enocean library and added Nodon MSC telegrams in the EEP.xml. MSC flag is taken from the MQTT topic like any other RORG. I did not succeed to use the repeater status telegram. Thank you very much for your help on this topic.