API-cal fail error 506

[Amokk123]

msg : { domain: "zaptec", service: "stop_charging", target: object, data: object } 13.5.2025, 17:12:49node: debug 44Sum : msg.payload : number 0.4848 13.5.2025, 17:14:32node: Turn off msg : error "HomeAssistantError: Command 'stop_charging_final' failed: Request to https://api.zaptec.com/api/chargers/xxxxx-yyyy-zzzzzz/SendCommand/506 failed after 5 retries"

This error i got each 15 min.

[sveinse]

Thank you. This is another issue that what was addressed in #161.

SendCommand is issued when a command is issued from HA, like start and stop charging. It does not happen on its own on regular intervals. So I'm curious, what in your system is issuing stop_charging_final very frequently? It should only be issued when a session is ongoing and you want to stop the session.

[Amokk123]

Now, it is not happening on its own. I have a node-red flow, thats run each 15 mintes a Day... From 20:00 it starts charge to 06:00( 10 cheapest hour between 20-06)outside this periode it sends stop charge. It has worked for aboute a year. But suddenly i got this error, without doping anything

[sveinse]

Does this node-red flow issue start charge before issuing stop_charging? Are you in a charging mode when the stop charging command is issued?

FYI I use "Available Current" in the installation device to control and pause/unpause the charging. I authorize the charging and starts it (which locks the cable) and then use "available current" to 0 to temporary halt the charging. When the price is low, I raise it to the wanted amount, typically 8 to 12A (3 phase) to not exceed 10kW of the whole house. Maybe you can experiment with something similar?

[Amokk123]

Okay, i will try to do something like that. I am not so good at node-red 😅😅

tir. 13. mai 2025, 20:24 skrev Svein Seldal @.***>:

sveinse left a comment (custom-components/zaptec#175) https://github.com/custom-components/zaptec/issues/175#issuecomment-2877544080

Does this node-red flow issue start charge before issuing stop_charging? Are you in a charging mode when the stop charging command is issued?

FYI I use "Available Current" in the installation device to control and pause/unpause the charging. I authorize the charging and starts it (which locks the cable) and then use "available current" to 0 to temporary halt the charging. When the price is low, I raise it to the wanted amount, typically 8 to 12A (3 phase) to not exceed 10kW of the whole house. Maybe you can experiment with something similar?

— Reply to this email directly, view it on GitHub https://github.com/custom-components/zaptec/issues/175#issuecomment-2877544080, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNRM7OHEOQS2HQVOZ3OMAD26I2F7AVCNFSM6AAAAAB5A57HT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZXGU2DIMBYGA . You are receiving this because you authored the thread.Message ID: @.***>

[Amokk123]

I authenticat with a rfid card, feks 16:00. But i dont want it to start charge the 10 cheapest hour between 20-06. This is how it have worked for a year or so. But suddenly stopped working

tir. 13. mai 2025, 21:22 skrev Jostein @.***>:

Okay, i will try to do something like that. I am not so good at node-red 😅😅

tir. 13. mai 2025, 20:24 skrev Svein Seldal @.***>:

sveinse left a comment (custom-components/zaptec#175) https://github.com/custom-components/zaptec/issues/175#issuecomment-2877544080

Does this node-red flow issue start charge before issuing stop_charging? Are you in a charging mode when the stop charging command is issued?

FYI I use "Available Current" in the installation device to control and pause/unpause the charging. I authorize the charging and starts it (which locks the cable) and then use "available current" to 0 to temporary halt the charging. When the price is low, I raise it to the wanted amount, typically 8 to 12A (3 phase) to not exceed 10kW of the whole house. Maybe you can experiment with something similar?

— Reply to this email directly, view it on GitHub https://github.com/custom-components/zaptec/issues/175#issuecomment-2877544080, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNRM7OHEOQS2HQVOZ3OMAD26I2F7AVCNFSM6AAAAAB5A57HT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZXGU2DIMBYGA . You are receiving this because you authored the thread.Message ID: @.***>

[sveinse]

I have the same system where I authenticate with rfid, but I use the available current to prevent it from actually starting the charging.

The reason it fails is because the Zaptec cloud is rejecting the command, so in itself there is little we can do about that. Are you only sending stop charging commands when the car is actually charging, or are you always sending stop charging even if the car is not charging? Because Zaptec cloud might not like getting stop commands for something that's not started.

[Amokk123]

Hello... I have stoped using this start\stop, and start using limit_current. It has been deactivated for about 48 hours, before i start using limit_current. But i still got errors : Log node-red

HomeAssistantError: Limit current failed: POST request to https://api.zaptec.com/api/installation/xxxx-yyyy-zzz/update failed with status 400: <ClientResponse(https://api.zaptec.com/api/installation/xxxx-yyyy-zzz/update) [400 Bad Request]> <CIMultiDictProxy('Server': 'nginx/1.27.4', 'Date': 'Sun, 18 May 2025 19:29:28 GMT', 'Content-Type': 'application/problem+json; charset=utf-8', 'Content-Length': '434', 'Connection': 'keep-alive', 'Cache-Control': 'no-cache, no-store, must-revalidate, max-age=0', 'Expires': 'Thu, 15 May 2025 11:41:22 GMT', 'Vary': 'Origin', 'Request-Context': 'appId=cid-v1:13ae8764-9e17-4375-8db5-90bfd2569e15')>

I have been in contact with Zaptec, and they says i am not blocked. It is escalated to second line support now.

Do you have a node-red flow for this, actually working??

tir. 13. mai 2025, 22:46 skrev Svein Seldal @.***>:

sveinse left a comment (custom-components/zaptec#175) https://github.com/custom-components/zaptec/issues/175#issuecomment-2877901330

I have the same system where I authenticate with rfid, but I use the available current to prevent it from actually starting the charging.

The reason it fails is because the Zaptec cloud is rejecting the command, so in itself there is little we can do about that. Are you only sending stop charging commands when the car is actually charging, or are you always sending stop charging even if the car is not charging? Because Zaptec cloud might not like getting stop commands for something that's not started.

— Reply to this email directly, view it on GitHub https://github.com/custom-components/zaptec/issues/175#issuecomment-2877901330, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARNRM7OYB5FOYLKDMLH2H2326JK2NAVCNFSM6AAAAAB5A57HT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNZXHEYDCMZTGA . You are receiving this because you authored the thread.Message ID: @.***>

[sveinse]

This last comment is similar to issue #166 . I suggest we keep the discussion of issues with the current limit function there. Thanks.

Please also note that we've received feedback from Zaptec that doing "stop" commands when not charging is not permitted. Please see https://github.com/custom-components/zaptec/issues/176#issuecomment-2879756278

[sveinse]

How can we help with this issue? If the issue has been fixed or no longer relevant, I'd like to close the issue.

[sveinse]

Closing the issue from inactivity.