Why are some log events marked [physical] though the event is produced by an automation action? I’m assuming that an event is tagged as physical when it’s caused by a person or thing outside the system performing an interaction, like pressing a button. The attached screenshot shows my porch lights…

[image] DZ6HD-1BZ does it need custom driver? Devices Unfortunately. It's a result of the way the driver works with Hail based devices. The device itself doesn't say that whether the change was triggered by a physical or digital command, it just sends a Hail message which …

The screenshot looks like it’s showing a preceding event that occurred about 3 hours before, so I think we’ve got all the events here unless I have an incomplete assumption about the data or this view. If a second event/response was logged, would it be shown here?

[image] aaiyar: What device is this? This is a Leviton DZ6HD Z-Wave Dimmer.

Did you already mention what type/make/model of device is involved, and which Device Driver you have selected for it (under Devices > device > detail page)?

[image] EdwardCorvus: This is a Leviton DZ6HD Z-Wave Dimmer. I used to have those. Not sure if it's a driver or device issue but those do no report physical/digital correctly. The bottom line is that physical vs. digital is often not very reliable. You must know how each device behaves. Can …

I looked around in the view for this device but couldn’t find which driver is in use. Do these screenshots show it? Is the driver called “Leviton DZ6HD Z-Wave Dimmer”? [image] [image]

[image] EdwardCorvus: Leviton DZ6HD Z-Wave Dimmer Please read this thread: [image] New driver for Leviton DZ6HD Z-Wave Dimmer in ver 2.2.4.148, several bugs 🛎️ Get Help The only way I found to implement the new driver was to exclude each device and re-include them …

Correct. If that were a custom / 3rd party / community driver, then you could read its source code under UI > Drivers Code to see how it is dispensing event data. Unfortunately (for you), the built-in drivers are not Open Source and therefore unavailable for review in the same way.

Thanks! It looks like this thread ends a couple years ago with @dennypage mentioning that there is a bug in the driver causing the device to report physical events . What’s a good way to ask Hubitat for this official driver to be fixed?

[image] EdwardCorvus: What’s a good way to ask Hubitat for this official driver to be fixed? You can submit it as a feature request. Or tag @support_team (which I've done). In the meanwhile, does the generic driver work (as @dennypage indicated)?

Thanks! I’ll try changing drivers to see what the results are.

Why are some log events marked `[physical]` though the event is produced by an automation action?

Custom Apps and Drivers Custom Drivers

aaiyar February 14, 2023, 4:41pm 17

Please read this thread: