Loosing Network Connection
ssummers-lime opened this issue · 2 comments
While trying to publish data with QoS 0 using TCP, if the network connection is lost then the main application is not notified of the lost connection. When the write vi is called, an error is generated from the TCP write and is passed into the setConnected.vi. Since this vi has an error case to capture incoming errors, the lose of connection is never set. A quick fix would be to remove the case structure. The vi also generates a user event "connection event" but I did not find this event being registered anywhere.
@ssummers-lime
Thanks for this report. You are correct and the error case structure should be removed to allow the code to execute even with an upstream error.
I'll reference this bug in the MQTT-Connection repo for action.
This is fixed and released in MQTT_Connection package 3.1.4.
Will show up on vipm.io shortly.