Powercalc - Virtual power sensors

tikismoke · January 3, 2022, 7:35pm

Thank’s did it use also the states to know if the device is on or off?
It can be off with 100%.

bramski · January 3, 2022, 7:50pm

When the fan is off it will be default to 0 watt. When you also want to define power draw when the device is off you can use standby_power option.

Like this:

- platform: powercalc
  name: Conso fan
  entity_id: fan.fan
  standby_power: 1
  linear:
    calibrate:
      - 33 -> 14
      - 67 -> 18
      - 100 -> 30

tikismoke · January 3, 2022, 8:26pm

Méga super great .

This is awesome.

I certainly ask more in few days as I’m measuring all my devices due to you components

AJediIAm · January 3, 2022, 9:21pm

The docker container to automatically measure a light is AWESOME!
It is very easy to use, so I’m planning to add a few lights soon.

bramski · January 3, 2022, 9:25pm

Thanks. glad you like it. cool you want to contribute!

tikismoke · January 3, 2022, 10:49pm

Me again

Do I understand this correctly (the power_sensor_id parts)…

- platform: powercalc
  name: ups power
  power_sensor_id: sensor.ups_real_power

The sensor is the live consumption in w from my ups.

Does it allow to create a energy and add it correctly in energy dashboard?

Could help a lot of people who wants to add ups in this new energy things (including myself).

May I made some PR on GitHub for those example (an example.md at root ie.) The readme is well documented but miss of some examples I think (no criticism). I understand that the base of this was oriented on light.

bramski · January 4, 2022, 7:31am

Do I understand this correctly (the power_sensor_id parts)…

Yes this is exactly the purpose of this option. Is your snippet working? Because I’m pretty sure entity_id is mandatory.

May I made some PR on GitHub for those example (an example.md at root ie.) The readme is well documented but miss of some examples I think (no criticism). I understand that the base of this was oriented on light.

Yes the base of this was lights, but has been extended to support a multitude of use cases later on.
We can add docs to the repository but I think there are two better fits for user contributed examples.

There is a section “Share your config” in discussions part.
But even beter fit for extensive examples would be the Wiki imho. I can add you as a collaborator. Than you could contribute by creating pages / articles.
In the main readme I can make a link to the Wiki section containing more configuration examples / use cases.

tikismoke · January 4, 2022, 3:42pm

I’ll look at this at the weekend

AJediIAm · January 7, 2022, 11:12am

Hi @bramski
I’m trying to measure the power consumption of some Innr spots. My Shelly plugs can only measure the power above 2 or 3 watts which is at 50% brightness with 5 spots connected. Any sugestions on how to improve the power measurement or is this good enough to submit?

bramski · January 7, 2022, 2:25pm

Strange, I did never experienced this before with my Shelly plug. It starts measuring from approximately 0.4 watt. Which shelly plug do you use?
Maybe someone else has an idea. You could also ask this question on discussions part of github repository, potentially users read there which are not on this forum.
It’s not good enough to submit. Needs to have quite accurate measurements across the full brightness range.

Jokerigno · January 8, 2022, 9:12pm

Hi, sorry for the noob question.

I updated to 0.14 and deleted my previous config to use autodiscovery. I rebooted HA and waited for the sensor to be created. Nothing happened. Any hint?

I checked the log and no error there

bramski · January 9, 2022, 8:37am

Did you enable debug logging? Than you should see an entry “Start auto discovering entities” followed by a lot of other log lines which should hopefully give some insight.

Jokerigno · January 9, 2022, 2:20pm

Yes I did. No entry like the one you described. I still can see some of the old “energy” sensors that now are unavailabe. That’s it.

This is the only entry I found:

2022-01-09 15:23:20 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration powercalc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

bramski · January 10, 2022, 7:29am

Than you either have debug logging not correctly enabled, or you have autodiscovery option disabled (should be enabled by default in v0.14 though).
I am 100% certain when these conditions apply you must see at least see “Start auto discovering entities” in the logs. And you should see a few log lines for each power/energy sensor created.

Enable debug logging:

logger:
  default: warning
  logs:
    custom_components.powercalc: debug

Try force enable autodiscovery:

powercalc:
  enable_autodiscovery: true

When you have still no logging lines with the above I really have no clue.

chpego · January 10, 2022, 9:53pm

Hi @bramski ,

Just thank’s for your stuff, amazing component, why not try to integrate it as an official HA component?
Once again, nice job !

Anthony

bramski · January 11, 2022, 8:52am

Thanks. No plans on that, please see this github issue for considerations.

bramski · January 15, 2022, 10:45am

@Jokerigno Please see issue 498 where two other users are experiencing similar issues. There is a resolution in my comment, however I’m still unsure why things are not working “out of the box”.

scoutamis123 · January 15, 2022, 11:18pm

Is there a way to create a group of daily_fixed_energy devices? I don’t see any examples and I can’t seem to find a way to make it work, since there’s no “entity” to supply the entities section with, just names

bramski · January 16, 2022, 9:21am

Hi, doesn’t seem to work currently, however I think I will be able to make this work. Could you please create an issue on github with this feature request?

Jokerigno · January 18, 2022, 8:39am

Adding

powercalc:
  enable_autodiscovery: true

Thank you!

worked for me as well!