V2.4.1

⚡️ Features

Support for Octopus Activation Mode

When the charger is controlled by🐙 Octopus Intelligent Go, the Activation Mode is fixed to Octopus. The schedule sessions are also populated from the Octopus scheduled sessions.

Just like the Hypervolt App, while Octopus mode is enabled, the charger can only be controlled through the Octopus Energy app. Addresses #68

🐛 Fixes

• We now allow up to 30 seconds to initialise the integration (login and get the current state). Fixes #78
• Updating websocket version dependency to fix #79
• Fix for Detected blocking call to load_default_certs #72

V2.4.0 Beta

⚡️ Features

Support for Octopus Activation Mode

When the charger is controlled by🐙 Octopus Intelligent Go, the Activation Mode is fixed to Octopus. The schedule sessions are also populated from the Octopus scheduled sessions.

Just like the Hypervolt App, while Octopus mode is enabled, the charger can only be controlled through the Octopus Energy app. Addresses #68

🐛 Fixes

We now allow up to 30 seconds to initialise the integration (login and get the current state). Fixes #78

V2.3.5

🐛 Fixes

Websockets are now proactively closed and reopened before the access token expires. Addresses #65, where commands are ignored the first time.

V2.3.5 Beta

🐛 Fixes

Websockets are now proactively closed and reopened before the access token expires. This may fix #65, where commands are ignored the first time.

V2.3.4

🐛 Fixes

Typo fix in tracker attribute, as part of fix for #66 (Octopus Energy v12 breaks set schedule)

V2.3.3

🐛 Fixes

Fix for #66 (Octopus Energy v12 breaks set schedule)
Thanks @Meatballs1

V2.3.2

🐛 Fixes

Handling case where no schedule is set with v2 charger. Previously caused init to fail #62
Added proactive refresh of access token before it expires. Should fix #63

V2.3.1

🐛 Fixes

Now using async method to retrieve version from manifest. Fixes #60

V2.3.0

⚡️ Features

Set Schedule service

Intended to be used by 🐙 Octopus Agile users with the Octopus Energy integration, specifically the Target Rates sensors which allow you to find the cheapest periods between two times. This allows an Agile user to set the schedule on the Hypervolt rather than switching the Hypervolt on or off based on the binary_sensor. This hopefully avoids failed charges due to cloud or connectivity outages that may occur overnight, and allows the user to check the schedule before settling down for bed 😴. A pseudo-intelligent automation could trigger when the car is plugged in (e.g. from a car integration), set a dynamic target rate between the current time until the morning, schedule the Hypervolt for those periods, and send a notification to the phone with the intended charging periods.

Thanks to @Meatballs1 for the work on this feature.

🐛 Fixes

Simplified and fixed periodic and initial update logic. Fixes #58

V2.2.6

🐛 Fixes

• Added logic in periodic update to check if sync websocket is still alive. If not, we will try a token refresh/login. This ensures connectivity is resumed after an outage. Should fix #57