That will be hard because it would be custom made for each of use. No one size fits all in this case.
Announcement
Collapse
No announcement yet.
Your method for House Modes & Occupancy?
Collapse
X
-
Originally posted by kideon View PostI still want to see someone write a plugin to handle all of this
https://forums.homeseer.com/forum/ul...n-for-homeseer
But I can write a new one, no problem.
Comment
-
Originally posted by alexbk66 View PostTo some extend my SmartDevice plugin was made for that
https://forums.homeseer.com/forum/ul...n-for-homeseer
But I can write a new one, no problem.
- Likes 1
Comment
-
Originally posted by viroid View PostI reset the occupancy status anytime an exterior door is opened or closed (seems redundant, unless you have children who leave the door open). Thus, once the house is closed, occupancy status is unknown until something within the house detects an occupant. I'll post my rules shortly.
Edit...
Photos of my WIAB Logic for the house are below; originally I had this in just 4 rules but I recently re-worked all of it to be a bit more modular when I started playing with the IFTTT integration for WyzeCam, thought maybe I could use those as a mechanism for detecting occupants. It is a lot more flexible as I can add new rules for occupancy detection devices without impacting any of the existing logic, and if one detection rule is misbehaving I can just disable it.
This just does occupancy detection and updates the house occupancy status. House "Mode" is a separate virtual device with it's own rules which are built on top of this base WIAB logic (and other stuff).
That said, there are two of your events that are troubling. It appears that you edited them by removing a Trigger, allowing the subsequent Condition to become a (non valid) Trigger.
In this first image you can see that the first Trigger is not valid as there is no Trigger on a device being at a value, only by being set or changed can a value be a Trigger. Look at the second group and you will see the correct trigger. The only way this Event can be fixed is to delete the primary Trigger along with the 3 associated Conditions, then add them in again. Or you can delete the Event and create it from scratch (do not copy the corrupted Event).
The second image shows a similar corruption.
These corrupted Events will usually not trigger at all, but may give unexpected results. To avoid this NEVER delete a Trigger, without first deleting the associated conditions. If it is your primary and only trigger, change it, do not delete it.
I put a post up in the Event Clinic Forum warning of and describing this problem here..HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
- Likes 1
Comment
-
Originally posted by rprade View PostThis discussion is interesting as we all have different needs and ideas as to how to achieve them. I use geofences from iPhones, motion detectors and a pressure sensor on the bed to determine occupancy and it works exactly as we need.
- Likes 1
Comment
-
Originally posted by rprade View PostThat said, there are two of your events that are troubling. It appears that you edited them by removing a Trigger, allowing the subsequent Condition to become a (non valid) Trigger.
In this first image you can see that the first Trigger is not valid as there is no Trigger on a device being at a value, only by being set or changed can a value be a Trigger. Look at the second group and you will see the correct trigger. The only way this Event can be fixed is to delete the primary Trigger along with the 3 associated Conditions, then add them in again. Or you can delete the Event and create it from scratch (do not copy the corrupted Event).
These corrupted Events will usually not trigger at all, but may give unexpected results. To avoid this NEVER delete a Trigger, without first deleting the associated conditions. If it is your primary and only trigger, change it, do not delete it.
I put a post up in the Event Clinic Forum warning of and describing this problem here..
I do recall noticing that the trigger wasn't quote right, but as the rule continued work, I left it alone. I'll go ahead and recreate them, thanks.
Comment
-
I simply use a countdown timer (i.e. 1 hr) - and any motion detectors (incl. cameras and alarm sensors) reset the timer. To be more exact - I have multiple "occupancy zones" - but they all combine into one "occupancy status". The only downside is - if we forget to press "Sleep" or "Away" manually - occupancy will go to "Away" after one hour. I.e. lights will stay on for an hour...
Comment
-
Originally posted by alexbk66 View PostI simply use a countdown timer (i.e. 1 hr) - and any motion detectors (incl. cameras and alarm sensors) reset the timer. To be more exact - I have multiple "occupancy zones" - but they all combine into one "occupancy status". The only downside is - if we forget to press "Sleep" or "Away" manually - occupancy will go to "Away" after one hour. I.e. lights will stay on for an hour...
https://forums.homeseer.com/forum/ho...ection-with-hs
Moving the house from awake to sleeping can be tricky, but WIAB solves a lot of the timer based occupancy detection issues as once motion is detected, it assumes the house is occupied until an exterior door is opened.
Sent from my LGUS997 using Tapatalk
Comment
Comment