There is definitely a platform issue that is causing problems. I have had several reports from various users. I haven’t had time to fully troubleshoot, but one thing that seems broken is commands returned with response() are not being processed. For example, I have a multichannel switch that sends a SwitchBinaryReport when either physical switch is toggled. My handler, when receiving this report, sends a switchBinaryGet to each endpoint to find out which one has changed.
def zwaveEvent(physicalgraph.zwave.commands.switchbinaryv1.SwitchBinaryReport cmd)
{
logging("SwitchBinaryReport ${cmd}", 2)
def result = createEvent(name: "switch", value: cmd.value ? "on" : "off", type: "digital")
def cmds = []
cmds << encap(zwave.switchBinaryV1.switchBinaryGet(), 1)
cmds << encap(zwave.switchBinaryV1.switchBinaryGet(), 2)
return [result, response(commands(cmds))] // returns the result of reponse()
}
Well, I never get a response. Sending the commands outside of a response() (which is what my refresh() method does), gets a response. This type of behavior is being seen in several different devices that use response(). @duncan @slagle do you know of any issues that may be causing this?