configure 'fake' entities?

[Mariusthvdb]

HI,

using a z-wave Aeotec Siren 6, I've found that it uses 2 w constantly being attached to the power wall socket (to load a backup battery inside the device (havent done any testing yet, iw=f and when the alarm sounds etc etc). And id like to add it to the system for that reason.

however, I dont think the integration caters for devices that dont have an entity (like a light or a sensor, or even a switch) we can add in the config? The Aeotec device only creates a device, with many Siren entities, but these are mere endpoints for the sounds to play.

so, how can we configure that using the integration?

maybe we should be able to use a fake name, like:

  - platform: powercalc
    entity_id: siren.fake_entity or sensor.fake_siren
    true_entity: false
    fixed:
      power: 2

and add some config option so the integration doesnt search for it in the HA states?

Or, did I miss the docs completely, and do you already have an option for this situation....

thanks for considering

[stefangries]

I think you can create a Template Switch for this device and make it always on. After that you can use it for powercalc.
https://www.home-assistant.io/integrations/switch.template/

Something like this should work (not tested):

switch:
  - platform: template
    switches:
      my_fake_device:
        value_template: "{{ true }}"

[bramstroker]

@stefangries that would also be my proposal, or create a input boolean. The powercalc component heavily relies on a entity as a source, to change that would be a huge refactor, so I will probably not do that. Especially since it is quite an edge case

[Mariusthvdb]

right, great ideas. thank you.

I did manage to find an entity, sensor.xx node_status which even has a few states to use.... however, Ive also found out that it doesn't always use 2 watts, there's also 0 (battery is full no charging necessary) and 6 shortly after an alarm has sounded.... all in all it does sound like an extra domain to support shortly. siren to add ;-)

[bramstroker]

Did you have a look into states_power this allows you to set a power value per state?
https://github.com/bramstroker/homeassistant-powercalc#power-per-state
This allows you to set a power value for each node status.

[Mariusthvdb]

oddly enough, using:

sensor:
  - platform: powercalc
    entity_id: sensor.hall_node_status
    name: Siren hall
    fixed:
      power: 2

powercalc:

  energy_sensor_naming: '{} energy'
  power_sensor_naming: '{} power'
  create_utility_meters: true
  utility_meter_types:
    - hourly
    - daily
    - monthly
    - yearly

only the sensor.siren_hall entities for utility_meter are created:

and no _power meters, nor there sensor.siren_hall_power or sensor.siren_hall_energy are created.

[bramstroker]

Please check the debug logs for clues

[Mariusthvdb]

I had renamed the entities, but the entity_id's were still on the original indoor_siren_6 ......
changed those too now ;-)