Lupus and VESTA compared
Common roots
Lupus Lupusec (XT1–XT4) and Climax VESTA – as well as Blaupunkt and Egardia – descend from the same manufacturer, Climax. Detectors, radio protocols and many concepts are identical or closely related; that's why the Alarmanlagenmanager serves both families with the same interface. The differences sit in the firmware and in remote access – and those are collected here.
The interface takes most of it off your hands: menu items your panel cannot handle are hidden automatically. This chapter explains what's behind that.
Connection and remote access
| Lupus | VESTA / Blaupunkt / Egardia | |
|---|---|---|
| Recommended route | P2P remote connection (QR code, no port forwarding) | Connection to our server (mode: direct or proxy) |
| Alternative | Direct address (LAN, VPN, DynDNS) | Additionally storable direct address for individual functions |
| Manufacturer cloud required? | No | No (direct) / manufacturer stays involved (proxy) |
| Manufacturer app afterwards | Usable independently | Loses remote access (direct) or keeps working (proxy) |
| Setup | Lupus chapter | VESTA chapter |
Technical background: over the remote route, Lupus panels speak the same complete protocol as locally. The VESTA firmware offers a fixed, smaller command set over remote access – for everything else the Alarmanlagenmanager automatically uses the stored direct address, if present, or tells you clearly that the step must be done on the panel itself.
Feature differences in the interface
| Feature | Lupus | VESTA |
|---|---|---|
| Home view, sensors, switching, cameras, log | ✓ | ✓ |
| Automation (IF→THEN rules) | ✓ | ✓ |
| Rule groups and profiles | ✓ – rules run only inside a group of an active profile | ✗ – saved rules apply immediately |
| Scenes | ✓ | ✓ (stored internally in the panel's rule table) |
| Universal remote control (IR/UPIC) | ✓ | ✗ |
| Statistics/measurement histories | ✓ | ✓ (queried per device, first build takes a moment) |
| Settings (email, SMS, GSM, DynDNS, sirens, reporting) | ✓ | ✓ – some pages only via the direct address |
Arm/disarm and codes
| Lupus | VESTA | |
|---|---|---|
| Code when switching in the browser | As configured on the panel | User code always required – the Alarmanlagenmanager checks it itself |
| Why? | – | The VESTA firmware would accept switching commands without a code; we don't allow that |
| Administrator code | – | Does not count for switching (the panel itself rejects it) |
| Per-code permissions | ✓ (e.g. "may only disarm") | ✗ – every user code may switch |
Automation: the fine points
- Lupus: After saving, a rule belongs in a rule group and the group in the active profile – otherwise it never fires (details). The rule editor and the AI integration guide you through this assignment.
- VESTA: No group/profile concept. But: the panel reports its rule inventory only after a rule has been saved once via the Alarmanlagenmanager (or a reachable address is stored) – before that, the view shows "automations not yet known".
- Rule names (VESTA): the characters
< > ' "are not allowed; the interface catches them before saving. - Battery devices (VESTA): write commands to sleeping devices (thermostats) take until the device's next wake-up.
Pairing detectors
The flow is the same (learning mode → button on the detector → adopt). One difference in detail: on VESTA the panel initially assigns its own values for area/zone/name on adoption; the Alarmanlagenmanager applies your wishes automatically right afterwards and verifies that the device was really created.
Cameras
Both families deliver images into the Alarmanlagenmanager. The transport differs: Lupus also via short P2P sessions (works even behind mobile connections), VESTA via the panel's media retrieval – for smooth live views a stored local stream address is recommended there.
For AI and Alexa: no difference
The AI interface and Alexa treat both families the same – the Alarmanlagenmanager translates every intent into the matching dialect. An assistant creating a rule doesn't need to know whether an XT2 or a VESTA sits behind it. Only the available features differ (a universal remote control, for example, exists only on Lupus – the tools for it are simply absent on VESTA).
Blaupunkt and Egardia
Blaupunkt and Egardia panels are technically VESTA devices under another label – everything in the VESTA part of this documentation applies to them as well. Special case, first device generation (around 2015): it only supports older encryption; the Alarmanlagenmanager runs a dedicated compatible access path for it – nothing changes for the setup.