EMS-ESP does not publish data on MQTT for Nefit Topline HRC30 boiler with Moduline 3000 thermostat

Moving4407 commented 1 month ago

DESCRIPTION

I have 2 S3 devices from BBQKees that run EMS-ESP 3.7.0 dev 39 attached to 2 Nefit Heaters (Topline HRC 30 and Topline HRC 45). Only the HRC 45 shows up in my HA dashboard. The temperature sensors (DS18B20) for both S3 devices do show up. The HRC 30 boiler and thermostat also don't show up as MQTT devices in HA:

REQUESTED INFORMATION

  Paste System information here....
2024-09-23 16:59:05.000 I 1: [emsesp] EMS-ESP version 3.7.0-dev.39 (app1 partition)
2024-09-23 16:59:05.000 I 2: [emsesp] Last system reset reason Core0: Software reset CPU, Core1: Software reset CPU
2024-09-23 16:59:05.000 I 3: [emsesp] Board profile set to S32S3
2024-09-23 16:59:05.000 I 4: [emsesp] Loaded EMS device library (120 entries)
2024-09-23 16:59:05.000 I 5: [emsesp] Starting Scheduler service
2024-09-23 16:59:05.000 I 6: [emsesp] Starting Custom Entity service
2024-09-23 16:59:05.000 I 7: [temperaturesensor] Starting Temperature Sensor service
2024-09-23 16:59:05.000 I 8: [analogsensor] Starting Analog Sensor service
2024-09-23 16:59:05.000 I 9: [emsesp] Starting Modules service
2024-09-23 16:59:05.000 I 10: [module] No external library modules found
2024-09-23 16:59:05.000 I 11: [emsesp] Starting Web Server
2024-09-23 16:59:08.696 W 12: [emsesp] WiFi disconnected. Reason: assoc fail (203)
2024-09-23 16:59:09.115 W 13: [emsesp] WiFi disconnected. Reason: auth fail (202)
2024-09-23 16:59:14.989 I 14: [emsesp] WiFi connected (Local IP=192.168.178.97, hostname=nefit-HRC30, TxPower=18.5 dBm)
2024-09-23 16:59:15.000 I 15: [emsesp] Starting Access Point with captive portal on 192.168.4.1
2024-09-23 16:59:15.383 I 16: [emsesp] Starting mDNS Responder service
2024-09-23 16:59:15.383 I 17: [emsesp] Starting NTP service
2024-09-23 16:59:15.541 I 18: [mqtt] MQTT connected
2024-09-23 16:59:15.547 I 19: [emsesp] IPv6 (WiFi) local: fe80:0000:0000:0000:eeda:3bff:fe46:94a0
2024-09-23 16:59:15.816 I 20: [emsesp] Detected EMS device: boiler (0x08)
2024-09-23 16:59:16.282 I 21: [emsesp] Detected EMS device: controller (0x09)
2024-09-23 16:59:16.379 I 22: [emsesp] Detected EMS device: thermostat (0x10)
2024-09-23 16:59:16.543 I 23: [emsesp] IPv6 (WiFi) global: 2001:1c05:3c81:5200:eeda:3bff:fe46:94a0
2024-09-23 16:59:18.285 W 24: [telegram] Incomplete Rx: 10 0B FF 00 01 A5 00 CE 31 00 00 00 00 25 00 01 01 01 03 00 01 89
2024-09-23 16:59:25.000 I 25: [emsesp] Stopping Access Point
2024-09-23 17:00:07.491 W 26: [telegram] Incomplete Rx: 10 0B FF 00 01 40 32 00 01 00 00 00 00 00 FF 03 F6 06 FF 00 00 B6

EXPECTED BEHAVIOUR

I expect 2 heaters and thermostats to shop up in Home Assistant

proddy commented 1 month ago

When running more than one EMS-ESP instance, make sure:

MQTT Entity ID format is set to Multiple instances
MQTT Client ID is unique
MQTT Base is unique (just be sure)
Network hostname is unique (to avoid conflicts)
EMS BUS ID are different (not both 0xB)

If you had sent the Support Info, I could have checked the above for you ;-) (see https://emsesp.org/Support/).

Moving4407 commented 1 month ago

Switching to multiple instances, short name did the trick. I followed your GH instructions, did not read the support page. Thanks for your help.

emsesp / EMS-ESP32