Multiple EVs not showing entities for intelligent

[steelixb]

Describe the bug

Recently Octopus introduced support for multiple EVs, however adding another EV clears the entities of previously added EVs

Reproduction steps

Add an additional vehicle to Octopus. Observe entities on previously added EVs in home assistant

Expected behaviour

Entities exist for all EVs currently added to octopus

Tariff Code

E-1R-INTELLI-VAR-24-10-29-A

Integration Version

16.3.1

Home Assistant Version

2025.9.1

Fresh Install?

Not specified

Home Assistant Logs

N/A

Confirmation

• I confirm that I cannot find my solution within the documentation
• I confirm that I cannot find my solution within the FAQ

[BottlecapDave]

Hello and thanks for raising this. I've re-labled this as an enhancement as it's due to OE changing functionality. I'll see if I can take a look at this within the next couple of weeks, as it would be a breaking change and would be good to bundle with the next release with the other breaking changes.

[BottlecapDave]

You might also be able to help me with how planned dispatches work that fall outside of your normal off peak period.

I assume you have two chargers that are both controlled by OE (or both vehicles are controlled by OE directly)?

If they are both charged outside of normal off peak hours, I assume both periods are charged at off peak rates (e.g if car 1 is charged at 10:00-10:20 and car 2 is charged at 10:40 to 11:00, then you will be charged at off peak for all electricity from your house between 10:00 and 11:00)?

[steelixb]

Got both vehicles controlled by OE, just one charger, so not sure how it would handle both cars charging at the same time. I would assume the same as you. I don't see any info on the website about how it handles multiple EVs, but the info in the FAQ about not supporting multiple EVs has now gone.

[danmiles86]

Ditto, same for me to this would be a great enhancement.

I charge both of mine at the same time and yes this is how it appears to work @BottlecapDave. However if the charging demand is similar on both it seems like they get given the same slots anyway.

[danmiles86]

In fact I may have to retract my previous statement but I'm interested in what behaviours others are getting. When Octopus tries to charge the first vehicle I added to the account it doesn't appear to be triggering the low rate but it does on the second. I perhaps didn't notice this as they often choose to charge at the same time. However this is worse behaviour than just having one vehicle on the account and triggering the other to charge when the low rate kicks in via HA.

[steelixb]

In fact I may have to retract my previous statement but I'm interested in what behaviours others are getting. When Octopus tries to charge the first vehicle I added to the account it doesn't appear to be triggering the low rate but it does on the second. I perhaps didn't notice this as they often choose to charge at the same time. However this is worse behaviour than just having one vehicle on the account and triggering the other to charge when the low rate kicks in via HA.

Where do you see this? I can't seem to see when it charged at the off peak rate until the bill comes through

[danmiles86]

The current rate sensor on this integration or go old fashioned and look directly on the smart meter.

[steelixb]

I checked the rate sensor history and it seemed to work fine in my case, off peak when either car charged during the slots. Maybe it's an issue if both cars are charging at the same time, in which case maybe needs raising with Octopus?

[BottlecapDave]

The rate sensor is altered based on dispatches. At the present time it picks the first vehicle that is returned from Octopus which is used for all current sensors. I've started looking at adding this, but will result in a breaking change in the integration as the entity naming will need to update to accommodate this. Expect a beta release to make sure there are no weird side effects.