Does this work for lights left on? Locks left unlocked?
I am trying to use this piston with my Inovelli light switches and Schlage locks. Neither of them are returning any messages.
Everything works fine with my door contacts. Attached is a screenshot of my configuration.
Also on line 24, 25, and 26 I noticed some devices not listed in doorsToCheck (line 17). They are all devices I selected when testing out but no longer need them to be monitored.
Similar logic could be used for lights or locks, but the piston would have to be revised because, as currently written, it checks the status of the deviceâs contact instead of switch or lock, as you can see on lines 56, 58, and 91 of your snapshot. Iâve never really given this any thought as lights and locks are easy to turn off or lock remotely if theyâve been on or open too long, but I would probably create separate pistons to accomplish this to avoid complications.
Also, note that you have an error on lines 40 and 93, as the originating piston is not correctly specified. If the originating piston is not paused and resumed, the âBâ piston may not always behave as expected.
With regard to lines 24-26, on the snapshot you provided those are fixed variables, so I donât think those are the lines you intended to reference. My suspicion is that you meant to reference one of list variables below the line that says âDo Not Modify.â If so, then what youâre describing is normal. Clearing and/or stuffing list variables has been a hot topic around here for a while, but I donât recall if the issue was ever fully addressed. In any case, while itâs annoying, itâs also harmless.
Everything was running fine up until 6 days ago when a notification started coming every 5 minutes for Contact Sensor 2 being open (should be every 300 minutes). Is there something wrong with the code?
Around this time the Smartthings app started getting the âSomethings Wrongâ error 90% percent of the time. Are these related?
Without a log, itâs hard to diagnose anything, but the fact that the app was working fine and then, without any changes, started failing around the same time as the âSomethingâs Wrongâ error began occurring, seems to suggest the problem may lie elsewhere. Iâd take a closer look at the log for errors, as that may help narrow down the issue.
this is probably a dumb question but how does this work without subscribing to any events to trigger it? Iâm getting that âno subscriptionâ warning on this piston indicating it wonât fire
ahhh lol, that explains the tags where you have to target another piston, so within the first piston you target the second and at the bottom of the second piston you target the first Iâm thinking, going to try this out thank you for the pointers! originally thought the second piston was an updated version of the first lol
do you have any idea how to modify the notifications? I want to change them to push notifications but they only show that they send an alert message to â{:xxxxxxxxxxâŚxx6}â
You can edit the text of the alert message on line 65 for variable alertmessage- that is the message you can send by push notification, sms if available in your region.
I noticed a couple of out-dated items that need correcting:
Is there any way to change the alert message to be a web request using the dame message information? I am using web requests via alexa to play audio notifications.
I expect that most people who have used this piston have modified the notifications to suit their preference. I myself have audio notification sent via web request to my Sonos speakers.
Generally speaking, for your purposes, you would use an expression to define the URL of the web request and incorporate the message variable into that expression.
Hello I was hoping to get some help. I successfully used your code on some freezer\fridge doors in my basement and it works great! No more defrosted meat! thank you!!!
I used your same basic code for my garage doors and modified it to shut them if left open⌠However I made a change to piston A that is not working 100% they way I want it to⌠I removed your âSmart Home Monitor statusâ check and added a Time check to work between Sunset and SunriseâŚ
It appears to work for every situation except 1⌠If the door is left open before Sunset and longer than the wait time, and then the time passes Sunset, the piston will not execute. This is the most important time for me as that is typically when the kids leave the door open the mostâŚ
Any thoughts on how to fix this?
Adding an inverted block to the very bottom should do the trick.
IF time happens daily at sunset + X min <-- Trigger
and Door has been open for X min <-- Condition
Then execute piston
END IF
Note: This block should only have one lightning bolt next to the trigger.
The lazy way to code this is simply:
IF time happens daily at sunset + X min <-- Trigger
Then execute piston
END IFIt has to be entirely outside the original IF block.
(and donât forget to add the proper offset⌠currently sunset + 5 min, or sunset + minimumAlertTime)
You can drag the block (at lines at 34-38) down to the bottom.
That is my confusionâŚ
The original Piston A code would do a check on the contact sensors and if found to be open longer than minimumAlertTime. This would execute Piston B which does a repeating check and sends out messages \ closes doors until the contact sensors are closed.
By me adding in the Timebetween sunset and sunrise condition, I think that it is creating a gap if the door is opened before sunset and stays open, it will evaluate the trigger and come up false. It does not check again once time passes sunset⌠Can use a piston to restart itself?
I do not think I want to have your code activate Piston B cause that bypasses the contacts check correct?
I was hoping that your code would force another check at sunset for this condition⌠Not sure if I am explaining this correctly
Correct. My advice was to point to the exact same piston at minimumAlertTime minutes past sunset
Pro Tip:
If your house is prone to lagging, you may want to use:
(minimumAlertTime + 1) minutes past sunset
