EnOcean MQTT - message not interpretable or data missing

Configuration
1

Hi,

I have setup an USB300 and integrated it with EnOcean MQTT (dev).
Overall the setup is ok, the devices entered in the config are getting created in MQTT as well. So far so good.
The problem is - I am not able to extract the values as probably the eep setting is wrong. I am migrating from FHEM so I used the eep´s that where set there but non of the devices/sensors is working in HA.

Temperature sensor Thermokon SR06 (no LCD, no buttons, just sensor)

2025-04-29 09:33:23,455 DEBUG: 00:03:8D:52->FF:FF:FF:FF (-91 dBm): 0x01 ['0xa5', '0x0', '0x7e', '0x6f', '0xf', '0x0', '0x3', '0x8d', '0x52', '0x0'] ['0x1', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()
2025-04-29 09:33:23,456 WARNING: Cannot find rorg 0xa5 func 0x3f type 0x6f in EEP!
2025-04-29 09:33:23,457 WARNING: message not interpretable: enoceanmqtt/OG.Bad.Tempunused

Open/Close sensor:

025-04-29 09:35:04,459 DEBUG: 00:00:DA:C6->FF:FF:FF:FF (-91 dBm): 0x01 ['0xd5', '0x9', '0x0', '0x0', '0xda', '0xc6', '0x0'] ['0x1', '0xff', '0xff', '0xff', '0xff', '0x5b', '0x0'] OrderedDict()
2025-04-29 09:35:04,460 WARNING: message not interpretable: enoceanmqtt/OG.Ankleide.Kuppel.Fensterkontakt

These two are a switches but are just showing last seen and RSSI, probably missing some further config here?:

2025-04-29 09:35:34,439 DEBUG: FF:D4:19:81->FF:FF:FF:FF (-73 dBm): 0x01 ['0xd2', '0x4', '0x60', '0x0', '0xff', '0xd4', '0x19', '0x81', '0x0'] ['0x1', '0xff', '0xff', '0xff', '0xff', '0x49', '0x0'] OrderedDict()
2025-04-29 09:35:34,440 DEBUG: enoceanmqtt/OG.Abstellkammer.Drucker: CMD (Command identifier)=Command ID 4 
2025-04-29 09:35:34,441 DEBUG: enoceanmqtt/OG.Abstellkammer.Drucker: DV (Dim value)=Dim to new output level - dim timer 3 
2025-04-29 09:35:34,441 DEBUG: enoceanmqtt/OG.Abstellkammer.Drucker: IO (I/O channel)=Output channel 0 (to load) 
2025-04-29 09:35:34,441 DEBUG: enoceanmqtt/OG.Abstellkammer.Drucker: OV (Output value)=Output value 0% or OFF 
2025-04-29 09:35:34,441 DEBUG: enoceanmqtt/OG.Abstellkammer.Drucker: Sent MQTT: {"_RSSI_": -73, "_DATE_": "2025-04-29T09:35:34.439210", "CMD": 4, "DV": 3, "IO": 0, "OV": 0}
2025-04-29 09:35:34,442 DEBUG: Sending PUBLISH (d0, q0, r1, m98), 'b'enoceanmqtt/OG.Abstellkammer.Drucker'', ... (92 bytes)

2025-04-29 09:40:31,869 DEBUG: FF:F0:F3:01->FF:FF:FF:FF (-83 dBm): 0x01 ['0xd2', '0x4', '0x60', '0x80', '0xff', '0xf0', '0xf3', '0x1', '0x0'] ['0x1', '0xff', '0xff', '0xff', '0xff', '0x53', '0x0'] OrderedDict()
2025-04-29 09:40:31,872 DEBUG: enoceanmqtt/OG.Ankleide.Licht: CMD (Command identifier)=Command ID 4 
2025-04-29 09:40:31,873 DEBUG: enoceanmqtt/OG.Ankleide.Licht: DV (Dim value)=Dim to new output level - dim timer 3 
2025-04-29 09:40:31,873 DEBUG: enoceanmqtt/OG.Ankleide.Licht: IO (I/O channel)=Output channel 0 (to load) 
2025-04-29 09:40:31,873 DEBUG: enoceanmqtt/OG.Ankleide.Licht: OV (Output value)=Output value 0% or OFF 
2025-04-29 09:40:31,874 DEBUG: enoceanmqtt/OG.Ankleide.Licht: Sent MQTT: {"_RSSI_": -83, "_DATE_": "2025-04-29T09:40:31.869583", "CMD": 4, "DV": 3, "IO": 0, "OV": 0}
2025-04-29 09:40:31,874 DEBUG: Sending PUBLISH (d0, q0, r1, m99), 'b'enoceanmqtt/OG.Ankleide.Licht'', ... (92 bytes)

Motion Sensor:

2025-04-29 10:01:57,973 DEBUG: 01:84:10:BD->FF:FF:FF:FF (-77 dBm): 0x01 ['0xa5', '0xd8', '0x7b', '0xff', '0x9', '0x1', '0x84', '0x10', '0xbd', '0x80'] ['0x1', '0xff', '0xff', '0xff', '0xff', '0x4d', '0x0'] OrderedDict()
2025-04-29 10:01:57,974 WARNING: message not interpretable: enoceanmqtt/OG.Ankleide.BWM

The config looks as follows:

[OG.Bad.Tempunused]
address      	= 0x00038D52
rorg            = 0xA5
func            = 0x3F
type            = 0x6F

[OG.Ankleide.Kuppel.Fensterkontakt]
address      	= 0x0000DAC6
rorg            = 0xD5
func            = 0x00
type            = 0x01

[OG.Abstellkammer.Drucker]
address      	= 0xFFD41981
rorg            = 0xD2
func            = 0x01
type            = 0x08

# Motion
[OG.Ankleide.BWM]
address      	= 0x018410BD
rorg            = 0xA5
func            = 0x07
type            = 0x01

I also checked the supported devices here https://github.com/mak-gitdev/HA_enoceanmqtt/wiki/Supported-devices

At least some should work. Motion sensor is there, the open/close contact. The switches and the temperature sensore are missing.

Do you have any ideas?

br
F.

2

Just checked again with one temperature sensor. It gets acknowledged in FHEM with EEP A5-10-06 Manufacturer: Thermokon.
This is part of the integration. By creating it accordingly in HA:

[OG.Bad.Tempunused]
address      	= 0x00038D52
rorg            = 0xA5
func            = 0x10
type            = 0x06

I still get the same issue:

2025-04-29 11:19:40,120 DEBUG: 00:03:8D:52->FF:FF:FF:FF (-80 dBm): 0x01 ['0xa5', '0x0', '0x7f', '0x70', '0xf', '0x0', '0x3', '0x8d', '0x52', '0x0'] ['0x1', '0xff', '0xff', '0xff', '0xff', '0x50', '0x0'] OrderedDict()
2025-04-29 11:19:40,121 WARNING: message not interpretable: enoceanmqtt/OG.Bad.Tempunused
3

I made some progress. Obviously the addon itself was causing the issues. I have used a different repository: https://github.com/ChristopheHD/HA_enoceanmqtt-addon

Now some data already is displayed! I´ll further evaluate it and keep you updated…

4

Another update.
Temperatures and contact sensors are working as expected now.
Switches are left. Integration seems ok but when I try switch on/off nothing happens:

2025-04-29 13:01:08,128 DEBUG: Trigger message to: enoceanmqtt/OG.Ankleide.Licht
2025-04-29 13:01:08,128 DEBUG: Retrieved command id from MQTT message: 0x1
2025-04-29 13:01:08,130 DEBUG: sensor data: {'CMD': 1, 'DV': 0, 'IO': 0, 'OV': 100}
2025-04-29 13:01:08,132 INFO: sending: FF:9C:08:80->FF:F0:F3:01 (-255 dBm): 0x01 ['0xd2', '0x1', '0x0', '0x64', '0xff', '0x9c', '0x8', '0x80', '0x0'] ['0x3', '0xff', '0xf0', '0xf3', '0x1', '0xff', '0x0'] OrderedDict({'CMD': {'description': 'Command identifier', 'unit': '', 'value': 'Command ID 1', 'raw_value': 1}, 'DV': {'description': 'Dim value', 'unit': '', 'value': 'Switch to new output value', 'raw_value': 0}, 'IO': {'description': 'I/O channel', 'unit': '', 'value': 'Output channel 0 (to load)', 'raw_value': 0}, 'OV': {'description': 'Output value', 'unit': '', 'value': 'Output value 100% or ON', 'raw_value': 100}})
2025-04-29 13:01:08,132 DEBUG: Clearing data buffer.
2025-04-29 13:01:08,150 INFO: Sending packet
2025-04-29 13:01:08,150 DEBUG: FF:9C:08:80->FF:F0:F3:01 (-255 dBm): 0x01 ['0xd2', '0x1', '0x0', '0x64', '0xff', '0x9c', '0x8', '0x80', '0x0'] ['0x3', '0xff', '0xf0', '0xf3', '0x1', '0xff', '0x0'] OrderedDict({'CMD': {'description': 'Command identifier', 'unit': '', 'value': 'Command ID 1', 'raw_value': 1}, 'DV': {'description': 'Dim value', 'unit': '', 'value': 'Switch to new output value', 'raw_value': 0}, 'IO': {'description': 'I/O channel', 'unit': '', 'value': 'Output channel 0 (to load)', 'raw_value': 0}, 'OV': {'description': 'Output value', 'unit': '', 'value': 'Output value 100% or ON', 'raw_value': 100}})
2025-04-29 13:01:08,251 DEBUG: 0x02 ['0x0'] [] OrderedDict()
2025-04-29 13:01:08,252 INFO: got response packet: OK
5

Hello,
This discussion is not tagged with enocean and I nearly missed it. If you have further questions or issues with Enocean2MQTT, please use Github to ask for help.

Switch integration is intended to trigger an automation when a button is pushed. Therefore you need to create an automation on the device.
If you want to retrieve the state of the device which is driven by the switch, please configure the device itself and not its switch.
If I misunderstood your request, please provide also the configuration.

6

Hi,

there is no enocean tag available - just checked it again.

Regarding the switch - it is an PEHA Easyclick 451 I think without checking behind the socket. I was under the assumption that this device gets created as MQTT device as well (which it does) and directly can be switched. If I hit the on/off button I can see the above shown message in the debugger.
So what do I miss then?

EnoceanMQTTSwitch
EnoceanMQTTSwitch328×626 16.3 KB

7

Did you follow the pairing procedure ? Pairing your device · ChristopheHD/HA_enoceanmqtt-addon Wiki · GitHub

Can you share the configuration of OG.Ankleide.Licht ?

8

According to it’s documentation, this device seems to have several EEP and I’m not sure which one must be set in the configuration.

9

You are right - my mistake. The device is currently paired with my FHEM server and the FGW14 Gateway. As long as I do not change it to the USB300 it cannot work - thx for the right hint. The sensors don´t matter as they are just senders.