I would put it this way - different machine learning problems require different machine learning network structures and associated data sets. Machine vision and autonomous driving machine learning have had thousands of researchers working for perhaps 10 years to to build comprehensive datasets (for training and testing) and to devise the most efficient and accurate types of networks for each… The Sense flavor of machine learning (power disaggregation or non-intrusive land monitoring - NILM) hasn’t had comparable resources targeted at it just yet, and most development has been against a diffuse bunch of different datasets. Sense is the one company that seems to have the ability to put together a comprehensive dataset, at least for the North American market.
The following examples might give you an idea of how the breakthroughs in image recognition and autonomous driving happened. It’s been a combination of collaborative datasets, competitions for the best results, plus accumulation of massive datasets. The same is likely to happen one time with Sense, but Elon is a little over-optimistic about how the process happens…
The Imagenet Challenge - competition to create the best neural network for vision.
Imagenet - the real breakthrough - a comprehensive dataset.
The race is on in autonomous driving. There are many public and private datasets as well as many competing models (neural network architectures). The winner is likely to be the guys who have the best datasets and are able to make use of academic competitions to create the best proprietary models. I have done a little work with one of the models, Mask R-CNN. But we’re only about 3 years into the adventure.
One more comment… We’re still in the early going for machine learning in another dimension as well - hardware. Machine learning is still mainly run on traditional Von Neuman processors (Intel, AMD, ARM) as well as traditional GPUs (NVIDIA, AMD), and FPGAs, though it’s not a good fit for any of these for power or performance efficiency. We’re seeing new hardware, especially for machine learning training that substantially speeds up and reduces power usage during training, and inference (detection in Sense-land). We just have to realize that machine learning is very early in it’s life cycle…
Keep in mind that Sense does not use AI, it’s machine learning and worlds apart in how the two work.
I’ve gone a couple months without detections and others even a year or more. After a couple months of nothing, I got a couple this past week. Not good one with history or anything I’ve been able to locate just yet.
The long spells of zero detections are just part of the experience.
It is puzzling as to why. My Keurig is detected the opposite of yours. I have a detection for when I brew a cup but not for the backup heater.
Hang in there
In several years, they have not been able to add something as simple as charging 9 cents per KW for the first 1,000 KWh then 12 cents per KW for additional use. A crappy programmer and a crappy tester could implement that in a day. How do we know if they are even working on improving their ML algorithms and code?
This and may other “this simple thing could be added” comes up all the time.
It is never that simple. Sure, an adjusted calculator like you suggested may be “easy”. But what about the more complicated version. People frequently ask for Time of Use… Now time of use with seasons. Ok, how about time of use, with season, with usage tiers. Those are much more difficult. Not just in the math, but how is the UI managed. What assumptions do they have to make. How many different slight variations of the above exist. How do you build to allow for all of those.
Then they make some of those decisions an implement some form of a new kWh $$ calculator, but what other versions didn’t they take into consideration. Now they are hearing from customers who are un happy because they took care of use case X, but not Y or Z. What is important to you may not be to someone else. Yes, there seem to be a lot of people who have TOU or tiered plans, but there are plenty that don’t. As said by the Sense team many many times, they are a small company. They have to prioritize resources and focus on features that impact the product and matter for the most people and the core product.
THE feature that Sense is marketed for is device detection and device usage. The money calc is just a handy sub feature.
I do not work for Sense, but I do own and run a SaaS platform with a growing client base and go through these development hurdles on a daily basis. Do we add the feature that client X is asking for? It is a simple code change, but what are the repercussions. What will it lead to next.
In its simplest form, its the adult version of “If you give a mouse a cookie”.
It is not about never giving anything because it just grows, but you have to take into consideration what giving that thing means and be prepared for where it leads next.
Second, in 2018, we increased the number of accurate device detections in homes by around 50%. On top of that, we introduced Community Names, smart plugs, broader EV detection, major refinements to how Sense refines its models and much, much more and we continue to push out model updates and improve our ML infrastructure constantly. I’d say that counts as “working on improving our ML algorithms and code.”
Third — For tiered and ToU support, as has been noted by us and others, it’s far from simple. For ToU, there’s a pretty solid overview of that (including some deep diving by @kevin1) here: Time of use pricing - #4 by MachoDrone and @ben gives another overview directly above . Moreover, even if it were simple, many factors inform product dev decisions beyond just ease of implementation.
At six months and four days, I have 41 active devices. Most of mine were detected in the first few months. Compare the rate and timeframe to what users experienced a couple years ago and it’s clear they are constantly working on ML.
Let me just add a simple caveat based on @samwooly1’s reply. Sense will work well in most homes and will detect a lot of devices. However, this is not necessarily true for every single home even if compatibility specs (200A, split-phase, good wi-fi signal, proper temp. range) are met. Sometimes other devices or utility line noise just get in the way and prevent good detection. For that reason, we offer a lengthy return period.
Yes indeed. In my case Sense engineering got involved and narrowed my problem down to a constant pressure (which uses both variable frequency and variable power) deep well pump, which creates “noise”. That not only prevented detecting the well (used for both my geothermal system and my domestic water) from being detected, but prevented reliable detection for most of the rest of my home.
Somethings are difficult, and some things are impossible.
Personally, I’d categorize multi-tier cost reporting as one of the least important features, because I (and many others) bought Sense to help us see where our power was going and that’s all about devices and KWH.
I would expect device detection to increase significantly in a year, even without any effort made to alter the algorithms, due to database population with new data.
I am from Texas where we chose power company on the web site powertochose.org. There are 3, 6, 12, 24, and 36 month contracts. I have always favored 6 & 12 month contracts. Hence, I have been thru quite a few electric companies to pick contracts every 6 months. Common: rate tiered by amount of usage. Rare is time of use plans.
Most people don’t know what a KWh energy unit is (most even confuse it with KW power unit). Thus, I think getting the simple usage tier would 1) be beneficial to FAR more people than the time of use tiers, 2) would benefit FAR more people than adding Alexa, Google Assistant, Hue, and the other things mentioned, 3) I see no reason to deprive the bulk of people from the usage tier simply because you are not addressing the more complex time of use tier. That would be like saying you are not going to implement Hue integration because you are not implementing LIFX!!!
You say people would complain if you implement usage tier but not time of use. Well, consider me complaining that you implemented Hue and not LIFX!!! lol
Bill, I’m not going to argue relative merits of TOU vs tiered vs Hue enhancements. But if you honestly want a quick and easy way to do tiered pricing calculations I can send you a spreadsheet or R code that does exactly that. Interested in being able to do your calculation today ?
One tricky part of the calculation for my utility, PG&E, is that my billing period doesn’t line up with a specific day within a months so I have to input a list of billing periods start dates as part of the calculation. How does it work for you ?
I would t write off the possibility that this feature will never be available , as @andy stated, it has to do with the priority list.
I’m on flat pricing but thinking of making the switch to TOU so it’s a feature I’d like to see also. When you visit the product wishlist, you’ll see tones of features that we all ask for. There are things I thought should already be there and are not. For instance, I would like to view the timeline without internet. Looks like it would be very simple from my point of view but I’m trying to be patient and enjoy the great features it already has.
In my early weeks I felt as you do and was quite outspoken about it. It took me some time to settle in. Thanks to the community my overall experience with Sense is terrific. There are many things I feel NEED improvement. Voicing your thoughts and opinions here is a great way to eventually get these things implemented.
There is all sorts of noise possible on incoming power lines and it’s highly dependent on the provider, distribution topology, neighborhood, age of systems, etc. “Noise” is caused anything from lightning, to equipment arcing, to high tension arcing, to other users of the local service. It varies from time to time.
The theoretical pure sinewave power that can come from a generator via a Utility is subject to all manner of corruption in delivery and distribution … not the least of which is the varying loads that are being supplied (i.e. the Devices on the customer end ultimately influence the purity of the distributed power).
The link you quote I believe is about RF interference (RF noise) created by power lines and is not specifically about the “line quality” referred to by @RyanAtSense, though technically there is some crossover.
Out of curiosity, have you thought of separating your noisy pump by placing the Sense CT’s after the pumps power and before all other power?
I’m thinking that if that pump was upstream, the rest of your home may be detected
There is also a potential method where you could loop the pump feed wires back through the CT clamps along with the mains [“in reverse”], though it would be tricky if the panel wiring is too short to allow that.
Real electricians would need to speak to the efficacy of such a method. I’m just guessing.
I haven’t, partially because that would require a major re-wire in what’s already a moderately complex (main box, auxiliary box, generator box, solar box, etc) configuration. Sense has already cost me hundreds of dollars in electrician fees, and I hate to make it even worse.
It also would remove one of the primary reasons I bought Sense in the first place, e.g. monitoring my geo-thermal system…by FAR the largest draw…which uses the constant pressure deep well pump.
I was afraid that pump was a main reason for monitoring. I also understand the added cost involved in making such a change. For those of us able to do our own electrical work, the cost is t that bad. It’s the labor that’s so expensive when hiring it done.
I know you’ve had problems with this pump from day one and it seems you’ve had more problems with this type of noise than anyone else. I hate it for you and would like to see something to help you you out with it. With more and more geothermal systems being installed these days, Sense is going to have to put more into this issue.