Energy compare does not accept sensor.

[ziat007]

Describe the bug
Inputting metric_octopus_import: shows 0 on the compare screen as price.

Expected behaviour
A compare price to be shown

Predbat version

v8.22.2

Environment details
apps.yaml

  compare_list:
    - id: 'current'
      name: 'Current Tariff'
    - id: 'spot'
      name: 'Electree Spot'
      metric_octopus_import: 'sensor.current_buy_electricity_price_raw'
      metric_octopus_export: 'sensor.current_sell_electricity_price_raw'

predbat (7).log

Screenshots

https://i.gyazo.com/1d0219ac79de55909c3f6e36bf50749c.png

Log file
[[Can you capture a log file from the time of the issue, debug mode is not normally required.

You can download the logfile from the WebUI on the Dash tab select predbat_debug.log](https://raw.githubusercontent.com/ziat007/misc/refs/heads/main/predbat%20(7).log)

[gcoan]

what format is the data in these sensors? Is it the format that predbat expects for a price sensor?

Does it work OK if you configure these sensors in apps.yaml as the import/export price sensors, but just doesn't work on the compare?

In the logfile it appears to be picking up the rates OK:

2025-07-09 00:27:50.781287: Compare Tariff: Electree Spot
2025-07-09 00:27:50.781381: Configuration: forecast_hours 48 num_cars 0 debug enable is False calculate_plan_every 10
2025-07-09 00:27:50.781695: Predbat mode is set to Monitor
2025-07-09 00:27:50.920997: Found 11521 load_today datapoints going back 8 days
2025-07-09 00:27:51.139606: Car charging hold True threshold 6.0
2025-07-09 00:27:51.139671: Current data so far today: load 0.21 kWh import 0.2 kWh export 0.0 kWh pv 0.0 kWh
2025-07-09 00:27:51.139877: Adding rate rates_import: {'rate': 7.37} => 07-09 00:00:00 to 07-10 00:00:00 @ 7.37 date None day_of_week [] increment False
2025-07-09 00:27:51.155756: Standing charge is set to 0.0 p
2025-07-09 00:27:51.444692: Rate min forward looking: now 7.37 at end of forecast 7.37
2025-07-09 00:27:51.444818: Import rates min 7.37 max 7.37 average 7.37
2025-07-09 00:27:51.465176: Export rates min 41.26 max 290.49 average 175.22
2025-07-09 00:27:51.465216: Rate thresholds (for charge/export) are import 7.47p (0.0) export 41.16p (0.0)
2025-07-09 00:27:51.490948: High export rate found rates in range 41.26 to 290.49
2025-07-09 00:27:51.517108: Low Import rate found rates in range 7.37 to 7.37

so maybe its just a display problem?

[ziat007]

The sensors have the raw_today and raw_tomorrow attributes used by the energydataservice.py.

They correctly show prices when configured as metric_octopus_import: 'sensor.current_buy_electricity_price_raw' for default import and export rate.

[springfall2008]

I think you should use:

metric_energidataservice_import: 'sensor.current_buy_electricity_price_raw'

[ziat007]

That seems to have changed nothing.

I assume the import (pence) and export (pence) should be populated (as seen in the screenshot)?
It seems as if it is calculating some comparison value, but the table isn't being populated, so the imaginary charge/discharge is very off.

compare graph
compare table

[springfall2008]

Can you share your apps.yaml and a snapshot of the sensor.current_buy_electricity_price_raw sensor?

[ziat007]

apps.yaml
https://github.com/ziat007/misc/blob/main/apps.yaml

sensor.current_buy_electricity_price_raw attribute data:
https://gist.github.com/ziat007/1bb48cff70e420a029436060d56fed89

(I couldn't find if snapshot of a sensor is some technical term, so I copied the attribute data from developer tools/states)
The data does show up for the sell sensor in the regular plan.

[ziat007]

@springfall2008 any update on this?
it is still not working :X

yet the same sensor in the current tarif works flawlessly, just as
metric_octopus_export: 'sensor.current_sell_electricity_price_raw'

[ziat007]

@springfall2008 I would love an update on this. As I am still considering a spot tariff.
I have tried to diagnose the problem, but with no success.

If I had the data that the octopus energy integration provides I could attempt to convert my spot prices into a format that is supported by that alternate sensor. But I cannot get that data as it needs an octopus api key and account.

current predbat_debug:
predbat_debug.yaml
sensor.current_buy_electricity_price_raw
https://gist.github.com/ziat007/ba5faf77c5e670f8cc6e5ea825d26c3a

sensor.current_sell_electricity_price_raw
https://gist.github.com/ziat007/b0ce27da6eeaedce8dda31e6db9985b9

[ziat007]

After further troubleshooting I found out the original nordpool sensor does not work in compare also:

  compare_list:
  - id: 'current'
    name: 'Current Tariff'
  - id: 'current_double_battery'
    name: 'Current Tariff Extra Battery'
    override_soc_max_kwh: 28.4
  - id: 'spot'
    name: 'Electree Spot'
    metric_energidataservice_import: 'sensor.nordpool_kwh_dk1_eur_2_10_025'

When I use my sensor direclty in predbat it works flawlessly. When used in compare neither does a vanilla nordpool sensor nor my customised czech spot price sensor.