Video Doorbell WiFi (the most popular one) has no configs block at all, plus actual data errors:
-
Protocols: ["http"] — wrong, it supports RTSP and ONVIF like the PoE version
-
Power listed as "rechargeable battery / hardwired optional" — wrong, the WiFi doorbell is wired-only (existing 12–24V doorbell wiring); the battery doorbells are the new 2026 models
-
nvr_compatible: false — it works with Reolink NVRs and the Home Hub
Video Doorbell PoE has a configs block, but it's the generic Reolink camera template. For a doorbell, the things people actually need are missing:
-
The button-press event — that's the entire point. Home Assistant's native Reolink integration exposes it as a Visitor sensor via ONVIF; Frigate users typically catch it through HA or MQTT. None of that is mentioned.
-
Two-way audio setup via go2rtc (needs the audio re-encoded to opus for WebRTC talk-back) — the most-asked Reolink doorbell question in the Frigate community.
Video Doorbell WiFi (the most popular one) has no configs block at all, plus actual data errors:
Protocols: ["http"] — wrong, it supports RTSP and ONVIF like the PoE version
Power listed as "rechargeable battery / hardwired optional" — wrong, the WiFi doorbell is wired-only (existing 12–24V doorbell wiring); the battery doorbells are the new 2026 models
nvr_compatible: false — it works with Reolink NVRs and the Home Hub
Video Doorbell PoE has a configs block, but it's the generic Reolink camera template. For a doorbell, the things people actually need are missing:
The button-press event — that's the entire point. Home Assistant's native Reolink integration exposes it as a Visitor sensor via ONVIF; Frigate users typically catch it through HA or MQTT. None of that is mentioned.
Two-way audio setup via go2rtc (needs the audio re-encoded to opus for WebRTC talk-back) — the most-asked Reolink doorbell question in the Frigate community.