EDIT 2: I originally posted this under the title "Help! Weird issue with Wiz lights and maybe Room Lighting app". I think I now understand where the issue is coming from. It appears the new model of light that I have isn't fully compatible with the built-in integration. I thought it would be better to edit this post rather than create a new one.
I've kept my original post below, but the TLDR is my Room Lighting app had, at times, been throwing errors or spamming the debug logs with multiple on/off commands for some of my bulbs.
After I deleted everything and started to built it back, I realized that the issue is that the built-in integration doesn't handle the new dual-zone Wiz Bulbs I have when only one zone is on.
Link to device: https://www.homedepot.com/p/HALO-RL-Dual-Zone-4-in-Smart-Wi-Fi-Canless-Integrated-LED-Recessed-Downlight-Connected-by-WiZ-Pro-RLWZDZC4/334557796)
These lights have a main center LED and a ring light around it. When you send them an on command from the hub they turn on both lights. However there are scenes that only turn on one light (the Night Light scene) or set the two zones to different colors. You can also individually control the zones from the Wiz app.
I have a room lighting app that includes these bulbs. Everything is fine as long as the lights are either off or have both zones on. If I turn off either zone while the other is on and I have debug logging on for the Room Lighting app, I start seeing the the light turning on and off rapidly in the logs.
If I access the Room Lighting app page while this is happening, I see status and switch indicators in the setup table flickering between on and off.
This happens whether I command the Night Light scene from the hub, or turn off either zone using the Wiz app.
I turned on debug logging for one of the lights and I see they're super chatty... this is a few seconds of debug logs for just one of the bulbs while both LEDs are on:
This is a few seconds of the debug log when I turn off the inner LED of that bulb:
As best as I can understand those logs, it looks like the bulbs alternate reporting the state of devices:1 and devices:2. When those are in opposite states, the hub freaks out.
@bobbyD Is there any chance someone at Hubitat can take a look at this to see if the driver can be updated to handle these new lights? I'm about to install a dozen more of these, so I really don't want them to cause issues for the hub.
ORIGINAL POST
EDIT: The issue I described below seems to have resolved itself. I recreated my Family Room Room lights app and it's no longer acting up or spamming the debug logs. I'll leave this post here in case anyone wants to wade through it and offer an opinion as to what went wrong in the first place.
I set up a few Room Lighting scenes that control 6 Wiz bulbs in my family room. The app was set to turn the bulbs off on a mode change that happens at bedtime. This morning I found the bulbs had not turned off as expected last night. I'm really confused by what I've found so far, so I'll just list some bullet points:
- I had multiple RL apps that referred to these same bulbs, but I don't think that is the issue.
- The logs were full of null pointer exceptions for a few of the devices. The hub threw these errors from the time the mode switched last night until the mode switched again this morning to one that was not listed as a "means to turn off" in the RL app. The hub logged over 65,000 errors overnight.
- While lots of other bad things happened in further testing, I did not get these exact errors again.
- I could turn the bulbs off and back on via the Turn Off and Activate buttons in the RL app.
- I set up a virtual button as a 'means to turn off'. The button press was logged as an 'off event' by the app, but the bulbs did not turn off when I used the virtual button.
- I did a reboot with database rebuild. That didn't seem to help.
- I did see some errors related to too many commands pending for two of the bulbs after the reboot.
- I turned on debug logging for the RL app and found it was continuously and rapidly logging on/off commands or events for each of the bulbs.
- Pausing the RL app got the debug logs to stop flying down the 'live logs' page.
- I checked the other RL apps that include these bulbs. They all behaved the same if I tried to use my virtual button as a means to turn off and they all had the continuous rapid-fire debug logs.
- I deleted all of the RL apps for these bulbs and created a new one. I just selected the bulbs, turned on debug logging, and clicked "Update" with no other settings changed. The live logs immediately started filling with the on/off commands for the bulbs until I paused the app.
This is what happened when the app was un-paused for about 10 seconds:
The other strange thing I've noticed is that when I add these bulbs to the room lighting app, the table for configuring them is lighting up like a christmas tree.
The state icons and the current switch states in the Switch column constantly change between on and off, even when the app is paused. This is consistent with what I see the debug logs showing when the app is un-paused, so I'm wondering if what I'm seeing in the logs is an underlying problem that is just getting exposed by Room Lighting, not an issue with this app.
This was happening while the lights were on. When I turned the lights off, the table stopped updating, but notice that bulb 3 is reported both as on (in the state icon) and off (in the switch column)
I've also tried disabling and re-enabling the Wiz integration.
Anyone have any thoughts on what to try next?
