activation can have the same time stamp from the same sensor to allow the server to distinguish between valid activations with the same time stamp and duplicate activations with the same time stamp an 8 bit counter see table 1 can be incremented with each activation if the server sees two activations with the same time stamp from the same sensor but different counts both activations are valid otherwise one is a duplicate and can be discarded multiple hubs may not have perfectly synchronized real time clocks rtc in the case where two or more of these out of sync hubs are within range of a single sensor each may record and time stamp the same activation event but the time stamps will not match this creates a situation that makes it difficult for the remote server to detect duplicate activations unless an 8 bit activation count is implemented by the sensor the sensor will create an 8 byte event record for each activation that occurs see table 2 this record will be transmitted to the nearest hub the event record will contain a factory programmed 32 bit device address that is unique to the sensor an 8 bit device id that will distinguish the current sensor from other sensors designed in the future an 8 bit event id to identify what kind of event occurred an 8 bit activation count to identify duplicate event records and an 8 bit time offset to resolve activation time for multiple events occurring before they can be transmitted the device id may have a value from 0 to 255 that identifies the type of sensor from which the event record originated the value.