New issue with setting backup reserve?

[amanensia]

Hi,

I have an automation which operates at 0530 each morning and among other things sets my PW2 backup reserve to 0. It's been working fine. However this morning it raised an error, which didn't stop the step from setting the backup reserve as required, but did stop the automation from completing.

After some tinkering with scripts it appears that this error is being raised whenever the action "Set value for Backup reserve" is invoked. An example trace is shown below - the first line is just an attempt to avoid the issue, but that doesn't work, perhaps as the error isn't a HA-recognised error. I presume something has changed in the Tesla API or something?

I can work around it by splitting out automations and ensuring this is the final sequential step, but thought it should be raised.

[skipishere]

Issue #1125 had been opened about this

[amanensia]

Ah, apologies, I'm very new to HA and github and didn't spot the separate "issues" area.

[skipishere]

No worries, it happens a fair bit on GitHub (you're not the first and I'm sure you won't be the last either 🤣)

[amanensia]

@skipishere I see this has been fixed now - sorry to bug you but what's the process to adopt the new code? Do I just scrap the old integration and reinstall the new one? I was hoping I wouldn't have to re-request a Tesla API token. Thanks!

[skipishere]

You can either wait for HACS to check there is an update, or click the three dots and click "Update information" which should cause the update to be noticed. From there you should then see under the Home Assistant Settings menu there is an update to install.

[amanensia]

Ah thank you, I wasn't sure if HACS integrations automatically picked up updates. I'm new to this stuff!

[billraff]

I'm wondering the same thing. Now that setting the reserve in HA is back to causing the error what happens next to get the 'fixed' code?

[amanensia]

I just downloaded the updated code - was prompted to do so in HA. All working fine for me now.