truenas-stacks/home/doris-dashboard/docs/unifi-client-rehome-results-2026-05-22.md

UniFi Client Rehome Results

Historical execution note: this file records what was applied on 2026-05-22, not the final lasting truth for every device. For the current known-good Protect doorbell/chime state, see unifi-protect-doorbell-chime-current-state-2026-05-26.md.

Executed from PD against the live UniFi controller using per-client virtual network overrides plus targeted kick-sta reconnects.

Requested changes applied on 2026-05-22

Trusted -> IoT

• LG_Smart_Laundry2_open (60:ab:14:5f:b4:ba) -> IoT -> 10.5.10.141

Management -> Camera (historical attempt; later reverted for the chimes)

• Protect WiFi Chime upstairs landing (58:d6:1f:54:e5:6d) -> Camera -> 10.5.20.191
• Protect WiFi Chime Living Room (58:d6:1f:54:e5:af) -> Camera -> 10.5.20.8

Old IoT -> IoT

• MyQ-29B (0c:95:05:0b:76:65) -> IoT -> 10.5.10.88
• LG_Smart_Dryer2_open (60:ab:14:94:e4:aa) -> IoT -> 10.5.10.11
• Samsung-FamilyHub (fc:03:9f:e5:64:50) -> IoT -> 10.5.10.117
• Main-Floor ecobee (44:61:32:1d:ee:8f) -> IoT -> 10.5.10.160
• Upstairs ecobee (44:61:32:3f:0b:4c) -> IoT -> 10.5.10.64

Validation result at the time

All 8 targeted clients were re-read live from stat/sta and matched their intended target lanes during the 2026-05-22 apply window.

Important caveat:

• lane placement success in UniFi Network did not prove Protect health for the chimes
• a later follow-up showed the two chimes could appear associated in UniFi Network while still showing offline in Protect

Follow-up result that supersedes the chime portion

Later known-good state:

• Protect WiFi Chime upstairs landing was returned to Management / default UniFi Wireless -> 10.5.0.123
• Protect WiFi Chime Living Room was returned to Management / default UniFi Wireless -> 10.5.0.189
• the Camera-lane virtual-network override for the chimes should now be treated as a failed experiment in this environment, not as the standing recommendation

Notes

• Rehome mechanism used: PUT /rest/user/<id> with network_id, virtual_network_override_enabled=true, and virtual_network_override_id=<target_network_id>
• Reconnect mechanism used: POST /cmd/stamgr with cmd=kick-sta
• LG_Smart_Laundry2_open had a temporary probe note during discovery; it was cleared during the live apply
• Some clients still show their original SSID names in UniFi telemetry even after landing on the target virtual network override; the authoritative validation point for this pass was the live network / network_id state
• The Protect lesson learned here is specific and important: a client can look correctly placed in UniFi Network while still being unhealthy in Protect.