You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the dbus-listener.js does not reconnect, if the connection to the system dbus was lost for some reason. This will cause the victron energy nodes to hang in case the dbus service is restarted (or dbus service started after node-red, for example).
Note that; as in real life your code will run on the venus device; this will never happen.
I know this is an old issue, but I just ran into this issue. Your statement is only true if you're using this on the Venus device itself, if you deploy them to an external node-red instance then this can and will happen, a simple reboot of the Venus device is enough to trigger the problem.
Currently, the dbus-listener.js does not reconnect, if the connection to the system dbus was lost for some reason. This will cause the victron energy nodes to hang in case the dbus service is restarted (or dbus service started after node-red, for example).
See
sbender9/signalk-venus-plugin#7
and
https://github.com/sbender9/signalk-venus-plugin/blob/master/dbus-listener.js
The text was updated successfully, but these errors were encountered: