Piston not alway responding to device change event

#1

Good morning and happy holidays to all.

I have a piston that changes some radiators temperatures when me or my wife work from home in the week. It has been working flawlessly until maybe the last month or so.

The issue now is it won’t trigger from the virtual WFH switch. I say it won’t trigger, this is not entirely true. I can go in and edit anything in the piston (even keeping everything the same), re save, flick the WFH switch and presto, it works perfectly. Then it goes back to not working.

I’ve deleted and recreated the virtual switch, but still no joy. I tried removing optimizations, but it’s just the same.

I’ve posted the piston for some advice. My next step will be to create a complete new piston and monitor that.

In case it’s my error, I’m still curious to understand what’s going on here

I’ve been a big Core/Webcore user and a follower on the forums for a long time. My home would not be to the level it is without all the contributions made here. I’m incredibly thankful for everyone’s input, developers and users alike.

change temps for WFH
change temps for WFH.png1178×824 43.8 KB

(I placed a timer in there as the WFH switch also sends an IFTTT to set our Honeywell EVO heating to set weekend mode, so I want that to trigger before this piston kicks to fine tune. Working from home room requirements are different from an EVO programmed normal day off mode.)

WFH LOGS

Mark

#2

Had similar issues. What I do with my pistons is make a single trigger point only at the beginning. So try doing this,

If Switch Changes (this will be the trigger).
---- if switch is on
---- ---- do your on stuff
---- else
---- ---- do your off stuff
---- endif
end if

This has been the most reliable for me.

#3

A couple of things don’t make sense to me:
I assume Switch 18 is named “WFH Switch” - it’s receiving an event, but condition 6 evaluates false?
“Condition group #7 evaluated false (state did not change)” - I don’t see condition 7 in the piston.

Could another piston be colliding?

#4

@jsducote, interesting. I hadn’t noticed that and it got me thinking about possible corruption somewhere. At one point two versions of the piston with the same name appeared (I assume as a result of multiple sessions, I’m not sure - same code, different backup codes). I deleted one of them. I also recreated the switch and later, recreated the piston, but it still wasn’t working correctly.

The latest piston (created after the one posted above) strangely wouldn’t even recognise the switch was changing at all.

So I removed the switch from everything, deleted the switch, deleted the piston and started again fresh with new names. Everything seems to be working OK now. Thanks for your help.