There are reports of a different thermostat failing and of multi channel devices failing, all of which started at about the same time. Eric has identified an issue with response() . Definitely report this to support if you have the problem and you might want to give them the link to the following thread:
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(zw…
The other thermostat that started failing
Anyone having issues with these?
They’ve been rock solid using @meavydev DTH but today I’ve had to setpoint changes not happen.
Symptoms as follows:
CoRE changes the setpoint to a pre-defined value at a specific time
The device acknowledges the setpoint change
The stat wakes up as expected
All appears fine, ST app thinks the stat is at the new set point but the stat does not. For example ST thinks the Stat is at 18 but it’s still at the previous setpoint of 16.
If I then moved the stat the ST app updates immediately.
Any ideas?
Even if it’s not that specific problem, it does look like there was a platform change in the last few days.
Update: After a lot more testing, the initial issue I explained below always existed, but manually applying the response command to each item in the list didn’t always work either so I think there’s a larger issue with the way the parse result is being handled.
The one thing I do know is that if you use sendHubCommand and sendEvent instead of returning items from the parse method, everything will work the way it’s supposed to…
A few days ago most of my devices started reporting that they were offline and I tracked the problem down to SmartThings ignoring the events being returned from the WakeUpNotification event handler.
I ended up changing all of my device handlers to use sendEvent instead of using createEvent and that solved the problem, but it didn’t explain why it was only effecti…
1 Like