Maybe get @dJOS to start building them
Or perhaps to do the mod on the Emporia Vue units? Apparently there is a mod that can be done to them to make them local, but I don't have the skills for that.
Is this for certain?
It's definite but he will do warranties and support accessories.
Hehe, I’m so behind on my current projects ATM, maybe I’ll take a look in July.
good thing I pretty recently ordered (and received) one…
Emporia Vue is a great device, although not compatible with Hubitat
Seems like they're still shipping 120v kits:
They connect single, split-phase 120/240VAC, Input Power Rating
100-240VAC 50-60Hz
https://www.emporiaenergy.com/how-the-vue-energy-monitor-works
Iotawatt was unavailable for several months, in the US at least, but can now be purchased again.
It used to be possible to customize orders with the number and size of current transformer clamps needed for your install, but now it’s just one kit with several clamps.
Not a big deal since it’s not hard to source similar CT clamps from elsewhere if the kit doesn’t meet your needs.
Inching closer to Iowatta. How long does it take for Iowatta to recognize when a specific device has turned on or off?
a few millisenconds as best I can tell. If you want to round it out, 1 second. (I've tested this with my dryer) You don't wanna poll that quick though.
It depends on what you mean…
The IoTaWatt is scanning it multiple CT inputs very quickly and accurately tracks power usage. Definitely sub-second scanning on all of the input channels.
However, the integration that I wrote to use an IoTaWatt’s data in Hubitat, relies on a polling architecture. Thus, Hubitat will only know about changes in power usage after a polling interval completes. I would not recommend polling faster than every 30s for a fully loaded IoTaWatt. That is the polling frequency I use to monitor my washer and dryer circuits, to allow Hubitat to generate laundry cycle complete notifications.
@JustinL - what is your specific use case? There are definitely other technologies that can be used to simply know if electrical current is flowing through a wire, and thus know if a device is on or off. This could provide a much more responsive solution, as long as knowing how much power is being used is not critical to your application.
Certainly overall energy usage monitoring and tracking is the primary use case. Trying to gauge if applicance on/off status would be a realistic secondary benefit, or if that would be too delayed to be of practical use. Sounds like it would indeed be a secondary benefit for any use case where a 30s delay is acceptable! Would be helpful for cases like:
- was the electric oven left on when mode changed to away or goodnight?
- dryer on/off notifications
- is the hot water recirculation pump running
- is the dishwasher running and dishwasher on/off notifications
wish it could be used for knowing whether the gas stove is on/off but i don't know that it would consume any electricity once lit....
I use it for washer and dryer message triggers. Works very well for that. For second to second use, you can export to influxdb/grafana if you want to watch overall combined phases or individual circuits.
The IoTaWatt excels in this regard. It has a local onboard microSD memory card which it uses to maintain years of history. It has onboard graphing tools which are convenient for a quick peak at energy usage.
However, as @rlithgow1 menitoned, setting up a local InfluxDB server on your home network allows a nice target for the IoTaWatt to send all of the data. The IoTaWatt will even buffer data and transmit it later should the InfluxDB server be offline for any reason. Once the data is in InfluxDB, it is easy to use a tool like Grafana to display and summarize the information.
For the vast majority of large power devices that one would use to monitor with an IoTaWatt, I do not believe the 30s poling interval poses much of an issue. We really like the automated laundry notifications. Also, the average delay in the notification is really only 15s, as the timing of when the power level drops versus the 30s polling interval, can occur at any point during the delay.