Want Arvio in your space? Tell us what you have and what you want. Talk to us ›

Language: Eng
Partner sign-in
Arvio
Contact

Trust

Reliability

What Arvio does when the internet, the power or a driver fails: the rules, the mechanisms and the design targets.

On this page
  1. When something fails
  2. After a restart: read, never write
  3. What happens to a command
  4. Updates that can go back
  5. Design targets
  6. The check before every release

A home has to keep working when the internet, the power or a piece of software fails. Here are the rules, the mechanisms and the design targets.

Works without the internet

  • Lights, climate and covers connected locally
  • Automations and scenes
  • Wall panels
  • The hub's logs

Needs the internet

  • The Home app and remote access
  • The TRU assistant
  • Devices that talk to an internet service, such as the Ajax alarm and weather
  • Notifications on your phone

When something fails

If…What happens
The internet or the cloud goes downLights, heating, automations and wall panels carry on from the hub. Arvio Home on your phone needs the internet to reach the house.
The power is cutThe hub starts by itself when power returns. On mini PCs this is a BIOS setting, and the installer tests it before handover. The outage is recorded in the log.
A driver crashesArvio Core restarts it, waiting longer each time, from 1 to 60 seconds. Core itself stays up.
Arvio Core hangsIf it stops reporting that it is alive for 30 seconds, the operating system restarts it.
The whole hub hangsThe board's hardware watchdog reboots it.
An update goes wrongThe hub goes back to the previous version without anyone asking.
There is no power or any way to reach itWe do not promise remote recovery. Nobody can reach a hub that is off from a distance.

After a restart: read, never write

The rule is that a hub starting up changes nothing in the house.

No replay

There is no command queue for when the hub comes back. What did not run will not run later.

No restoring state

The hub does not put devices back as they were. A light comes on after a power cut only if the device itself does that.

Missed time stays missed

A 22:00 automation does not run at 22:30 because the hub was off at 22:00.

A returning device is not a trigger

When a device reappears after a restart, that starts no automations.

What happens to a command

  1. One tap, one command

    Each intention gets its own identifier. The app never resends by itself. Retrying is your choice and counts as a new command.

  2. Hub offline

    The cloud refuses it immediately and stores nothing.

  3. Hub slow

    The command waits until it expires: up to 45 seconds for comfort, 30 for security. Then the screen says it did not happen and offers a retry.

  4. Only the hub confirms

    The cloud accepting a command does not mean it happened. Done means the hub answered.

Updates that can go back

Arvio Core and drivers

The hub downloads the update, checks SFK's signature twice, switches version and waits for a healthy answer. If none comes, it puts the previous version back.

Arvio OS with two slots

The system is read-only and exists twice. A new version goes into the slot that is not running. The computer starts from it once and keeps it only if Arvio turns healthy within 5 minutes.

Your data stays

Data lives on its own partition and does not change through an update or a rollback. The database is fully synced to disk on every write, so a power cut does not damage it.

Design targets

WhatTarget
Local control availableAt least 99.9% a month
From command to device confirmation, locally (Zigbee, Shelly)95% of commands in under 1 second
Recovery with no one involvedUnder 3 minutes
Updates that need a site visitNone
Data lost in a power cutOnly the last seconds of history
A crashing driverAffects only its own devices

The check before every release

Every release has to pass the same test before it goes out: 72 hours of continuous running, power cuts, killing and hanging Core and each driver, an update with a forced rollback, a day without internet, and a restore from backup.

One limit worth knowing: SFK's LAN drivers can share a process to use less memory. If that process goes down, they restart together, while Core stays up.

Read next

Tell us about your space

Tell us what you have and what you want, and we will work out together what your space needs.