Physical Switch/Dimmer as triggers are very useful to pause/resume lighting automations.
For my thermostat automations, it would be super convenient if digital setpoint changes made by Hubitat could be distinguished from setpoint changes that originate outside of Hubitat (i.e. "physical set point changes"). Such a distinction would make it easy to pause/resume rules that control indoor comfort. Which would greatly increase the WAF.
I don't think this platform change would break any existing apps or automations.
Have you tried this? Because I don’t understand how that would work if the thermostat drivers cannot distinguish between physical and digital events. AFAICT, they don’t.
Yes, I tested that piston I posted with my T6 Pro thermostat before I posted it. I changed coolingSetpoint on the driver page (got a Logical Event), and then with the Thermostat controls (got a Physical Event)
If you thermostat driver does not, it is just your particular thermostat and driver.
Ah, so you must be using the matter driver. Matter drivers for thermostats are pretty limited, so that explains it.
" * Missing feature from Matter: Unlike some proprietary protocols that report the physical running state, the Matter standard for thermostats does not mandate or consistently report this information in a standardized way.|
So I don't think this is something Hubitat can address for you.
" * Workarounds: In some cases, users have found alternative ways to get the information by routing through the thermostat's native cloud app, though this defeats the purpose of local-first Matter control."
That's not how "physical" works on HE. The hub only knows if the command came from itself (digital) or somewhere else (assumed physical - if the driver is coded to make a difference between the two).
Yes, but the Homekit integration uses matter, and that is between the hub and Homekit.
The device is not connected directly to Hubitat though, it is connected directly to HomeKit. Hubitat should see everything from Homekit as logical.
If the matter protocol allowed that information to be sent over matter though the Homekit integration that uses matter, the driver could use that. The device is not connected directly to Hubitat for it to make that determination itself, however.
No - as @jkudave has explained above. And as @hubitrep indicated, physical events occur from outside Hubitat; digital events are generated by the Hubitat driver.
No. This is incorrect. It uses the HomeKit protocol, which is not Matter.
Sorry, Google let me astray on that question. What about this from Google, then, about HomeKit?
"No, HomeKit cannot natively determine if a thermostat command was physical (made on the device itself) or logical (made via the Home app, Siri, or an automation). All commands, regardless of their origin, update the state of the accessory in the same way, so HomeKit only sees that the state has changed"
How does a Hubitat driver using HomeKit know physical from logical if it is not sent by HomeKit then?
Again, how does it know physical from logical when it comes from HomeKit though the integration then?
No, the HomeKit Accessory Protocol (HAP) does not report whether an event was triggered by a physical action or a remote/logical command. HAP focuses on reporting the accessory's resulting state, not the cause of the state change.
If you understood how Hubitat distinguishes between digital and physical events for the Lutron devices, you’d understand the same process applies for other connected devices.
