WebCore Piston - Programmatically not working?

Sergio_Ferreira · 2017-07-13 19:44:31 UTC

Regardless if I use the Programmatically or Physical option the piston runs…
Any idea why?

regards

RobinWinbourne · 2017-07-13 20:18:23 UTC

The device handler has to report the details to webCoRE… most handlers don’t.

What device are you using?

Sergio_Ferreira · 2017-07-13 20:32:18 UTC

Aeotec switch.

thanks

RobinWinbourne · 2017-07-13 21:17:00 UTC

I’ve never managed to tweak a handler to make it work… and I don’t have any devices that already have working handlers so nothing to compare to for testing

Some info here:

What do these log entries mean?

I think (strong emphasis on think… maybe just believe) that this is the difference between the device’s response to the BasicSet versus the SwitchBinarySet commands. I encoded my device type over here to differentiate between the two. /** COMMAND_CLASS_BASIC (0x20) * Short value 0xFF for on, 0x00 for off / def zwaveEvent(physicalgraph.zwave.commands.basicv1.BasicSet cmd) { [name: “switch”, value: cmd.value ? “on” : “off”, type: “physical”, displayed: true, isStateChange: true] } /* COMMAND_CLASS_SWITCH_BINARY (0x25) * Short value 0xFF for on, 0x00 for off */ def zwaveEvent(physicalgraph.zwave.commands.switchbinaryv1.SwitchBinarySet cmd) { [name: “switch”, value: cmd.value ? “on” : “off”, type: “digital”, displayed: true, isStateChange: true] }