FlashMQ reconnect issue and triggered dbus-flashmq VRM registration race condition #1269
Assignees
Milestone
Comments
wiebeytec
added a commit
to victronenergy/dbus-flashmq
that referenced
this issue
May 15, 2024
When one bridge was connected and the other one wasn't, the MQTT topics for connection status signalled 1 and 0 respectively. This caused it consider it a 'connection/disconnection' event. This fixes installations continously registering at VRM when one bridge was connected and the other wasn't. victronenergy/venus#1269
|
FlashMQ 1.13.0 fixes it. |
mpvader
added a commit
to victronenergy/meta-victronenergy
that referenced
this issue
May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A bridge reconnect issue (triggered under certain circumstances) was found in FlashMQ. Fix has been written, extra testing underway.
A situation that can subsequently arise, is that of two bridges, one is connected and the other is not, which triggers a bug in dbus-flashmq where the connection state
$SYStopic updates of those bridges race with each-other and keep redoing the VRM token registration (which is an action done on disconnect normally).The text was updated successfully, but these errors were encountered: