Het rode lampje van de omvormer wou deze keer niet zeggen dat hij weer niet op de wifi raakte (zoals gewoonlijk), ik kon 'm mooi bereiken om daar de melding te lezen dat L en N gewisseld zijn π
Is niet fataal voor deze 1-fase aansluiting maar echt pro is het niet.
P1 actief en met ESPhome alles naar MQTT laten doorsturen
consumed power is mooi aan het updaten, produced blijft op nul staan π
meh, de watermeter zit niet in de config... rebuild vanavond
note to self: https://github.com/peno64/slimmemeter/wiki
oh no, that's not how to 'fix' dsmr water readings π
So I planned to dig into this and figure out why the water measurement config was giving an error when building esphome (according to this repo)
That was a very short debugsession
Not sure what the problem was because I can't find any recent changes that touch this, but hey...
Water meter data flowing now and one item off the todo list π
Now what?
Apparently gave up around 19:55 and even a power cycle doesn't fix it... #P1 #DSMR #smartmeter
@peturdainn I've got this one https://www.zuidwijk.com/product/slimmelezer-plus. I've had to reboot it 2β3 times in the past year while nothing had changed. I suspect Fluvius does something occasionally.
This seems different though β¦ π Is this the raw data, or already processed data?
@wimleers yeah, same product but with my own esphome config on it (no HA, but MQTT), the above errors are in the webinterface of esphome
This is my first project with esphome so I still have stuff to figure out.
Will run a debugbuild
reboots of the reader did not help, and didn't fancy killing my main fuses to reboot the fluvius meter :)
I removed the peak capacity entries(*) and now it works again
Or maybe it started working again during one of the tests
(*)
active_energy_import_maximum_demand_running_month
active_energy_import_maximum_demand_last_13_months