Skip to content

Gateway settings for Australia #169

Description

@callifo

Hi,

Can anyone assist what I would need to use for Australian servers? Previously I could use '--saic-uri=https://tap-au.soimt.com' and this has worked well, but since upgrading and saic-uri being removed, I am unable to login.

If I use default settings, I get:
return code: 1000036, message: The account is not registered.

Changing the --saic-region to AU and saic-rest-uri with eu replaced with au, does not work.

Activity

  1. nanomad commented on Feb 17, 2024

    @nanomad
    Contributor

    Did australia get the "facelift" of the MG app? Or is it still using the classic "black" version?

    If so I fear you have to use the old gateway version. If you want to investigate more you can reach me out on telegram (@nanomad)

  2. bullantmm commented on Feb 17, 2024

    @bullantmm

    I believe I have the same issue... Any further details for configuring for Australia that you could provide would be great!

  3. nanomad commented on Feb 17, 2024

    @nanomad
    Contributor

    @bullantmm see if you can provide an answer to the question above

  4. jamescreer commented on Feb 17, 2024

    @jamescreer

    @nanomad at this point I believe AU and NZ are still using the classic "black" version.

    In the end I rolled back to the old gateway version and it worked again for me in Australia.
    IMG_8018

  5. bullantmm commented on Feb 17, 2024

    @bullantmm

    @jamescreer which version exactly are you using? 0.4.6 or one of the 0.5.x ones? Also are there any other region specific settings that you need for AUS other than --saic-uri=https://tap-au.soimt.com/
    ?

  6. callifo commented on Feb 17, 2024

    @callifo
    Author

    I'm using 0.4.6 according to the changelog in my directory. Was on holiday from the 14th Jan, so wasn't able to test any interim build since.

    For Aus, I did not use any other specific settings except --saic-uri=https://tap-au.soimt.com/

  7. jamescreer commented on Feb 17, 2024

    @jamescreer

    @bullantmm I'm also running 0.4.6 with https://tap-au.soimt.com as the saic-uri

  8. pinned this issue on Mar 4, 2024
  9. changed the title [-]SAIC settings for Australia[/-] [+]Gateway settings for Australia[/+] on Mar 4, 2024
  10. nanomad commented on Mar 4, 2024

    @nanomad
    Contributor

    Solution is to stay on the 0.4.6 release. Help is more than welcome to back port fixes from the current version

  11. Tonno87 commented on Mar 6, 2024

    @Tonno87
    Contributor

    @nanomad I will try it out in the next few days. I think it's a good chance to learn more about python and github.

  12. nanomad commented on Mar 10, 2024

    @nanomad
    Contributor

    @callifo @bullantmm off topic question... Can you confirm that you see negative values for the latitude in the API responses?

  13. 4 remaining items

  14. nanomad commented on May 5, 2024

    @nanomad
    Contributor

    @pmannk let's keep this to track the backporting to the legacy version

  15. hamishfagg commented on May 8, 2024

    @hamishfagg

    @bullantmm i havent sorry. As usual life has got in the way of me starting something new :P

  16. karter16 commented on Sep 18, 2024

    @karter16
    Contributor

    Hi - for what it's worth I've just been playing round with this. I don't know if it's newly available, but https://gateway-mg-au.soimt.com/api.app/v1/ is now available and I have been able to use the latest version of this gateway to connect to my ZS EV.

    SAIC_REST_URI: https://gateway-mg-au.soimt.com/api.app/v1/
    SAIC_REGION: au

    Hope this helps

  17. bullantmm commented on Sep 18, 2024

    @bullantmm

    Thanks @karter16! I just tried but looks like that URI is not available... Anyway it might mean we are getting closer!!

  18. karter16 commented on Sep 18, 2024

    @karter16
    Contributor

    Thanks @karter16! I just tried but looks like that URI is not available... Anyway it might mean we are getting closer!!

    Interesting - so if you try to go to the URI (https://gateway-mg-au.soimt.com/api.app/v1/) from your browser what do you get? I get a {"code":6,"message":"The service is not available,please try again later."} response, which means that the API exists and is responding. If I use the latest version of "saic-python-client-ng" and specify that URI I'm able to use my iSmart username and password to connect to and control the vehicle - I have this working now.

  19. bullantmm commented on Sep 24, 2024

    @bullantmm

    Thanks @karter16! I just tried but looks like that URI is not available... Anyway it might mean we are getting closer!!

    Interesting - so if you try to go to the URI (https://gateway-mg-au.soimt.com/api.app/v1/) from your browser what do you get? I get a {"code":6,"message":"The service is not available,please try again later."} response, which means that the API exists and is responding. If I use the latest version of "saic-python-client-ng" and specify that URI I'm able to use my iSmart username and password to connect to and control the vehicle - I have this working now.

    I gave it some more work and now it works... Just had to spend some time ensuring the variables were correct. Thanks for the notifying about the updated address!

  20. hamishfagg commented on Sep 26, 2024

    @hamishfagg

    Tried this and it doesn't seem to work in NZ. I get the 'service not available' at that endpoint, but when the gateway tried to log in it gets an "incorrect password" response (it's definitely the correct password).

    @karter16 how did you find that endpoint? I might need to capture my phone's traffic

  21. karter16 commented on Sep 26, 2024

    @karter16
    Contributor

    Hi @hamishfagg - fyi I am NZ-based so don't think it's a NZ vs AU thing.

    I believe that there is a separate known issue/limitation (here it is: #255) that your password can't contain special characters (needs to be only alpha-numeric) could it be that?

    You won't get that endpoint by monitoring traffic when using the iSmart app. the NZ/AU iSmart app still uses the old endpoint. I found this endpoint by taking the new EU endpoint and substituting "au" in the place of "eu". (on the basis that they've probably stood up the endpoint and just not migrated AU/NZ to the new app yet, which indeed seems to be the case).

  22. hamishfagg commented on Sep 26, 2024

    @hamishfagg

    My password is alpha-numeric, but you gave me an idea - turns out the app just ignores anything after the first 16 characters in your password (yay, security).

    So, I just needed to set the env var to the first 16 chars of my password and now it's working! Thanks!

  23. nanomad commented on Sep 27, 2024

    @nanomad
    Contributor

    Can you guys confirm it works for AU and NZ then? I'd love for you to update the README if so with the right settings to use

  24. bullantmm commented on Sep 27, 2024

    @bullantmm

    Can you guys confirm it works for AU and NZ then? I'd love for you to update the README if so with the right settings to use

    Definitely working for me in AU using

    SAIC_REST_URI: https://gateway-mg-au.soimt.com/api.app/v1/
    SAIC_REGION: au

  25. karter16 commented on Sep 27, 2024

    @karter16
    Contributor

    So that's confirmed - works in both AU and NZ using:

    SAIC_REST_URI: https://gateway-mg-au.soimt.com/api.app/v1/
    SAIC_REGION: au

  26. thiagofigueiro commented on Apr 1, 2025

    @thiagofigueiro

    Amazing news because version 0.4.6 just started throwing errors for me:

    saic-mqtt-gateway  | 2025-04-01 02:29:47,350 [  INFO  ] Updating charging status - __main__
    saic-mqtt-gateway  | 2025-04-01 02:31:19,093 [ ERROR  ] handle_vehicle loop failed during SAIC API call - __main__
    saic-mqtt-gateway  | Traceback (most recent call last):
    saic-mqtt-gateway  |   File "/usr/src/app/./mqtt_gateway.py", line 91, in handle_vehicle
    saic-mqtt-gateway  |     charge_status = self.update_charge_status()
    saic-mqtt-gateway  |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    saic-mqtt-gateway  |   File "/usr/src/app/./mqtt_gateway.py", line 118, in update_charge_status
    saic-mqtt-gateway  |     chrg_mgmt_data_rsp_msg = self.saic_api.get_charging_status_with_retry(self.vin_info)
    saic-mqtt-gateway  |                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    saic-mqtt-gateway  |   File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/saic_api.py", line 566, in get_charging_status_with_retry
    saic-mqtt-gateway  |     return self.handle_retry(self.get_charging_status, vin_info)
    saic-mqtt-gateway  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    saic-mqtt-gateway  |   File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/saic_api.py", line 457, in handle_retry
    saic-mqtt-gateway  |     return self.__handle_retry_with_app_data(func, vin_info=vin_info, max_retries=max_retries)
    saic-mqtt-gateway  |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    saic-mqtt-gateway  |   File "/usr/local/lib/python3.11/site-packages/saic_ismart_client/saic_api.py", line 499, in __handle_retry_with_app_data
    saic-mqtt-gateway  |     raise SaicApiException(f'API request failed after {iteration} retries{additional_info}')
    saic-mqtt-gateway  | saic_ismart_client.exceptions.SaicApiException: API request failed after 4 retries, error message: The remote control instruction failed, please try again later.
    
  27. locked and limited conversation to collaborators on Jun 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions