Visonic Intruder Alarm
davesmeghead/visonic · v0.12.6.0
Visonic Custom Component for integration with Home Assistant
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
alarm_control_panel | Security system | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) | |
select | Mode picker (as switches) |
1 report below say how a device from this integration behaves in the Home app.
What people report
Local push support for Visonic PowerMax and PowerMaster panels, plus a newer cloud server option. Users report entity update problems on some PowerMax Pro firmware and errors when exposing the panel through HomeKit.
- Works3
- Partly works2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Visonic MCT-302 sensor | Works Local | Wrong sensor type fixed after owner added the sensor definitionSaved copyHi, Thanks for the info. You have 2 choices .... 1. Set your logger settings to debug as per the wiki here and post the sensor settings from the log file, here are my settings as an example ``` [Process Settings] Processing settings - panel code index 0447 [Process Settings] Z01 : VisonicSensorRef=0XE4 zoneInfo=0XC ZTypeName=Interior Chime=Off SensorType=motion zoneName=Kitchen [Process Settings] Z02 : VisonicSensorRef=0XE4 zoneInfo=0XC ZTypeName=Interior Chime=Off SensorType=motion zoneName=Living room [Process Settings] Z03 : VisonicSensorRef=0XD3 zoneInfo=0XC ZTypeName=Interio Excerpt saved from GitHub on 2026-10-23. | Issue #94 · 2023-09 | |
| Visonic PowerMaster 30 (cloud server) | Works Cloud | Cloud server option found no entities until fix in 0.13.0.37+Saved copyHi, I just wanted to test the Version 0.13.0.37 Visonic Cloud Server Option. I could add: Visonic Cloud Server - Panel 0, Serial xxxxxx, PowerMaster 30 But I can't find any Devices or Entities. Do I muss something or is there any Bug ? I am user a Power Master 30 and the latest Version of Home Assistant: Installation method Home Assistant OS Core 2026.8.3 Supervisor 2026.08.0 Operating System 18.2 Frontend 20260729.7 Excerpt saved from GitHub on 2026-10-23. | Issue #275 · 2026-08 | |
| Visonic PowerMaster PIR camera | Works Local | PIR camera images, request button and saved clips supportedSaved copySummary End-to-end support for PowerMaster PIR camera images. - Display, decode F4 PIR camera frames into an `image` entity per camera. - Request, per-camera "Request image" button. - F4 image ack, compute the ack checksum (CRC-16/CCITT) and use the correct ack scheme so the panel advances through and *completes* the image sequence instead of retransmitting/stalling. Optional opt-out (`visonic_no_ha_f4_ack`) when an external serial bridge answers the acks. - Saved clips, each capture is saved as a per-camera animated GIF (+ frames) under HA's media directory, in one sub-folder per camera. … Excerpt saved from GitHub on 2026-10-23. | PR #255 · 2026-07 | |
| Visonic PowerMax alarm panel | Partly works | Broken in Home Alarm panel state dispatch errors logged with HomeKit integration; owner blames core | Panel works; alarm state events raise errors for HomeKit integrationSaved copy… helpers/event.py:341 Eerst voorgekomen: 15 september 2026 om 23:50:10 (4 gebeurtenissen) Laatst gelogd: 15 september 2026 om 23:50:40 Error while dispatching event for alarm_control_panel.visonic_alarm_2_2 to >> Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 341, in _async_dispatch_entity_id_event hass.async_run_hass_job(job, event) ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 935, in async_run_hass_job hassjob.target(*args) ~~~~~~~~~~~~~~^^^^^^^ File … Excerpt saved from GitHub on 2026-10-23. | Issue #280 · 2026-09 |
| Visonic PowerMax Pro | Partly works Local | Arm/disarm work but sensor entities stopped updating until reload; range and firmware suspectedSaved copyYour panels are reporting what they are as follows: Panel 1: [handle_msgtype3C] PanelType=2 : PowerMax Pro , Model=27 Powermaster False Panel 2: [handle_msgtype3C] PanelType=4 : PowerMax Pro Part , Model=87 Powermaster False These are extracted from your log file Even if they physically look the same, Panel 2 is reporting as a PowerMax Pro Part with a later Model number than I have myself (71). Panel 2 will auto enroll, that is why there are no panel settings to manually enroll. Now on to the main issue as I've taken a bit more of a look at your log file. I can see that you're using the … Excerpt saved from GitHub on 2026-10-23. | Issue #118 · 2024-07 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Found automatically over
- Bonjour (zeroconf)
Details
| Installs (analytics) | 111 (0.02%) |
|---|---|
| GitHub stars | 111 |
| Latest version | 0.12.6.0 (2026-10-20) |
| Set up in the UI | Yes |
| Maintainers | @davesmeghead |
| License | Apache-2.0 |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
Sources
- Documentation: https://github.com/davesmeghead/visonic/wiki
- Source code: https://github.com/davesmeghead/visonic
- Issues: https://github.com/davesmeghead/visonic/issues
- HACS: https://hacs.xyz
