I have a full IoT house but Black Friday messed with my inquiring mind.
I have no WiFi stuff but I added some Govee RGB bulbs to play with.
All my ZB bulbs always have power, as they should, being part of a mesh.
All the other bulbs are on ZW wall switches.
If I replace standard LED bulbs, on the ZW switches, with these WiFi bulbs do I have to leave the power always on or does WiFI not care as they aren't really a mesh?
If I can just power on the bulbs with my WC pistons/ZW switches and then set the attributes with a power on delay that would be great.
Otherwise I have to change the pistons to always leave these switches on and remove them from their current Activator/Scenes.
As you guess, they won't cause problems like Zigbee or Z-Wave devices would, since they are just Wi-Fi clients and won't participate in a mesh network like those devices can (where taking one off could risk it having been a router/repeater for another device and taking time to catch up, assuming another route is even available).
It may still be a good idea to avoid doing this, as they're effectively "dumb" bulbs in the meantime, so most of your automations won't be any good (aside from ones that turn on the Z-Wave switches it sounds like they're behind). Their power-on behavior may or may not be configurable as well, which could be undesirable, depending on what they do and what you need. For example, some bulbs turn on to their last state, some turn on to some sort of default (warm white at 100%?), while others have a configurable option (Hue is a notable example).
I'd still personally try to avoid it for these reasons. What kind of Z-Wave switches do you have? Many modern ones have "smart bulb mode" or a "disable local control" feature that allows them to be always powered and send Z-Wave Central Scene commands (which typically get translated into button events on Hubitat), which you can use to ultimately control the bulbs in a "smart" way.
But if none of the above bothers you, I don't see a reason you couldn't!
1 Like
Thanks for the steering mono-committee. 
Agreed, best alter things (WC) to always leave the power on; didn't think about the power on default implications.
All my switches are GE Enbrighten so no fancy Prefs there.
I just noticed, after I asked this question, that the logs are filling with polling errors on both bulbs even though one of them is still powered but logically Off.
java.net.SocketTimeoutException: Read timed out on line 610 (method poll)
Yea the Govee Cloud API has been in a strange way this last week or so. Based on my logging it shoud of gotten better a little after 9pm.
@bertabcd1234 i am thinking about adjusting the timeout on the httpPost or HttpGet calls. What is the default timeout if it is not specified.
Looks like the default is 10 seconds.
Forgot to mention this as a possible downside if you're using polling-based integrations on LAN (or possibly some cloud) devices, but, yes, that's another concern. 
(But harmless if you know where they're coming from and have a good explanation, as you would -- though still probably still good to avoid if you can.)
