Temp/rH sensor missing entities

[Kohhal]

Hi,

Great work on this integration. Long time needed for EnOcean and very slick.

All my Thermokon D5-00-01 contacts appeared automatically, all seems good there.

I also have Thermokon sr04 (A5-04-01) and sr65 (A5-04-02) temp/rH sensors which I've added manually after seeing the data in the logs, example below:

• 2026-01-04 17:13:15,378 - core.serial_handler - INFO - 📦 RAW PACKET #197 RECEIVED
• 2026-01-04 17:13:15,378 - core.serial_handler - INFO - Type: 0x1
• 2026-01-04 17:13:15,378 - core.serial_handler - INFO - Data length: 10
• 2026-01-04 17:13:15,379 - core.serial_handler - INFO - Raw data: a500b9640a0510828600
• 2026-01-04 17:13:15,379 - core.serial_handler - INFO - ✅ This is a RADIO TELEGRAM - processing...
• 2026-01-04 17:13:15,379 - main - INFO - ================================================================================
• 2026-01-04 17:13:15,379 - main - INFO - 📡 TELEGRAM RECEIVED
• 2026-01-04 17:13:15,380 - main - INFO - Sender ID: 05108286
• 2026-01-04 17:13:15,380 - main - INFO - RORG: 0xa5
• 2026-01-04 17:13:15,380 - main - INFO - RSSI: -68 dBm
• 2026-01-04 17:13:15,380 - main - INFO - Data: a5 00 b9 64 0a 05 10 82 86 00
• 2026-01-04 17:13:15,380 - main - INFO - ✅ Known Device: Kitchen Temp/rH (A5-04-01)
• 2026-01-04 17:13:15,381 - eep.parser - INFO - 📊 Parsing telegram with profile A5-04-01
• 2026-01-04 17:13:15,381 - eep.parser - INFO - Full data length: 10 bytes
• 2026-01-04 17:13:15,381 - eep.parser - INFO - Full data hex: a5 00 b9 64 0a 05 10 82 86 00
• 2026-01-04 17:13:15,381 - eep.parser - INFO - Data bytes (DB3-DB0): 00 b9 64 0a
• 2026-01-04 17:13:15,381 - eep.parser - INFO - Parsed result: {'TMP': 16.0, 'HUM': 74.0}
• 2026-01-04 17:13:15,381 - main - INFO - Parsed data: {'TMP': 16.0, 'HUM': 74.0, 'rssi': -68, 'last_seen': '2026-01-04T17:13:15Z'}
• 2026-01-04 17:13:15,382 - main - INFO - → Published to MQTT (retained)
• 2026-01-04 17:13:15,382 - core.serial_handler - INFO - 🔍 Waiting for sync byte (0x55)... Listening for EnOcean devices...
• 2026-01-04 17:13:24,311 - core.serial_handler - INFO - ✅ Found sync byte (0x55) after reading 1 bytes!

When I check the MQTT entities there is only an RSSI and Last Seen entity, none for the temp or rH?

Sensors
Last Seen: 4 minutes ago
RSSI: -70 dBm

I also have a couple of motion sensors but I've not had a chance to test them yet...

Thanks!

[Kohhal]

Some logs for the Thermokon SR-MOC Motion Sensor (A5-07-01) :

2026-01-04 20:33:55,144 - core.serial_handler - DEBUG - Read byte: 0x55
2026-01-04 20:33:55,144 - core.serial_handler - INFO - ✅ Found sync byte (0x55) after reading 1 bytes!
2026-01-04 20:33:55,160 - core.esp3_protocol - DEBUG - Parsed ESP3 packet: type=0x1, data_len=10, opt_len=7
2026-01-04 20:33:55,160 - core.serial_handler - DEBUG - Received packet: ESP3Packet(type=0x1, data_len=10, opt_len=7, sender=0501facd, rorg=0xa5)
2026-01-04 20:33:55,160 - core.serial_handler - INFO - 📦 RAW PACKET #34 RECEIVED
2026-01-04 20:33:55,161 - core.serial_handler - INFO - Type: 0x1
2026-01-04 20:33:55,161 - core.serial_handler - INFO - Data length: 10
2026-01-04 20:33:55,161 - core.serial_handler - INFO - Raw data: a58200ff090501facd00
2026-01-04 20:33:55,161 - core.serial_handler - INFO - ✅ This is a RADIO TELEGRAM - processing...
2026-01-04 20:33:55,161 - main - INFO - ================================================================================
2026-01-04 20:33:55,162 - main - INFO - 📡 TELEGRAM RECEIVED
2026-01-04 20:33:55,162 - main - INFO - Sender ID: 0501facd
2026-01-04 20:33:55,162 - main - INFO - RORG: 0xa5
2026-01-04 20:33:55,162 - main - INFO - RSSI: -71 dBm
2026-01-04 20:33:55,162 - main - INFO - Data: a5 82 00 ff 09 05 01 fa cd 00
2026-01-04 20:33:55,163 - main - INFO - ✅ Known Device: Hall Motion Sensor (A5-07-01)
2026-01-04 20:33:55,165 - core.device_manager - DEBUG - Saved 16 devices to /data/devices.json
2026-01-04 20:33:55,165 - eep.parser - INFO - 📊 Parsing telegram with profile A5-07-01
2026-01-04 20:33:55,165 - eep.parser - INFO - Full data length: 10 bytes
2026-01-04 20:33:55,165 - eep.parser - INFO - Full data hex: a5 82 00 ff 09 05 01 fa cd 00
2026-01-04 20:33:55,165 - eep.parser - INFO - Data bytes (DB3-DB0): 82 00 ff 09
2026-01-04 20:33:55,165 - eep.parser - DEBUG - Parsed PIRS: 255 (raw: 255)
2026-01-04 20:33:55,165 - eep.parser - DEBUG - Parsed SVC: 2.6 (raw: 130)
2026-01-04 20:33:55,166 - eep.parser - INFO - Parsed result: {'PIRS': 255, 'SVC': 2.6}
2026-01-04 20:33:55,166 - main - INFO - Parsed data: {'PIRS': 255, 'SVC': 2.6, 'rssi': -71, 'last_seen': '2026-01-04T20:33:55Z'}
2026-01-04 20:33:55,166 - core.state_persistence - DEBUG - Saved 16 device states to /data/device_states.json
2026-01-04 20:33:55,166 - core.state_persistence - DEBUG - Saved state for device 0501facd
2026-01-04 20:33:55,167 - core.mqtt_handler - DEBUG - Published state for 0501facd: {'PIRS': 255, 'SVC': 2.6, 'rssi': -71, 'last_seen': '2026-01-04T20:33:55Z'} (retain=True)
2026-01-04 20:33:55,167 - core.mqtt_handler - DEBUG - Published availability for 0501facd: online
2026-01-04 20:33:55,167 - main - INFO - → Published to MQTT (retained)

