Nomad 1.0.6 Release
Applies to: Nomad Release Track: Stable Version: 1.0.6 Requires action: Yes, once. See below.
Summary
Your system can now update itself overnight, which is what the switch always said it did. A false shore power alarm has been silenced, and when we let ourselves in to help, you now hear it from us rather than finding out later.
Overnight updates now actually happen
Automatic updates has been on by default since launch, the switch reported itself as on, and your system agreed. It was not updating, and never had. The overnight check ran and gave up before it got as far as looking for a new version, so no system on this build has ever taken an update on its own. Every signal said the feature was working, which is why it went unnoticed for as long as it did.
It now installs on its own, overnight, exactly as described: the switch has to be on and a version has to genuinely be waiting. If your system cannot work out what the latest version is, it waits rather than guessing. Not being able to check is not the same as knowing there is something to install.
Two quieter improvements came with it. An automatic update that is skipped because the disk is full, or because a backup is running, no longer raises a red banner and a failure entry for something you never asked for. It waits and tries again. And it no longer leaves the update card stuck showing "preparing" for a run that never started.
The fix travels inside the update it fixes, so it cannot arrive by the route that is broken. Open Settings, then Admin, and press Update now once to get onto 1.0.6. After that your system keeps itself up to date without you.
A shore power alarm you should not have had
Shore power dropped told some people their hook-up had failed when it had not.
A MultiPlus that finishes charging overnight switches itself off, and a unit that is off stops measuring its own input and reports zero volts. On that reading alone, a charger that has quietly finished its job looks exactly like a bollard that has tripped. Sensa now checks the unit's own state first and stays quiet when it is simply off. On a van with two inverters each alarm is paired to its own unit, so one being off never silences the other.
Restarting your system no longer sets it off either. A restart used to leave the watch primed, so the first proper reading afterwards, zero volts on a van that had never been plugged in, was read as the supply failing.
If your system cannot read the charger's state at all, the alarm still goes ahead. Not being able to check is not the same as being told all is well, and this is not the alarm to be clever about.
When we open support access, you hear it from us
You control remote support with a switch, and that is still true. Sometimes the fault is the thing stopping you reaching the switch, and in that case we can open a session from our end for a fault you have reported.
We now email you when we do, at the address on your Sensa account, at the moment we ask your system to let us in. It is sent from our end rather than from the van deliberately: a session opened this way is usually a session opened because your Home Assistant will not start, and a message that depends on the broken thing is no message at all.
The reason for opening it is no longer optional, and the name of the person who opened it now travels with it. The banner, the Log entry and the panel all carry both, so you can see who let themselves in and why, not only that somebody did.