Apple home integration overrides power off/on behavior

[jtp10181]

If debug logging was on there should be more info. Also the Events tab from the device page has good info in it, like showing exactly what commands were called from apps, and in what order.

Screenshots would be better than copy/paste for readability. Use Windows Snipping Tool.

[JoeNY]

ok. here is on then off from the device tab:

and here is on then off from the home app:

[JoeNY]

here's the same info from the events tab:

[bill.d]

Lutron's native integration to Apple Home definitely behaves differently. I normally like to minimize hops, but Lutron's native integration just is not good. I've got RadioRA 2 and almost none of my dimmers are set to come on at 100% at the switch. So using the native Lutron to Apple integration is not satisfying at all. Hubitat's Lutron drivers let you set the 'on' level to fixed or previous. And Hubiitat's integration with Apple Home uses those settings when turning on (so did the Homebridge integrations). Much better.

[jtp10181]

Ok thanks that givces all the info needed I think.

@JoeNY Please verify, you are just tapping the icon for the light to turn on/off correct? Not opening it and using the slider?

@gopher.ny is this intentional where it does On then setLevel right away or is that coming from Apple Home itself? For some reason the integration is sending a setLevel 100 to the device causing the lights to come on then ramp up to full brightness instead of the last brightness. I dont think I get this with the Homebridge plugin.

I can do some more testing to get more data if needed, let me know.

[JoeNY]

Yes. I can confirm I am just tapping the light icon.

[JoeNY]

@gopher.ny any update on this?

[bill.d]

There was another user with a HomeKit issue yesterday. There were no good leads for the cause. I asked him to try removing/re-adding the device from/to HomeKit. It seems to have fixed his issue. You might try that.

[pexer95039]

I am having this issue too. I was Googling and came across this thread. There appears to be a bug in Hubitat's HomeKit implementation.

To test, create a virtual dimmer switch and expose it to HomeKit.

Find the dimmer on the Home App. Set the dim to 60%. Then, turn off the dimmer switch. Then, turn it on again. It should automatically set itself to 60% dim.

Now, completely exist the Home App (reboot your phone). When you tap to turn the dimmer back on, it goes straight to 100%.

This behaviour does not happen on native HomeKit devices, such as Philips Hue or Meross devices.

And because this happening on a virtual switch, it is not a driver issue. This issue is also occurring on Zooz Z-Wave dimmers.

[woodsby]

@pexer95039

Find the dimmer on the Home App. Set the dim to 60%. Then, turn off the dimmer switch. Then, turn it on again. It should automatically set itself to 60% dim.

Now, completely exist the Home App (reboot your phone). When you tap to turn the dimmer back on, it goes straight to 100%.

I can confirm the same behavior. I happened to notice this the other day and figured something flaked for a minute. But I just repeated this same sequence with the same results. I am running 2.3.9.176 - have been reluctant to upgrade due to posts I read about HomeKit and SSL issues.

[jtp10181]

@jtp10181

I just tested it with a Virtual dimmer and it does the same thing, those drivers are super basic. Basically just takes whatever commands you send and sets the device that way.

This is 100% something that Apple HK app is doing.
I am thinking Homebridge may be filtering this out, I dont think my lights do this and I have everything through HB.

I could probably have the driver block it, your example the commands are only 13ms apart. I would feel OK specifically blocking a setLevel 100 if it is sent within 100ms of an on command.

From the other thread

[pexer95039]

Thank you for testing.

This HomeKit dimming behavior still exists on the latest release.