spud
I have several events using ETs global variables and noticing, specially on Door Locks. Looks like the data is flushed too quickly for HS3 to process when there are events that occur within a second or so of each other? My PC is an I7 with a 12k benchmark... super fast so not a PC problem.
For instance...
simple 2 line Event using ET DoorLockAccess group::
THEN
Pushover $$GLOBALVAR:ETDeviceLocation1: - $$GLOBALVAR:ETDeviceStatus: - $$GLOBALVAR:ETDeviceValue:
ET is capturing/sending data (living room motion) which occurs seconds after I entered the door I just unlocked? (screenshot attached) I do not have a motion event that send that data, never have had that. Also, you'll notice the event just prior, with the same time stamp, is the old event that uses the actual device (not ET) works as expected.
You can also see it happened with Garage Motion... which, again, I dont have any event for that. Its being sent through the same door lock event.
I have several events using ETs global variables and noticing, specially on Door Locks. Looks like the data is flushed too quickly for HS3 to process when there are events that occur within a second or so of each other? My PC is an I7 with a 12k benchmark... super fast so not a PC problem.
For instance...
simple 2 line Event using ET DoorLockAccess group::
IF | Any device in group DoorLockAccess has its value changed |
Pushover $$GLOBALVAR:ETDeviceLocation1: - $$GLOBALVAR:ETDeviceStatus: - $$GLOBALVAR:ETDeviceValue:
ET is capturing/sending data (living room motion) which occurs seconds after I entered the door I just unlocked? (screenshot attached) I do not have a motion event that send that data, never have had that. Also, you'll notice the event just prior, with the same time stamp, is the old event that uses the actual device (not ET) works as expected.
You can also see it happened with Garage Motion... which, again, I dont have any event for that. Its being sent through the same door lock event.
Comment