Differences from Octopus integration to Target Timeframes

[jon273]

Hello, I am having a bit of trouble migrating from the Octopus Energy target rate sensors to Target Timeframes.

1. In the Octopus integration if I update the target number of hours in a target rate sensor the new target times are recalculated within seconds. If I update the target hours in the new Target Timeframe sensor I am not seeing the new target times being calculated.

2. In the Octopus integration I can set a value of 0 (£0.00) as the maximum value for a target hours sensor. In Target Timeframes I get an error "expected float". (Use case is I heat up the lower part of my thermal store when the price is negative, but the thermal store has a finite capacity so I still want the cheapest periods during a day of negative prices).

3. It does not seem possible to change the name of the created Target Timeframe sensors listed on the integration page. I did try renaming the entity as suggested elsewhere but that didn't seem to work.

Thank you in advance for any help with this as the Octopus Energy integration has been incredibly useful so far.

[BottlecapDave]

Hello

In the Octopus integration if I update the target number of hours in a target rate sensor the new target times are recalculated within seconds. If I update the target hours in the new Target Timeframe sensor I am not seeing the new target times being calculated.

This is a limitation within HA and is highlighted within the FAQ. However, it looks like they've introduced a way to update the config and reload the entry within the upcoming 2025.9, so I will update the codebase once that's out.

In the Octopus integration I can set a value of 0 (£0.00) as the maximum value for a target hours sensor. In Target Timeframes I get an error "expected float". (Use case is I heat up the lower part of my thermal store when the price is negative, but the thermal store has a finite capacity so I still want the cheapest periods during a day of negative prices).

This is a bug within the integration and will be fixed in the next update

It does not seem possible to change the name of the created Target Timeframe sensors listed on the integration page. I did try renaming the entity as suggested elsewhere but that didn't seem to work.

This would be a HA issue. I've just tried myself and managed to change the name of the entity.

[jon273]

I was on 1.3.0. Just upgraded to 1.3.1 today so I can check going forward if the behaviour is the same.

[BottlecapDave]

It's probably still an issue. I'll see if I can recreate the scenario over the next week

[jon273]

Hello, sorry for late reply. This issue is still present. Updating the integration also happens to reproduce this behaviour, presumably as it has to recalculate all the target times when it restarts.

[BottlecapDave]

Sorry I usually go off issues to fix things. I've created #58 to represent this issue, but not sure when I'll get a chance to look at it

[BottlecapDave]

This should hopefully be fixed as part of v1.4.1