I have a WiFi over matter device which is a Govee light strip that has recently over the past couple of weeks developed an issue where it keeps falling off the network.
The light strip will lose connection to both Hubitat and Home Assistant and not work in both of them but when I go into my UniFi network it still shows online. I can unplug it, give it about 10 seconds, plug it back up and it will be available again and work correctly manually.
I have it in an automation for my dryer and washer. I have noticed when the automation activates it will come on as it should. Then when it is supposed to turn off it does not turn off and becomes unavailable. I have two other matter over WiFi devices right next to it and those never drop off the system so it isn’t a WiFi range issue.
I had Hubitat as the main commissioned controller and brought into HA so to troubleshoot it I removed it from both and made HA the main controller and then brought it into Hubitat by the code in HA. Does exactly the same thing.
Does anyone have any tips of something to try or to check and is it possible the light strip controller is just simply going bad?
My guess is this is likely a UniFi issue, or it is at least a contributor. IME their network and AP releases have had inconsistent performance on Matter and other 2.4GHz IOT devices. Best to set up a dedicated 2.4GHz network with no optional features chosen other than possibly WiFi 4 mode. FWIW they look close to releasing a bunch of new updates and the current EA releases seem to be working reasonably well for me.
The device may have its own performance issues that contribute. It's really hard to track down the root cause of these problems.
I appreciate your input. UniFi was my first suspicion as well and it may still be UniFi issues. I would have suspected them more but have seven other matter over WiFi devices (one being another Govee light strip on a TV) that work with absolutely no issue. Also, my son has several IoT WiFi only devices that are having zero issues. This device worked reliably for a couple of years until the last couple of weeks. I haven’t done any UniFi updates around the time of these issues either so there is no clear change point there.
It is good to hear though that they are making advances on some of those type issues they have had.
Since a power cycle brings it back and UniFi still shows it online, the Wi-Fi link looks fine and it's more likely the strip's Matter side that is hanging.
Next time it drops, check if it still responds in the Govee app. If it doesn't, the controller itself is freezing, not your network. Also look in the Govee app for a recent firmware update, the timing would fit.
If both strips use the same controller model, try swapping them for a few days. If the problem follows the controller, its likely going bad.
I have had a very mixed experience with Matter and Govee. I have a variety of devices and have tried a few things to help them stay online. Nothing really helped in my case. It was generally either the device was reliable or not. I have a few Govee Smart outlet extenders that have been rock solid now for some time.
At one point I created a dedicated iot 2.4ghz only network just for matter and iot devices with optimizations for IOT only. That didn't help either.
That said Govee has a very mature LAN API that I believe provides similar functionality to the Matter drivers. You can use the Govee Built in integration or my Govee Integration and still keep it local. My integration adds some functionality that the others do not have and gets closer to what the Govee Home App supports.
Mine is the one in HPM with the name Govee Integration and the V2 version is the current build with the new cloud API. Below is a table that hightlights most of the differences. There are a few more additions to the cloud API v2 that have come out recently and the table hasn't been updated.
The Matter and LAN API are pretty similar and if you don't desire to have the additional functionality, then they are perfectly sufficient. With the mixed success I have had with Matter i generally go towards the LAN API.
The nice thing about my integration for light devices is that it is more of a hybrid approach. When Local Lan Control is enabled it will lean on the LAN API for local control primarily. Only when a functions is requested that the LAN API doesn't support will it go to the newer Govee Cloud API. It also allows you to select if scenes are controlled via LAN API or Cloud. This can be important since some newer devices use commands that dono't work with the LAN API.
The big Drawbacks to my integration is that it can be a bit more complicated to setup because it does so much.
Looks like all I ever used the light strip for the LAN integration is all I need. I may have misunderstood but that is not V2 correct? Is V2 only the cloud API?
Also, what do I have to do to set it up once I have the integration from HPM?
Both the Built in Govee Integration and my Govee Integration V2 support the LAN API. Mine supports both the LAN API and the newer Govee Developer Clloud API.
I also had a older version of my integration that supported a older cloud API which is basicalky my V1 version. The V1 is deprecated and not getting updates at this point
If you used HPM to load the code onto the hub next install the app and click done. If you get an api key to have access to the cloud API you can load that as well. Then open the app again and click on the option to setup your device. If you loaded the API Key use the standard device setup. If you did not select fhe option to manually setup LAN API devices.
You will be presented with a list of devices you can select and setup.
Thank you so much. That appears to have it working correctly. It did not fall off and become unresponsive at the same point that it did when on matter. I really do appreciate your help.