A way to document known always on?

Feature Requests
1

So, I know we can’t easily train the sense. Is there anything I can do to account for known always on items?

first example: I have a hardwired radon ventilation system that runs 24/7. No plugs. It is a pretty fixed draw, sure it’s a motor and does vary a bit but it is quite reliable. Can i create a fake device in sense and assign it what I know to be that motor’s energy consumption? I know sense won’t monitor it, but at least I can label a portion of my unknown always ons. I can toggle the breaker it’s (by itself) hardwired into and determine energy change to measure it.

Second example: we have outdoor lights on a timer. They’re actually zwave switches on a specific schedule and using led bulbs (typical lights outside a home). I know exactly the energy usage from 6p-6a that they represent. I’d love to quantify that. Not sure if you’d pull them out of always on to their own bubble, or divide always on up into pie slices and shade the ones we claim to know than sense can’t ID yet?

Thoughts?

–Andrew

2

The way you could implement this is:

  1. define a counter
  2. Trigger an automation every hour that increments the counter
  3. Define a template sensor that multiplies your counter by the known ventilation motor power in kW.

This will give you a sensor that measures your always on load in kWh.

For the lights, do the same thing but only trigger the counter increment automation every hour that the lights are on (use a condition).

You can reset the counters whenever you want as well (e.g. when you get your energy bill).

3

Clearly I had the wrong product community group open! Sorry.

Andrew