After updating a remote Intel NUC device from balenaOS 2.48.0+rev3 to balenaOS 2.50.1+rev1, the device went offline. Sometimes the device gives the api heartbeat true status after visiting the device diagnostics - supervisor state page, but the api heartbeat goes back to false afterwards (seems like a little bug).
The device api still reports:
"provisioning_progress": 50, "provisioning_state": "Running OS update",
Any suggestions? We have had some other Intel NUC devices going offline after an update in the past, having to execute a power cycle to solve the problem. But that is not always possible without manual intervention.
Thanks in advance.