Driver crashed looking up portal id about dbus-mqtt-devices HOT 6 CLOSED

Very puzzling. The driver gets the portal id before it even connects to MQTT so I don't see how the payload caused this. I guess we just wait and see if it happens again. Feel free to post another log file if it happens again over the next few days.

from dbus-mqtt-devices.

Sorry was my fault: was Sending:
"{ "clientId": pvInverterTest3, "connected": 1, "version": "1.0", "services": {"pv10" : "pvinverter"} }"
instead of this:
"{ "clientId": "pvInverterTest3", "connected": 1, "version": "1.0", "services": {"pv10" : "pvinverter"} }"
this crashed the thing :P

from dbus-mqtt-devices.

Thanks for sharing the error and your fix. Unfortunately I can't see how missing the quotes around pvInverterTest3 would have caused this particular error. The error points to a point in the code where the driver reads the VRM portal id from the dbus. An invalid json payload should not have gotten that far. Please can you send the whole log file. Besides, if a badly formatted json file causes the driver to crash, then the validation needs to be improved.

from dbus-mqtt-devices.

There is not much I can add from this file but here you go :)
current.txt

If you need an other file, let me know

from dbus-mqtt-devices.

Can you provide details about the Venus GX device you are using? CCGX, Cerbo, Raspberry Pi (which model) or other? What Venus OS version you are running?

The log file suggests things are very unstable. The driver is continually re-starting . That's not good.

from dbus-mqtt-devices.

A normal Cerbo

Since I fixed my mistake, the dbus-mqtt-devices not restarting anymore

Edit: /service/dbus-mqtt-devices: up (pid 4707) 1976 seconds this was always resetting after sending a "corrupt" payload

from dbus-mqtt-devices.