Sorry for not originally including that!
All 3 device types have same behavior via HomeKit. Also they are all set up with Zwave secure pairing if that matters.
@gopher.ny so glad to hear fix is being tested! Thank you very much!
I'm noticing I can set any brightness level using voice commands now; that was failing before. But if I try to set maximum brightness/100% it ignores me.
Noticed the same situation with dimmers exposed to HomeKit.
The best thing is that SOME dimmers have this issue and some don't, and I have a hunch why.
For one dimmer, when I tap "on" in HomeKit app on my phone, the integration sends two commands, first ON and then set level (0).
But for another dimmer, it's in the reverse order:
And for this particular dimmer it just works, because a set 0 is very quickly followed by ON().
My hunch is that you had this bug for a long time, but you changed something that made the order of commands being issued now different, like unordered maps somewhere.
1 Like
@gopher.ny By the way, why does the HomeKit integration try to set the value when there is on/off command being issued? If the dimmer supports on/off commands, then it is responsibility of the device (or driver) to switch on with the last non-zero level, and this is how most devices do it.
1 Like
I have no clue. It's an incoming command. Could be that commands are queued up wrong? Either way, I could not reproduce the issue.
However, the log screenshot you provided should be enough to create a workaround, to be included in the next build.
1 Like
Did you this post on another thread also: Homekit dimmer switches - #59 by shaun.rockett
Has details and steps to reproduce. May be a slightly different issue.
1 Like
Still an issue with Lutron dimmers. Dimmer driver is set to come on at previous level.
Here is an 'on' event while keeping the Home app open. The dimmer comes on to the previous level as expected:
Here is an 'on' event after closing then re-opening the Home app. The dimmer comes on to 100%:
@gopher.ny very excited to hear that this might finally be fixed in next build!!
just to be clear, I dont think it is just matter of commands queued up wrong.
Correct me if I’m wrong, @bogus.wojcik mentioned above, the setLevel shouldn’t be called at all when just on/off command is made.
so when HomeKit just wants to on/off -> only on/off command should be made instead of setLevel as well.
when HomeKit wants to setLevel (and turn on) -> only setLevel should be called
Thank you!
It might not be fixed in the next build, but there will be some logic tweaks and added logging. Based on the feedback and that extra logging, it will eventually get fixed over the next few builds 
6 Likes
Here is the on command on zwave dimmer with latest build (2.4.1.155) with the additional logging via HomeKit.
That's all just normal and debug logging from the device itself, nothing from the integration.
@gopher.ny Does this extra logging need to be turned on somewhere? Is it visible to users in the system logs, or is it engineering logs for you?
2 Likes
The extra logging is in the engineering logs.
Checking now.
1 Like
I assume you have the Hub ID of @dismal.quakes.0x then. Don't look at my logs, I don't use the HK Integration. I am just facilitating because this impacts a lot of Zooz devices, so I hear a lot of noise about it. I could try to replicate on my test hub if needed, I have a couple switches on there already, Zooz and Leviton.
PMing my ID. I just ran through a cycle with both Lutron and virtual dimmers that have the issue.
1 Like
yes, I had sent my Hub ID to @gopher.ny previously. thank you all.
1 Like
@gopher.ny saw this in the 2.4.1.156 release notes:
Not sure if/what I was to expect with the 100% issue. In any case, there's no change, the 100% issue is still present.
The issue seems to be mitigated!
On 2.4.1.156
However, you can see the lights being turned on happening twice…
I think there is room for optimization?
Thanks for mitigating the main issue!
@gopher.ny setting dimmer percentage via HomeKit voice (Siri) doesn't seem to be working:
but setting it via Home app is working:
1 Like
It's amazing to see Hubitat finally beginning to address this long standing issue.
However, I notice the bug remains when using an Apple HomePod. If you say "Siri, set living room dimmer to 50%", nothing will happen.
Looking at the Hubitat logs, it seems like nothing is happening either.
2 Likes
My experience is similar to pexer95039. It remains an oddity why Siri works with my iOS devices and miniHomePods but not with my first generation HomePods.
