Closed spamajor closed 1 year ago
If you are running some other software at the same time I will have to ask you to reset the device, reinstall dbus-mqtt-devices on it's own and then reboot. Judging by the post you shared earlier it sounds like it could be shm-et340 that is causing this problem not dbus-mqtt-devices.
I installed the firmware back to 2.94 and tadaa the mqtt works again. your script is disabled, but et340 is active.
I would have prefered you install and test the other way round, install dbus-mqtt-devices but not sun-et340.
Have you rebooted yet, since it was rebooting that caused you problems.
I performed a reboot and mqtt works fine. To reset the whole system is not so easy because this is my productive system that powers my house. Do you have a test system where you can test it maybe?
At this point in time, I feel dbus-Mqtt-devices is well tested. I haven't seen anything to suggest the problems you are experiencing are caused directly by dbus-Mqtt-devices. Unless you can provide evidence of the contrary, I am sorry, but I will be closing this issue.
The mqtt service stopped working and I have no idea what happened.
Do you know that MQTT will stop sending data after ~1min? For me that was a surprising behave at the beginning.
Yes i know that. That's why you have to send the keepalive every 55 seconds ;)
Nothing more I can do here so closing this issue.
Hi, on my Raspberry Pi PyYalm fails on install and with workaround the storage + VRM updates breaks on ver 2.92. See screetshot: