Support for covers (and other devices)

[dagobert]

I started to use this great integration and found that many of my devices are not in the library. Hence, I started to add them by creating local profiles and am happy to share them after I am finished.

Now I got stuck on adding profiles for my covers. It seems that covers and other device types are not supported as profiles. This is too bad. Is there any way to add cover support?

I guess it would be similar to a switch but instead of watching states on and off it should check for moving up and down.

[bramstroker]

I started to use this great integration and found that many of my devices are not in the library. Hence, I started to add them by creating local profiles and am happy to share them after I am finished.

That's great.

Now I got stuck on adding profiles for my covers. It seems that covers and other device types are not supported as profiles. This is too bad. Is there any way to add cover support?

I guess it would be similar to a switch but instead of watching states on and off it should check for moving up and down.

You could use states_power using fixed strategy.
https://docs.powercalc.nl/strategies/fixed/#power-per-state

assuming for example the motor is using 400W.

powercalc:
  sensors:
    - entity_id: cover.my_cover
      fixed:
        states_power:
          opening: 400
          closing: 400

This configuration should also be supported in library profiles model.json files.

{
  "name": "Cover profile",
  "standby_power": 0,
  "calculation_strategy": "fixed",
  "fixed_config": {
    "states_power": {
        "opening": 400,
        "closing": 400
    }
  }
}

When this is working for you I can also add device type cover, so it is also a separate section in the library, but this requires some additions to the codebase.

[dagobert]

Thanks. I will try that.

[dagobert]

I have tried to configure the cover but the following configuration file does not work. In the logs I can see that the device is recognized as amodel in the local database but it is not showing as discovered in the integration page of HA.
Can you point me to my mistake? Thanks!

{
  "measure_description": "Manually measured",
  "measure_method": "manual",
  "measure_device": "From manufacturer specifications",
  "name": "HmIP-FROLL",
  "standby_power": 0.2,
  "standby_power_on": 0.2,
  "sensor_config": {
    "power_sensor_naming": "{} Device Power",
    "energy_sensor_naming": "{} Device Energy"
  },
  "calculation_strategy": "fixed",
  "fixed_config": {
    "opening": 40,
    "closing": 40
  },
  "created_at": "2024-09-06T18:37:40",
  "author": "CV"
}

[bramstroker]

Btw I see you are missing the device_type. When not specified it is defaulting to light.

Add to the JSON:

"device_type": "cover",

[dagobert]

I added device_type but nothing changed. The debug log shows that the cover I setup was found:

2024-09-17 10:09:14.586 DEBUG (MainThread) [custom_components.powercalc.discovery] cover.home_poolraum_pool_solarventil: Auto discovered model (manufacturer=eQ-3, model=HmIP-FROLL, model_id=None)

It is still not showing in the GUI as discovered.
When using the UI Add -> other Instance -> Virtual power (library) -> source entity no covers are showing.

After each change I am restarting HA fully.

[bramstroker]

Let me have a closer look:

2024-09-17 10:09:14.586 DEBUG (MainThread) [custom_components.powercalc.discovery] cover.home_poolraum_pool_solarventil: Auto discovered model (manufacturer=eQ-3, model=HmIP-FROLL, model_id=None)

This only means an entity was found in your HA instance which has manufacturer and model information. It does not mean the profile is actually found in the library or custom profiles directory.

Please share where you put the model.json, the exact directory structure.

[bramstroker]

I see there was a small mistake in the code I added to support covers.
This is fixed now, and just release 1.14.7. Could you try again please?

[dagobert]

Top. Now they are showing up. I will test further. Thanks for now.

[dagobert]

As I wrote, the device was discovered. I added/configured the cover device but after that no powercalc device and entities were created.
The powercalc entry states "no device or entity".

Any suggestions?

[bramstroker]

Your config is wrong looking at your model.json you provided some comments above.

{
  "measure_description": "Manually measured",
  "measure_method": "manual",
  "measure_device": "From manufacturer specifications",
  "name": "HmIP-FROLL",
  "standby_power": 0.2,
  "standby_power_on": 0.2,
  "sensor_config": {
    "power_sensor_naming": "{} Device Power",
    "energy_sensor_naming": "{} Device Energy"
  },
  "calculation_strategy": "fixed",
  "fixed_config": {
    "opening": 40,
    "closing": 40
  },
  "created_at": "2024-09-06T18:37:40",
  "author": "CV"
}

You don't have state power under fixed_config.

"fixed_config": {
    "states_power": {
        "opening": 40,
        "closing": 40
    }
  },

[dagobert]

Sorry I just noticed

[dagobert]

Perfect, now it works! Almost...

I guess since cover does not have an on and off state standby power is not registered while the cover is not moving (not available). When moving, it is added correctly to the power set in the model.

[dagobert]

OK. Self answer.

A workaround is defining the states "open" and "closed" in the model. It is not really nice but ok.

{
  "measure_description": "Manually measured",
  "measure_method": "manual",
  "measure_device": "From manufacturer specifications",
  "name": "HmIP-FROLL",
  "standby_power": 0.2,
  "standby_power_on": 0.2,
  "sensor_config": {
    "power_sensor_naming": "{} Device Power",
    "energy_sensor_naming": "{} Device Energy"
  },
  "device_type": "cover",
  "calculation_strategy": "fixed",
  "fixed_config": {
    "states_power": {
      "open": 0.2,
      "closed": 0.2,
      "opening": 40,
      "closing": 40
    }
  },
  "created_at": "2024-09-06T18:37:40",
  "author": "CV"
}

[bramstroker]

Perfect, now it works! Almost...

I guess since cover does not have an on and off state standby power is not registered while the cover is not moving (not available). When moving, it is added correctly to the power set in the model.

Ok great!
Will be "fixed" with #2503