01-04-2026, 07:05 AM
Hi,
@admin - thank you for the updates, unluckily i have no USB-RS485 available yet to test the latest firmwares. See below suggestion to User Vega which is working OK for two devices at the moment.
@Vega - we ran into same problem as you with N30 devices. Our solution in ESPHome now was:
-removed all Energy and Current Sensors from Modbus
-create new Energy Sensors calculated by ESPHome Link with source data coming from N30 Power readings
-tweaked modbus interval for power Sensors down to 3s
To mention it, the energy Sensors in ESPhome reset at Midnight (daily_energy), but no problem for Homeassistant statistics.
An ESPHome Device Update may also Reset a daily Energy Sensor.
For correct energy calculation time component is important. Setup high priority during boot to avoid miscalculated energy sensors (did happen on mine previously)
br
@admin - thank you for the updates, unluckily i have no USB-RS485 available yet to test the latest firmwares. See below suggestion to User Vega which is working OK for two devices at the moment.
@Vega - we ran into same problem as you with N30 devices. Our solution in ESPHome now was:
-removed all Energy and Current Sensors from Modbus
-create new Energy Sensors calculated by ESPHome Link with source data coming from N30 Power readings
-tweaked modbus interval for power Sensors down to 3s
To mention it, the energy Sensors in ESPhome reset at Midnight (daily_energy), but no problem for Homeassistant statistics.
An ESPHome Device Update may also Reset a daily Energy Sensor.
For correct energy calculation time component is important. Setup high priority during boot to avoid miscalculated energy sensors (did happen on mine previously)
Code:
esphome:
name: kinconyn30
friendly_name: kinconyn30
on_boot:
priority: -100
then:
- delay: 1s
- wait_until:
condition:
lambda: |-
return id(ha_time).now().is_valid();br

