Replies: 1 comment
-
|
It appears that you have used AI to help you construct your custom sensor and apps.yaml, that's the first mistake you've made ! There is extensive documentation on what predbat is expecting for energy rates https://springfall2008.github.io/batpred/energy-rates/ and in particular what it is expecting for custom template rates https://springfall2008.github.io/batpred/energy-rates/#other-energy-spot-rate-sensor-integrations It looks like your sensor doesn't have an end time for a start All these lines in your apps.yaml are AI fabrications that Predbat will ignore, please read the documentation and not believe anything AI tells you ... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am using PredBat v8.34.1 and hass-entso-e (JaccoR ENTSO-E integration) to integrate day-ahead electricity prices into Home Assistant. However, I have not been able to successfully integrate the day-ahead prices into Predbat.
The error I keep getting is:
Warn: record_status Error: Import rates are all zero, not able to compute a plan
Error: Import rates are all zero, not able to compute a plan
The approach I am using is a dedicated sensor (sensor.predbat_import_price) in Home Assistant that Predbat should read.
The sensor value is a number, attributes:
unit_of_measurement: EUR/kWh
friendly_name: Predbat Import Price
state_class: total
device_class: monetary
rates:
value: 0.12053
value: 0.11173
...
Predbat apps.yaml:
Energy rates
metric_import_rate: sensor.predbat_import_price
metric_import_rate_import_code: "rates"
metric_import_rate_scaling: 100
metric_import_rate_type: "generic"
import_rate_min: -0.5
Any ideas what am I doing wrong?
Beta Was this translation helpful? Give feedback.
All reactions