[SEM-4-1-00 / NodOn] Bad power consumption since update ( Firmware v15 id 01.00.15)

[phanotaux]

What happened?

Consumption is false.
After recharching a car and then stopping the charge, the power is always high (2500W).

What did you expect to happen?

I expected the power was 0 after end of charge

How to reproduce it (minimal and precise)

Restart Nodon (power on/off) is not efficient .
'Reconfiguer' in HA/Z2M is ok, but I need to check a new charge process

Zigbee2MQTT version

2.9.2 (unknown)

Adapter firmware version

{"build":397,"ezsp":14,"major":8,"minor":0,"patch":2,"revision":"8.0.2 [GA]","special":0,"type":170}

Adapter

EmberZNet

Setup

os: #1 SMP PREEMPT_DYNAMIC Tue Apr 7 10:23:47 UTC 2026 - 6.12.77-haos - x64
node: v22.22.2
ha: true

Device database.db entry

No response

Debug log

No response

Notes

Device

definition: SEM-4-1-00 - NodOn (v0.0.0)
software_build_id: 01.00.15
date_code: undefined
endpoints:

{"1":{"bindings":[{"cluster":"haElectricalMeasurement","target":{"endpoint":1,"ieee_address":"0x943469fffefd6211","type":"endpoint"}},{"cluster":"seMetering","target":{"endpoint":1,"ieee_address":"0x943469fffefd6211","type":"endpoint"}}],"clusters":{"input":["genBasic","genIdentify","seMetering","haElectricalMeasurement","haDiagnostic"],"output":["genIdentify","genOta"]},"configured_reportings":[{"attribute":"activePower","cluster":"haElectricalMeasurement","maximum_report_interval":65000,"minimum_report_interval":10,"reportable_change":5},{"attribute":"rmsCurrent","cluster":"haElectricalMeasurement","maximum_report_interval":65000,"minimum_report_interval":10,"reportable_change":5},{"attribute":"acFrequency","cluster":"haElectricalMeasurement","maximum_report_interval":65000,"minimum_report_interval":10,"reportable_change":100},{"attribute":"powerFactor","cluster":"haElectricalMeasurement","maximum_report_interval":65000,"minimum_report_interval":10,"reportable_change":10},{"attribute":"rmsVoltage","cluster":"haElectricalMeasurement","maximum_report_interval":65000,"minimum_report_interval":10,"reportable_change":500},{"attribute":"currentSummDelivered","cluster":"seMetering","maximum_report_interval":65000,"minimum_report_interval":10,"reportable_change":10},{"attribute":"currentSummReceived","cluster":"seMetering","maximum_report_interval":65000,"minimum_report_interval":10,"reportable_change":10}],"scenes":[]}}

Health

time: Fri Apr 24 2026 11:49:35 GMT+0200 (heure d’été d’Europe centrale)
os.load_average: 0, 0.02, 0
os.memory_percent: 29.2662
process.memory_percent: 3.3115
process.uptime_sec: 15003

{"leave_count":0,"messages":650,"messages_per_sec":0.0434,"network_address_changes":0}

[Nerivec]

The issue should be reported to the device's manufacturer.

Meantime, you can try downgrading if the device supports it, you can use the checkbox in frontend.

[phanotaux]

Thanks for your answer.
I've reported the issue to Nodon.
I've downgraded my nodons from v15 to v11, but during night, all were again blocked to a fixed value.
I saw on HACS forum that it could be caused by Z2M (updated 2 times since yesterday)

[BastR]

Same problem here with 2 SEM-4-1-00.

The only solution for me was to pair again the module (without removing it in Z2M) and then press "Reconfigure" in the bottom right of the About page.