Obstacle photos work fully local through the server (Saros 20 Neo)

[Killekon]

FYI for anyone wondering whether obstacle photos need the cloud: they don't. On a Saros 20 Neo (a296, fw 02.29.56) with local_roborock_server v1.2.1 and the robot's WAN blocked, the obstacle photos can be fetched through the server with no server changes. The server relays the get_photo RPC and the binary reply (protocols 300/301) like any other MQTT traffic.

• type: 1 gives a 285×285 crop around the obstacle (single 301 frame).
• type: 0 gives the full 640×480 camera frame (300 frame plus continuation).
• Photo ids are in map block 15. On this model the records are 36 bytes, with the id at bytes 12-28.

I'm using this in Home Assistant (a gallery of the last cleaning's obstacles with their spot on the map). Two client-side gaps are reported in python-roborock (photo_name None with 36-byte records, type: 0 not reassembled): Python-roborock/python-roborock#991. LocalRock feature request: DonSidro/LocalRock#36.

Maybe it's worth a line in the docs' feature list.