ESPHome emontx component - sensors missing

Mmm I seem to have lost the Sensor entries for the emonTx6 wifi, the sensor readings are no longer listed under the ESPHome device:

I can see the emonTx6 is still connected since the values are visible in the emonPi/Tx Config

Any idea why the sensor entities are not visible in HA? @FredM67 @borpin

Do you see the log output in the Serial Terminal?

[edit]
And then what is the output of the ESPHome Builder logs?

@FredM67 I saw this in the logs. Not completely up to date though

[13:07:03.961][E][esp32.crash:329]: *** CRASH DETECTED ON PREVIOUS BOOT ***
[13:07:03.974][E][esp32.crash:332]:   Reason: Fault - Unknown
[13:07:03.974][E][esp32.crash:336]:   Crashed core: 0
[13:07:03.974][E][esp32.crash:337]:   PC:  0x403832F2  (fault location)
WARNING Decoded 0x403832f2: esp_cpu_wait_for_intr at /data/cache/platformio/packages/framework-espidf/components/esp_hw_support/cpu.c:64
[13:07:04.624][E][esp32.crash:302]:   BT0: 0x403832F2  (backtrace)
WARNING Decoded 0x403832f2: esp_cpu_wait_for_intr at /data/cache/platformio/packages/framework-espidf/components/esp_hw_support/cpu.c:64
[13:07:05.147][E][esp32.crash:302]:   BT1: 0x403832E2  (backtrace)
WARNING Decoded 0x403832e2: esp_cpu_wait_for_intr at /data/cache/platformio/packages/framework-espidf/components/esp_hw_support/cpu.c:57 (discriminator 1)
[13:07:05.662][E][esp32.crash:302]:   BT2: 0x420CE32E  (stack scan)
WARNING Decoded 0x420ce32e: prvCheckTasksWaitingTermination at /data/cache/platformio/packages/framework-espidf/components/freertos/FreeRTOS-Kernel/tasks.c:4576
 (inlined by) prvIdleTask at /data/cache/platformio/packages/framework-espidf/components/freertos/FreeRTOS-Kernel/tasks.c:4301
[13:07:06.065][E][esp32.crash:358]: Use: addr2line -pfiaC -e firmware.elf 0x403832F2 0x403832F2 0x403832E2 0x420CE32E
[13:07:06.065][I][app:154]: ESPHome version 2026.4.3 compiled on 2026-05-03 15:18:09 +0100
[13:07:06.065][I][app:161]: ESP32 Chip: ESP32-C3 rev0.4, 1 core(s)

All the logs from ESPHome look fine:

