Repository navigation
Lights
Any AiDot / Leedarson RGB, RGBW, CCT, or dimmable-white bulb is exposed as a
standard Home Assistant light entity:
- On / off
- Brightness
- Color (RGBW)
- Color temperature
The exact controls available depend on the bulb - a CCT bulb gets color temperature but not RGB, a dimmable-white bulb gets brightness only, and so on.
Light state is pushed over TCP and arrives almost instantly - there is no polling interval for lights. Changes made in the AiDot app or by a physical switch are reflected in Home Assistant promptly.
- Lights work without ffmpeg or go2rtc - those are camera-only requirements (see Installation).
- Standard Home Assistant light features apply: include them in scenes, use transitions, and group them as you would any other light.
A light whose address is outside every network Home Assistant is on (another subnet or VLAN) cannot be controlled locally. The address comes from discovery or from the cloud's last-known one. From 2.36.0, once its local login has failed enough times in a row, Settings -> Repairs shows the light, that address and Home Assistant's own networks. Move the light (or Home Assistant) onto the same network, or let the two networks route to each other; the issue clears by itself once a local login gets through, or when the light is removed. A light that is simply switched off, last seen on another subnet, can show it too, so check it is powered first.
AiDot for Home Assistant / camera-capable fork of AiDot-Development-Team/hass-AiDot / device communication via python-aidot-cameras / MIT licensed / Open an issue
Getting started
Cameras
- Cameras overview
- Dashboard cards
- PTZ control
- Two-way audio
- Resolution (removed)
- Cloud recordings
- On-device recordings
Lights
Using it
Help