I think there is a problem that needs to be investigated. Wyze Plug V1 in multi-access point environment, The scenario is consumer grade wifi, primary router with built in wifi access point and DHCP enabled on this device. Then there is a secondary router, with DHCP disabled and using just as an access point. Both routers have the same SSID. When the primary router reboots, the problems begin. It appears that the plugs cannot roam (standard wi-fi client feature), The Wyze plug instead experiences a disconnect and then it attempts to reconnect without DHCP being reachable from the secondary AP. Normal clients would roam to the next AP, but in this case, the Wyze Plugs will go into pairing mode.
I think Wyze need to look into this and examine the logic
My speculative evaluation of this (also posted on the redit Linked):
- I think it’s a timeout issue and they go into pairing mode (flashing blue light). I think that a plug that is configured, should never go into pairing mode unless manually put into that mode. They should indefinitely attempt to connect to the configured wi-fi network.
- I think it’s most evident in a multi-AP environment where DHCP address cannot be assigned to the client. Typically, a client should roam to the other AP without need to check-in with DHCP. I think in this case, the device doesn’t roam. Instead it likely experiences a ‘disconnect’ and then upon reconnect, the need to communicate with DHCP creates an issue and then it decides (timeout) it is on a network with no DHCP and goes into pairing mode.
- In the absence of DHCP, client should use previously assigned IP address and continue to use DHCP half-life timer logic.
Workaround 1: Tweak (play with) the reboot schedules on each router.
Workaround 2: Add secondary DHCP that is up when the primary router (with DHCP) is down. This way, when re-connect occurs (should be a roam without need for DHCP), the plug can pull an IP address. Caution: When adding secondary DHCP, need to ensure gateway IP is the correct gateway IP, not IP of the secondary AP. Also, secondary DHCP likely needs to be a separate range of IP addresses, as these low tech DHCP servers on routers, there would be IP address conflicts likely. You need a more advanced DHCP environment to avoid this kind of issue. You’ll see clients split between both DHCP servers during the normal course of day to day usage. Added benefit of some amount of redundancy.
Workaround 3: Make DHCP separate to the router/AP, i.e. DHCP always up when APs reboot. Need to ensure that you don’t use the main router switch ports else secondary AP has no connectivity to DHCP server when primary router reboots.