You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using LTSS for about a year and just recently noticed that some entities that should be covered by the sensor domain include in my configuration isn't logged to TimescaleDB. I cannot really find any obvious patterns such as the same unit or similar. The behavior can be noticed when looking at historic values in HA. For LTSS-logged sensors there is historic data, for the ones missing it there is only Recorder data from the last 10 days.
Not sure where to start debugging this though. Sensors missing from LTSS is both real entities (ESPHome) and calculated (Helpers/Templates).
My configuration block from configuration.yaml. An example of a sensor missing from the LTSS data is sensor.anemometer_vindhastighet_by.
Did some queries on the ltss table in PostgreSQL/TimescaleDB and was somewhat surprised to find historic entries for all sensors with missing LTSS data in the HA interface.
My problem seems more related to how the HA History view picks up LTSS data...
Thanks for a great component!
I have been using LTSS for about a year and just recently noticed that some entities that should be covered by the
sensor
domain include in my configuration isn't logged to TimescaleDB. I cannot really find any obvious patterns such as the same unit or similar. The behavior can be noticed when looking at historic values in HA. For LTSS-logged sensors there is historic data, for the ones missing it there is only Recorder data from the last 10 days.Not sure where to start debugging this though. Sensors missing from LTSS is both real entities (ESPHome) and calculated (Helpers/Templates).
My configuration block from
configuration.yaml
. An example of a sensor missing from the LTSS data issensor.anemometer_vindhastighet_by
.Any ideas or hints on where I should start troubleshooting this?
The text was updated successfully, but these errors were encountered: