Long Term Statistics

[andyblac]

@BottlecapDave do you have any ideas why sensor.octopus_energy_gas_xxxxx_xxxxxx_current_consumption, would not show in the new History dashboard for LTS?, it does have the data according to Statistics in dev view

but it not showing...

it is also the same with Electric.

The sensor.octopus_energy_gas_xxxxxx_xxxxxx_current_accumulative_consumption seems fine.

[andyblac]

state_class: total
last_reset: "2023-12-18T13:53:04.226073+00:00"
unit_of_measurement: kWh
device_class: energy
icon: mdi:fire
friendly_name: Gas Current Consumption
last_evaluated: "2023-12-18T13:53:04.226073+00:00"

I see your using state_class: total for the sensor, should it not be state_class: measurement ??

Measurement: The state represents a measurement in present time, not a historical aggregation such as statistics or a prediction of the future. Examples of what should be classified measurement are: current temperature, humidity or electric power.

Total: This state class should not be used for sensors where the absolute value is interesting instead of the accumulated growth or decline....

[BottlecapDave]

Hey. I'm not sure why they're not coming through. The measurement type is not right as it can't be used in the energy dashboard and you can't have energy as the device class. It might be the last reset isn't working properly.

Tbh I've been thinking about deprecating this sensor as it existed before the accumulative sensor was a thing. But I'll take a look when I get a chance.

[andyblac]

but we dont use this sensor in Energy Dashboard, we use Current Accumulative for that ???

[andyblac]

Tbh I've been thinking about deprecating this sensor as it existed before the accumulative sensor was a thing. But I'll take a look when I get a chance.

what, why this sensor is really handy to see current usage hour to hour for GAS.

[BottlecapDave]

The sensor was originally the only sensor available due to how current consumption data was retrieved. It was built to be used in the energy dashboard, and some people still use it for this purpose. Therefore if anything changes it needs to change for this purpose. The fact the energy dashboard displays the data correctly means the LTS data is there and at least in that scenario in a form HA is expecting.

As for hourly views, I believe (but will need testing) that you can use a utility meter with an hourly reset with the accumulative sensor as the source.

Basically the sensor is hang over from the before times and consuming a lot of my time trying to keep it working for different use cases which could be used for other features. It's just a consideration atm, but it's good to get people's use cases so I can have alternatives ready if the time comes.

[borpin]

would not show in the new History dashboard for LTS?

I've seen an error at startup re the sensors not being added to LTS data.

[andyblac]

the data is there in the Database. so is being added to LTS.

[andyblac]

on looking closer the data is there, but it is not correct, it does not correspond to what is in the DB.

I think it is being averaged, I think this is to do with the state type of total, it is expecting to increase or decrease over time.