"Alpha ESS: Set Battery Charge" not setting #138
Comments
|
I have the same problem, as well as with the discharge |
|
Same problem on my Smile5 but it doesn't even work once per day so I don't imagine that's the issue. I really need to convert to a direct MODBUS connection but I can't get it to work on my system for some unknown reason. |
|
But it doesn't work with Postman either. So the problem seems to be with the API |
|
My SMILE5 isn't working either, but only the charge setting for some reason? Is throwing up an error of "unknown action". |
|
Just done some testing via my scheduled automation. |
|
Cheers for the reports guys, I'm working on a new PR to hopefully improve the charging/discharging stuff. Great to have alpha throw some edge cases these last few weeks so I can verify if the whole system works 😅 |
And the on-going work on this (by everyone involved) is appreciated as always. |
|
I've raised a ticket with Alpha assuming it's their issue. |
|
Here's the reply from Alpha We are working on this issue and expected to take few days to resolve. If you still experience the issue on 28/10, please create a new support request again. Sorry for any inconvenience it may caused. Kind Regards, Eddie Yam Alpha ESS UK |
|
Thanks for the update |
|
It's now 31st October and my battery charge / discharge setting still didn't work last night. Are others still having issues? |
|
I got fed up with the constant issues caused by the AlphaESS updates and have finally moved to MODBUS which is well worth the effort, the Inverter responds immediately to commands now and unlocks features that aren't possible otherwise, e.g. stopping the batteries charging from solar. |
Personally not, what inverter you got? could be related some what to that? the PR i got going here should give more transparency regarding the currently set charge and discharge times (when the API polls) Should give you a little bit of info to give to alpha if its not fixed on your end |
|
I still have the problem and have raised the case again as they requested |
I have a SMILE B3 battery and inverter |
|
Yes, I have a B3 and can read data via the open API but still cannot write charge/discharge settings since the 'upgrade' event. It is playing hell with my battery SOC when Intelligent octopus starts the car charging outside 'usual' times. I can still change the settings manually via the Alpha app. BTW does anyone have experience of writing to modbus registers on a B3? I know it needs an RS485 converter at the very least... |
|
Hey there, do you have the full name (the model of it) so I can add it to the blacklist? Should show in your logs as Model: xxx Serial: xxxx |
|
Thank you everyone for updates, I'm not using this repo but read it to get the good information! Instead I'm using the alphaess-openAPI. I have a Smile5 and am having the same issues - reading works, but updates |
|
Mine is Alpha Smile B3 serial AL7002022040171 |
|
Sorry @pjhum should of been more specific. when the integration is started, there is a string printed to the logs, this includes the model and serial number (these are case sensitive). it looks something like this:
Cheers! |
|
Apologies, I'm fairly new to HA. which log, exactly? I've searched <settings> <system> <logs> and there is no entry adding an inverter.
Peter
From: Joshua Leaper
Sent: Saturday, November 2, 2024 6:24 AM
To: CharlesGillanders/homeassistant-alphaESS
Cc: pjhum ; Mention
Subject: Re: [CharlesGillanders/homeassistant-alphaESS] "Alpha ESS: Set Battery Charge" not setting (Issue #138)
Sorry @pjhum should of been more specific. when the integration is started, there is a string printed to the logs, this includes the model and serial number (these are case sensitive). it looks something like this:
image.png (view on web)
Cheers!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
OK- removed the integration and re-added. The start up message was My version still reports 0.5.5 BTW |
|
To view logs in Home Assistant, you can navigate to Settings > System > Logs then click on view all logs. If you reboot the integration, click ctrl + f (page finder thing) and look for "Model". It should bring up that line I posted earlier |
|
Also, to force upgrade to 5.6.0, Under the integrations page on HACS, you can click the RELOAD DATA button under the SETTINGS tab (should be like the top right of the page) and then an update will appear. Maybe do this and verify you can't set the discharge/charge via the buttons before i blacklist that model inverter |
Mine's "New Inverter: Serial: AL4001020050581, Model: Storion-SMILE-B3" Also, I tried the 15 min charge button with no effect |
|
Thanks, I now have 0.5.6 showing.The new controls have appeared.They do not appear to work, though. I pressed the "reset charge discharge button" and my AlphaEss app reports no change in settings.I'm presuming it should be instant, or nearly so?What I don't understand if the hardware is incompatible is that it was happily letting me set the overnight charge% until the last Alpha update/outage. PeterSent from Android deviceOn 2 Nov 2024 16:34, Joshua Leaper ***@***.***> wrote:
Also, to force upgrade to 5.6.0,
Under the integrations page on HACS, you can click the RELOAD DATA button under the SETTINGS tab (should be like the top right of the page) and then an update will appear.
Maybe do this and verify you can't set the discharge/charge via the buttons before i blacklist that model inverter
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Yeah, if you click on any of the time periods, you then should be able to open your app and see the time settings set. Cheers for that all! |
|
Cheers for the logs, ill add the inverter to the blacklist and push a minor update soon, the current/discharge charging time (1 & 2), and the charging range within the diagnostics section of the stuff will stay, just your ability to set anything (within the Configuration area) will be removed |
|
@renamedthewild what model are you connecting via modbus? I can't get my B3 to respond on RS485 (it doesn't support modbus over TCP) whatever I try... |
|
SMILE5-INV EMS 2.01 No issues with Modbus using the RS485 port (ethernet adaptor) just trying to save having to mess around with all that stuff just so they can sell a few kWh between 6-9pm lol |
|
I also use my self a SMILE-T10-HV-INV - that has modbus over TCP and that works amazing |
|
The original B3 seems a bit of an outlier. did you have to mess about to get the converter working? mine is set up as a simple TCP server with the serial side on 9600 no parity as per the docs I can find. HA has RTU over TCP set, but getting nothing.
My freebie modbus tester connects to the bridge just gets time outs.
Now thinking the B3 doesn't do modbus at all...
From: renamedthewild
Sent: Tuesday, November 5, 2024 11:59 AM
To: CharlesGillanders/homeassistant-alphaESS
Cc: pjhum ; Mention
Subject: Re: [CharlesGillanders/homeassistant-alphaESS] "Alpha ESS: Set Battery Charge" not setting (Issue #138)
I also use my self a SMILE-T10-HV-INV - that has modbus over TCP and that works amazing
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
I have now downloaded the new 5.6.1 release and will see whether changing the charge/discharge settings via automation (service call) works this evening with my SMILE B3. |
|
I just got another response to my support ticket from Alpha. I'm not quite sure where this leaves us, "Sorry for our late reply. According to the Web API team, there are no reported issues with the OpenAPI command integration at this time. Could you please try again? |
|
Looking on the German users' forum, it seems European data is now stored on the (new) European server. I suspect this is also hosting the new API that UK customer support gave me. (https://apiservice-eu.alphaess.com/v1/Open/XXXXX) |
|
I'd been holding out for a reply from Alpha regarding this same issue on my one year old B3-plus. I got exactly the same response from them this morning as braindeadmalc. Like others , I'd been able to set charge and discharge periods and desired SOC using the OpenAPI via Home Assistant a couple of times a day so as to make best use of Octopus Agile and prevailing weather conditions. Since the global update I can read SOC but cannot set it or charge periods via HA. I pulled the latest version of the OpenAPI yesterday. I believe I am on 0.5.6.1 version. |
|
Interesting, seems like i'll have to make the API dynamic, and what will happen is you guys will have to manually edit your files and place the API URL in the files (will require an update to the integration + API) |
The optimum solution would be to have the API library be aware of both API endpoints and to accept a parameter that would select a specific endpoint for each time data is requested. We would then be able to configure the Home Assistant integration with an extended setup dialogue that asked for a radio button type question "EU or worldwide API endpoint" I can make the appropriate change to the library later this week. |
|
Wonderful, ill see if i can get a full list of region specific list of URL's (if there is any more) |
|
I'm in the UK and despite downloading 5.6.1 yesterday my automations still failed to effect any changes to the charge / discharge settings on of my SMILE B3 last night. |
|
I've just been experimenting with the new EU URL https://apiservice-eu.alphaess.com/v1/Open/getLastPowerData . It seems to almost work, but every call fails with the error |
|
The old api wanted the time stamp in the china time zone, with a 5 minute latitude. Which time zone did you timestamp it for? I can’t find any documentation either, though I’m still getting to grips with trying to interrogate the api.
…Sent from my iPad
On 6 Nov 2024, at 22:50, Tony Butterfield ***@***.***> wrote:
I've just been experimenting with the new EU URL https://apiservice-eu.alphaess.com/v1/Open/getLastPowerData . It seems to almost work, but every call fails with the error {'code': 103, 'info': 'Timestamp is Wrong！'} Switching back to the old URL, it works again. Not sure if Alpha has updated the API in other ways too? I havent seen any doc updates.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
|
Im unfortunately not in the EU, so i wont be much help, but is there any documentation on this website: https://apicloud-eu.alphaess.com/#/? |
|
I wish Alpha made this information easier to find! Does anyone know how to get login credentials for https://apicloud-eu.alphaess.com/#/ ? If I use the ones created on https://open.alphaess.com/login it says "no such user". @pjhum on the original API the timestamp was in seconds since 1970 Epoch which should be timezone independent AFAIK |
|
I've been wrong before...😉I was using the timestamp generator linked from the open API documentation, and it appeared to return a value in Beijing local time when I decoded it.May simply be the decoding that was corrected to their local time- Google wasn't making such a good job of translating the page from Chinese.I couldn't log in to the German server's API either, though I'm not confident my request was properly formed.PeterSent from Android deviceOn 7 Nov 2024 10:06, Tony Butterfield ***@***.***> wrote:
I wish Alpha made this information easier to find! Does anyone know how to get login credentials for https://apicloud-eu.alphaess.com/#/ ? If I use the ones created on https://open.alphaess.com/login it says "no such user".
@pjhum on the original API the timestamp was in seconds since 1970 Epoch which should be timezone independent AFAIK
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
I am beginning to think that there is confusion within AlphaESS between the OpenAPI and their older commercial API services. According to this page https://urlscan.io/domain/alphaess.com the apiservice.alphaess.com URL has been around since 2021, whereas the URL for openapi.alphaess.com is only from 2023. In the absence of any comment on the OpenAPI developer portal I wonder if there's a chance that people are being given mistaken information by the EU support team? |
|
I may be wrong but something got fixed! |
|
I'm seeing the same thing as braindeadmalc. It does seem to be working. I did, initially, find that my two automations were no longer valid. I pulled the latest GitHub version and it made no difference. So I investigated further and discovered that the SOC condition definition has changed from (whatever it was before, as I didn't write it down) to "current <serial number"_State of battery level . I made changes to my automations and I've run both automations a number of times and it appears to be setting the battery charge/discharge settings properly and quickly. Fingers crossed ! Who ever has changed things to make it work .... thank you! |
|
My original automations run overnight- I'll see if they've restarted working.If so, I'll then see if the new force charge/discharge features work on the B3.PeterSent from Android deviceOn 8 Nov 2024 18:08, purrcat33a ***@***.***> wrote:
I'm seeing the same thing as braindeadmalc. It does seem to be working.
I did, initially, find that my two automations were no longer valid. I pulled the latest GitHub version and it made no difference. So I investigated further and discovered that the SOC condition definition has changed from (whatever it was before, as I didn't write it down) to "current <serial number"_State of battery level .
I've run both automations a number of times and it appears to be setting the battery charge/discharge settings properly and quickly.
Fingers crossed !
Who ever has changed things to make it work .... thank you!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Same here. Set battery charge finally worked today again. I'm in UK.
And had a message yesterday from UK support saying we should still be using
the original open API address not the EU one.
…On Fri, 8 Nov 2024, 7:48 pm pjhum, ***@***.***> wrote:
My original automations run overnight- I'll see if they've
restarted working.If so, I'll then see if the new force
charge/discharge features work on the B3.PeterSent from Android deviceOn 8
Nov 2024 18:08, purrcat33a ***@***.***> wrote: <br> I'm seeing the
same thing as braindeadmalc. It does seem to be working. <br> I did,
initially, find that my two automations were no longer valid. I pulled the
latest GitHub version and it made no difference. So I investigated further
and discovered that the SOC condition definition has changed from (whatever
it was before, as I didn't write it down) to "current <serial
number"_State of battery level . <br> I've run both automations a
number of times and it appears to be setting the battery charge/discharge
settings properly and quickly. <br> Fingers crossed ! <br> Who ever has
changed things to make it work .... thank you! <br> <br> —Reply to this
email directly, view it on GitHub, or unsubscribe.You are receiving this
because you were mentioned.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BIALCZHNAYVC4GJVJXR2GULZ7UIPXAVCNFSM6AAAAABQHTBGF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVGYZTINJVGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
|
I'm also in the UK with a SMILE B3 battery, and my overnight automation was able to set the charge / discharge parameters last night for the first time since the AlphaESS upgrade. I'm a bit lost as to what the problem actually was, and who did what to fix it, but my thanks to everyone involved in getting to the bottom of this and getting the issue fixed. |
|
+1 here with another B3 Automations worked, and the “reset charge/discharge” button reset my charge parameters to the values set in the boxes and cleared the charge times I had set. I’ll experiment with forced charge and discharge buttons later on, but something has definitely improved. Thanks to the integration developers for the effort this has taken- even if ultimately it turns out to be Alpha’s SNAFU |
|
Haha what an ending, must of been something wrong with the firmware on the batteries or something, super weird that it just suddenly started working one day Maybe enough people complained that it finally got escalated 🙈 |
|
OK, back to what My B3 will and won't do.Set charge works fine, both as an action in an automation and by the new x-minute charge buttons. Big relief for me as I use Solcast forecasting.At present, I cannot alter the discharge settings via this integration- though If someone at Alpha is working in the background that might change? If I alter the discharge parameters in the app, it is reflected in this integration.Will report back if anything changes.Meanwhile I expect I can solve my discharge problems by forcing the unit to charge instead- I'm not on an export tariff (on FIT here ) so it isn't critical for me to force export, just stop the battery emptying during cheap periods.PeterSent from Android deviceOn 9 Nov 2024 10:55, Joshua Leaper ***@***.***> wrote:
Haha what an ending, must of been something wrong with the firmware on the batteries or something, super weird that it just suddenly started working one day
Maybe enough people complained that it finally got escalated 🙈
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
I asked Alpha what they did to correct the problem (if, indeed, it was them). The reply that I got was this : "There's a bug in OpenAPI identified and is expected to be fixed this week, therefore you may still experience the issue in coming days. Sorry for any inconvenience caused." I'm not sure exactly what this is saying, but it does suggest that something has been found and is being addressed. It doesn't explain why things magically started working last week though. |
|
Sounds like AlphaASS are one of the first to use quantum computing at scale. Rather than relying on logic to produce known outcome based on inputs, the result is actually the outcome of some inexplicable probability function... |
They probably hitched a ride on the infinite improbability drive and derived a result from absolutely everywhere. |
|
As of this morning, I see discharge control also working via this integration on my B3. AFAIK my B3 now works fully with this, and the model does not need blacklisting. I am thinking this was a bug in the API all along. As an aside, now I have a different modbus gateway the Smile B3 model also supports modbus control. Thanks again to the developers of this integration. |
Automations using "Alpha ESS: Set Battery Charge" don't set the battery charge period on my Smile B3.
No errors, just not setting the times
These automations worked prior to the latest Alpha upgrade.
Looking at the Alpha API site, they appear to be stating that setting once per day is allowed which is what caused problems for a lot of us. It got changed to once every 10 mins but I'm wondering if they've put it back to once per day?
The text was updated successfully, but these errors were encountered: