$currentEventDevicePhysical

#1

Hi

Is the command $currentEventDevicePhysical [still] supported?

I ask because I have multiple non-dimmer GE switches that DO support $currentEventDevicePhysical detection; note the dimmers do not. Functionally they worked just fin in the old Core.

Roundabout May 3 2017 I asked in the thread “[DEPRECATED THREAD] webCoRE Beta Milestone 1”, post #283 if the switch attribute interactions Any, Physical, Programmatic are available. AT THAT TIME, I was advised they are not & to use $currentEventDevicePhysical…

Here is my code in use; no matter how I interact, by pressing the wall switch, through an app or via code, it always reports as FALSE

image
image.png701×255 8.58 KB

But alas it appears this is no longer functioning, at least not for me… Is there any other recommended way to detect if a switch was switched on or off programmatically or physically?? Or am I missing something very obvious?

Thoughts please, clever peoples.

J

#2

There’s an option for physical or programmatic rite in the builder.

2322E83F-C99C-4A2B-95B1-18D7DA0C38B1
2322E83F-C99C-4A2B-95B1-18D7DA0C38B1.jpg1242×2208 298 KB

#3

Thanks, I know about that option
But it doesn’t address my question…

Does $currentEventDevicePhysical work or not, for if it doesn’t we cannot check programmatically any more. Perhaps @ady624 can weigh in on this.

Thanks
J

#4

It should work, provided your DTH offers support for it - it relies on a piece of information passed along with the switch event. Check your IDE events and see if isPhysical is provided in those events.

#5

Hi @ady624

I am not home right now & will check tonight to be 100% sure.

BUT, keep this in mind:

  • the DTH (stock ST “Z-Wave Switch”) is the same one I have been using since forever
  • the device is a GE 12722 Switch which does support it in hardware (the GE Dimmers DO NOT)
  • it worked flawlessly in Core

I still have my instance of Core installed & will recreate a test for it tonight as well & report…

Thanks
J

#6

@ady624 & Others

It looks like both Adrian and I was right, Adrian more so of course!

As mentioned, I didn’t change my setup at all & $currentEventDevicePhysical stopped working (this is the part where I am right :slight_smile: )

In the post shown below (post #527) it is explicitly mentioned that Hub firmware 18.18 BROKE / REMOVED support in the DTH & this is no longer available at all for the “Z-Wave Switch” handler, and that a custom handler will be required. (this is the part where @ady624 was right)

So now I have to ask, WTF. It appears to have been working just fine for many, many of us. And I seriously have to ask how it could possibly have been negatively impacting the ST world. All I know it is now worse off because the functionality hasn’t been replaced with something better, or anything else for that matter.

Yes, I could use another DTH, but then it won’t run locally anymore - catch 22, or in the that case of DumbThings, 1 step forward & 2 back.

It also means that functionality like @Baz2473 pointed out ALSO no longer works, which I confirmed.

Anyways, rant over
J

#7

Sorry :frowning: that sucks