Device Off-Event Detection: I’m one of Sense’s biggest fans, however - I’d like to get the community’s individual feedback/input on the below-listed observation. This is a base-function, cornerstone to Sense’s level of accuracy and touches every customer - regardless of their local configuration (solar or non-solar) or available powered device types (EV, Smart Home, or standard appliances).
Conditions: Always On is (87w), quiet electrical signatures, and strong Google WiFi mesh network signal of 361 Mbps (up) / 34 Mbps (down)
Observation: I opened the microwave door and the internal light came on. After about 10 seconds, I simply closed it - without using it to cook/warm anything. Sense indicated that my microwave’s natively-detected (29w) appliance light-bulb was on from (3:53am - 5:47am) and again from (6:39am - 7:05am).
Results: Obviously, these are two clear indications that Sense successfully identified the On-Event - triggered by the light turning on (door open). Unfortunately, Sense missed the device’s final “off-event” triggers - light off (door closed). Subsequently, the resulting “Event Timeout” function engaged to act as the default Off-Event . Sense shows me various examples like this, throughout any standard week, involving various types of devices - despite active electrical activity levels (quiet or noisy).
- What are your individual conditions and experiences?
- If this occurs for “detected” devices, does it happen to non-detected “Other” devices?
- Are programmatic adjustments made to adjust “Always On” and if so, how fast are the adjustments made?
- Is the Off-Event detection information availability anywhere or is it encompassed within the Sense area of proprietary information?
I’m eager to hear your answers!