New version on GitHub... 
update child app and driver.
1.0.3 - 05/05/20 - Added delay before status is updated
1 Like
Fantastic... and that was fast!
Can't wait to try it out.
1 Like
One more bonus for today...
When using 'and' you can set the number of sensors required to change status. ie. 3 sensors picked but only any 2 required to change status
1.0.4 - 05/05/20 - Added number of sensors required to change status
2 Likes
Heck I'm on a roll, might as well finish all the requests on this one today!
1.0.5 - 05/05/20 - Added Advanced Arrival section giving users a second set of arrival options
@dman2306 - this should cover the scenario you described.
1 Like
New version on GitHub...
1.0.6 - 05/12/20 - Added separate delays for Arrival and Departure
3 Likes
Bryan, can you clarify a nuance regarding the logic here? Say I combined three presence sensors to detect departure using "AND" and with only 2 of the 3 sensors need to be "not present".
Does that mean 2 sensors are in a "not present" state (one sensor triggered and the other sensor was already not present), or does that mean 2 sensors both changed states to not present within a certain period. I could see it working either way, just trying to understand how PP operates. Thanks.
Anytime a sensor triggers this app, it checks all sensors selected to see the status. So if 2 (or 3 or 4) sensors are "not present" state (one sensor triggered and the others are already not present), it would change to not present.
There is no within a certain time option.
1 Like
A follow-up to your answer, Bryan, if I may.....
If one of the presence devices triggers not present, and a sufficient number of other devices are present, will the master device change to present? Or the master device only will change congruent with the triggered device?
Okay, now I have to ask you a question... Have you installed the app? 
Under 'Departure Options'.
Look for 'How many sensors does it take to change status for Departed (leave blank for All)', you choose how many it takes.
Go ahead and install the app, play around with it, kick the tires. If it meets your needs, Great! If not, trade it in for something else. 
There are plenty of options here.
1 Like
Yes of course. And I have 8 children operating (big family!). My problem is that the scenario is such an edge case that, even with logging on, and a spyglass surgically attached to my eyeball 
, it’s difficult to infer behavior. Which is why I asked. NBD either way.
1 Like
Bryan,
First I want to say thank you for all the development you do. It is very appreciative. I'm just making sure that I'm not missing anything here.
Here is first thing that I have been seeing.
7:53:32 <--Presence Plus
7:48:50 <-- One: Life360
7:48:52 <-- Two: Hubitat Sensor
7:50:05 <-- Three: Wifi Presence Sensor
7:53:31 <-- Four: Unifi
The rule I have setup for departure is ALL 4 Sensors but 2 trigger.
However, as you can see it didn't trigger until the last one had left. One of the other things that I noticed is it doesn't detect the Wifi Presence Sensor at times or the Hubitat. I have done various tests that seems to indicate this. This does occur on arrivals too.
The other issue that is a little more concerning that had recently started (don't know if this is a result of Firmware update to the habitat) but suddenly with out reason (none of the trigger sensors had changed) the Presence Plus sensor changes it status. Yet none of the sensors had trigger this from the logs.
Some of this is difficult to narrow down when it happens and I don't see it right away; it can be hours later, missing the log information.
I would have to see a debug log to troubleshoot.
I figured you would need. I have the debugging for everything turned on. Once I get something I'll see it to you.
Untrigged event just happened.
2020-09-01 09:06:02.238 pm infoIn Presence Plus Driver - Turning Switch On
app:17332020-09-01 09:06:02.231 pm debugIn statusUpdateHandler - Sending ON for Present if needed (switch is off)
app:17332020-09-01 09:06:02.227 pm debugIn statusUpdateHandler (1.0.6) - pStatus: true
app:17332020-09-01 09:06:01.149 pm debugIn depSensorHandler - Arr - Will set status to true after a 1 second delay
app:17332020-09-01 09:06:01.147 pm debugIn arrSensorHandler - Arr - sensorCount: 2 - presentCount: 0 - theArrNum: 2
app:17332020-09-01 09:06:01.081 pm debugIn arrSensorHandler (1.0.6) - ArrTriggerType: false
app:17332020-09-01 09:05:07.228 pm debugUpdated with settings: [DepTriggerType:true, depNumOfSensors:2, runEvery:Every 1 Minute, ArrTriggerType:false, ArrTriggerType2:true, DepPresenceSensors:[Pixel XL Location/Notifications, Carrie Android, Carrie Life360, Carrie Phone WiFi], ArrPresenceSensors:[Pixel XL Location/Notifications, Carrie Life360], ArrPresenceSensors2:[Carrie Android, Carrie Phone WiFi], mySensor:Carrie Sarcone, useAdvancedArr:true, arrNumOfSensors:2, logEnable:true]
app:17332020-09-01 09:04:47.394 pm debugIn createChildDevice (1.0.6)
app:17332020-09-01 09:04:46.669 pm debugIn getHeaderAndFooter (1.0.6)
None of the presence senors are Present.
presence not present Carrie Android is OFFLINE DEVICE 2020-09-01 07:50:05.958 AM EDT
presence not present Carrie Life360 has departed DEVICE 2020-08-31 05:37:45.513 PM EDT
presence not present Pixel XL Location/Notifications has departed DEVICE 2020-09-01 07:48:50.341 AM EDT
presence not present DEVICE 2020-09-01 07:53:31.479 AM EDT
Okay, issue #1 - please read 'When reporting problems' from post number 1. I can't make heads or tails from that log. 
issue #2 - no such thing as an 'untriggered event'. Something has to happen in order for it to run. In this apps case, either something arriving/departing or the fails safe is run.
Will know more with a proper log. 
1 Like
I wasn't send the logs for issue1 because I had just turned all the logging for all of the devices for the one user.
However, I was send everything I had gotten from the logs in for issue 2. Please, let me know how to get the proper logs that you need.
For that user only thing in the log it was turned on
Presence Plus debugging only had
2020-09-01 09:06:02.238 pm infoIn Presence Plus Driver - Turning Switch On
app:17332020-09-01 09:06:02.231 pm debugIn statusUpdateHandler - Sending ON for Present if needed (switch is off)
app:17332020-09-01 09:06:02.227 pm debugIn statusUpdateHandler (1.0.6) - pStatus: true
app:17332020-09-01 09:06:01.149 pm debugIn depSensorHandler - Arr - Will set status to true after a 1 second delay
app:17332020-09-01 09:06:01.147 pm debugIn arrSensorHandler - Arr - sensorCount: 2 - presentCount: 0 - theArrNum: 2
app:17332020-09-01 09:06:01.081 pm debugIn arrSensorHandler (1.0.6) - ArrTriggerType: false
app:17332020-09-01 09:05:07.228 pm debugUpdated with settings: [DepTriggerType:true, depNumOfSensors:2, runEvery:Every 1 Minute, ArrTriggerType:false, ArrTriggerType2:true, DepPresenceSensors:[Pixel XL Location/Notifications, Carrie Android, Carrie Life360, Carrie Phone WiFi], ArrPresenceSensors:[Pixel XL Location/Notifications, Carrie Life360], ArrPresenceSensors2:[Carrie Android, Carrie Phone WiFi], mySensor:Carrie Sarcone, useAdvancedArr:true, arrNumOfSensors:2, logEnable:true]
app:17332020-09-01 09:04:47.394 pm debugIn createChildDevice (1.0.6)
app:17332020-09-01 09:04:46.669 pm debugIn getHeaderAndFooter (1.0.6)
Finally, the 4 sensor had change in hours.
Let me know what logs you need from where and how best to get them to you. I will have to wait and see if this issue happens gain. It's happen 3 or 4 times already in the past 72 hours.
I'm willing to provide what I can.
Again, see post #1 on how to report problems. I need a screenshot of the logs, not copy and paste.
Thanks
1 Like
Here you go it just happened again.
Presence Plus-Debug
Logging messaging for that sensor.
WiFi Sensor
Hubitat Sensor
Unifi controller sensor
L360 sensor
Please, let me know if this helps.
Alright, looks like it's just the Fail safe running. It's just double checking that the presence status is correct. It will run at the interval that you set within the app (you have it set to 1 minute).
BTW, only need the 'Presence Plus-Debug'. Save you some work.
Thanks
Correct. I noticed that last night too. It didn't capture anything only the saved settings. Thank you again for looking at this.
