My Wiz scenes appear to be working fine when setting all the bulbs to a particular scene.
There are a couple ways to work around the lack of explicit scene support: 1) custom commands (not supported much outside of Rule Machine and Button Controller) and 2) a combination of a virtual button device and a Button Controller app.
For #2, set up a virtual button device with as many buttons as scenes you want to control. Then set up a Button Controller app, In the BC app add an action and choose 'Set Variable, Mode or File, Run Custom Action', 'Run Custom Action', 'Dimmer', select the bulbs, and then use custom command setScene and enter the scene name as a string parameter. Do that for each button/scene you want to be able to trigger. Now you can use the buttons in many more apps to set the scene. Also, you may want to have a button that turns all the bulbs off.
I don't use the Hubitat dashboards. Test the buttons out on the virtual button device. Here is my Button Controller setup - 3 Wiz scenes for 3 bulbs, 1 all off scene.
Thanks @bill.d for your help, as I now have my Pico's Favorite button (#3) set to cycle through the various scenes. Now if anyone can suggest a way to use the Raise (#2) and Lower (#4) buttons to raise and lower the dim level. What I've done so far doesn't work. Perhaps the driver/device is missing the necessary functions? There is a setLevel, but no increaseLevel, for instance. I assume I can't do a "setLevel +10". Thanks...
I followed Bill's advice above and kept at it until I made it work. However I still have some inconsistency with my Virtual Buttons on the dashboard. Most of them work but a couple do not. All the Buttons I made in the button controller work with "Run Actions" so I know the button in the Button Controller App is setup correctly. But in the Dashboard the results are unexplainable at the moment
I have noticed on a few occasions the button controller app loosing the event subscription details. I had to completely wipe out that button presses action from the app and recreate it.
Click on the gear to the left of the app and check that the event subacription is present for the action/button you are tring to setup.
OK I have all my buttons working now. Some tips for anyone working on this.
Make sure when you make a new virtual button to go back into your parent button controller app and add those new virtual buttons.
If you experience control issues like I did, then delete the entire child button app and rebuild it.
There is one part where you first make a new button in the button controller app and you may be tempted to manage conditions. That leads you down the wrong path. You want to 1st add a new action to even have any conditions to manage or at least that was how I saw it.
I have 8 functional scenes now and this is freaking awesome.
Wiz doesn't do start/stop raising. But Button Controller can adjust levels. Chose the 'Adjust dimmer' action. You would get rid of your held/released actions and put adjust dimmer actions on the pushed events.
I'm not sure why you have all those virtual button device instances. You only need 1 virtual device. In your case you'd set the # of buttons to 6 in the virtual device. Then in the Button Controller app you set up push actions for buttons 1-6. Here is my virtual button device with 4 buttons:
That was to have a unique button name in the dashboard so I would know what I was doing. Otherwise they all would have the same name and then I would have to memorize the numbers for the scenes I want.
Ok one more tip. Make and include any virtual button BEFORE you make the button controller app that will use it or it will not work even if you try to go back and include it in the parent button controller app. That really is what I was doing wrong on some buttons.
I see, as I think I said I don't use the Hubitat dashboards. I'm not sure what the issue with adding new button devices is as I cannot replicate it - I have no problem adding new virtual button devices to the BC app. I don't think it's the cause, but maybe make sure your virtual button devices all have 6 buttons?
You have to make then include the virtual button into the parent button controller app before making a new button app or it does not let it work correctly is what I found. Thus why I had to delete and rebuild some button apps after the inclusion of the virtual button into the parent app. It solved my issue.
Man, I am having such odd connection issues with these wiz bulbs. I regret not investing into sengled.
Everyday a handful of my bulbs go offline. I have a RM notification for any wiz bulb that shows offline status for more than 5 minutes. This is getting absurd how I have to power cycle them all the time. It's not a hubitat issue as they're even offline in the app and from voice control.
I'd love to know what I can do to mitigate this. They're all on their own DHCP reserved IP's. I assumed that would fix it, but they just keep randomly going offline and sometimes back on their own, and sometimes nothing but power cycling will bring them back online.
Does anyone else monitor their status and see them falling offline?
Is it all of them or just certain ones. This is more of a wifi issue then hubitat i think. What kind of router/AP are you using. Some have device limits you need to be careful of. Mine are rock solid on a Google Wifi Mesh network. My max number of connected devices generally runs around 50 which could bring some cheap routers to their knees.
Almost certainly a Wifi issue - signal strength or AP device limit as noted above. What is the RSSI as shown in the Wiz app (settings for the bulb, the down chevron next to the device name)? Mine can be pretty bad - around 90 (higher is worse), but they still work.
