Arvio Core
Arvio Core on UGREEN NAS
UGOS Pro with its Docker app, as a project from compose.yml.
Arvio Core as a Docker project on UGOS Pro, from the same compose.yml as on any Linux. The NAS downloads SFK's ready images and activates with the code from your invitation.
What you need
- 64-bit Linux with Docker and Docker Compose, on x86-64 or ARM64.
- Host networking for the container (network_mode: host): Arvio finds devices on the local network.
- About 1.4 GB of disk for the two images, and room for your data.
- Ethernet to the router.
- The machine stays on and starts by itself after a power cut.
Steps
Ask for an invitation
On the Arvio Core page, with your email. SFK emails you the activation code, ARV-XXXX-XXXX, valid for 7 days for one installation.
Download and fill in compose.yml
From https://arvio.systems/core/compose.yml, on your computer. On the ARVIO_ACTIVATION_CODE line, put your code in place of ${ARVIO_ACTIVATION_CODE:-}.
Upload it to the NAS
With UGOS's file manager, or from your computer over SMB, into a folder, for example /volume1/docker/arvio.
Docker → Project → Create
Name it arvio, pick the folder you uploaded and the file compose.yml. Then start it: the NAS downloads SFK's images.
Check that it is healthy
Within a minute the arvio-core container must read healthy in Docker's list.
Sign in to Arvio Home
At home.arvio.systems, with the invitation's email. Your home shows up there as soon as the machine activates, and you are its owner.
Zigbee and Z-Wave USB sticks
Zigbee: yes, with a USB stick
The stick goes into the machine on a short USB extension. In a container it is passed in with the devices: line of compose.yml, once no other program holds it.
Z-Wave: yes, with a USB stick or a controller
The Z-Wave stick goes in like the Zigbee one, and into a container with the same devices: line. Or Z-Wave goes through a Fibaro or Yubii Home controller on the network.
Updates
SFK sends Arvio Core updates from its Console, signed with its key; the machine refuses anything unsigned. Core tries a new version and keeps it only if it starts healthy and stays up for a minute; if it is not healthy within 5 minutes, it goes back to the one before. The images change rarely; when a new one comes out, docker compose pull and docker compose up -d, and it always wins over an older update. Docker and the operating system itself are yours to update.
Backups
Every night at 03:30 Core encrypts its data for two keys, the owner's and SFK's, and keeps the newest 7 copies, inside its data volume. Keep a copy of the volume somewhere else too, for example with the NAS's snapshots.
Without internet
Lights, heating, blinds, scenes, automations and wall panels carry on. What stops: access from outside, updates, TRU and whatever goes through a cloud, such as Ajax.
See also
Tell us about your space
Tell us what you have and what you want, and we will work out together what your space needs.
