There is no resolution control. The select.<camera>_resolution entity was removed in 2.11.9, and 2.12.0 clears the leftover entity from Home Assistant's registry when you upgrade.

If you still see an unavailable select.<camera>_resolution after upgrading, reload the integration once - the cleanup runs at setup.

Not because the cameras ignore the command. They do not.

The library can now read the replies cameras send back, and measured on 2026-08-07 an M3 Pro (A000088):

• acknowledges the stream-quality command within 0.03 s, and
• reports the new value back when asked - it reads MIDDLE at session start, MIDDLE after selecting SD, and MAX after selecting HD.

So the camera accepts the command and remembers it. What does not change is the video. With the setting confirmed by reading it back first, then recorded and inspected frame by frame:

setting confirmed on the camera	frames	resolution	bytes per frame
MAX (HD)	728	1280x720	2592
MIDDLE (SD)	651	1280x720	2682

Same picture, same bitrate, either way.

The entity accepted a value, restored it across restarts, and reported a setting that had no effect on the stream. A control that reports success while changing nothing is worse than no control, because it is what people reason from when something else looks wrong.

An earlier version of this page, and the 2.11.9 release note, said the cameras "ignore" the command. That was wrong, and it was wrong in a way worth explaining: every check had been made in the SD direction, and SD sends the value the camera is already on. Those checks only ever showed that setting a camera to its current value changes nothing. Measuring the direction that actually moves the camera gave the answer above.

The measurement above covers one model and the two settings the app exposes, which left room for the control working on a value or a camera nobody had tried. It does not.

On 2026-08-07 a Spotlight Cam PTZ (A001064) was swept across every value the stream-quality command defines - six of them, only two of which the HD/SD toggle ever used - and afterwards across the separate value the app sends for Auto. Each was sent, then followed by a second session that asked for nothing, because a setting that only takes effect on the next stream would look exactly like one that does nothing:

setting	acknowledged	this stream	next stream
0	0.05 s	1280x720	1280x720
1 (HD)	0.17 s	1280x720	1280x720
2	0.02 s	1280x720	1280x720
3	0.19 s	1280x720	1280x720
4	0.01 s	1280x720	1280x720
5 (SD)	0.11 s	1280x720	1280x720
16 (Auto)	0.54 s	1280x720	1280x720

Fourteen streams, fourteen identical results, inspected frame by frame so a change partway through would have shown. Every setting was acknowledged. None of them changed anything.

The last row is worth singling out. 16 is the value the app sends for Auto, and it is not part of the numbered set the others come from - so the first sweep, which walked that set, could not have sent it. It was measured separately for exactly that reason.

It will look like it works. The app sends the camera exactly the same command this integration used to send - the same command id, the same values - and then, when the camera acknowledges it, the app changes the label on screen and reports success. That is the whole of it: there is no reconnect and no second request that could produce a different stream.

So the AiDot app has the same problem the resolution select had here, and it is harder to notice there because the label moves. If you have switched between Auto, HD and SD in the app and felt the picture did not really change, that matches what the camera actually does.

Only with evidence that a camera's encode actually changes. The command itself is still in the library and is still correct, so a future firmware could act on it - but the control will not return on the strength of the command being accepted, which it already is. Seven settings across two camera families, Auto included, now say it changes nothing.

The one per-camera stream setting is the Camera audio (in HA stream) switch on SDES cameras (the battery models and the PTZ), which decides whether that camera's Home Assistant live stream carries audio. Everything else about streaming is tuned in the integration's options - see Configuration options.