Skip to content

v1.0.18

Choose a tag to compare

@lollox80 lollox80 released this 01 Oct 23:41
fe72f0d

Highlights

  • A shorter page in HACS: what the integration does, compatibility, installation in four steps and links; the full reference is now in docs/, in English and Italian (#69), with badges at the top (#71).
  • HACS installs from a release zip (#72), attached by a workflow to every release: nothing changes for you, and the README can now show a download count.
  • One slow card no longer delays the others (#67, @Apeiv): each audio WebSocket client has its own queue.
  • simulate_ring is a whole test ring (#68, @Apeiv): ringing state, doorbell event and webhooks, then it ends by itself, with no SIP traffic.

Changed

  • HACS installs from a release zip: every release gets vimar_intercom.zip attached by a workflow, and
    HACS downloads that instead of the source archive (zip_release). Nothing changes for users; it lets the
    README show a download count (installs and updates from the first release with a zip on).
  • README badges: latest release, HACS, minimum Home Assistant version, test status, licence and stars.
  • Documentation: the README (the page HACS shows) is now short: what the integration does, compatibility,
    installation in four steps, and links. The reference moved, unchanged, to docs/ in English and Italian:
    CONFIGURATION, ENTITIES, CARD, TROUBLESHOOTING, plus an Italian HOMEKIT page. Three statements
    were corrected on the way: the away message entities are admin-only since 1.0.17, the 40515's port 80
    refuses the connection, and how long "Vedi esterno" lasts depends on the plant.

Fixed

  • One slow card no longer delays the others: each audio WebSocket client gets its own small
    queue and sender, so the voice and video loops never wait for a client's network. A client that
    falls too far behind drops its own backlog and gets video again from the next keyframe (#54).
  • vimar_intercom.simulate_ring now simulates a whole ring (#33 item 14): the
    state goes to ringing (card popup, sensors, binary sensor), the doorbell event and the start
    webhook fire, and after duration seconds (default 20) it ends like an unanswered ring, end
    webhook included. Before, the end never came and a doorbell switch driven by the webhooks stayed
    on. Still no SIP traffic: Answer just ends it, the away message never answers it, a real ring
    replaces it, and it is not written to the ring log or counted in the stats.