Thank you, long slow process but getting better every day.
I just ran a test scenario,
I opened my front door
Waited 5 minutes and then made a virtual presence sensor come home.
Nothing triggered because the door was already open.
Waited a few minutes past the 'considered' time
Opened a second contact and no announcement needed because I've been here too long.
I then went over and closed the front door. No announcement needed, been here too long.
The key to any announcement is the 'last activity time' found within any device page.
I recommend the next time you get an out of place message, go check the 'last activity date' of the presence sensor associated with that announcement (right away ). Would be interesting to see if it is within your 'considered time', even though you haven't left or come home recently.
Here is the log from my test: app:53552019-06-03 11:50:42.482 am debugIn contactSensorHandler - Contact: Living Room Front Door Sensor - Status: closed
app:53552019-06-03 11:50:10.081 am infoBryan - Front Door - Sensor 1 - No announcement needed. Time Diff = 5
@bptworld So not sure what you mean. Here is the last activity for the presence sensor that this issue occurred with. As you can see the device has been present since yesterday. The time diff is not working correctly in the app and/or driver. Also keep in mind this happens with all presence sensors I have Welcome Home monitoring.
Exactly! Look at your first screenshot of the device page, notice the Last Activity 9:08 pm and then look at your second screenshot, three lines below the highlighted blue line... lastActivity: 21:08! They are the same, as they should be. The app ran at 09:09 pm, which is less than the time you specified... so it made the announcement. Worked perfectly.
Remember, all it can do it pull from the device, so if the device says you just got there it's not Welcome Home's fault. You have something else going on with your presence sensor.
In this case you'd be better off starting a new thread showing how the lastactivity on the device page doesn't match the events page. Bruce won't try do dig through a post like this to find out what's going on. Would take too much time.
I haven't updated this in a while and I am noticing that there is a driver called WelcomeHomeDriver. Does this replace the Global Variables Driver? If I update this will I need to update anything in the app? My Global Variables Driver is 1.0.2 and my Welcome Home App is 2.0.2. I also use Departures App which I think also uses the Global Variables Driver.