Bring the wiki up to 2.35.0: four option pages, the defaults that are on, HLS audio, go2rtc repair; talk needs no live view Configuration options lists the four pages and every option with its current label and default (Pin camera video to H.264, Direct publish into go2rtc, Audio in HLS and recordings and In-sync audio for recordings are on; Open the clip inside the Home Assistant app is off). The HLS dialog has sound by default since 2.30.8. Cameras publish straight into go2rtc. Troubleshooting gains the duplicate-key repair issue, the pinned camera that answers H.265, the stale cached stream fixed in 2.30.6 and the clip that lost its first seconds. aidot.talk opens its own session when no live view is running; PTZ buttons follow what the camera advertises (the reference model pans only). The IR-light switch and the hub row are gone; the integration is listed as AiDot Cameras; the library floor is rc40.
Resolution: the app's Auto value, and what the app's switch actually does Two corrections, both from reading the AiDot app rather than reasoning about it. The sweep walked the numbered settings the command defines. The app's Auto is a value outside that set, so the sweep could not have sent it. Measured on its own: acknowledged, and the stream unchanged in that session and the next, like every other value. The page also guessed that the app's switch works by reconnecting and asking for something different. It does not. The app sends the same command, and when the camera acknowledges it the app changes the label on screen and reports success - there is no reconnect and no second request. So the switch looks like it works because the text moves. That is worth saying plainly for anyone who has used the app and formed an impression from it, since this page asks them to accept that the control does nothing here.
Resolution: settle it across every setting and both camera families The page proved the control inert using one model and the two settings the HD/SD toggle exposed. That left room for it working on a value or a camera nobody had tried, which is a fair thing for a reader to wonder. A Spotlight Cam PTZ was swept across all six values the command defines, each followed by a stream that asked for nothing so a next-stream effect could not hide. Twelve streams, twelve identical results, inspected frame by frame. Also answers the question a user actually arrives with: the AiDot app's Auto/HD/SD switch may well work for them, and that is not a contradiction - the app restarts the stream and asks for something different on reconnect rather than sending this setting to a running one.
Resolution: record that the control is gone, and why The select was removed in 2.11.9 and 2.12.0 clears the leftover entity, but the wiki still documented it as a working control with a caveat. Six pages referenced it. The reason also needed correcting. This page said some models ignore the command; they do not. With the library able to read camera replies, an M3 Pro acknowledges it within 0.03s and reports the new value back when asked. The video is simply identical either way - 1280x720 at the same bytes per frame under both settings, measured with the setting confirmed by read-back first. The earlier checks had all been made in the SD direction, and SD sends the value the camera is already on, so they only ever showed that setting a camera to its current value changes nothing. That is worth stating on the page rather than quietly rewriting, because it is the kind of measurement error that looks like a finding.
Use plain ASCII throughout the wiki Replaces em dashes, en dashes, arrows, smart quotes, ellipses and decorative symbols with ASCII equivalents across all pages, so the published docs render identically everywhere and copy/paste cleanly into terminals and issue reports. Two glyphs needed wording rather than substitution: the HACS kebab-menu icon is now written as 'the three-dot menu', and the middle-dot separators became slashes (a pipe would have broken the markdown table cell in Home.md).
Initial wiki: install, config, cameras, PTZ, audio, recordings, automations, troubleshooting, FAQ