Intelligent API changes Beta 01

[BottlecapDave]

This release includes everything in v11.2.0 as well as the updates outlined in #853 which includes

• fix: Migrated planned and completed dispatches request to use new fields (5 minutes dev time)
• fix: Migrated retrieving intelligent device to new endpoint (1 hour dev time)
• fix: Migrated retrieving intelligent settings to new endpoints (1 hour dev time)

If you are on intelligent, it would be good if you could try the beta and report any issues in the linked discussion thread.

---

This discussion was created from the release Intelligent API changes Beta 01.

[Cameleon99]

@BottlecapDave having a few issues (as per TwiX):

Trying to set Intelligent Charge Limit (% to add) or Ready Time results in the following error:

Trying to set Bump charge or Enable/disable smart charge has no effect or error

[Cameleon99]

Seems to be working now. My automation has been able to set the percent to add and change the ready time. Schedule has come through from the OE app notification and looks good 👍

[Cameleon99]

Spoke too soon. It's updating the percentage to charge and ready time ok, but the status of the Smart Charge (I think) is wrong. I have a valid schedule set in OE app but Smart Charge is showing as off?

Can't see anything untoward in the logs. Any idea what to look for?

[BottlecapDave]

I think I'm misinterpreting the smart charge flag - it should be on all of the time unless you've explicitly disabled control. I've released https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/intelligent-api-changes-beta-04 which should fix this issue.

[Cameleon99]

Spot on, the Smart Charge status is showing if OE can control the device so should be on unless you've disabled the control (pretty hidden away in the app).

Working as expected now 👍

I'm probably in the minority as I switch it on and off using my automation because I leave it plugged in most of the time, and if I don't disable it, OE tries to create a schedule each evening even when the car doesn't need it.

[BottlecapDave]

No bother. Want everything to continue working as expected :)

[BottlecapDave]

@springfall2008 - Didn't know how else to alert you to this. OE are deprecating some of the existing intelligent APIs in favour of new ones. The side effect of this is that users won't get both vehicle battery size and charger power, only one of them depending on how they're integrated (e.g. tesla communicates with the car to my knowledge, but Zappi communicates with the charger) - see #921 (reply in thread).

I've raised this in the forums, but they currently have no plans of exposing both values

This isn’t currently exposed but the values are not as useful as you may think beyond registration.
They are simply used as an initial starting point and best guess. The system learns and adjusts its internal view of these, as customers often pick the wrong options.

I know that these were included in this integration as part of request of your predbat integration, but not sure how you use the info. If you're needing both, it would be good to propose a case to OE.