[SmarthomeElektroniker]

Problem

The Android app reads the device order through IHomeApiV2:

GET /api/v1/home/{homeId}/devices/order
→ ApiWrapper<DeviceSortContainerV2>

From the app's serializers:

DeviceSortContainerV2 = {"type": DeviceSortType, "listOrders": [DeviceSortBeanV2]}
DeviceSortBeanV2      = {"source": DeviceSource, "did": String, "order": Int}
DeviceSortType        = HOME
DeviceSource          = UNDEFINED | TUYA | RR | THIRD_PARTY

The server returned a bare list of duids:

{"code": 200, "msg": "success", "data": ["<duid>"]}

The app fails with:

RR/rrRunCatching: Expected start of the object '{', but had '[' at path: $.data

Fix

{"code": 200, "msg": "success",
 "data": {"type": "HOME",
          "listOrders": [{"source": "RR", "did": "<duid>", "order": 0}]}}

getHomeDetail.deviceListOrder stays a flat list. That is a different type.

Tests

tests/test_home_devices_order.py checks the container shape and the order of two devices.

Full suite: passing.

Live check (Oct 2026): verified together with the other fixes of this series (all based on current main) against the Android app 4.60.06 and a real Q7 Max (roborock.vacuum.a38). The app called /api/v1/home/<id>/devices/order and the home screen loaded without the Expected start of the object error.

Notes (not changed here)

IHomeApiV2 also has POST on the same path to save the order, and that method returns Boolean. match_home_devices_order ignores the HTTP method, so a POST currently gets the GET payload as well. Persisting the order is out of scope for this PR.

🤖 Generated with Claude Code

[Lash-L]

TY