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
Currently, the onboarding screen will always show on start-up when run via wasm on a VRM read-only system. This is because the system is unable to write to /Settings/Gui2/OnBoarding to clear the onboarding flag.
Need a straightforward way to determine whether the system is read-only.
One possible solution is to set a cookie in this case, instead of writing a value via MQTT.
The text was updated successfully, but these errors were encountered:
Currently, the onboarding screen will always show on start-up when run via wasm on a VRM read-only system. This is because the system is unable to write to
/Settings/Gui2/OnBoarding
to clear the onboarding flag.Need a straightforward way to determine whether the system is read-only.
One possible solution is to set a cookie in this case, instead of writing a value via MQTT.
The text was updated successfully, but these errors were encountered: