No sensors on HA with Nodon SIN-2-1-01

The problem

First one, thnks for this great project that make EnOcean usable ;-) I've an issue with this Nodon module who has Enocean protocol D2-01-0F (https://nodon.fr/support/module-multifonction/) Identification and paring was fine but I cannot find in HA the two sensors of this module. I have only the swith sensor visible to get feedback of the firt contat of the module but not access to the second contact in anyway. As I ues for monitoring stage on my electrical pannel I miss one info per module (I've three of them) A bug or native Enocean issue?

What type of installation are you running?

Standalone

What version of HA_enoceanmqtt has the issue?

0.1.27 (dev)

What was the last working version of HA_enoceanmqtt?

No response

What type of Home Assitant installation are you running?

Home Assistant OS

Anything in the logs that might be useful to solve the issue? (Strongly recommended if applicable)

2023-11-05 13:21:58,481 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-61 dBm): 0x01 ['0xf6', '0x10', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3d', '0x0'] OrderedDict()
2023-11-05 13:21:58,481 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna
2023-11-05 13:21:58,585 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-64 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x40', '0x0'] OrderedDict()
2023-11-05 13:21:58,586 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna
2023-11-05 13:21:59,173 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-64 dBm): 0x01 ['0xd2', '0x4', '0x60', '0xe4', '0x5', '0x98', '0x7', '0xfe', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x40', '0x0'] OrderedDict()
2023-11-05 13:21:59,174 DEBUG: Retrieved command id from packet: 0x4
2023-11-05 13:21:59,179 DEBUG: enoceanmqtt/supervisor/borne/sauna: PF (Power Failure)=Power Failure Detection disabled/not supported 
2023-11-05 13:21:59,180 DEBUG: enoceanmqtt/supervisor/borne/sauna: PFD (Power Failure Detection)=Power Failure Detection not detected/not supported/disabled 
2023-11-05 13:21:59,181 DEBUG: enoceanmqtt/supervisor/borne/sauna: CMD (Command identifier)=Command ID 4 
2023-11-05 13:21:59,181 DEBUG: enoceanmqtt/supervisor/borne/sauna: OC (Over current switch off)=Over current switch off: ready / not supported 
2023-11-05 13:21:59,182 DEBUG: enoceanmqtt/supervisor/borne/sauna: EL (Error level)=Error level not supported 
2023-11-05 13:21:59,182 DEBUG: enoceanmqtt/supervisor/borne/sauna: IO (I/O channel)=Output channel 0 (to load) 
2023-11-05 13:21:59,183 DEBUG: enoceanmqtt/supervisor/borne/sauna: LC (Local control)=Local control enabled 
2023-11-05 13:21:59,184 DEBUG: enoceanmqtt/supervisor/borne/sauna: OV (Output value)=Output value 100% or ON 
2023-11-05 13:21:59,184 DEBUG: Sending PUBLISH (d0, q0, r1, m80), 'b'enoceanmqtt/supervisor/borne/sauna'', ... (55 bytes)
2023-11-05 13:21:59,185 DEBUG: enoceanmqtt/supervisor/borne/sauna/CMD4: Sent MQTT: {"_DATE_": "2023-11-05T13:21:59.172981", "PF": 0, "PFD": 0, "OC": 0, "EL": 3, "IO": 0, "LC": 1, "OV": 100}
2023-11-05 13:21:59,186 DEBUG: Sending PUBLISH (d0, q0, r1, m81), 'b'enoceanmqtt/supervisor/borne/sauna/CMD4'', ... (106 bytes)

Additional information

Extract of debug level log when one contact is activated on the module.

Hi @mainate,

I cannot find in HA the two sensors of this module. I have only the swith sensor visible to get feedback of the firt contat of the module but not access to the second contact in anyway. As I ues for monitoring stage on my electrical pannel I miss one info per module (I've three of them)

This module has only one contact (one output), hence the single switch you have that allows you to control that contact. Could you give more details about what you were expecting ?

One question out of curiosity:

2023-11-05 13:21:58,481 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-61 dBm): 0x01 ['0xf6', '0x10', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3d', '0x0'] OrderedDict()
2023-11-05 13:21:58,481 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna

Did you activate the repeater mode of your NodOn module ?

Hello,

Thanks for answering. Yes this module has only one contact but he as tow binary sensors I1 and I2, and i1 would also locally toggle the swith

[image: image.png]

With Native Enocean of HA; after added the module in the configuration.yaml file, these were not visible in HA too, but the change of state of these tow binary sensors was triggered an event button_pressed and via the automation bellow can set entities. Unfortunately that not works anymore :-(

For you question if I remember , yers one of the three modules is active as repeater.

alias: Supervision alimentation borne et sauna description: Annonce changement d'état alimentation borne et ou sauna trigger:

platform: event event_type: button_pressed event_data: id:
- 5
- 152
- 7
- 254 pushed: 1 action:
service_template: >- {% if trigger.event.data.which == 1 %} {% if trigger.event.data.onoff == 0 %} input_boolean.turn_off {% elif trigger.event.data.onoff == 1 %} input_boolean.turn_on {% endif %} {% elif trigger.event.data.which == 0 %} {% if trigger.event.data.onoff == 0 %} input_boolean.turn_off {% elif trigger.event.data.onoff == 1 %} input_boolean.turn_on {% endif %} {% endif %} data_template: entity_id: >- {% if trigger.event.data.which == 1 %} {% if trigger.event.data.onoff == 0 %} input_boolean.sauna_active {% elif trigger.event.data.onoff == 1 %} input_boolean.sauna_active {% endif %} {% elif trigger.event.data.which == 0 %} {% if trigger.event.data.onoff == 0 %} input_boolean.borne_active {% elif trigger.event.data.onoff == 1 %} input_boolean.borne_active {% endif %} {% endif %} mode: single

Last but not least, the log shows "not interpretable message comming from the I2 binary sensor of the Nodon.

2023-11-07 12:00:25,853 WARNING: message not interpretable: enoceanmqtt/supervisor/deslestage/LL/Heaters 2023-11-07 12:00:25,955 WARNING: message not interpretable: enoceanmqtt/supervisor/deslestage/LL/Heaters 2023-11-07 12:45:16,617 WARNING: message not interpretable: enoceanmqtt/supervisor/delestage/chauffe-eau 2023-11-07 12:45:16,718 WARNING: message not interpretable: enoceanmqtt/supervisor/delestage/chauffe-eau

Any idea? Other only way for me is to replace these three 1 switch Nodon with double swith one :-(

Philippe Besson

Le lun. 6 nov. 2023 à 01:11, mak-gitdev @.***> a écrit :

Hi @mainate https://github.com/mainate,

I cannot find in HA the two sensors of this module. I have only the swith sensor visible to get feedback of the firt contat of the module but not access to the second contact in anyway. As I ues for monitoring stage on my electrical pannel I miss one info per module (I've three of them)

This module has only one contact (one output), hence the single switch you have that allows you to control that contact. Could you give more details about what you were expecting ?

One question out of curiosity:

2023-11-05 13:21:58,481 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-61 dBm): 0x01 ['0xf6', '0x10', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3d', '0x0'] OrderedDict() 2023-11-05 13:21:58,481 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna

Did you activate the repeater mode of your NodOn module ?

— Reply to this email directly, view it on GitHub https://github.com/mak-gitdev/HA_enoceanmqtt/issues/91#issuecomment-1793894227, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFPG5PJMKRBTZXTL2AJEI73YDATKZAVCNFSM6AAAAAA66JZERKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTHA4TIMRSG4 . You are receiving this because you were mentioned.Message ID: @.***>

Let me complet few information. I've sent an e-mail in support of Nodon. The answer was: No reporting of Input state from the module, Only the switch state :-(

But after I have activated the log_packets on the addon, I can see these packets transmitted by the Nodon module ?? (i have added few personal comment on it:

## Activation of the first input (I1)

2023-11-08 14:27:02,802 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-60 dBm): 0x01 ['0xf6', '0x10', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3c', '0x0'] OrderedDict()

2023-11-08 14:27:02,805 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna 2023-11-08 14:27:02,904 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-61 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3d', '0x0'] OrderedDict() 2023-11-08 14:27:02,906 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna##

##Message of the Switch status (OK)

2023-11-08 14:27:03,479 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-61 dBm): 0x01 ['0xd2', '0x4', '0x60', '0xe4', '0x5', '0x98', '0x7', '0xfe', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3d', '0x0'] OrderedDict()

## Activation of the second input (I2)

2023-11-08 14:27:06,834 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-61 dBm): 0x01 ['0xf6', '0x50', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3d', '0x0'] OrderedDict()

2023-11-08 14:27:06,836 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna 2023-11-08 14:27:06,936 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-60 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3c', '0x0'] OrderedDict() 2023-11-08 14:27:06,938 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna

## deactivation of the first input (I1)

2023-11-08 14:27:18,703 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-60 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3c', '0x0'] OrderedDict() 2023-11-08 14:27:18,705 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna 2023-11-08 14:27:18,805 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-55 dBm): 0x01 ['0xf6', '0x30', '0x5', '0x98', '0x7', '0xfe', '0x31'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x37', '0x0'] OrderedDict() 2023-11-08 14:27:18,807 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna

##Message of the Switch status (OK)

2023-11-08 14:27:19,044 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-60 dBm): 0x01 ['0xd2', '0x4', '0x60', '0x80', '0x5', '0x98', '0x7', '0xfe', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3c', '0x0'] OrderedDict()

## Deactivation of the second input (I2)

2023-11-08 14:27:22,751 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-59 dBm): 0x01 ['0xf6', '0x70', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3b', '0x0'] OrderedDict()

2023-11-08 14:27:22,753 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna 2023-11-08 14:27:22,853 INFO: received: 05:98:07:FE->FF:FF:FF:FF (-58 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3a', '0x0'] OrderedDict() 2023-11-08 14:27:22,856 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna

Do you think we can do something with these info? Best regards

Philippe Besson

Le mar. 7 nov. 2023 à 17:08, Philippe Besson @.***> a écrit :

Hello,

Thanks for answering. Yes this module has only one contact but he as tow binary sensors I1 and I2, and i1 would also locally toggle the swith

[image: image.png]

With Native Enocean of HA; after added the module in the configuration.yaml file, these were not visible in HA too, but the change of state of these tow binary sensors was triggered an event button_pressed and via the automation bellow can set entities. Unfortunately that not works anymore :-(

For you question if I remember , yers one of the three modules is active as repeater.

alias: Supervision alimentation borne et sauna description: Annonce changement d'état alimentation borne et ou sauna trigger:

platform: event event_type: button_pressed event_data: id:

5

152

7

254 pushed: 1 action:

service_template: >- {% if trigger.event.data.which == 1 %} {% if trigger.event.data.onoff == 0 %} input_boolean.turn_off {% elif trigger.event.data.onoff == 1 %} input_boolean.turn_on {% endif %} {% elif trigger.event.data.which == 0 %} {% if trigger.event.data.onoff == 0 %} input_boolean.turn_off {% elif trigger.event.data.onoff == 1 %} input_boolean.turn_on {% endif %} {% endif %} data_template: entity_id: >- {% if trigger.event.data.which == 1 %} {% if trigger.event.data.onoff == 0 %} input_boolean.sauna_active {% elif trigger.event.data.onoff == 1 %} input_boolean.sauna_active {% endif %} {% elif trigger.event.data.which == 0 %} {% if trigger.event.data.onoff == 0 %} input_boolean.borne_active {% elif trigger.event.data.onoff == 1 %} input_boolean.borne_active {% endif %} {% endif %} mode: single

Last but not least, the log shows "not interpretable message comming from the I2 binary sensor of the Nodon.

2023-11-07 12:00:25,853 WARNING: message not interpretable: enoceanmqtt/supervisor/deslestage/LL/Heaters 2023-11-07 12:00:25,955 WARNING: message not interpretable: enoceanmqtt/supervisor/deslestage/LL/Heaters 2023-11-07 12:45:16,617 WARNING: message not interpretable: enoceanmqtt/supervisor/delestage/chauffe-eau 2023-11-07 12:45:16,718 WARNING: message not interpretable: enoceanmqtt/supervisor/delestage/chauffe-eau

Any idea? Other only way for me is to replace these three 1 switch Nodon with double swith one :-(

Philippe Besson Route de Forchy 20 1146 Mollens VD Contact : @.*** Téléphone : +41 79 625 18 21

Le lun. 6 nov. 2023 à 01:11, mak-gitdev @.***> a écrit :

Hi @mainate https://github.com/mainate,

I cannot find in HA the two sensors of this module. I have only the swith sensor visible to get feedback of the firt contat of the module but not access to the second contact in anyway. As I ues for monitoring stage on my electrical pannel I miss one info per module (I've three of them)

This module has only one contact (one output), hence the single switch you have that allows you to control that contact. Could you give more details about what you were expecting ?

One question out of curiosity:

2023-11-05 13:21:58,481 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-61 dBm): 0x01 ['0xf6', '0x10', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x3d', '0x0'] OrderedDict() 2023-11-05 13:21:58,481 WARNING: message not interpretable: enoceanmqtt/supervisor/borne/sauna

Did you activate the repeater mode of your NodOn module ?

— Reply to this email directly, view it on GitHub https://github.com/mak-gitdev/HA_enoceanmqtt/issues/91#issuecomment-1793894227, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFPG5PJMKRBTZXTL2AJEI73YDATKZAVCNFSM6AAAAAA66JZERKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTHA4TIMRSG4 . You are receiving this because you were mentioned.Message ID: @.***>

Hi @mainate,

As NodOn said, the EEP used by the NodOn module does not report the inputs state.

What you are observing is that the NodOn module has its repeater mode activated and the telegrams that lead to the "message not interpretable" message come from a rocker switch telegram getting repeated by the NodOn module.

So it seems that you somehow use an EnOcean rocker switch to control your NodOn module.

Could you tell me exactly what is connected to the inputs I1 and I2 of your NodOn ? It would be better if you can give a schematic or a picture of your installation of your NodOn module.

I can promize to you that no roker swithes are in my "Chalet" and that the messages were not relayed by the Nodon, but send by it ! I've got the message exacly when I close/open the supervised relays (tested any times). See bellow attach a basic diagram of the connections. As the Nodons are in my "chalet" I would peak one back next weekend to make few "sniffing" with dolphinViewer to get the complete transmission from it. With native HA Enocean I was able to mannage these via automation and trigger event "button_pressed" I'm sure that the information is transmit, but not the actual state. I mean didn't have sensor present but trigger fired. No way to use Nodon Filpilote wiht the HA integration, but easy with yours ;-) Last but not least, I've send back mail to Nodon to clarify why I get message when they said it has not! Wait and see for the answer

Your job is great and really help to integrat Enocean on HA, even if something is not working as expected.

Nodon_connections

Hi @mainate

So let's wait for the NodOn answer.

As far as I'm concerned, I can't understand your setup as indicated in the schematics:

It seems you don't use ES so I don't get the purpose of the NodOn module in your setup.
Also, what is the reference of the Schneider Electric relay ?
Finally, what are the kind of pushbuttons on the live phase on the top of the relays ? Do you have a reference for those as well ?

Thanks.

@mak-gitdev; I've got some informations from Nodon support and these confirm that in bi-stable input configuration (as I have) the module would send EEP F6-02-01 messages. First one let me clarify the diagram:

Yes the ES input is not use only I1 and I2 are used
The "manual" swithes connected to the I1 and I2 are in fact the external command comming form the Eletricity provider for "délestage" of the heaters, the boiler or the washing machine This is these three different states I want to supervise with two Nodon modules. The third module is to do the same check when my Sauna or the wall connector for my Electrical car are activated.
For me as the is not may main home it is important to chek the real status of the relays and not just the command given to them.

Then about I1 I2 messages: The answer from Nodon is: C'est EnOcean2MQtt qui ne sait pas interpréter ces télégrammes. En principe nous ne communiquons pas ce genre d'infos, mais voici à quoi cela correspond : State switch: This parameter is effective only if external switch/push button type is set as “bi-stable”. When this setting is enabled, the device will turn ON output(s) when contacts are closed and turn OFF output(s) when contacts are open. When this setting is disabled (default mode), a change of contacts state will toggle the output(s). In this mode, when output state change, a broadcast D2-01-XX cmd 0x04, and two F6-02-01 telegrams are sent.

Debug message from last test with config shows: I1 swith on: 2023-11-13 21:55:50,121 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xf6', '0x10', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict() 2023-11-13 21:55:50,224 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-45 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2d', '0x0'] OrderedDict() 2023-11-13 21:55:50,477 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xd2', '0x4', '0x60', '0xe4', '0x5', '0x98', '0x7', '0xfe', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict() I1 swith off: 2023-11-13 21:57:03,671 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xf6', '0x30', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict() 2023-11-13 21:57:03,773 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict() 2023-11-13 21:57:03,979 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xd2', '0x4', '0x60', '0x80', '0x5', '0x98', '0x7', '0xfe', '0x0'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict() I2 swith on: 2023-11-13 21:57:35,527 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xf6', '0x50', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict() 2023-11-13 21:57:35,630 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict() I2 swith off: 2023-11-13 21:57:53,176 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xf6', '0x70', '0x5', '0x98', '0x7', '0xfe', '0x30'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict() 2023-11-13 21:57:53,279 DEBUG: 05:98:07:FE->FF:FF:FF:FF (-44 dBm): 0x01 ['0xf6', '0x0', '0x5', '0x98', '0x7', '0xfe', '0x20'] ['0x0', '0xff', '0xff', '0xff', '0xff', '0x2c', '0x0'] OrderedDict()

We can see that all messages are correctly build (If I understood correctly the content) but not sent to the Broker :-( (nothing n log) and last but not least, when I check event in HA developper tools for button_press nothing happen.

It looks like the EnOceanMQtt does not interpret correctly the message or don't trig to forward it to the broker.

If really no chance to get these I should replace my module with 2 channels version, but was not planned to buy new one now.

Best regards

Hi @mainate,

Thanks a lot for these details. As I couldn't find this information anywhere, I didn't know it would be possible that those modules generate F6 telegrams.

In your use case, do you need to control or monitor the ES state from HA ? If you don't need to, then simply use this module as F6-02-01. This way, the F6 telegrams from I1 and I2 will be interpreted as rocker switch. For example:

[myNodon]
address = 0x059807FE
rorg = 0xF6
func = 0x02
type = 0x01

If you need to control or monitor ES state, then at the moment, this is not possible as we can only accept one EEP per device address. But it is not a big deal to add multiple EEPs per address and I am working on it.

Hi @mak-gitdev, I've changed the EEP in config file Reset the nodon module (keep small button on it press for 5 seconds then press one more time to validate the reset) Did new pairing with EnOceanMQTT And now I get the message on HA. They are not suitable as binary_sensor but fully usable via state_change event and automation. I'd like to read that you are working on multiple EEPs per adress as on my three modules, one is configured to command the swith and to get status of I2 :-) Thanks for your support and the quite good job that you're doing to make Enocean easy to use on HA.

To be fixed with the introduction of models in 0.2.1

mak-gitdev / HA_enoceanmqtt