Add WallBox Support and other various bugfixes

[Poshy163]

This is still a work in progress, all feedback is welcome

prerequisites

• Various fixes to support new API calls (VitaPower and Wallbox) alphaess-openAPI#15
• alphaessopenapi version 0.0.12
• Bump version to 0.6.0

New Features:

• Add a new service/separate panel for the alphaess chargers (segregated from battery/inverter)
  
  
• Use Currency set within the alpha app, rather than the currency used by HA
• Remove all the sensor names being appended to the serial number (shouldn't override any existing/custom names)
  more to come

Bug Fixes

• Fixes a bug where its possible you wouldnt get 'OneDayPower' data if your API calls had no throttle

Resolves #159

[CharlesGillanders]

Re: removing serial number prefix: when I initially went with this convention it was intended to allow those with multiple inverters to identify which sensor went with which inverter. If the prefix is removed does that result in either potentially duplicate sensors or potential confusion about how to tell those sensors apart?

[Poshy163]

Inverters are now separated into their own "services" (done via S/N) if you have multiple inverters (or now an additional service made for it.

I've deleted and re-initialised the API credentials a few time and it seems to be working

2 inverters:

Single inverter and EV plug:

[CharlesGillanders]

Sounds great! Thank you.

[Poshy163]

I was doing some testing with the alpha wall box (ev charger), and it seems like alpha has either dropped, or massively reduced the limit to the POST requests? was able to make multiple within a few minutes? might query the support team on it (if it goes anywhere and attempt find out what happened) and if it was an intentional change

[Poshy163]

Also seems like the arbitrary limit on the amount of api calls that can be made per minute has been removed? will follow up on this before releasing, but its very strange

[DavidqStokes]

Even if they have relaxed the limitations on the frequency of API /POST calls, I think that we still need to set a sensible limit in the integration. We don't want people to have the option of abusing this making too many calls.

[Poshy163]

Interesting, might verify these claims, but it seems much more relaxed then when elvenfan was running the show. No overall restriction anymore

[Poshy163]

i have removed the throttle if you have multiple inverters, with my testing (with 2), you don't seem to run into any issues with being rate-limited. with the natural delay between API calls, it should be more than enough to conform to what the "new" limits apparently are

[Poshy163]

Its basically done, just pending hearing back about vitapower support for charge and discharge, @mauricebish and i are in contact with EvaPower/AlphaESS to hopefully speed this up

[Poshy163]

Haven't heard anything back, ill just merge this PR and will deal with the vitapower stuff whenever we hear back

[CharlesGillanders]

Let's get this in now but I'm thinking that using hard coded English strings for the charger states is probably against the design guidelines for home assistant. I'm guessing we should be using the built in language capabilities even if the only language we provide is English.

Have you any experience with that?

[Poshy163]

Yeah, can do. Will fix tonight

[djangopap]

thank you for this integration.
Is there a way to have a button to make the selection between different type of charge ? green slow, general, fast,...

[Poshy163]

Heya @djangopap, currently AlphaESS does not expose this info to the openAPI,

Your best bet might be asking them if they can allow it? Otherwise there isn't much I can do here unfortunately