custom-components
Failing to set current limit from HA
I consistently get an error "Request to https://api.zaptec.com/api/installation/****/update failed after 5 retries" when using the action update current limit.
HA: v2025.2.4, HAOS Installation: one Zaptec Go, running firmware v. 2.4.2.4 (the problem has been there for some time, also before the last firmware update).
Some details:
Logger: homeassistant.components.websocket_api.http.connection Kilde: components/websocket_api/commands.py:245 integrasjon: Home Assistant WebSocket API (dokumentasjon, problemer) Første forekomst: 11:40:26 (1 forekomster) Sist logget: 11:40:26
[140375849328000] Unexpected exception Traceback (most recent call last): File "/config/custom_components/zaptec/number.py", line 60, in async_set_native_value await self.zaptec_obj.set_limit_current(availableCurrent=value) File "/config/custom_components/zaptec/api.py", line 447, in set_limit_current data = await self._account._request( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ f"installation/{self.id}/update", method="post", data=kwargs ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/config/custom_components/zaptec/api.py", line 1007, in _request async for response, log_exc in ctx: ...<39 lines>... raise log_exc(error) File "/config/custom_components/zaptec/api.py", line 923, in _retry_request raise RequestRetryError( f"Request to {url} failed after {iteration} retries" ) from None custom_components.zaptec.api.RequestRetryError: Request to https://api.zaptec.com/api/installation/****/update failed after 5 retries
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 245, in handle_call_service response = await hass.services.async_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<7 lines>... ) ^ File "/usr/src/homeassistant/homeassistant/core.py", line 2794, in async_call response_data = await coro ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/core.py", line 2837, in _execute_service return await target(service_call) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call single_response = await _handle_entity_call( ^^^^^^^^^^^^^^^^^^^^^^^^^^ hass, entity, func, data, call.context ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call result = await task ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/number/init.py", line 122, in async_set_value await entity.async_set_native_value(native_value) File "/config/custom_components/zaptec/number.py", line 62, in async_set_native_value raise HomeAssistantError(f"Set current limit to {value} failed") from exc homeassistant.exceptions.HomeAssistantError: Set current limit to 6.0 failed
Hi,
Any updates on this issue ?
Messes with my load-balancing blueprint.
kind regards.
Hello... I have exactly yhe same issue. Did you find any solution on this??
This is so strange. I'm using this function all the time and I have no problems. I use it to actively regulate the amount of current to the car to ensure the house doesn't overspend its power input.
What happens if you try to adjust the current in Zaptec Portal? Front page -> Installations -> Select your installation -> Settings -> Power management -> Scroll down to "Charging mode" where the Available current phase 1-3 fields can be found. These three are the same as controlled by the Zaptec HA integration.
Hello. IT works when i do this in Zaptec Portal: settings -> Power management - charging management - Available current phase 1-3. I still think the issue is, that Zaptec integration is not allowed to talk to zaptec api portal. (somehow blocked because off stop messages, when not charging)
Hello. I kinda give up this in Home assistant. I have also a setup in Athom homey pro 2023, that works flawless... At the moment i need to keeps home just for this... The one thing i can't understand... When i run command in Zaptec portal, The same command zaptec use, it works... But not in node-red... The node-red flow is the same, that is has been in 2 years. So i dont understand this
I'm sorry to hear. To be able to help we need to identify why it's not working.
Are you willing and able to test something? (I'm sorry if this procedure is well-known, I don't know how much experience you have with these things.
- Open https://api.zaptec.com/help/index.html#/
- Login by pressing "Authroize"
- Go down and find the "/api/installation/{id}/update" press the arrow key and then press "Try it out"
- Fill in the form. You need to provide your own Installation ID and edit the "Installation properties to update" to what the image shows.
- Press "Execute". If this is successful you get a "200" response and something that looks like this:
Hello.. As i tried to explain. This works . Everything works from the Zaptec portal. My problem is with the node-red flow, thats uses the same command . In node-red i got this message: "HomeAssistantError: Command 'stop_charging_final' failed: Request to https://api.zaptec.com/api/chargers/f9fc7ece-19ff-4e6b-b99f-992309915175/SendCommand/506 failed after 5 retries" It has worked a year ore so, but stoped working in april, i think. Now i got this message.. Any ideas what causes this??
Oh, ok. That wasn't what the traceback error in the first message suggested.
When are you sending the "stop_charging_final" command? How often du you send it? I know that Zaptec (cloud) have changed the rules on when you're allowed to send it and have started failing on the command. E.g. sending the command when not charging is not permitted. -- We're working on a fix for that so that this command fails in this integration if you try it, but it haven't been published yet.
To quote the Zaptec API docs: "The command will be rejected if the charger is already paused (state ChargeOperationMode, 710 = 5 and FinalStopActive, 718 = 1) or disconnected (state ChargeOperationMode, 710 = 1)"
Hello again.. It runs every 15 min. I have also tried to remove the start/stop node, an used limit current. It also gives me the same error... Do you have an eksampel on a working limit current node?
man. 21. jul. 2025, 11:42 skrev Svein Seldal @.***>:
sveinse left a comment (custom-components/zaptec#166) https://github.com/custom-components/zaptec/issues/166#issuecomment-3095940483
Oh, ok. That wasn't what the traceback error in the first message suggested.
When are you sending the "stop_charging_final" command? How often du you send it? I know that Zaptec (cloud) have changed the rules on when you're allowed to send it and have started failing on the command. E.g. sending the command when not charging is not permitted. -- We're working on a fix for that so that this command fails in this integration if you try it, but it haven't been published yet.
To quote the Zaptec API docs: "The command will be rejected if the charger is already paused (state ChargeOperationMode, 710 = 5 and FinalStopActive, 718 = 1) or disconnected (state ChargeOperationMode, 710 = 1)"
— Reply to this email directly, view it on GitHub https://github.com/custom-components/zaptec/issues/166#issuecomment-3095940483, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNRM7IAIBSHC55OCEOXJD33JSYXZAVCNFSM6AAAAABXQOZEXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJVHE2DANBYGM . You are receiving this because you commented.Message ID: @.***>
Unfortunately I do not have any examples at hand for running this from node-red. I don't use node for that purpose. This integration doesn't have direct support of node-red. Perhaps others have some experience with it?
Have you tried setting the current limit work by adjusting the number dial in the HA GUI with the "Available current" slider?
Sending the "stop_charging_final" command every 15 minute, regardless if its charging or not it something I think Zaptec prohibits and probably the reason why you're seeing the errors.
Okay. I guess someone else experience the same issue. 🤔🤔. I havent tested with adjust the available current sider. I will try this
man. 21. jul. 2025, 12:31 skrev Svein Seldal @.***>:
sveinse left a comment (custom-components/zaptec#166) https://github.com/custom-components/zaptec/issues/166#issuecomment-3096095624
Unfortunately I do not have any examples at hand for running this from node-red. I don't use node for that purpose. This integration doesn't have direct support of node-red. Perhaps others have some experience with it?
Have you tried setting the current limit work by adjusting the number dial in the HA GUI with the "Available current" slider?
Sending the "stop_charging_final" command every 15 minute, regardless if its charging or not it something I think Zaptec prohibits and probably the reason why you're seeing the errors.
— Reply to this email directly, view it on GitHub https://github.com/custom-components/zaptec/issues/166#issuecomment-3096095624, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNRM7PDU24C457HXH7V6Z33JS6Q5AVCNFSM6AAAAABXQOZEXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJWGA4TKNRSGQ . You are receiving this because you commented.Message ID: @.***>
Is there anything else we can assist with here. If not, I'd like to close this issue.
There is a v0.8b2 beta / pre-release out if you want to try it out. It will give a failure if you attempt to send commands if not in the right mode.
Hello again. I could try the beta 👍 You can close this case.
ons. 30. jul. 2025, 11:18 skrev Svein Seldal @.***>:
sveinse left a comment (custom-components/zaptec#166) https://github.com/custom-components/zaptec/issues/166#issuecomment-3135484807
Is there anything else we can assist with here. If not, I'd like to close this issue.
There is a v0.8b2 beta / pre-release out if you want to try it out. It will give a failure if you attempt to send commands if not in the right mode.
— Reply to this email directly, view it on GitHub https://github.com/custom-components/zaptec/issues/166#issuecomment-3135484807, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNRM7INB2ZLJMWUVUWVLFD3LCEVTAVCNFSM6AAAAABXQOZEXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMZVGQ4DIOBQG4 . You are receiving this because you commented.Message ID: @.***>