Consider uncomment state_class for long term stats

[aviadlevy]

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

I saw that the state class for some sensor is commented out. Without it we'll have only 15 days of history, and it would be nice to get more

Describe the solution you'd like

Uncomment the state class

Describe alternatives you've considered

Maybe there are other to reasons why it's disabled, and if so it's okay

Additional context

• I don't mind write the PR myself (seems straight forward)
• Maybe you'll want to publish this as beta at first to make sure it's working and get feedbacks

[GuyKh]

Can you reference the code you're talking about?

[aviadlevy]

For example, https://github.com/GuyKh/iec-custom-component/blob/main/custom_components%2Fiec%2Fsensor.py#L149

[GuyKh]

Please read here about state classes

In your example - the forecasted usage - I don't really see a point of adding a state class to it.
It doesn't need a long-time statistical data nor affects how it is presented.

[aviadlevy]

It was just an example for commented out state class, maybe others are more suitable

In general it would be nice if I could see comparison month to moth of my power consumption and cost. if it's possible it would be great

[aviadlevy]

I didn't say device_class, I said state_class.
Some have it already but I want it for this:

• next_electric_bill_forecasted_cost
• next_electric_bill_forecasted_usage

at least this is what I use for my dashboard but I can check if I can change to other sensor

[GuyKh]

I meant state_class.

You can easily get this sort of dashboard section:

type: grid
cards:
  - type: heading
    heading: Electrics
    heading_style: title
  - type: statistic
    entity: iec:iec_meter_1234_energy_consumption
    period:
      calendar:
        period: month
        offset: -1
    stat_type: change
    name: Last Month Consumption
  - type: statistic
    entity: iec:iec_meter_12345_energy_est_cost
    period:
      calendar:
        period: month
        offset: -1
    stat_type: change
  - type: tile
    entity: >-
      sensor.iec_contract_31234_meter_1234_next_bill_electric_forecasted_usage
    features_position: bottom
    vertical: false
    name: Forecasted Consumption
  - type: tile
    entity: >-
      sensor.iec_contract_31234_meter_1234_next_bill_electric_forecasted_cost
    features_position: bottom
    vertical: false
    name: Forecasted Cost

I don't have previous monts' cost, but you can easily calculate it:

[aviadlevy]

building the dashboard is not an issue. the issue is that for the sensors above I don't have data for more than 15d

[GuyKh]

I still cannot understand the need for a history of a sensor state that does estimation based on current values

[aviadlevy]

I want to have also the current ongoing bill cost and also history of cost. Maybe I'll merge 2 entities together

Anyway, I understand your point, and I'll try to find other ways around it