This all day. I have 8 smart outlets that report wattage like DCdyer, along with a DSB09104 that uses amp clamps like the sense that you can put on a single circuit (in my case a hot tub) that tells me exactly how many watts it is pulling all the time. This would be a great way for people with 240v applicances and cars to be able to help sense learn what is happening and what power is being used.
+1 on this thread. There is a TON of information in a smrtthings network that would make sense MUCH smarter. The smart plugs give direct energy listings (like TP-link) and the switch status provides energy insights. I’m sure the community would have an integration out in a matter of days if there was an open API. I have to believe smart things has a much greater bang for the buck vs. the existing integrations with TP-link or wemo.
Two issues with your basic assumptions…
- Energy sampling is far more valuable than switch status (on/off) when it comes to “ground truth” for machine learning.
- Fast, regular energy sampling is critical. The current HS110 and Wemo Insight smartplugs are sampled at somewhere between 1 and 2Hz (1-2 times /sec). I have seen numerous postings in SmartThings-land like the one below, that say Z-wave and zigbee meshes aren’t up to that task… Maybe I’m missing something, but are there SmartThings power sampling devices that communicate via WiFi ? That’s probably the real gating factor.
On the flip side, there seems to be a big overlap between SmartThings users and Sense users, so there could be good leverage if the right parameters are met.
I would assume the customer base trump’s what is technically simple to implement. Smart things has a massive community whereas TP-link is a niche product.
Smart things requires a different approach, you wouldn’t want to sample at a few hz unless customer complaints about crashing the network were a project goal. One minute polling is probably a realistic goal. For many devices that would be plenty accurate to garner better ML info. This switch was on a minute ago and is now off, power dropped by X is a pretty strong signal, etc. In a smart things home, you can literally know the state of every light switch, window and appliance – not to mention the integrations with other apps, like nest that tell you the heater is on.
Love the Cornell avatar
Hey thanks, on the avatar … Love the newish tough bear…
Agree that once per minute sampling would be sufficient for simple “digital” on/off devices with a single consistent power level like lighting, if the device’s off and on periods are many multiples of 1 minute. But outside of lighting and small fans, I can’t think of anything else that behaves like that.
I have a few reasons for believing that the 1-2Hz sample rate was carefully chosen for maximum benefit.
- Many of the power waveform features, like spikes and dips I see in both the Power Meter and in detail from my smarplugs, are 5-15 seconds in size. 1 second samples are sufficient to catch them.
- Most recent research datasets for power disaggregation, like REDD or ECO use 1 second samples for ground truth.
- Going too small, also brings complications. Going much below 10x per second, you start worrying about sampling alignment with respect to the 60Hz power cycle and about accurate data interval alignment.
ps: I can see integrations with smart thermostats as being quite useful, since a significant amount of electricity flows to both heating and cooling.
Yeah, the bear in my day was pretty sad
The power spike of a motor kicking in is definitely a 1hz phenomenon. I think you can see major appliances by the steady state in a longer time scale. An electric dryer is a pretty unique load as is a dishwasher. One option is to try to finger print the dynamic load, another is to look at power and dwell time. Nothing hovers at 4kw for 30-45min in my house except the dryer (followed by 10min cycles).
In any event, wouldn’t it be awesome if the sense SWE team solved this so we could end the debate?
Sense has solved the issue for me. My dryer is detected everytime.
Having a few smartplugs installed was eye-opening to me. I thought my washer might have a few simple modes/patterns, but a basic cycle looks like this:
Sure, there are places in the waveform where power is constant, but the multiple patterns are defined by the spikes and changes. A one minute sample would average most of the changes in this part of the patterns away.
Sense has detected some of our big loads like my dryer heating element as well as my furnace fans, but misses other components (dryer motor, furnace igniter and ignition blower). With the furnace (below), some of those auxiliary component features would only be resolved by a seconds magnitude sample (or smaller).
Even though it runs contrary to your home automation strategy, I would suggest you blow 30 bucks on a pair of HS110s and see what the unruly plug-in power consumers in you house look like.
Go Big Red !
Its going to vary ALOT by washer. You can see mine kicking in here and its very easy to detect on a low duty cycle. The refrigerator compressor has the telltale spike and ~1hr duty cycle, whereas the dishwasher looks like a resistor – this would be pretty easy to detect on 1/60Hz.
I have the TP-Link as well as smartthings. You can do a lot more (as its a much higher power standard than zwave). I agree its better, but I’m not going to rewire my home just to get a better sense signal – so the question is can they build (or enable the community to build) an integration with smartthings that extracts what is knowable.
Yes there are. For example my Sengled Light Bulbs are connected over WiFi to my SmartThings hub and do report power usage through SmartThings. I do not know what their sampling rate is though.
That said, ZigBee/Z-Wave should be fine for energy sampling as Philips Hue does it over ZigBee and is supported by Sense, so why couldn’t others do this?
Zwave energy meters are far more configurable. One device could be set to send power every x seconds, another set to send power on x wattage change. Sense would have no idea how the device is configured by the user. This plus cloud delay of smartthings is probably going to be quite the challengefor something sampling as frequently as sense.
You are right Frank,
ZigBee/Z-wave is sufficient for the event-driven Hue-type power reporting model, where the controller, rather than a power measurement device, updates the power usage in response to changes in the switch setting (physical or virtual switches). That model relies on the devices to have a time-invariant power usage that is a simple function of the line voltage and their intensity setting (0% to 100%). Zigbee can handle this model because the bandwidth requirements are much lower, and latency can be much greater. So yes, Smarthings could report power usage via that model, to Sense.
But that model doesn’t work for most devices. Lighting, and specifically LED lighting, is very well behaved over time (though all lights have a warm-up cycle, where the load changes a little). Some single speed, constant load motors and perhaps other devices may also be consistent enough to use this model. But eventually you get back to the other challenge, learning. Even though Sense obtains the estimated power data from the controller, the data is less desirable for learning. Why ?
- Features - may lack critical waveform features, that sampling would have provided.
- Latency - reporting delays may skew the data. I have seen Hues and Smarthings that have a half second or more in switch to light latency.
- Redundancy - why try to learn the device if the data is already provided, but is less amenable to machine learning.
Yes totally agree with those points, but that said Sense is using Hue w/ these “known” problems, so why not use SmartThings as well, at least for “the time being” until the ML gets to a point where these kinds of integrations are no longer “needed” as Sense can then detect them through ML!? I think the ML models are still far from accurate enough to even start to recognize lights, etcl.
Yes there may be certain SmartThing devices that have a variable power model, although I don’t know of any from the top of my head, nor do any of my 50+ SmartThings devices (that matter, ie that are connected to the power grid, and not run on a battery) have a variable power model as they’re all light bulbs and a “smart switch”.
@frankwin.hooglander, that approach would work, and if it is easy to do, would be a nice addition. But most of my response was directed at the proposal to have Sense read Smarthing smartplug data ahead of TP-Link and Wemo WiFi-based devices. I still contend that that Zigbee/Zwave-supplied sampled data is less valuable to learning, than data flowing from WiFi smartplugs, due to bandwidth limitations and latency.
I agree with Staze. I’d like to be able to hook Sense into SmartThings.
In fairness, I’ve switched to Hubitat. So I’d much prefer integrating with that… =)
Alternatively, exposing individual devices to Alexa or Google Home via their integrations would work too. ifttt is just too slow for a lot of it’s integrations. =/
Native ST or Hubitat integration would be great though. =)