[Kohhal]

So with the assistance of Claude.ai I was able to get the missing entities working, below is what I did:

Workaround Found - Manual MQTT Discovery
I've found a workaround for the missing temperature and humidity entities while we wait for a permanent fix.

The Problem
The add-on correctly receives and parses the temperature and humidity data (visible in logs), but only creates RSSI and Last Seen entities in Home Assistant. The MQTT discovery messages for TMP/HM (or HUM) sensor entities are not being published.

The Workaround
Manually publish MQTT discovery configuration messages via Home Assistant's MQTT integration.

Steps:

Go to Developer Tools → MQTT in Home Assistant
Use the "Publish a packet" section
Publish the following two messages (check "Retain" for both)

For A5-04-02 Sensors (uses HM for humidity):
Temperature Entity:

Topic: homeassistant/sensor/enocean_DEVICEID_TMP/config
Payload:

json{
"name": "DEVICE_NAME Temperature",
"device_class": "temperature",
"unit_of_measurement": "°C",
"state_topic": "enocean/DEVICEID/state",
"value_template": "{% raw %}{{ value_json.TMP }}{% endraw %}",
"unique_id": "enocean_DEVICEID_TMP",
"availability_topic": "enocean/DEVICEID/availability",
"payload_available": "online",
"payload_not_available": "offline",
"device": {
"identifiers": ["enocean_DEVICEID"],
"name": "DEVICE_NAME",
"model": "A5-04-02",
"manufacturer": "EnOcean"
}
}
Humidity Entity:

Topic: homeassistant/sensor/enocean_DEVICEID_HM/config
Payload:

json{
"name": "DEVICE_NAME Humidity",
"device_class": "humidity",
"unit_of_measurement": "%",
"state_topic": "enocean/DEVICEID/state",
"value_template": "{% raw %}{{ value_json.HM }}{% endraw %}",
"unique_id": "enocean_DEVICEID_HM",
"availability_topic": "enocean/DEVICEID/availability",
"payload_available": "online",
"payload_not_available": "offline",
"device": {
"identifiers": ["enocean_DEVICEID"],
"name": "DEVICE_NAME",
"model": "A5-04-02",
"manufacturer": "EnOcean"
}
}
For A5-04-01 Sensors (uses HUM for humidity):
Same as above, but replace HM with HUM in both the topic and value_template.
Example:

Topic: homeassistant/sensor/enocean_DEVICEID_HUM/config
value_template: "{% raw %}{{ value_json.HUM }}{% endraw %}"

Replace in the payloads:

DEVICEID → Your device ID (e.g., 05160bb5)
DEVICE_NAME → Your device name (e.g., Outside temp/rH)
Model number → Match your EEP profile (A5-04-01, A5-04-02, etc.)

Results
After publishing both messages, all four entities appear correctly grouped:

✅ Temperature sensor (with correct °C units)
✅ Humidity sensor (with correct % units)
✅ RSSI sensor
✅ Last Seen sensor

The entities will continue to receive updates from the add-on and persist across restarts.
Note
This workaround won't interfere with future fixes - when the add-on is updated to automatically create these discovery messages, they'll either overwrite the manual ones or the manual ones can be safely removed.
What Needs to be Fixed
The add-on needs to automatically publish MQTT discovery messages for all sensor objects defined in the EEP profile, not just RSSI and Last Seen. The data is already being parsed and published to the state topic correctly - only the discovery configuration messages are missing.

Hope this helps someone.

I'm going to try get the Motion Sensor working now...