Wiz Integration - bulb goes offline

I use the built-in-app to find the BULB, it finds it... I edit the label, and put in in an room
and its done... at that point it says its offline... which its not (thier app on iPhone works perfectly)
i even removed it, and added it again, only for it to go "offline" again

pretty much useless for me... anyone solve?

Is there anything in the logs around that time? That might help provide a clue to the issue…

It may be of some bearing that the Wiz app accesses your bulb via their cloud, whereas Hubitat accesses your bulb over the W/LAN.

Are there any routing issues between the wired and wireless segments of your LAN? I am asking this because your hubitat is on a wired segment while the bulbs are WiFi-connected.

I rebooted the hub, and now its connected to bulb
turned on debug logs for the device... seems pretty chatty for a bulb

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:53.098 PM

debug

[result:[dimming:100, rssi:-60, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-60, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:48.395 PM

debug

[result:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:47.620 PM

debug

[result:[dimming:100, rssi:-61, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-61, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:38.969 PM

debug

[result:[dimming:100, rssi:-61, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-61, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:36.136 PM

debug

[result:[dimming:100, rssi:-60, temp:5020, sceneId:0, state:false, mac:d8a0116f8f98], method:getPilot, env:pro]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:34.263 PM

debug

[result:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:29.563 PM

debug

[result:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:24.846 PM

debug

[result:[dimming:100, rssi:-63, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-63, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:20.139 PM

debug

[result:[dimming:100, rssi:-63, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-63, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:15.436 PM

debug

[result:[dimming:100, rssi:-63, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-63, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:11.429 PM

debug

[result:[dimming:100, rssi:-61, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-61, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:16:01.312 PM

debug

[result:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:15:56.608 PM

debug

[result:[dimming:100, rssi:-61, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-61, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:15:51.903 PM

debug

[result:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

[dev:1204](http://192.168.1.4/logs#)2025-10-09 12:15:47.202 PM

debug

[result:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240], method:syncPilot, env:pro, params:[dimming:100, rssi:-62, temp:5020, devices:1, src:hb, sceneId:0, mqttCd:0, state:false, mac:d8a0116f8f98, ts:1760023240]]

So rebooting the hub resolved the issue? That’s good…

On those same devices, do you see any warnings or errors? (You can filter by devices)

When including logs, a screenshot is prefered. They are easier to read than an copy/paste.

no errors, i will keep eye on it
also i had to roll back to 2.4.3.131 (for another reason)
not sure if that plays in to this

The only way to know for sure would be to role back up and see if it works…

the next day (today):
image

so there is a PROBLEM!

rebooted HUB and boom its back

Any errors showing in the logs?

nope
just its chatty self

oh and it never goes "offline" in their app, when Hubitat says offline, i still can control it in wiz app (which might be though cloud, but it still works)

Hmmm…. I don’t have any experience with the Wiz bulbs, so I’m a bit stumped, but hopefully someone else who has can chime in…

In the mean time, have you tried a reboot with advanced option to rebuild the database?

OK, yes hopefully someone else chimes in
no, only regualr reboot.
the only other issue (which a made a post in feedback category) i got is something broke with eventstreams in 2.4.3.133
otherwise Hubitat perfect

I would try the DB rebuild. Likely won’t change anything, but it doesn’t hurt anything either!

I tried the rebuild...
no change

and today its offline again...
i got two of these bulbs (only 1 in use)

Sounds like they were online for a bit longer this time though…?

i doubt it, i just didn't check/notice..
rebooting now 11:58am - 10/14/2025 - back online

1 Like

@support-team, any suggestions?

Didnt take long to go "offline"
6:41pm - 10/14/2025

There’s a thread that speaks to some early Wiz issues. Have you checked to see if there might be any nuggets in there?