v0.4.9

[lbbrhzn]

Changes

• prevent exception at close (prevent exception at close #322) @lbbrhzn
• increase test converage (increase test converage #323) @lbbrhzn
• Measure connection latency (Measure connection latency #317) @lbbrhzn

📦 Dependencies

• build(deps): bump release-drafter/release-drafter from 5.17.5 to 5.17.6 (build(deps): bump release-drafter/release-drafter from 5.17.5 to 5.17.6 #316) @dependabot
• build(deps): bump pre-commit from 2.16.0 to 2.17.0 in /.github/workflows (build(deps): bump pre-commit from 2.16.0 to 2.17.0 in /.github/workflows #315) @dependabot

What's Changed

• build(deps): bump pre-commit from 2.16.0 to 2.17.0 in /.github/workflows by @dependabot in build(deps): bump pre-commit from 2.16.0 to 2.17.0 in /.github/workflows #315
• build(deps): bump release-drafter/release-drafter from 5.17.5 to 5.17.6 by @dependabot in build(deps): bump release-drafter/release-drafter from 5.17.5 to 5.17.6 #316
• Measure connection latency by @lbbrhzn in Measure connection latency #317
• increase test converage by @lbbrhzn in increase test converage #323
• prevent exception at close by @lbbrhzn in prevent exception at close #322

Full Changelog: v0.4.8...v0.4.9

---

This discussion was created from the release v0.4.9.

[GrantKeymer]

Unfortunately, the Maximum_Current slider still shows as Unavailable for me. I used the 'Update' button in HACS to install v0.4.9. I've also used all the 'Fix Issue' links under Developer Tools, but none of them seemed to help with this issue. Is there anything else I need to do in order for this slider to work?

[GrantKeymer]

I've tried this when charging and not charging and the result is the same...

1. Set Maximum_Current to 16 in Developer Tools
2. Go back to Overview
3. The slider is available and says 16
4. A few seconds later it returns to Unavailable

I can't see anything specifically in the log about this, but some of the entries are truncated and I may be missing the vital one.

Does that give any clue as to what is going on?

[drc38]

If you set State to available in Dev tools does that make a difference, or does it go back to unavailable?

[GrantKeymer]

I set the state of Maximum_Current to 'available' in Developer Tools.
Went back to Overview and it was showing as available, with the value of 6 Amps that I'd previously set using the Wallbox app.
However, after a few seconds it went back to unavailable again.

[drc38]

Hard to know what's going on, I don't have an issue using the HA docker environment

[GrantKeymer]

Looking at the logs, I can see that Meter Values are sent every 15 minutes when not charging, so that can't be the cause.

My HassOS uses Docker as part of the image, so there doesn't seem to be much difference between my setup and yours. The plot thickens 😕