as there is no way to error out of the two publish states, there is no way to reconnect to an MQTT Server once a connection is lost. => Yes, I have seen this effect during testing too, thanks for reminding me to make this ticket😀
A solution had already been thought off but the current seqnums issue has higher priority.😔
Suggested solution;
After loss of connection, make sure the EoN can return to the offline step.
The trigger to detect this is programmed outside the StateMachine.
It is then forwarded into the state machine in form of an input command to let the EoN StateMachine go-to
The offline state.
The above mechanism will also trigger devices to go to plugged but offline as they monitor the EoN continuously.
Whenever the connection restores the EoN will reconnect and the devices will automatically follow after the connection is restored with no programming required (by design)
Diff:
Sounds simple but will probably prove to be difficult as many of the simple sounding problems do
Is implemented in trunk v1.3.3.5