FAQ - cbrightly/hass-aidot-cameras GitHub Wiki
Is this the official AiDot integration? No. It is a community-maintained, camera-capable fork of the upstream AiDot-Development-Team/hass-AiDot (which is lights-only). It is not affiliated with or endorsed by AiDot or Leedarson.
What's the difference between this fork and upstream? Upstream supports lights only. This fork adds full camera support - WebRTC live streaming, motion/person events, two-way audio, PTZ, cloud-recording playback, and the camera control entities.
Do I need go2rtc? For low-latency browser playback, yes. Standard cameras stream through Home Assistant's built-in go2rtc, and fall back to higher-latency HLS without any go2rtc. SDES cameras (the L2 battery models and the A001064 PTZ) need a separate go2rtc - the go2rtc add-on or the WebRTC Camera integration - and are not streamed at all without one; Settings -> Repairs says so. Lights need neither go2rtc nor ffmpeg. See Installation.
Registering a camera with go2rtc also makes it pullable as plain RTSP by anything that can reach go2rtc, with no Home Assistant login. See What go2rtc exposes.
Why does the first view of a camera take so long? A cold (idle) camera runs a proprietary handshake before video appears. The camera starts sending video in about 2.4-3.3 s on a mains standard model, 2.3-2.8 s on a mains SDES model (PTZ / spotlight), and 3-6 s on a battery model, where nearly all of it is the camera waking. A warm view starts immediately. What you see on a dashboard adds Home Assistant's own stream pipeline on top - see Cameras.
A battery camera's figure is almost all camera wake-up time, and it varies - an occasional first view takes considerably longer than the range above. The view waits it out rather than failing. See Cameras.
Why can't Home Assistant connect while the AiDot app is open? Each camera serves only one live session at a time. Close the live view in the app first. Snapshots and recorded clips are unaffected.
Where did the HD/SD toggle go?
Removed in 2.11.9. Cameras accept the command and report the new value back, but
the video is identical either way - same 1280x720, same bitrate - so the control
was reporting a setting that changed nothing. 2.12.0 clears the leftover
select.<camera>_resolution entity when you upgrade. See
Resolution.
I still see an unavailable select.<camera>_resolution.
Upgrade to 2.12.0 and reload the integration once; the cleanup runs at setup.
My PTZ buttons / battery sensor are missing.
Some entities are disabled by default (PTZ buttons, sensor.battery,
sensor.sd_card_status). Enable them from the device page. See
Supported devices.
Why don't I see recorded clips in the Media panel? Cloud recordings require an active AiDot cloud storage subscription on the camera. See Cloud recordings.
Can I use a device that isn't in the supported list? Most likely yes - the list reflects only what's been explicitly confirmed. If a device works (or doesn't), please open an issue so the list can be updated.
Where do I report a bug or request a feature? On the issue tracker.