Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

[GUIDE] Automations for Octopus Intelligent with Home Assistant

This site may earn commission on affiliate links.
I set up a really simple automation for when the Octopus rate changes & tested it last night.

It triggers when the current rate goes below a certain level, checks to make sure the car is plugged in, wakes it up & starts charging. This one just leaves it charging until the max set charge is reached. It would be relatively simple to add a trigger to stop charging if the electricity rate goes up. If/when I switch back to Agile I'll flesh it out a bit to make sure the best rates are being used. For now I'm just testing it with my Tracker rates.

1698485495273.png
 
I set up a really simple automation for when the Octopus rate changes & tested it last night.

It triggers when the current rate goes below a certain level, checks to make sure the car is plugged in, wakes it up & starts charging. This one just leaves it charging until the max set charge is reached. It would be relatively simple to add a trigger to stop charging if the electricity rate goes up. If/when I switch back to Agile I'll flesh it out a bit to make sure the best rates are being used. For now I'm just testing it with my Tracker rates.

View attachment 986061
Ummm, why do you need to wake it up!?
 
Ummm, why do you need to wake it up!?
I was playing around with the different data calls yesterday & it seemed like a good idea. I wasn't certain the charge would start without sending a wakeup signal first, so I left it in there. It probably doesn't, I'll take it out next time I need to use it & check that it works without it.
 
Has anyone with HA automations updated to 2023.38.6 yet? I've not deferred an update since I got my car but this one I'm waiting to see if it breaks anything, like it has with TeslaMate...
Mine did on Friday night.

It looks like the only thing that has gone is when I utilise car is at home (car tracker).

I need to figure out a work around. Although I could potentially remove the need for it.
 
I mean there can be other ways to automate. the car's location is not necessary.

I for example use Pod Point's integration to check if car is plugged in. I found, earlier, that car's location was not so reliable and it was some time until it managed to update location
 
Is it just me or others as well has issue with HA integration, when IO does not send signal when IO slot is over?

I read somewhere that API changed a bit and the entity for Io to go off is called differently.

I find that sone of my automations which depends on the entity do not run :/
 
Is it just me or others as well has issue with HA integration, when IO does not send signal when IO slot is over?

I read somewhere that API changed a bit and the entity for Io to go off is called differently.

I find that sone of my automations which depends on the entity do not run :/
In v9.0.0 of BottlecapDave's integration, this new feature was added:

  • updated intelligent sensors to include account id. This is to support future functionality (57e3d79)

With breaking changes including:

  • Any references to intelligent sensors will need to be updated based on name changes including account id

This resulted in my automation not knowing when the intelligent dispatching slots were on or off until I selected the new sensor.

The trigger now looks like:

1705311933245.png


The obfuscated part is my octopus account ID. If you compare this to previous screenshots in the guide, you'll see that the sensor/entity used was not linked to the account.
 
In v9.0.0 of BottlecapDave's integration, this new feature was added:



With breaking changes including:



This resulted in my automation not knowing when the intelligent dispatching slots were on or off until I selected the new sensor.

The trigger now looks like:

View attachment 1009015

The obfuscated part is my octopus account ID. If you compare this to previous screenshots in the guide, you'll see that the sensor/entity used was not linked to the account.
i upadted my automations.

now it works fine.

but yesterday I noticed some strange anomaly.

1) Intelligent dispatching was off, Pod-point charging was not allowed. it was around 9 pm.
2) car started to charge.
3) I stopped charging manually. Slot was created, 23:30 charging started.
4) at end of charging I get notification that Pod-Point automation ran and charging is not allowed now.. Ok, cool, as it should be.
5) start precondition in the morning - suddenly charging is allowed and car sucks power from the gid.

do you notice same behaviour? What am I doing wrong?
 
i upadted my automations.

now it works fine.

but yesterday I noticed some strange anomaly.

1) Intelligent dispatching was off, Pod-point charging was not allowed. it was around 9 pm.
2) car started to charge.
3) I stopped charging manually. Slot was created, 23:30 charging started.
4) at end of charging I get notification that Pod-Point automation ran and charging is not allowed now.. Ok, cool, as it should be.
5) start precondition in the morning - suddenly charging is allowed and car sucks power from the gid.

do you notice same behaviour? What am I doing wrong?
If you can post screenshots of your automation in an expanded form I can take a look for you. GUI is fine.
 
I can't see anything obviously wrong with this setup, but the automation is triggered based on a state change so it may have failed based on the charging state that the podpoint was in before you last saved/edited the automation. That could explain why the car started to charge when you plugged in at 9am but not why it started to charge when pre-conditioning.

I made a few updates to the template since my original post, making use of trigger IDs, adding provision for bump charging and removing the condition for whether the car is plugged in or not as that only really serves to make sure no one else uses your charger when your car is not at home, during a dispatch slot. (I'm covering that in a separate automation now).

Not sure if you want to tweak your automation as per the images I've attached, or leave for another night to observe it? After making any edits to the automation, set the podpoint charging allowed value to off so that it's in the correct state when the automation for the dispatch slot runs.

1705678185582.png 1705678305562.png
 
  • Love
Reactions: KennethS
UPDATE: So looks like my issue was caused by failing wifi unit. Now it completely failed, and it is "dumb" charger (meaning once you plug it in - it immediately starts charge, unless schedule is set by car or Octopus.

It is well known issue with Pod-Points and once it is out of warranty - the only solution Pod-Point offers is to purchase new unit.

So now my automation has changed.
Now HA checks if IO intelligent slot is on, Tesla's charger door is opened AND if my phone is at home.