So, I’m attempting to setup some home arrival TTL. I have everything working in core with one main problem. Our doors have TTL notification messages for when they get open, for example ‘Front Door Opened’ since we have little kids and my wife wants to know if they run outside and via which door they ran outside. (Especially my 3 year old, he takes off.) My arrival core rule is set as follows;
“If wife presence sensor changed in the last 3 minutes AND wife presence sensor is set to ‘present’ AND either front door or garage entry door opens, then play greeting via SONOS.”
So, I can see in my core engine rules that this rule does trigger, but so does the ‘Front Door opened’ message, and all we actually hear is the ‘front door opened’ message occur. Since I have 2 rules both triggering to the same device, how do I overcome this? I tried turning on ‘global override’ to the wife arrival greeting rule but that didn’t change anything. Suggestions?
Add the two conditions to a basic piston, then tap the AND in between the conditions and change it to THEN IF. Also, the door will be a trigger - the only thing triggering an action.
IF
Front Door changes to open
THEN IF
Wife was present for leas than 3 minutes
>>> when true > using sonos play text "hi honey"
>>> when false > using sonos play text "door open"
If this helps you to help me, I had removed core at one point. before removal everything worked just fine. Now I’m trying to reinstall it and running into this problem. Could it be that something was left over causing the problem? As far as I know I deleted everything related to core before reinstall.
I have noticed I have some pistons showing up in my activity feed when I would have thought they wouldn’t be triggering. I think they are being triggered by motion detectors seeing motion. The multiple conditions prevent the piston from ever being true as well as I have set the only execute during an alarm state that is not active as well as set the task to only run on state change. The tasks are not running as the conditions don’t evaluate to true, but is there a way to prevent it from running in this manner? Maybe this is just how the activity feed works, I’ve never watched it too closely, but wasn’t sure.
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
4332
I’m pretty sure you’re seeing the built in recovery actions of CoRE
Basically I have a dog door that allows the dog into the garage and another dog door that allows the dog outside. If any garage door is open ( all matched with sensors) or either side door is open I don’t want the dog doors to unlock. So she can’t get into the garage while we pull in or run into the street if of the door is open. The pet safe doors have a small RF tag that hangs on the dogs collar, that only allows her into the dog door and not other animals.
i’m trying to sync a virtual dimmer LEVEL to my RGBW sonoff switch, but i think i need to store the level of the RGBW sonoff switch to a variable and then set it to the virtual dimmer, but i have no clue how Anyone?
Try a simple piston. This will give you IF/THEN/ELSE.
IF - ALL of xxx doors IS closed
THEN - using xxx locks - UNLOCK
ELSE - using xxx locks - LOCK
This will unlock the selected doors if all selected contacts are closed. If any of those contacts become open then the piston is now false and will lock those doors.
Also wondering about how these dog doors work? Are they the connected ones that lowes sells? Isnt the purpose of the rf tag to unlock the doggy door if it’s within range?
Can I use CoRE to refresh or poll a sensor for an up to date temperature reading, I have looked, but it’s not obvious to me how to do this, I have seen threads with other people doing this I believe.
Yes its possible. Now I would be worried about battery life depending on how frequent you want to do this. What kind of sensor are we talking about here? How do you want to update the temp, every so many minutes/hours, when certain events happen, etc.
I see reference to watching for UserCode (for locks)in the main CoRE release candidate thread, but I can’t see where it is in the piston settings… am I just blind?
