Open mpvader opened 2 weeks ago
We have the heartbeat status, which we can expose from the MqttProvider - this basically allows us to know whether the device is connected to the VRM. Just need to figure out some "rules" for how to react to this heartbeat inactive status.
The system in this screenshot is offline, yet gui-v2 now says connected.
i think I know why, (even though wasm cannot connect to the device itself., it can connect to mqtt cloud) so need to come up with something for this.
there are two related issues: 1) perhaps vrm should show some warning or something about system being offline before hand, however we don’t want to delay making it possible to open gui-v2 by first doing a mqtt online check.. 2) the wording and terms shown during that connection process could be made less technical 3) the whole loading process when loading locally can also be better