Troubleshooting

Panel not reachable

Symptom: Cockpit tile says "not reachable", views don't load.

Check in this order:

Does the panel have power and network? (LED status on the panel, router.)
Lupus with direct address: Is the stored address still correct? After a router change or a new IP, "Edit" → update the address. With DynDNS: does the name still resolve?
Lupus P2P: Header says "P2P connecting"? Establishing can take a minute after a panel restart. If it stays that way, check on the panel whether P2P remote access is still enabled.
VESTA: The panel reports in to our server on its own – after a power or internet outage this takes a minute or two.

"The panel does not offer this function over remote access"

VESTA only: the firmware doesn't provide some functions (certain settings pages) over the remote tunnel. Two ways out:

Store an address under Edit that this server can reach (VPN or DynDNS) – those functions then automatically run over the direct route.
Or perform the step once on the panel's own web interface.

"Device is currently unreachable"

The panel has no radio contact with this device. Check the device's battery/power, check the location (Sensors → Range), if necessary move the device closer to the panel or plan a repeater.

Arming is rejected

"This code is not authorised for this area" (VESTA): the entered code is not among the area's user codes. The administrator code doesn't count – create a user code under Alarm system → PIN codes.
"No user code is stored for area X": create a user code first, then switch.
Missing permission: switching requires the arm/disarm permission on this panel.

A rule doesn't fire

Lupus: In 9 out of 10 cases the assignment is missing – rule in a group? Group in the active profile? See Rule groups and profiles.
Rule set to active?
Is the condition really met? (Time window, right detector, right mode.) The log shows whether the trigger arrived at all.

"Automations not yet known" (VESTA)

Not an error: the panel has never reported its rules. Save one rule once (or store a reachable address) – after that the inventory is permanently there. Background in the chapter Adding a VESTA panel.

AI assistant reports missing permission

The message names the missing scope (e.g. "settings"). Two possible causes, both fixed under AI access or Access:

The key/link was created without this scope – re-link or generate a new key with the right scope.
The owner's account lacks the permission on this panel – the main user can grant it under "Access".

No camera image

"View cameras" permission present? (Installers: operator approval additionally required – see Cameras.)
Camera online in the panel? Camera Wi-Fi changed?
Systems reachable only via P2P deliver images at a lower rate – wait briefly instead of reloading.

Use your username or email address; reset the password via Forgot your password if needed.
With 2FA: check the phone's clock (TOTP needs correct time) or use a backup code.
Account not yet approved? During the beta, accounts are approved individually – usually within a day.

If none of this helps

Write to us – with the panel's name, the approximate time and the exact message. The log (System → Log) and the header display ("Direct"/"P2P …") are gold for diagnosis.