Maarten

After some minutes, the value started flipping again. I've set the max import back to 6A at 11:09, variation increases.  Why does this happen?

It's the EVSE that is throttling back and forth: https://photos.app.goo.gl/iqvHoNuMvBxxS5LX7 But why? Setting the import to 0A make the current stable again.

The measurements are p1 telegrams, the same as the sensorbox receives. (Which is blinking green)

> Any news in enabling the wifi in the sensorbox? I would also like to intergrate into my home automation and before I put too much effort in trying to...

I 2nd that. Now I need to boot my desktop to debug MQTT clients, because I have a raspberry as desktop in my toolshed.

I'm digging into the logs (/var/log/ebusd.log) and noticed [bus errors] at the same time as the clicking in the VWZ AI happened. Among the regular log entries messages, these things...

Running over night still yields [bus errors]: 2024-03-29 00:04:43.181 [bus error] poll basv Hc1ActualFlowTempDesired failed: ERR: read timeout 2024-03-29 00:21:13.162 [bus error] poll basv OpMode failed: ERR: read timeout 2024-03-29...

Currently on Build: [20240317] I saw the symptoms about a month ago and then switched to the JonesPD repo. I've switched to --configpath=https://cfg.ebusd.eu and ran the ebusd again, bus errors...

Running for a while noticed a bus error signal lost: 024-03-30 15:08:48.280 [mqtt error] decode basv SFMode: ERR: invalid position 2024-03-30 15:08:52.017 [bus error] signal lost 2024-03-30 15:08:52.325 [bus error]...

Ok, those read timeouts are nothing to worry about then. Updated to 20240330 yesterday, does the update have any effect on the symptoms: > avoid unnecessary wait when sending to...