Open braindeadmalc opened 1 month ago
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. Although HA doesn't appear to be throwing any errors into the logs, the update to the SMILE B3 settings fails (as confirmed via the AlphaESS app)
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 😅
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. Thanks for the hardwork carried out making this integration, it was a great help before Alpha ESS messed it up.
Are others still having issues?
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
Are others still having issues?
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 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 updateChargeConfigInfo
isn't having any effect despite returning no errors. I hope alpha get their stuff sorted and at a minimum are more transparent about whats going on.
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
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 Alpha ESS Energy Statistics : AL7002022040171 Storion-SMILE-B3 (AlphaESS) that looks like the same string ?
My version still reports 0.5.5 BTW Peter
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
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
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
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
Ah, I have a support ticket open with Alpha. If they fix the API issue will I be able to check it works?
ill keep it as a draft PR until you hear back, ive also talking with one of the guys behind the API to see if its intended or not.
Do keep us updated 👍🏻
Thanks; I really need Alpha to fix this otherwise I am going to have to change energy tariffs!
Resetting the charge/discharge data manually in the app makes the unit very little useto me.
I'm clinging to the belief that they broke this accidentally in the last upgrade rather than deprecating the older inverters without notice...though neither is a recommendation of the company.
Many thanks for all the hard work on this integration- it had served me very well.
Peter
All good @pjhum, just curious to see if this works, if set the charge/discharge data manually in the app (for some time) does it show up in the integration in the config area (you may need to restart the integration, or wait a few mins)
Yes, I can see the charge/discharge settings and they updated pretty quickly (2-3 min max) in the 'diagnostic' card of the integration to match a change made in the app. I can't tell what _batHighCap or _batUseCap refer to in the 'config' secrtion, but they don't change. I had assumed they were to do with battery protection in the background.
Peter
From: Joshua Leaper Sent: Sunday, November 3, 2024 11:37 AM To: CharlesGillanders/homeassistant-alphaESS Cc: pjhum ; Mention Subject: Re: [CharlesGillanders/homeassistant-alphaESS] "Alpha ESS: Set Battery Charge" not setting (Issue #138)
All good @pjhum, just curious to see if this works, if set the charge/discharge data manually in the app (for some time) does it show up in the integration in the config area (you may need to restart the integration, or wait a few mins)
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Here is from the API docs: batUseCap | Discharging Cutoff SOC [%] batHighCap | Charging Stops at SOC [%]
Its basically the "bounds" for how much the batteries connected can charge and discharge, this is sent to the API when one of the buttons are pressed, obv if the set discharge and charge calls arnt working, i dont think it would be doing much
OK- so it should set the same values that are reported in the diagnostic card. That is the part that isn't happening...
Peter
From: Joshua Leaper Sent: Sunday, November 3, 2024 12:07 PM To: CharlesGillanders/homeassistant-alphaESS Cc: pjhum ; Mention Subject: Re: [CharlesGillanders/homeassistant-alphaESS] "Alpha ESS: Set Battery Charge" not setting (Issue #138)
Here is from the API docs: batUseCap | Discharging Cutoff SOC [%] batHighCap | Charging Stops at SOC [%]
Its basically the "bounds" for how much the batteries connected can charge and discharge, this is sent to the API when one of the buttons are pressed, obv if the set discharge and charge calls arnt working, i dont think it would be doing much
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Well, yeah. which likely means that either you haven't pressed the charge/discharge (and waited up to a min for the next fetching of the API), orrr the setcharge and setdischarge isn't working, which seems to be the case here, i have asked for clarification by am yet to hear back
The batUseCap should also be the minimum amount the battery can discharge (its set as the Discharging cut off SOC in the settings)
while the batHighCap is only shown as the Charging stops at SOC setting (aka is only used for force charging the battery)
Yes, that is clear. The different names in the integration were confusing me, but a moment's thought tells me they need to be unique...
I previously used the Alpha ESS Set Battery Charge successfully in my automations to set summer night charging based on Solcast forecasts.
I was trying to set up & test an automation to stop my battery emptying into the car on Intelligent Octopus using the Alpha ESS Set Battery Discharge call when I realized neither was working... TBH the 'new' controls are less important to me than the existing ones resuming.
I have reached out to Alpha UK- without holding out much hope.
thanks again for your work and explanations. Peter
From: Joshua Leaper Sent: Sunday, November 3, 2024 12:33 PM To: CharlesGillanders/homeassistant-alphaESS Cc: pjhum ; Mention Subject: Re: [CharlesGillanders/homeassistant-alphaESS] "Alpha ESS: Set Battery Charge" not setting (Issue #138)
The batUseCap should also be the minimum amount the battery can discharge (its set as the Discharging cut off SOC in the settings)
while the batHighCap is only shown as the Charging stops at SOC setting (aka is only used for force charging the battery)
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
I have a very similar issue: Setting the charge and discharge times worked perfectly via the integration until about 2 weeks ago, but no longer seems to work. Only reading the diagnostics now seems to work via the integration. Manually setting the charge and discharge time via the app still works - and then shows correctly in the diagnostics. Have removed and re-added the integration but can't get it to work to set the timings anymore.
@ppootle do you also have a Storion-SMILE-B3?
@pjhum you might have some luck with alpha support, translates to: "This charge and discharge setting is applicable to all models. If it does not work, you need to submit a customer complaint and contact our after-sales service."
No. It's a Smile5INV.
On Mon, 4 Nov 2024, 1:04 am Joshua Leaper, @.***> wrote:
@ppootle https://github.com/ppootle do you also have a Storion-SMILE-B3?
— Reply to this email directly, view it on GitHub https://github.com/CharlesGillanders/homeassistant-alphaESS/issues/138#issuecomment-2453667253, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIALCZGYYWQA6QPPUH46KUDZ63B2NAVCNFSM6AAAAABQHTBGF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJTGY3DOMRVGM . You are receiving this because you were mentioned.Message ID: @.*** com>
Thanks @Poshy163, I'll wait and see when they get back to me.
Was that a Google translate job or can you read Chinese? If so, I'm impressed...
I cant get the discharge setting to work with t10HV or Smile5
Haha, I used google translate, I'm not that good.
Also, did some more digging. Seems to be a widespread issue. See the video below. Setting the discharge time seems to disable it? I'll do some digging as to if it was something on my end. Or the API
https://github.com/user-attachments/assets/7d74ccd6-8f63-4157-a331-7907c3e6bfa4
Ah well, found the issue. if anyone needs an fix now, and knows how to get to the source files of home assistant,
On line 93 of the coordinator.py, there is a 0 in the updateDisChargeConfigInfo call, change to a 1, save. then reboot and it will work. otherwise and update will go out as soon as Charles approves my PR
Can this fix be done at a home asssit level ?
Sent from Outlook for iOShttps://aka.ms/o0ukef
From: Joshua Leaper @.> Sent: Monday, November 4, 2024 8:05:50 PM To: CharlesGillanders/homeassistant-alphaESS @.> Cc: renamedthewild @.>; Comment @.> Subject: Re: [CharlesGillanders/homeassistant-alphaESS] "Alpha ESS: Set Battery Charge" not setting (Issue #138)
Ah well, found the issue. if anyone needs an fix now, and knows how to get to the source files of home assistant,
On line 93 of the coordinator.py, there is a 0 in the updateDisChargeConfigInfo call, change to a 1, save. then reboot and it will work. otherwise and update will go out as soon as Charles approves my PR
— Reply to this email directly, view it on GitHubhttps://github.com/CharlesGillanders/homeassistant-alphaESS/issues/138#issuecomment-2454214871, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL3QDYLIKRPXX7ORRGBARPLZ645XNAVCNFSM6AAAAABQHTBGF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUGIYTIOBXGE. You are receiving this because you commented.Message ID: @.***>
you can use the visual studio code add-on, but i would not recommend it if you are not sure, rather wait for the PR to be merged
Got it
Sent from Outlook for iOShttps://aka.ms/o0ukef
From: Luke Wilden @.> Sent: Monday, November 4, 2024 8:08:24 PM To: CharlesGillanders/homeassistant-alphaESS @.>; CharlesGillanders/homeassistant-alphaESS @.> Cc: Comment @.> Subject: Re: [CharlesGillanders/homeassistant-alphaESS] "Alpha ESS: Set Battery Charge" not setting (Issue #138)
Can this fix be done at a home asssit level ?
Sent from Outlook for iOShttps://aka.ms/o0ukef
From: Joshua Leaper @.> Sent: Monday, November 4, 2024 8:05:50 PM To: CharlesGillanders/homeassistant-alphaESS @.> Cc: renamedthewild @.>; Comment @.> Subject: Re: [CharlesGillanders/homeassistant-alphaESS] "Alpha ESS: Set Battery Charge" not setting (Issue #138)
Ah well, found the issue. if anyone needs an fix now, and knows how to get to the source files of home assistant,
On line 93 of the coordinator.py, there is a 0 in the updateDisChargeConfigInfo call, change to a 1, save. then reboot and it will work. otherwise and update will go out as soon as Charles approves my PR
— Reply to this email directly, view it on GitHubhttps://github.com/CharlesGillanders/homeassistant-alphaESS/issues/138#issuecomment-2454214871, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AL3QDYLIKRPXX7ORRGBARPLZ645XNAVCNFSM6AAAAABQHTBGF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUGIYTIOBXGE. You are receiving this because you commented.Message ID: @.***>
Ah well, found the issue. if anyone needs an fix now, and knows how to get to the source files of home assistant,
On line 93 of the coordinator.py, there is a 0 in the updateDisChargeConfigInfo call, change to a 1, save. then reboot and it will work. otherwise and update will go out as soon as Charles approves my PR
I made the change, however it did not seem to resolve the issue
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?