hello, first : great work!
But I have issues to turn on the heat or the defrosting : 2 sec after I put it On it goes off (the unlock features does not have the problem)
so i suppose it s better to wait your next version
hello, first : great work!
But I have issues to turn on the heat or the defrosting : 2 sec after I put it On it goes off (the unlock features does not have the problem)
so i suppose it s better to wait your next version
Can you provide your logs? Better open an issue on Github (Issues ¡ ad-ha/mg-saic-ha ¡ GitHub) and I will have a look.
It might be something with your specific model, so it might be worth to check whatâs happening.
Cheers
Many thanks.
I have just restarted HA after a HACS installation that required it.
The MG/SAIC integration failed to start up again.
I went into the iSmart app and saved the secondary account (without changing anything) then reloaded this integration and it worked.
A bit odd and inconvenient but, at least I can get it running after a restart now.
Anything I can do to figure out why itâs happening?
Also, am I the only on experiencing this?
Be good to hear from anyone using a secondary account.
Never mind this, i was just being âNot very brightâ
No worries. Glad you were able to sort it.
Hi everyone,
Just release a new 0.9.0 version with quite a few changes and improvements. More info here:
THIS UPDATE BRINGS SEVERAL BREAKING CHANGES
MAKE SURE TO CAREFULLY READ THE BELOW INFORMATION
All breaking changes are marked with
Removed AC Blowing Switch
Refactored Unique IDs for entities in:
This will cause you to now have old entities being replaced by new ones.
You will have to manually remove the old entities and rename the new ones (if you would like so)
Thank you all, once again, for your support and patience with the development of this integration.
I hope that this version is able to solve a lot of the issues reported and addresses some of the needs/improvements identified by all of you. I tried on this occasion to bring forward everything that was outstanding in issues and also make some improvements to the whole integration, which I hope translates into a easier usage for all of you.
If you have any issues or improvement suggestions, do not hesitate to provide your feedback here: ISSUES
Thanks again for working on this integration. Finally made the âcommitted changeâ today and cleared up the old SAIC containers of my box and fully using this HACS integration now and its great.
Thanks a lot. Glad it is working fine for you
Hi @VaReTaS very good work!
Thanks, and well done.
There doesnât seem to be much discussion here about automations.
What Iâm finding is that âUpdate Vehicle Dataâ works OK.
But both âLock Vehicleâ and âUnlock Vehicleâ do not.
However if I request lock and unlock from the dashboard these operations work OK.
(I havenât tried any others automation actions.)
The logs seem to confirm this.
This is with an MG4.
Hi @gwatuk
Thabks for the comments.
So, both Actions and Buttons use the same logic, so it should not be an issue.
However, I may have a look in case I missed something. However, before setting up switches and buttons I tried all Actions/Srvices and they were working fine.
If you have the logs those would be handy to try to spot any issue.
Cheers
Hi
Just installed the latest update for HA and rebooted.
Now i get this :
Setup failed for custom integration âmg_saicâ: Requirements for mg_saic not found: [âsaic-ismart-client-ng==0.6.0â].
Was working prior to reboot and did try another reboot but still comes up like this and now everything is âunavailableâ
Hi,
Check solution here: [ISSUE] Integration cannot be loaded because of unsatisfied dependencies ¡ Issue #104 ¡ ad-ha/mg-saic-ha ¡ GitHub
Cheers
Thanks, that made it work again
Glad it helped. Cheers
Hi
Just updated to 2025.2.1 and the problem came back after HA restarted.
Ran the 4 commands in SSH again and restarted HA and it started working again.
Is it normal to have to do this every time i update HA ?
Hi,
It should not. I already created a pull on the API to revise those dependencies that are causing the issue.
When that gets merged, the issue must be sorted.