Why is the word [physical] tacked on to the end of some of my devices? I am not pressing the physical button on the device, just controlling it with other button switches and timed events.
What button switches?
Aeotec NanoMote Quad.
Any z-wave direct associations?
Not on this device or the NanoMote controlling it.
This doesn't make sense to me. (I know, I'm SO much help.) 
Maybe share the automation that turns the bulb on/off whenyou press a button on the NanoMote?
And just to confirm - things are working fine, you're just wondering why the "Physical" notation in the logs, right?
Okay I turned the dimmer module on an off from the button , followed by on/off from the Hubitat device page In both cases it reports the [physical] info. Perhaps the Leviton DZPD3 is at fault. FIY I'm using the Leviton DZ6HD driver (which is supposed be the same hardware but packaged in a plug-in device instead of wall dimmer).
So your switch (dev295) is your Leviton, and it's named "Bedroom Lamp" and it's controlling a lamp w/a dumb bulb in it, correct?
Try controlling the "Bedroom Lamp" device directly from its device details page on the Hubitat hub. This will take the button device and App out of the equation for a quick test. When you control the "Bedroom Lamp" from its device details page, do you still see the [Physical] showing up in the "Events" subpage of the device's details page?
Have you clicked CONFIGURE on the device details page for the "Bedroon Lamp" device? It sounds like you may have changed the driver type, and one should always click CONFIGURE after doing so. This tells the physical device how Hubitat expects the device to send status updates to the hub.
1 Like
For what it’s worth, I have noticed all my Sonoff S31 lite plug in modules are like this and keep reporting their current state using the Generic zigbee outlet driver.
I have learned to disable description Text logging on these devices.
I'm not so sure about that. The DZPD3 I had was a z-wave device, while the DZ6HD is a z-wave+ device.
What happens if you use the "Generic Z-Wave Dimmer" driver with your DZPD3? Or, if it genuinely is a z-wave+ product, the "Generic Z-Wave Plus Dimmer" driver?
Also, click Configure as @ogiewon recommends!
Yes, dev295 is the Leviton dimmer, attached to a table lamp with a dumb LED bulb. In my previous post I switched the device on and off using the Nanmote button and then from the device details page and it shoed up in both.
This is not something new. The device has been installed like 2 months. I turned on text logging for most devices for a different issue, and this showed up. Note there doesn't seem to be anything wrong with controlling the device, I am just curious why this is happening.
The button on the Nanmote just turns 'Bedroom Lamp' either dimmed or off with no other devices or rules attached to the buttons.
Either the driver (and hub) are unaware of the device's capabilities (pressing Configure will fix that), or there is a mismatch between the driver and device.
Actually this is a DZPD3-2BW which is a Plus device, I will try switching drivers to see if it makes any difference.
1 Like
No, press Configure if you haven't done that first. The driver might be ok for it.
Okay, I fixed it. I switched the driver to the "Generic Z-Wave Plus Dimmer" and it went away. Would be nice in a future version to have a dedicated driver for the DZPD3.
Are there specific (or essential) device capabilities not addressed in the generic driver?
Where is "Configure" button? All I see is "Save Device" on the details page.
Here's an example for the Generic Z-Wave Plus Dimmer driver. But built-in drivers for all physical devices will have a Configure button.
Whether a community-developed driver has it or not is up to the developer of that driver.
I went back to the Leviton driver and did a "Save Device" and a "Configure", and the [physical] indicator came back.
1 Like