INFO ESPHome 2026.5.2
INFO Loaded validated config cache for emontx6.yaml, skipping validation.
INFO Starting log output from emontx6.local using esphome API
INFO Successfully resolved emontx6.local in 0.066s
INFO Successfully connected to emontx6 @ 192.168.86.22 in 0.005s
INFO Successful handshake with emontx6 @ 192.168.86.22 in 0.055s
[15:58:05.030][I][app:154]: ESPHome version 2026.4.5 compiled on 2026-05-19 16:28:04 +0100
[15:58:05.034][I][app:161]: ESP32 Chip: ESP32-C3 rev0.4, 1 core(s)
[15:58:05.035][C][logger:219]: Logger:
[15:58:05.035][C][logger:219]:   Max Level: DEBUG
[15:58:05.035][C][logger:219]:   Initial Level: DEBUG
[15:58:05.035][C][logger:226]:   Log Baud Rate: 115200
[15:58:05.035][C][logger:226]:   Hardware UART: USB_SERIAL_JTAG
[15:58:05.038][C][logger:235]:   Task Log Buffer Size: 768 bytes
[15:58:05.045][C][uart.idf:254]: UART Bus 0:
[15:58:05.050][C][uart.idf:152]:   TX Pin: GPIO21
[15:58:05.050][C][uart.idf:152]:   RX Pin: GPIO20
[15:58:05.050][C][uart.idf:259]:   RX Buffer Size: 2048
[15:58:05.050][C][uart.idf:259]:   RX Full Threshold: 114
[15:58:05.050][C][uart.idf:259]:   RX Timeout: 2
[15:58:05.054][C][uart.idf:268]:   Baud Rate: 115200 baud
[15:58:05.054][C][uart.idf:268]:   Data Bits: 8
[15:58:05.054][C][uart.idf:268]:   Parity: NONE
[15:58:05.054][C][uart.idf:268]:   Stop bits: 1
[15:58:05.054][C][uart.idf:268]:   Wake on data RX: ENABLED
[15:58:05.060][C][emontx_ha_bridge:035]: EmonTx HA Bridge:
[15:58:05.061][C][emontx_ha_bridge:036]:   HA events : esphome.emontx_raw, esphome.emontx_json
[15:58:05.061][C][emontx_ha_bridge:037]:   HA service: send_command
[15:58:05.074][C][emontx:080]: EmonTx:
[15:58:05.094][C][emontx:088]:   Sensor support: DISABLED
[15:58:05.094][C][captive_portal:134]: Captive Portal:
[15:58:05.094][C][wifi:1505]: WiFi:
[15:58:05.094][C][wifi:1505]:   Local MAC: 88:56:A6:6C:C4:A4
[15:58:05.094][C][wifi:1505]:   Connected: YES
[15:58:05.098][C][wifi:1216]:   IP Address: 192.168.86.22
[15:58:05.103][C][wifi:1227]:   SSID: [redacted]
[15:58:05.103][C][wifi:1227]:   BSSID: [redacted]
[15:58:05.103][C][wifi:1227]:   Hostname: 'emontx6'
[15:58:05.103][C][wifi:1227]:   Signal strength: -47 dB ▂▄▆█
[15:58:05.103][C][wifi:1227]:   Channel: 1
[15:58:05.103][C][wifi:1227]:   Subnet: 255.255.255.0
[15:58:05.103][C][wifi:1227]:   Gateway: 192.168.86.1
[15:58:05.103][C][wifi:1227]:   DNS1: 192.168.86.1
[15:58:05.103][C][wifi:1227]:   DNS2: 0.0.0.0
[15:58:05.104][C][esphome.ota:071]: Over-The-Air updates:
[15:58:05.104][C][esphome.ota:071]:   Address: emontx6.local:3232
[15:58:05.104][C][esphome.ota:071]:   Version: 2
[15:58:05.104][C][esphome.ota:078]:   Password configured
[15:58:05.118][C][safe_mode:026]: Safe Mode:
[15:58:05.118][C][safe_mode:026]:   Successful after: 60s
[15:58:05.118][C][safe_mode:026]:   Invoke after: 10 attempts
[15:58:05.118][C][safe_mode:026]:   Duration: 300s
[15:58:05.137][C][safe_mode:043]:   Bootloader rollback: support unknown
[15:58:05.137][C][web_server.ota:256]: Web Server OTA
[15:58:05.137][C][api:235]: Server:
[15:58:05.137][C][api:235]:   Address: emontx6.local:6053
[15:58:05.137][C][api:235]:   Listen backlog: 4
[15:58:05.137][C][api:235]:   Max connections: 8
[15:58:05.140][C][api:242]:   Noise encryption: YES
[15:58:05.186][C][mdns:194]: mDNS:
[15:58:05.186][C][mdns:194]:   Hostname: emontx6
[15:58:14.683][D][emontx:034]: Received line: {"MSG":1618,"V1":240.53,"P1":94,"P2":0,"P3":0,"P4":0,"P5":0,"P6":0,"E1":4316948,"E2":-6,"E3":-35,"E4":-87,"E5":-52,"E6":-98}
[15:58:24.503][D][emontx:034]: Received line: {"MSG":1619,"V1":240.61,"P1":92,"P2":0,"P3":0,"P4":0,"P5":0,"P6":0,"E1":4316949,"E2":-6,"E3":-35,"E4":-87,"E5":-52,"E6":-98}
[15:58:34.325][D][emontx:034]: Received line: {"MSG":1620,"V1":240.70,"P1":93,"P2":0,"P3":0,"P4":0,"P5":0,"P6":0,"E1":4316949,"E2":-6,"E3":-35,"E4":-87,"E5":-52,"E6":-98}
[15:58:44.143][D][emontx:034]: Received line: {"MSG":1621,"V1":240.69,"P1":94,"P2":0,"P3":0,"P4":0,"P5":0,"P6":0,"E1":4316949,"E2":-6,"E3":-35,"E4":-87,"E5":-52,"E6":-98}

Looks like there a crash :thinking:

Yes (this is mine and unrelated to Glyn’s problem).

Apart from this line!

@FredM67 - that is an error generated by the emontx component.

I’ve moved it to a new conversation.

@Gwil I think we could do with an ESPHome topic somewhere, or perhaps and emonWiFi topic as they are closely linked (or both).

This line would tell, sensors have been disabled… Thats why there’s no sensor. If it crashes, there’s for sure a bug somewhere.
Have to take a look.

Have they returned? Have you tried a full reboot?

Do you have an input to emoncms running as well?