Problems retrieving entities / initialising

[DavidqStokes]

I suspect that this is an AlphaESS issue, however...

Yesterday morning I noticed that some entities (e.g. SOC from my Smile B3 battery and PV production figure from my monitored PV system) were missing. They appeared intermittently during the day and would then disappear.

This morning I noticed that the integration will not initialise (error log below). I also cannot log in to the AlphaESS app on my phone and am thinking that AlphaESS are 'tinkering' this weekend.

Anyone else have problems?

Error log below:

Logger: homeassistant.config_entries Source: config_entries.py:594 First occurred: 08:00:03 (2 occurrences) Last logged: 10:13:10

Error setting up entry alphabeb5fe159238b3ae for alphaess Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/alphaess/init.py", line 49, in async_setup_entry for unit in ESSList: TypeError: 'NoneType' object is not iterable

[blackshroud]

I suspect this has to do with the global maintenance being done by AlphaESS (for the last 38 hours the app itself has been intermittently down/not displaying data, however, it might be that the API service itself has been changed/updated.

Lets wait and see once the outage is marked as resolved.

[DavidqStokes]

Thanks for confirming it's not just me.

I agree that we need to wait and see what happens and respond accordingly. I have significant faith in this development community.

[jamiergrs]

Was about to ask the same thing, I've had basically all instantaneous data not available and the app showing the device as "offline" but a solid COM light. Visiting cloud.alphaess I can see the device is online but also missing all live data and SOC

I'm assuming everyone is having similar issues and is an issue with the AlphaESS api

[Poshy163]

Spot on, due to the current "maintenance" that has been going on for the last few days. its producing most of the response from the API as null

[DaveBinM]

Based on this comment, it seems as if it’s an issue with AlphaESS’ servers, rather than an API change.

https://github.com/alphaess-developer/alphacloud_open_api/issues/88#issuecomment-2408756845

[TheSimTek]

Same issue here. App and web back online but cannot initialise the integration.

[Poshy163]

API is still down, throwing a bunch of errors on the API responses, would be a bunch of "Unexpected error fetching alphaess data" errors in your logs.

They seem to be prioritising getting the app interface fixed first, then moving onto the OpenAPI, whenever that might be

[dan-s-github]

Interesting strategy to close Issue 88 and then open a new issue Issue 89

[DavidqStokes]

This is clearly an AlphaESS issue and I will therefore close this issue when/if the API comes back working okay with the integration. If it comes back broken we can use this issue to identify what needs to be revised. Thanks for the input and feedback everyone.

[MonsterEnergy-wtf]

It starts to piss me off to see that internet relying devices get inaccesible while maintenance. The manufacturer xould lock us oht when ever they want to.

I think I will start to use Modbus to grab data directly from the device with IOBroker rather than using the workaround with the unreliable API...

Not sure why the device cannot be used locally only via LAN... 🤷‍♂️

[dan-s-github]

Unrelated but I also wanted to swap to modes integration, now my supplier replaced my smile 5v2 with a smile 5v1 where the modbus connector is not easily accessible and I forgot to connect a cable at the time of replacement :-(

[puja108]

My AlphaESS App is already working again, but the HA plugin is still erroring out. Might still related to the maintenance window as there could different servers/endpoints being used. Just wanted to put it here, in case people were also wondering.

[DavidqStokes]

Same here

[eviltabouleh]

I think that the API has changed , I understand that they are still possibly having issues with the platform but I am seeing this error [alphaess.alphaess] Error: when calling https://openapi.alphaess.com/api/getEssList [homeassistant.config_entries] Error setting up entry alphaXXXXXXXXXX for alphaess

I am in Australia and using a VPP (Amber Electric) and they use this API to control our batteries , this started working correctly around 4pm yesterday afternoon

[Poshy163]

Yeah, im with amber too, weirdly enough thats working. odd, ill reach out to elevenfan and see if anything has changed with the API. super odd. maybe they are web scraping or just not using the openAPI at all?

[Meigl89]

Now we have the nginx error page. Thats the same we had last time, when there were problems with the API. Fingers crossed.

[Poshy163]

Appears to be back giving data, but some of it is going to be null.... at least the integration wont error out anymore

[jamiergrs]

My integration still is failing to initialise with the below

[strickersuk]

[DavidqStokes]

I tried to reinitialise. All entities except one were Unavailable. The error log shows the following:

Logger: homeassistant.config_entries Source: config_entries.py:594 First occurred: 08:40:46 (1 occurrences) Last logged: 08:40:46

Error setting up entry alphabeb5fe159238b3ae for alphaess Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/alphaess/init.py", line 49, in async_setup_entry for unit in ESSList: TypeError: 'NoneType' object is not iterable

[blackshroud]

I have a new home assistant setup, so trying to setup the add-on for the first time, and I am just getting "an unknown error occured" through the UI when entering app secret etc etc

Checking the logs it shows a 502

[dan-s-github]

The APP no longer shows the maintenance warning, so hopefully everything will resolve soon

[lweberru]

The integration is now able to intialize again, but most sensors are not filled.

[Poshy163]

Yeah, seems like the API is up now, is anyone seeing anything regarding "cbat" in their logs? i have a feeling for some reason the getOneDateEnergy call isn't being made, meaning some of the data is being left out? super strange ill have to look into it

[jamiergrs]

Couldn't see anything in my logs about cbat. Looks like all data has come back except the "live" data I.e all instantaneous data such as SOC and Load is missing

[Poshy163]

Ah thanks for that. just checked again and the API is still down, all good. still spilling null data for getLastPowerData. assuming that the integration doesnt error out, the data should return and start updating again whenever the data is fed back through without being null

[dmutsaers]

I just checked and it looks like the integration is available again:

[cpmueller]

As far as I can see the service is flapping. It is not stable an not all data is available. We have to wait :-(

[dmutsaers]

@cpmueller You're right the service is unavailable again.

[Poshy163]

Im currently working on a new pull here for some new charge/discharge features.

I can add some edge cases to the API so that the whole thing doesn't reset/error out when the API doesn't return data, rather just throws an error to the user, but still continues to try and grab new data every 5 mins.

is that something you'd be interested in seeing? resolves manually having to restart the integration when either your internet goes down and it cant reach the API, or the API refuses to connect (like now)

[Meigl89]

That would be awesome!

[jamiergrs]

I'm also just getting null from postman. I'm assuming this will just resolve itself once the data starts coming back through? Seems all requests are passing ok now

[jamiergrs]

Has there been any update? Seems they've removed the issues from the AlphaESS Open API GitHub, can't even see them any more

[Poshy163]

Yeah, they closed the issues, and are just referring people to contact support about it....

[MonsterEnergy-wtf]

Awesome. You pay a shit amount of money for the whole system (in my case 25k €) and all you get is a shitty support. Awesome. I guess I will go for Modbus integration within IOBroker and send data via MQTT to HA. The my whole system will be unplugged from the net. I'm tired of intransparent support like this. I mean: when the official API is down, how will the owner of this project bring back the integration?

But I guess this is the common way of a lot of service providers.

Time to change something.

[blackshroud]

interesting, I cannot even open the open.alphaess.com website anymore....

Just get a 500 error

[eviltabouleh]

interesting, I cannot even open the open.alphaess.com website anymore....

Just get a 500 error

It's still flaky and I've noticed that it may need a cache clear for some browsers

[strickersuk]

I can login to the API website. Weird how some data is showing from the API and some isn't. App and Website seem OK now so I assume it's just a waiting game.

[tonbut]

The API seems to be back online for me now with getLastPowerData returning correct values.

[strickersuk]

Interesting, I've just restarted HA for a different reason and I'm back to can't initialise.

[strickersuk]

All back now. Quick question slightly off topic, I had my inverter replaced and I now have 2 services. One populated one not, I've removed the entities but would appreciate some help removing the service?

[Meigl89]

On my end still nothing. But let's wait and see. Last time it also came in batches if I remember correctly..

[puja108]

It's generally back for me, but I still see some flapping every now and then, which does resolve itself without reload/restart though.

[DavidqStokes]

I can now initialise the integration, but many values are either reporting 'unknown' or 'unavailable'. It's almost six days now that this has been unreliable.

[speedyhb]

Everything is working again !

[Meketh74]

Working again for me too. Still also thinking about a Modbus integration within IOBroker that sends data via MQTT to HA. Anybody know a good guide for the MQTT to HA part?

[dry]

This works very well https://github.com/dxoverdy/Alpha2MQTT.

On Thu, 17 Oct 2024, 16:59 Meketh74, @.***> wrote:

Working again for me too. Still also thinking about a Modbus integration within IOBroker that sends data via MQTT to HA. Anybody know a good guide for the MQTT to HA part?

— Reply to this email directly, view it on GitHub https://github.com/CharlesGillanders/homeassistant-alphaESS/issues/136#issuecomment-2419935046, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACTWF7K5HF5U6IVHD7DZWLZ37NHDAVCNFSM6AAAAABP3IBQUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJZHEZTKMBUGY . You are receiving this because you are subscribed to this thread.Message ID: @.*** .com>

[DavidqStokes]

I now have only one entity reporting unavailable and I'm not 100% sure it's relevant to my battery/inverter.

If it's all good in the morning I will close this issue.

[gregpetersau]

Conforming finally working for me in Syd Aus too. Took quote a few restarts to get them all, but all entities seem to now report correctly

[kaffeetrinker71]

the API apparently provides data according to POSTMAN (see screenshot). But the integration (0.5.5) still does not receive any data.