The built in app uses UDP multicasting instead of TCP. Make sure you have the networking properly setup to allot route the traffic as needed.
I suspect that the use of UDP multicasting will make this difficult to have the bulbs and the hub on different network segments.
The community driver uses TCP which is a bit friendlier to multi network segment setups.
I just migrated to C8 hub. Everything went smooth. Only issue so far is that my wiz lights shows offline. Oddly not all of them. The ones offline are still controllable via hubitat commands. And if re-run discovery in the app integration, some devices switch online and the others become offline or stay offline.
Hub is still on lan connection in same location. Just swapped. Only thing that changed is the hub and the IP my router assigned to the hub is different from previous hub.
Any ideas to troubleshoot? @gopher.ny
I've attached to back to back discoveries showing how they switch between offline and online.
To add, all my automations are working just wiz lights are showing offline.
Same experience here after c8 upgrade.
Tried deleting wiz integration and reinstalling. Hubitat detects ips of my 2 devices but they still show as offline. Automations and lights unresponsive here but I can operate them with native wiz app.
Devices going on/off generally means that regular updates from those devices don't reach the hub. I'll relax the timing on a bit in the next build, hopefully that solves it.
Just a follow-up to the c8 migration issue. I have deleted Wiz integration, re-installed and resynced my lights. They seem to work for a day or so and then drop off again. I used to be able to run a discovery again with the C7 hub if this ever happened and they would sync up fine. I'm running the last update (2.3.5.105).
Does this behavior still occur on 2.3.5.110? I've relaxed the timing before a device is considered offline in that build.
Sorry for the delayed response. Updated to latest build yesterday and Wiz lights have been working well so far. Will keep you updated.
I greatly appreciate your work. Thanks !
I'll chime in here as well. I have not had a C7, C8 was my first so I have not done any migration. Setting up as new. The app/driver discovers the bulb fine, and I'm able to rename it and all that. I have them on the same circuit as a Zooz Zen72 smart switch which are in smart bulb mode, I've created a group for each room and a Basic Button Controller thing with just 2 commands, up to turn on group, off to turn off group. It works in one room, but doesn't in the other 2 rooms. Same issue here, some bulbs in the integration app showing as offline despite them all being on and controllable with both Hubitat commands and through the Wiz app. I am on the latest Hubitat software as of 3/27/23 at 19:00EST. The whole reason I decided to upgrade from my dumb switches was in an attempt to prevent killing power to the Wiz bulbs so that they always kept track of where in the Rhythm they were supposed to be and I wouldn't have to manually re-enable the Rhythm when turning the switch on in the morning. Thus far even just this one concept hasn't worked, which has been a huge bummer. Hoping something can work out 
Which now I see where it states the platform version. I'm on 2.3.5.118
Another quick update. Any lights showing in the Wiz Integration app page that were showing as (offline) I removed/deleted, waited for them to automatically show up again, went in to their settings and renamed and assigned the Type and the room and all that, did that for every one and for awhile it was remaining while I was experimenting with other things I'm working on. I rebooted the hub eventually, and it "forgot" some of my Wiz bulbs (evidence: it forgot the specific names I had assigned individual bulbs, and upon clicking in to the device it had also forgotten the room which they were previously assigned) so I'm having to re-do all that pretty frequently and they're again showing as offline.
Are you sure those last 6 aren't on another server using Hub Mesh? (that's what the verbiage looks like)
I'm positive. This is what it looks like after the Wiz Integration app has its brain fart and just forgets stuff. I have gone through this extensively, noted IP addresses and MAC addresses, confirmed that the bulbs ARE on the network via Alexa control and effective control through the Wiz iOS app.
When I get done deleting/readding it looks like this for awhile, then some time later it just decides to pout and forget things.
Okay, looking closer I can see the redacted values are IP addresses, thought they were hub names. Haven't played with this integration so just spit-balling here, but is it possible that these bulbs are having issues staying connected to the LAN that are not related to power, i.e. low WiFi signal strength, RF interference, etc.
Looks like you may have multiple threads going on with this:
This other post also mentions the Wiz Integration issue, but that thread specifically was started on how to make buttons and automations work with Zooz switches/Hubitat C8/Wiz bulbs. This thread is specific to the Wiz bulb built-in integration that also is occuring. Separate issues
I painted over the IP addresses because I'm ignorant to whether someone out in the interwebs could/could not try to do something malicious with it, so I crossed it out to be safe. And to answer your question no it definitely isn't a LAN or wifi issue. Though the Hubitat/Wiz Integration app says they are offline, the bulbs themselves always retain their connectivity and functionality, verified by Alexa commands to bulbs still working as well as the Wiz iOS app always retaining full connection to and control over the bulbs. I've checked in the router itself to see if its doing something funky with reassigning IP addresses or something and its not, they remain consistent. I'm on Hubitat version 2.3.5.118. I have not yet been specific enough to notice if its the SAME physical bulbs that end up getting forgotten by HE, or if theres any pattern at all to that, but I do at least know the bulbs themselves have good connectivity to the network and functionality. Either Hubitat or the Wiz Integration app itself (I'm not sure of the innerworkings of all that) seems to be where the disconnect arises.
But here is the problem, a ton of other people use these bulbs and they use them fine with Hubitat. So logic indicates it probably isn't a Hubitat integration issue perse.
I think some important information is being left out here in reguards to @user4745 setup.
That is all great, but when you add all that together what you get is potentially a perfect storm to make wifi network less reliable.
My speculation is that he/she is in a condo surrounded by a ton of wifi network all flooding the air waves and making communication somewhat unreliable. That along with the fact that UDP is used for at least part if not all of the communication potentially means the devices are less reliable.
I have suggested reverting back to the community integration to remove any chance of there being a UDP packet drop issue occurring. Along with setting up DHCP reservations for all of the bulbs involved.
It’s most likely the Netgear router that’s the problem. I had nothings but problems with integrated TP-Link devices working in Hubitat when I had a Nighthawk router. They would also work fine in the Kasa app. I also had constant problems using AirPrint and thought it was my printer at fault. The problems magically vanished when I switched to my current Velop MX-5 router.
Definitely a fair point. But, this lengthy thread exists because I couldn't find answers anywhere to get it to work, which IS working now... And it was not a new implementation of Wiz bulbs, the Hubitat and Zooz switches were the new parts. But you're right that it's not fair to just blanket say "It's Hubitat's integration issue," but that's where my homework and investigation and trialling is pointing me toward. But at the end of the day it's just a matter of working through the issues and sharing the results for others.
No definitely not, that sounds like a nightmare I intentionally live in a place away from other students. It's an average neighborhood. Yes there are a number of wireless networks floating around, but definitely not in a way that hasn't been experienced by numerous others. But yes, definitely something that could contribute.
Definitely agree, I just haven't had any network issues before, and no other devices have had performance affected after the implementation of Hubitat and Zooz switches (ie my non-HE compatible smart plugs on 2.4 haven't experienced any issues, the bulbs themselves are as reliable as they ever have been when controlling through the app. I know it's been stated that Hubitat and iOS app talk to the bulbs in different ways, I'm just saying I haven't experienced any network issues before.)
This is definitely going to be what I dig into deeper next if the way the system is set up now proves to continue being problematic (though I honestly don't think it will. I think its in a good spot finally).
Done. And it was SO easy to do since I had already made a little Excel spreadsheet with each bulbs name, IP, and MAC addresses. Flew right through it, rebooted the router, and things are rolling again. I'm hopeful!
Download the Hubitat app
