Recently I noticed my other usage was way up. I started looking into it and found around a week ago several previously detected items devices no longer have a bubble. Their usage shows as other now. My microwave, water heater and game room fridge are a few of the main ones. The fridge was the very first thing detected way back years ago when I installed Sense.
Has there been some change in updates or software? A new bug or is this part of the slow death of the stand alone Sense Unit as your attention is now focused on meter integration?
Pretty sure Sense has given up on improving individual device detection and switching to more of a category or type of device model. Which is more along the lines of what utilities and goverment want. Heating and cooling costs, fridges, cooking appliances, lighting, EV charging, etc… which can be used for device type peak demand pricing. Additionally for remote energy audits and programs for low income households.
I wouldn’t expect individual device detection to go away just more lumped together to conserve bandwidth, storage and processing on the backend. Showing non technical people they used about this amount for your fridges, is a lot easier and realistic than trying to explain to customers about ‘Fridge8’ who argue they only have 1 fridge. Can’t imagine what Amazon would charge for millions of additional ‘Sense customers’ using the same methods Sense has in the past.
1 Like
@obscuredtrip
I understand what you’re saying but the problem is they sold a Sense unit to ME not the Govt or a Utility. They were never stellar at detecting new devices so they didn’t stop improving. They gave up!
Also my utility Co. already has that capability (generically), They even send me a weekly summary that graphs usage. It compares to the week before, shows daily usage and weekly usage by kWh and cost. They even rate and compare me to other houses in my area.
Thing is my individual device detection did go away. I said this somewhere in another post that if I removed all the smart plugs and Hue lights my screen would be just an Other, Always on and one DCM bubble for the mini-split. The few things that worked without a reach around assist from another smart device are dropping like flies.
I export my Sense data to CSV and process it in a spreadsheet to look for trends. Below are two graphs comparing data from native devices that are also recorded by integrations. That ratio is expressed as a percent. A perfect match would be ideal, and would show up in the graph as a horizontal line at 100%.
The efficiency of each of these devices was originally fairly close to 100%, but they have all drifted since discovery. I think the Sense AI updates the device definition from time to time with the intention of improving things, but that is not achieved in practice.
1 Like
A bit ago I disabled integrations so see what would happen as I had a feeling my 50+ integrations may have been bogging things down. That didn’t help. I then reset my monitor but didn’t set up any integrations. ‘Microwave’, ‘Gas dryer’, ‘sump pump’, ‘Mystery Heat 1’ and a ‘Light’ have been detected. ‘Mystery Heat 1’ was my stove but shortly after started reporting cycling at random times for no reason. ‘Light’ appears to be some sort of 50w strobe light turning on over 50 times per min at times. I’ve deleted it a few times and it quickly comes back reporting even more on cycles each time.
I can’t explain why you don’t have any native detection, but I can say native detection has seemingly gone to hell especially as of recent. Seeming coinciding with smart meters coming online. Sense has not announced any major changes, ‘improvements’ or otherwise to ‘device detection’. They certainly wouldn’t announce any ‘downgrades’. They did announce the discontinuance of the ‘orange box’. Which leaves the only logical conclusion being that they are slowly changing things over to cater to the (more generic) utility segment and cutting backend resources that were previously dedicated to people like us. I can’t completely rule out the servers being overloaded, though there doesn’t appear to be the typical lag associated with such. It’s not just a delay with detection, it’s just not there as it once was.
