-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ISSUE] After idle status, start charging not possible #100
Comments
Hi @jeroen84s Do you have any logs on this? Seems odd that it does not work. This morning I had my car on Idle and was able to start the AC without issues. If you have logs it will be helpful, but none of those actions are linked together in anyway. |
Deze fout is ontstaan door een aangepaste integratie. Logger: custom_components.mg_saic Error fetching vehicle status: Vehicle status is None.. Retrying in 15 seconds... (Attempt 1/5) Deze fout is ontstaan door een aangepaste integratie. Logger: custom_components.mg_saic Vehicle status returned None. Deze fout is ontstaan door een aangepaste integratie. Logger: custom_components.mg_saic Error retrieving vehicle status: return code: 4, message: The remote control instruction failed, please try again later., event_id: 1364183879 Deze fout is ontstaan door een aangepaste integratie. Logger: custom_components.mg_saic API call failed: return code: 4, message: The remote control instruction failed, please try again later., event_id: 1364183879 Logger: homeassistant.components.binary_sensor Setup of binary_sensor platform mg_saic is taking over 10 seconds. |
Above are the log files. Maybe it is not linked, but it is a coincidence that this problem occurs 1 hour after stopping loading |
Hi @jeroen84s Thanks for the logs. As you may see on the messages received, that's an issue on the API side, not getting the data from the vehicle first ( Those issues are both on MG end and I cannot do much about it. From my experience, when that happens, just try again until you are able to get the message properly sent/received to the vehicle. |
Ok... But why do other switches and functions work fine, and the charging switch is the only one that not working anymore. This talks to the same API |
Can you please confirm which switch does not work? You mentioned AC on the issue title, but you are now mentioning the charging switch. Edit. I believe I got the idea. You are referring to AC (alternate current) is that it? So this switch is only available if there is "charging data". If the API returns empty data for the "charging" the switch does not become available. MG API is a bit unstable these days, so I would suggest that you try to reload the integration and see if the data gets available and so will be the switch. There is nothing else on the code stopping the switch from being available. |
I understand the confusion. I mean the charging switch (AC, alternating current, and not the Air Conditioning). If possible I changed the title. I try tomorrow again and let you know |
Clear now. Thanks Sometimes the API fails to send charging data, and if that happens the integration keeps going with the latest values. Although, the charging switch is dependent on having that data, so it might be available for BEV/PHEV vehicles but not for HEV's, for example. Please try again and check the logs to see the response from the integration and the API, so I may understand better what might be happening. |
Below log files try I diferent situations:
But now, I try also the original MG app for charging.
I have a MG ZS EV model 2021-2024 Let me know if you need more information 2025-02-02 09:33:18.534 ERROR (MainThread) [custom_components.mg_saic] API call failed: return code: 8, message: The request timed out. Please try again later.(253), event_id: 1566644667 |
Thanks @jeroen84s I will have a look. Seems like the command is successful and that the vehicle starts the charge, but stays at "Idle" (bmsChrgSts=5)
On the AC not starting, I see this:
Cheers |
Hi, for the AC climate its possible, because the boot was open(i try this for the first check). For the charging was all closed, and its not starting realy, I check this to the light from my car. After few minuts you see this also back in Home Assistant and see the message Idle. |
Fyi: the blue light glows up for receive the charging message, and de green light is realy charging. And the green light is not glow up |
That's what I was saying. The car stays in idle rather than start charge. I really don't see the issue yet, but let me have a look. Were you able to start the charging ever from the Integration? |
sure, that charging integration works fine until the moment that charging is stopped with the integration and shows the idle status. From that moment i can't start again. |
If you change the switch charging before showing the idle status its works always properly |
Below is a working situation from the integration 2025-02-02 15:25:36.749 DEBUG (MainThread) [custom_components.mg_saic] No changes detected in monitored keys or charging status. |
Home Assistant Version
2025.01.04
MG/SAIC Integration Version
0.9.1
Installation Method
HACS
Did you check for existing issues?
Did you enable debug logging before and are ready to post logs?
Describe the Issue
After Idle state I can not restarting the AC loading from the intergration. The car receive the message (i see this on the front light indicators), the only solution that solved: reconnect the AC plug.
MG app (android) works fine
Logs
Additional Context
No response
The text was updated successfully, but these errors were encountered: