I have two doors in order to enter my apt, one in the first floor and another one upstairs, the inclusion of seconds on the time an event takes places (open or closed sensor) would allow me to know if someone is coming in or leaving my home.
I agree with @macutan that Sense events should include the full timestamp in the form hh:mm:ss just like the camera events. It would help in determining the sequence of triggers from sensors and cameras.
Hello. Same problem here. I want to setup either 2 contact sensors or a contact sensor and motion sensor to determine if someone is coming or going. But without seconds, this is kind of a bust.
BTW, @macutan and @jjr, are you using IFTT for automate actions? If so, how to combine multiple triggers? I am trying to setup google sheet to track the sequence of actions. Any tips?
I’m not using IFTTT yet, just the Wyze functions.
Yes, I am using IFTTT , need to install the second sensor but I feel through using IFTTT and Setting up a routine that would add a row to a spreadsheet should work as it will show which sensor was triggered first.
I’ve ran into a related issue that could be resolved by including full timestamp for the trigger time in the trigger data. I have a sensor on a door that opens and closes within seconds. Both events are being triggered, but IFTTT sometime fires them out of sequence.
I’ve had to set up a convoluted process using counters in HA to ensure that I have an accurate open/close state for the door and a method to trigger other automation on door open events.
It’s unfortunate that a local web-socket connection is not available to overcome the lag inherit to IFTTT, not providing the timestamp on IFTTT makes it even more cumbersome (if not impossible) to ensure that events on in the proper sequence.
Completely agree. Until we have seconds added to the timestamp, control will remain hit and miss.
I’m sorry, but I have to ask how hard it would be to accomplish this on Wyze’s end? I think that’s what irritates me the most about this problem. It’s probably as easy as digging into the code and adding “:ss” on a single line.
It’s just such an obvious omission…