Ubiquiti
UniFi Access Intercom Viewer UA-Int-Viewer
Doorbells · Security
Partly worksLocal
1 report: 1 says it partly works.
Reported with 1 integration: UniFi Access.
What people report
| Integration | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| UniFi Access | Partly works Local | Websocket updates with null category caused validation errors; fix expected in 2026.5Saved copyThe problem I’m seeing repeated websocket parsing failures from the UniFi Access integration in Home Assistant which I alluded to in #167128 and was finally able to chase down: [code] I was able to capture the exact offending raw websocket payload. ## What is causing the error The failing event is an `access.data.v2.device.update` from my Intercom Viewer: - `device_type`: `UA-Int-Viewer` - firmware: `1.5.30` - the payload contains: - `cap: null` - `category: null` The parser currently expects `category` to be a list for `V2DeviceUpdate`, so this raises a validation error before Home Assistant … Excerpt saved from GitHub on 2026-10-23. | Issue #167698 · 2026-04 |
Each row is one report from a GitHub thread, an integration’s docs, or r/homeassistant. Check the date and the linked source before you buy.
In ReReHome
Once Home Assistant’s HomeKit Bridge shares it, this device reaches Apple Home as a HomeKit accessory behind your Home Assistant bridge, so ReReHome shows and controls it like any other.
Identifiers
| Brand | Ubiquiti |
|---|---|
| Model | UA-Int-Viewer |
| Category | Doorbells |