Piston to Have Hue Wireless Button Control a Wired GE Switch Not Firing, Waiting at Sephamore

#1

1) Give a description of the problem
Built first piston under webcore, very simple, does not seem to be functioning.

2) What is the expected behavior?
Hue wireless button in ST (verified working and seen by smartthings including presses) to remote control a GE wired switch for on and off.

3) What is happening/not happening?
Receiving a waiting at a sephamore message in log, no action happening to fire GE switch even though the piston sees the Hue button presses.

4) Post a Green Snapshot of the pistonimage

image
image.png1178×466 20.3 KB

5) Attach any logs (From ST IDE and by turning logging level to Full)

0/25/2018, 12:34:44 PM +494ms
+1ms ╔Received event [Hue Dimmer Switch (ZHA)].button = released_off with a delay of 86ms
+10260ms ║RunTime Analysis CS > 24ms > PS > 10216ms > PE > 21ms > CE
+10262ms ║Piston waited at a semaphore for 10135ms
+10264ms ║Runtime (36764 bytes) successfully initialized in 10216ms (v0.3.108.20180906) (10262ms)
+10265ms ║╔Execution stage started
+10277ms ║║Comparison (enum) released_off gets (string) pushed = false (1ms)
+10280ms ║║Condition #2 evaluated false (7ms)
+10281ms ║║Condition group #1 evaluated false (state did not change) (9ms)
+10283ms ║╚Execution stage complete. (18ms)
+10285ms ╚Event processed successfully (10285ms)
10/25/2018, 12:34:41 PM +330ms
+2ms ╔Received event [Hue Dimmer Switch (ZHA)].button = pushed_on with a delay of 93ms
+10245ms ║RunTime Analysis CS > 22ms > PS > 10185ms > PE > 37ms > CE
+10246ms ║Piston waited at a semaphore for 10099ms
+10248ms ║Runtime (36762 bytes) successfully initialized in 10185ms (v0.3.108.20180906) (10245ms)
+10249ms ║╔Execution stage started
+10260ms ║║Comparison (enum) pushed_on gets (string) pushed = false (1ms)
+10262ms ║║Condition #2 evaluated false (6ms)
+10264ms ║║Condition group #1 evaluated false (state did not change) (8ms)
+10266ms ║╚Execution stage complete. (17ms)
+10268ms ╚Event processed successfully (10267ms)

#2

I don’t have this device but the first thing I’m seeing is it looks like the events pushed_on and released_off are happening within 3 secs of each other.

Also, the piston is looking for event pushed but the device driver is giving you pushed_on, now how to catch that event is the next question lol.

Edit: Try it in this format…

image
image.png758×392 6.52 KB

#3

Thanks, will try this shortly. In the interim I removed and re-added the Philips hue remote button back in. In doing so I realized there was a SmartApp called ABC(Advanced Button Controller) that basically did the same thing I was trying to do with the piston.

Here’s the interesting part - it also fails. It sees the remote and it’s 4 sub-buttons just fine, and can also tell a short press from a long press. But the smartapp is ineffective in controlling any other switches when it senses a press on the Philps Hue remote buttons, the same as the WebCore piston was.

For this reason I’m thinking that the device has been rendered crippled in a hub update, and the device handler needs work. Am I getting the most detailed logs I can out of WebCore? I’m wondering if we might be able to collect more info to see where the failure is happening in the hopes the creator of the Hue Alpha Device Handler (https://community.smartthings.com/t/alpha-hue-dimmer-switch-zha-beta-no-hue-bridge) to remedy.

#4

This was it! It looks like the syntax for this button’s commands changed somewhere and there was a mismatch. Changing that expression above to ‘pressed_on’ did it. The programmer in me enjoys this stuff.

Now I just need to add in the piston for the 2 off buttons and an additional one for the second on button (the switch has dim/bright as well but since my switch is just on/off I want the top 2 buttons to do ON and the bottom 2 buttons to do OFF).

Thank you! This was great!