Wiz plugs become unavailable (while still connected and responding in the wiz app) about core HOT 9 OPEN

Hey there @sbidy, mind taking a look at this issue as it has been labeled with an integration (wiz) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

wiz documentation
wiz source
_{^{(message by IssueLinks)}}

from core.

I have A19 bulbs with same issue.

from core.

Same here for ~7 different type WIZ lights

from core.

I have the same issue on all a19 bulbs I own, have tried two different sets.
I have removed from Wiz app and home assistant and re added.
I also am using 3x B12 bulbs that have no issue with staying connected to home assistant.
I can provide any logs or do any trouble shooting steps necessary to help with this.

from core.

It seems not a direct issue with the integration. Because of different connectivity stacks, the app uses MQTT via TCP and the integration (must use) UDP.
This means,

• it could be an issue in your network configuration
• it could be an issue with a specific type of bulb/device

If it is a general issue, no bulbs will respond.

Please check:

• Network connectivity via UDP to the bulbs (especially if you have the bulbs in separate Subnets, WiFis or VLANs)
• Try to trace the traffic on your HASS (will the UDP datagram be sent?)
• Use the pywizlight CLI to issue a light-on or light-off manually (https://github.com/sbidy/pywizlight?tab=readme-ov-file#cli) - Please try this from the HASS system AND another connected one.
• Check the WiFi connectivity state at the bulb via echo '{"method":"getSystemConfig","env":"dev","params":{}}' | nc -u -w 1 <theIPofYourBulb> 38899
• Check if the IPs of the bulbs are changed - assign static IPs (via your router) to the bulbs. HASS will not recognize these changes!
• If you use docker for your HASS instance, check the network config also here (but unlikely because some bulbs are working)

In the past most of the time the issue is a weak Wi-Fi connection to the bulb which results in UDP datagram package lost.

Hope this helps. I try to continuously test new bulb FWs and App updates to keep this integration alive.

from core.

Two problems got mixed up in this thread, for the sake of clarity i will just precise à few things.

I have problems with Wiz plugs i've had zero problems with Wiz bulbs.

So this trhread was meant to adress à probleme with Wiz plugs only.

The bulbs were still completely operational on the Wiz app when they appeared unavailable in home assistant. So if it was a connectivity issue i guess my plugs would have been unavailable in the app too which was not the case.

Anyway since disabling roaming on my unify Network and updates of the home assistant I don't have the problem anymore.

from core.

Basically, there is no different between bulbs and switches regarding the communication and API call approach.
But, what I discovered, the plugs have more problems to establish a "good" WiFi connection because these are hidden behind e.g. cupboards etc.

As mention above - there IS a big difference between the integration and the app usage. The HASS integration use a UDP stack which is in wireless networks, especially with small devices without a proper antenna and really close to high voltage systems, a bad idea. UDP can not verify if a package is transmitted successfully. There is no back channel - that's why the integration will send out a UDP datagram multiple times (kind of spamming) to ensure that the command reaches the device.
Additionally, some access points or router will block or "manage" these type of UDP stuff, because normally you use UDP for e.g. data streaming.

The app uses MQTT-TLS with TCP.

from core.

Oh ok i didn't get the part regarding UDP on in the hass integration.

Thanks for the clarification.

Anyway bulbs and plugs are working perfectly now.

from core.

Just chiming in here with another solution. I had the same issue with about 10-15 older A19 bulbs. I have a UniFi network setup. It looks like the bulbs were constantly jumping between multiple access points (APs). I could tell there was an issue when I went on the Wiz integration in HASS. I saw a ton of reconnecting issues in the integration. I went into the UniFi application and locked each bulk to an AP. I immediately saw the reconnection issues resolve in the Wiz integration in HASS. All my issues with the bulbs have now resolved, and I'm getting very quick and consistent response times on all of them now.

I wanted to put forward this as an alternate solution to @EscapeRush 's solution of turning off "roaming" in UniFi. I put "roaming" in quotes here, because I'm not sure there's a a way anymore, as of June 2024, to disable roaming on a WiFi network. It appears this feature may, sort of, used to exist, but not really anymore with the latest UniFi OS. I think you have either set the WiFi network to a single AP or you have to lock each network client device (e.g. each Wiz Smart bulk) to a specific AP within the client devices settings. Locking each bulk to a specific AP basically does the same thing (at the bulb level) without disabling network-wide roaming that might be useful on other devices.

from core.