So I keep searching this thing, but yet to find it.
Want a rule to alert me if any windows are open and it starts raining. I installed the Weather Station 2 DTH, but can figure out how to use that to get if it is raining or not. Is it even possible?
Every time I use CoRE is am just more and more WOWED⊠so my latest, I have CoRE use the Blink cameras and if motion is detected to send my google voice a text which in turn sends me an email⊠(I sometimes have email, but no phone). Then it takes a picture⊠so here is the question, can I get CoRE to text me that picture?
Playing around with some notification optionsâŠwhatâs the difference between Notification and Push Notification? (I know what a Push Notification is, just wondering how CoRE/ST handles the two differently)
Ok, I believe I got the basics⊠now trying to move on to the more advanced.
What I have
If
both presence senors change to away
then enable Blink camerasâŠ
works great
so how do I add
BUT IF
either presence sensor returns disable the cameras? Part of me thinks that would be another condition⊠but no, then the then would be different⊠can I do this with one Piston?
What am I missing here. I want core to wait till ALL motion sensors are changed to awayâŠbut as I read this it will look at either not both. I choose ALL in the options
âŠfeel like Iâm doing something wrong with thisâthe If section shows as true in the app, however, in the dashboard it shows false and no notifications are sending.
Not sure if this is a reading comprehension issue on my part, or Iâm actually doing it wrong. Neither would shock me!
I do want it to notify me to shut the windows when itâs greater than 75 degrees outside, any temp sensor is greater than 72 inside, or (the worst) any inside temp sensor hits whatever it is outside. Currently reading 80 outside and 72 on two different sensors, nothing appears to happen.
Use a simple condition instead of triggers. Replace âchanges to not presentâ with âis not presentâ and âchanges to presentâ with âis presentâ. Then you can use All.
Since youâre using âexecute on state change onlyâ you need to design the piston to actually flip states once in a while. The ELSE IF is an OR in disguise. If any of the two is true, the piston is true. When both are false, the state flips to false. It seems like you never reach that false state? Try changing the mode to Latching instead of Else If.
âŠI can also get rid of the state change; I duplicated a similar one I had. In fact, if I do that, the If condition is true, but the piston remains false.
Latching is different. State becomes true only when it is already false and the main IF is true. It turns false when it is already true and the BUT IF condition is true. Different
The past few days my âstays on forâ events havenât been triggering, at least not reliably. They seem to fail to occur most of the time right now, although once in a while one will seem to trigger. Iâm going to reboot my hub and see if that helps, but are there other ideas & suggestions?