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
If Miniserver gets disconnected, eg. by saving a new config file to Miniserver, the online node sends a lot of messages with value false.
Ideally the not connected message in Node Red shold be sent only once if disconnetc happens. That would be the same behavior as for the connect message, this connect message is only sent once per connect.
Can easily be reproduced on MS Gen 2 by saving config to the Miniserver, happens not always bot often enough.
The text was updated successfully, but these errors were encountered:
If Miniserver gets disconnected, eg. by saving a new config file to Miniserver, the online node sends a lot of messages with value false.
Ideally the not connected message in Node Red shold be sent only once if disconnetc happens. That would be the same behavior as for the connect message, this connect message is only sent once per connect.
Can easily be reproduced on MS Gen 2 by saving config to the Miniserver, happens not always bot often enough.
The text was updated successfully, but these errors were encountered: