ok. I have been trying to control my hue bulb with my zen22 switches and something always fails. I have the switches with the physical load disable, so they can control smart bulbs. I have tried Mirror me, Switch Bindings, Simple Automation rules and always the same issue that I haven't been able to figure it out.
So if I only use the switches, everything is perfect they turn on and off as they should and I see this in the logs and I see the status changes correctly in the hue app.
Below is what happen when I turn on the lights using Alexa. Everything is reported correctly in hubitat and Hue app and the lights responded as they should.
Everything seems to be ok. If I check their status in the Hue app and hubitat devices they, lights and switches, show the right status, off at the moment. But here is where the problem starts. Now if I go to the switch and turn it on I see their status, switches and lights, change correctly in hubitat and hue apps, they are being show as on, but the lights never turn on. this is what I see in the log
Here it doesn't matter now what I do with the switch turn it on or off, the light wont come on, it is light the load would have been turn off, and the only way to recover the light back is going to the kitchen device page and from there click off and then on again and finally the lights will be back on, like if they would be reset. this is from the log
This only happens if the lights are on and I turn them off using Alexa. if they are off and turn them on using Alexa there are no problems they keep responding. I have tried different methods to link the switches and the light as I mentioned at the beginning, but I am always getting this problem only when I turn them off using Alexa. Any help feedback will be appreciated.
It would probably be helpful if you showed at least one of your setups (I do understand that you said none of them worked for you), but one thing that isn't clear to me from the above: how do you have the ZEN22 configured? You said you have physical control disabled, so I'm guessing you have parameter 15 set to 0 instead of the default of 1. This disables physical control (tapping the paddle won't turn on/off or dim the load), but remote control still works (meaning Z-Wave, so the "On" and "Off" commands on the ZEN22 from the hub will still work--including from Alexa if you're trying to control the ZEN22 and not the bulbs this way). You can avoid the latter by setting this parameter to 2instead (disables both physical and Z-Wave control).
However, there are also parameters 20 and 21, which affect how the level (brightness) and switch (on/off) status gets reported to the hub when one or both of the above is disabled. If you want to use any "mirroring" type automation, these must be set to still internally track level and switch state so they can be mirrored: parameter 20 as either value (0 or 1; 0 would probably be closer to what you expect but might spam your Z-Wave network with reports and bog things down) and parameter 21 to 0 (as it is by default). You can then use the paddle on the ZEN22. the Hubitat device directly (via Z-Wave), or Alexa (via the Hubitat device--so eventually also Z-Wave) to turn on/off or dim the ZEN22, and the bulbs should "mirror" that state if you have such an automation (e.g., Mirror Me) configured. You can see all the ZEN22 parameters here: https://www.support.getzooz.com/kb/article/319-zen22-dimmer-switch-ver-4-01-advanced-settings/
You can do it with any combination of settings that you like, but my personal preference for these is to disable all "tracking" on the switch/dimmer itself and pretty much ignore the device on Hubitat for all purposes except the button/scene events it generates. I also don't expose it to Alexa directly; instead, just expose the smart bulbs themselves. Then use the ZEN22 as a button device that manipulates the bulbs as you want: e.g., button 1 pushed turns on the lights, button 2 pushed turns off the lights; multi-taps can do whatever you want; and holds/releases might dim up or down. To do this, you can set parameter 15 to either 0 or 1 (maybe 1 if you don't trust yourself to not accidentally turn the dimmer on/off via Hubitat) and parameters 20 and 21 to anything, but they might as well be both 1 so you minimize the number of events sent to the hub that you'll never use. In other words: the ZEN22 is then basically a remote, and if you want to set the bulbs to 50%, for example, you'd tell Hubitat or Alexa to set the bulbs to 50%, not the ZEN22.
Basically, there are two ways to do this. It sounds like you might be trying to do the first way (at least with one of your automations). I prefer the second. But either should work if you have the device configured correctly and a Hubitat app that works with that configuration (e.g., Mirror Me for the first or Button Controller for the second, or a custom rule for either).
Thanks for your reply, I am kind of new using Hubitat and the switches. I may read carefully all the options you gave me and check which one will be better for me. To be honest I havent play a lot with all the switches values but only disabling the load, below the actual configuration.
So far Alexa is only configured to control the lights directly through the Hue connection and not through Hubitat, haven't really check how to connect my hubitat to my Alexa speakers, probably I should start looking at this too. So far all the automation are pretty simple with mirror me or switch binding just telling them that if the switch or the light change status then the other one should change, nothing more, nothing complicate because like I mentioned so far.
I haven't gotten really into the Rules machine world as I thought for the lights I didn't need anything complicate. When I saw that mirror me and Switch binding were having issues I tried Simple rule Automation, nothing complicated.
What is a little weird for me is that everything seems to be working fine even when I turn the lights on with Alexa, the switch is still able to control the light and this respond as they should, but this doesn't happen when the light is on and I turn them off with Alexa, so what is the difference why one work and not the other? Even after I see the status of the lights changes everywhere in habitat and the Hue app, everywhere they are shown like if they are on, but the lights are not. when this happens like I mentioned the only way to make them work again is to restart the switch from Hubitat turning off and on directly from the device section, so the lights start responding again.
What devices are what in your screenshot above? I assume that one of "Comedor" and "Dining" is a ZEN22 and the other is a Hue bulb or group, but I can't tell from the screenshot, and the logs in the first post show entirely different device names ("Group (concina)" and "Kitchen"), so I'm just really confused.
You are right Dining is the zen22 switch and comedor is a hue group, with 2 bulbs. sorry for the difference in the devices name, I just wanted to show a little bit more info and because all the test I have done that was the only rule I left in the simple rule automation. I delete the others when I saw they didnt work, but it is the same configuration in all of them and I have tried the same in all of them (one zen22 switch with the load disable and one hue group, all of them with the same problem). In the other example Kitchen is the zen22 and Cocina is the hue group. Just wanted to provide a little more context and not create confusion.
Hmm. So that Simple Automation Rules app looks like it should work, though it will really only "sync" the on and off states, so you'd need something else for level. The Mirror/Mirror Me app should handle both. I'd avoid Switch Bindings, since that goes in both directions, and you don't want to turn the ZEN22 off under any circumstances (which that app will if the bulbs get turned off; switch state syncs in both directions). That could explain some of your problems if you were either using this app or had another automation set up to do something similar. If you want to avoid accidentally turning the ZEN22 off under any circumstances, you could set parameter 15 to 2 instead of 0 (to disable physical and Z-Wave control instead of just physical control).
If that doesn't help and you want to know how I would do it, I would keep something similar to what you have now but use a Button Controller or Rule automation (actually, I have a custom app, but these are built-in options you may want to use to get started) to respond to button (Z-Wave Central Scene, technically) events from the ZEN22. I would ignore the level and switch (on/off) events from the ZEN22. Multi-taps (and single taps, holds, and releases) on the ZEN22 will still generate button events on Hubitat, and I think it makes a lot of sense to respond to the button events instead. If you don't see button events, I'd make sure you're on at least firmware 3.01 (the back of your switch may say what it shipped with, but you can request an updated firmware file from Zooz as long as it's still compatible with your hardware).
Then, you can do something like I suggested above. For example, button 1 pushed could turn on the Hue lights and button 2 pushed could turn them off. You can use things like double-taps to set them to different colors or whatever you want. You can do the hold and release thing to dim, too, but you'll have to use the individual Hue bulbs (not the group) for that to get that to work the best way, IMHO, because Hue groups on Hubitat don't support the startLevelChange() and stopLevelChange() commands that make this work (though I wrote a custom integration that does).
