Skip to main content

Comelit ViP / HSrv

Comelit ViP intercom controllers and HSrv home servers (Mini Handsfree 6741W, Planux Manager, HSrv 6741W) over the local icon-based HTTP API. GEM uses this to drive door / gate strikes, bus-attached lighting and shutter actuators, and to surface intercom call state. The cloud-mediated path is not used — everything goes direct on-LAN.

Prerequisites

  • HSrv firmware that exposes the local icon_desc.json / icon_status.cgi / user.cgi endpoints. Most HSrv 6741W, Planux Manager, and Mini Handsfree units on firmware 2.x do.
  • The HSrv on a reserved LAN IP (router DHCP reservation, or set statically on the unit itself).
  • The 4-digit installer or user code that signs into the local web UI at http://<hsrv-ip>/.

Setup steps

  1. Confirm http://<hsrv-ip>/ shows the Comelit ViP login screen and that the 4-digit code grants access.
  2. Create a Device using driver comelit_vip. Fill in ip and paste the 4-digit code into password (it is stored encrypted; the field is marked secure).
  3. Run the get_devices command on the device. The response is a flat list of icons, each with id, name, sub_type, and type. Door / gate releases typically appear with a name containing "Apri" or "Cancello".
  4. Create one GEM Zone per icon you want to control. Set zone.address to the numeric icon id from step 3.
  5. Set the zone's subsystem so verb dispatch maps correctly:
    • gate / dooropen / close actuate the strike.
    • lightson / off toggle the relay.
    • shadeopen / close / stop drive the shutter.
  6. (Optional) For dry-contact door strikes that need a momentary pulse, the pulse command is an alias for open and is the preferred verb in macros — it makes the intent obvious in the macro log.

Attribute reference

Required

AttributeTypeDescription
ipstringHSrv LAN IP. No scheme — driver builds http://<ip>:<port> internally.
passwordstring4-digit installer/user code. Stored encrypted (the name password triggers auto-encryption).

Optional

AttributeTypeDefaultDescription
portint80Override HTTP port if the HSrv runs behind a port-mapped NAT.
status_intervalint5000Per-icon poll interval in ms. 1000–60000.

Zone address format

zone.address is the numeric icon id returned by get_devices. Strings are accepted but treated as ints for the wire request — keep them numeric to avoid confusion.

Commands

CommandArgsNotes
open / pulseaddressSends action 1 to the icon. Use pulse in macros for door strikes.
closeaddressSends action 0.
stopaddressShutter stop (action 2).
on / offaddressSame as open / close — exposed so light-subsystem verbs route cleanly.
get_devicesEnumerates all DOM icons.
get_statusaddressReads one icon's status JSON.
logoutForgets the session cookie. Status loop re-logs in automatically.

Known limitations

  • The HSrv API is the only path supported. The Comelit cloud (vipmobile) flow is not implemented and not planned — it is unreliable and rate-limited compared to the LAN endpoint.
  • SIP audio / video preview of the intercom stream is out of scope. GEM surfaces "is the doorstation ringing?" via zone state but does not pipe audio.
  • Some HSrv firmware revisions emit a different icon-id space when accessed through the cloud-mediated bridge. This driver only reads the on-LAN icon ids; do not mix the two address sources.
  • Lighting dim levels are not yet implemented — only on/off through the icon action=0/1 path. If the bus actuator is a dimmer, the dim slider stays a no-op until that is wired.

Troubleshooting

  • Login keeps failing (driver logs "login failed"): verify the 4-digit code by signing in to http://<hsrv-ip>/ from a browser on the same LAN. The HSrv intentionally rate-limits repeated bad codes; wait a minute between retries.
  • get_devices returns an empty list: confirm the user code has admin privileges. Read-only codes can sometimes log in but see no icons.
  • State updates lag by tens of seconds: lower status_interval (default 5000 ms). Going below 1000 ms is rarely worth it; the HSrv tends to drop session cookies under heavy polling.
  • 401 in driver logs every few minutes: expected — the driver transparently re-logs in. If the cycle is constant, the HSrv has another active session (browser open elsewhere) bumping us off. Close the other session.