Have any questions? Ask Sense! - April 2019



I’m collecting questions for April, so ask away!


Awesome, send my thanks to the team @RyanAtSense!


Why does Sense only detect one leg of a device? Or show the wattage from one leg even if both of a device have been detected?

On 240 device, the electricity comes near equally from both legs but sense commonly only see one side. Sometimes later (not always) it will detect the other leg as a different device.


That’s a great question.

Keep them coming, guys!


I actually have a question that would go along with @samwooly1 question or maybe its an idea or suggestion. I know that some 240V devices like EV’s in particular are hard to detect and accurately track because of the slow ramp down time at the end of the charge cycle so my question is it possible to have the device tracking software use both phases to better track when a 240V device has actually turned off for those devices that use two phases?


I believe it already does use both legs @mike_gessner.
I don’t quite understand how though. I had my first water heater detected (very first detection) by both legs at 4600 watts but then after removed and another installed it was one leg at a time.
My heat pump which I thought was one leg is actually both and has always been that way.
Why both legs are caught from the beginning and others aren’t, who knows? But apparently the software does look at both sides.
Where I think there is a problem is when it does see and detect one leg and lets use my heat strips for example; I had one leg, 7500 watts detected and that is half. When these strips at 7500 came on, the timeline increased by 15,000. So sense could see both legs but detected one and placed the other into “other”. Looking at the timeline it appears to be one device because it is. Sense does not but should be seeing this and recognizing it. This is a big failure I feel.


I guess what I am asking is can it be tracked by using the software to determine that the device is still on because both legs are increasing or decreasing by the same amount and only drop the device i.e. if the current drops by a specified amount meaning it was unplugged that way it can track it until it has completely stopped it charging cycle. it appears that once my car enters that slow ramp down cycle sense says my EV has turned off even though it is still charging and that slow ramp down cycle can take in excess of an hour to complete but if there was a way to keep tracking until it drops over a specified amount or has completely ramped down and both phases drop.


This is common for me on two devices. My washing machine and dishwasher. My washing machine will have a slight pause when the drum stops turning one direction and start the other. I bet about 30 on and off notifications for each wash cycle.
Not exactly the same @mike_gessner but I feel very closely related.


New User ---- Question

Is Devices display real time or historical some sort of recent average?

For some time on a quiet afternoon i have monitored:
on Devices: Always On = 968w
on Now: Current usage 634w



Hello @d26brait and welcome to the forum.
This thread is for compiling questions to “ASK SENSE” where they pick a few and then address them. So you won’t get an answer from support here but the manager @RyanAtSense will probably reply.
Understanding how “ALWAYS ON” is calculated would answer your question. There is one member in particular that has addressed always on numerous times and very knowledgeable about it. You can search his name and the subject to find answers but here is a thread that might be helpful.
Always on- real time?


How much progress been made on detecting variable speed motors? Is there still an emphasis on detecting these types of devices and we closer to having Sense identify these workloads?


On this topic of EV ramp downs is there any plans to do post processing of say the last 24 hours?

It certainly is very nice you have real-time data for when devices are on/off, but also having accurate trends is important. I think particularly EVs could benefit from a “second look pass” to fix the ramp down. I wonder if there are other devices that could be made more accurate (or identifiable) in post processing rather than real-time.