search

albertogeniola / MerossIot

Async Python library for controlling Meross devices
https://albertogeniola.github.io/MerossIot/
MIT License
463 stars 85 forks source link

https://iotx-eu.meross.com returns error 404 #363

Closed MaierJuerg closed 1 month ago

MaierJuerg commented 2 months ago

Beginning early March 2024 trying to connect with https://iotx-eu.meross.com returns error 404. The Android Meross App still shows my devices, status and consumptions. Has this service been terminated? Any other ways to connect through the python library?

MaierJuerg commented 2 months ago

Customer service of Meross state, they have not made any changes to their servers. Any idea what could be the reason I can not connect any more?

sebampuero commented 2 months ago

Also experiencing this

MaierJuerg commented 2 months ago

I think l will dispose of these meross Devices with the dependecy of the shitty Cloud solutions and will install a cheap tasmota solution with my own mqtt server

Sebastian @.***> schrieb am Di., 19. März 2024, 19:16:

Also experiencing this

— Reply to this email directly, view it on GitHub https://github.com/albertogeniola/MerossIot/issues/363#issuecomment-2007843181, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGXJ63PVMDO6EERW4OBVXBDYZB6IFAVCNFSM6AAAAABEN56AOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBXHA2DGMJYGE . You are receiving this because you authored the thread.Message ID: @.***>

albertogeniola commented 2 months ago

Beginning early March 2024 trying to connect with https://iotx-eu.meross.com returns error 404. The Android Meross App still shows my devices, status and consumptions. Has this service been terminated? Any other ways to connect through the python library?

Hi! I believe you are hitting 404 because you are fetching an invalid URL via API. Path / on https://iotx-eu.meross.com is invalid. You should point to valid API paths. For instance: https://iotx-eu.meross.com/v1/Auth/signIn where the path is /v1/Auth/signIn.

The library has been working flawlessly for me. If you still are experiencing the issue, can you please post the error logs provided by the library? Thanks.

MaierJuerg commented 2 months ago

Hi Alberto Thanks for your reply. This is what I try but I do not get connected:

Setup the HTTP client API from user-password

try:
    http_api_client = await MerossHttpClient.async_from_user_password(
        email=EMAIL,
        password=MEROSS,
        #api_base_url="https://iotx-eu.meross.com")
        api_base_url="https://iotx-eu.meross.com/v1/Auth/signIn")
    config.merossConnected = True
except Exception as e:
    config.logMeross(f"exception http_api_client: {e}")
    config.merossConnected = False

2024-03-30 10:02:37 exception http_api_client: Failed request to API. Response code: 404

Regards Jürg

Am Do., 28. März 2024 um 19:21 Uhr schrieb Alberto Geniola < @.***>:

Beginning early March 2024 trying to connect with https://iotx-eu.meross.com returns error 404. The Android Meross App still shows my devices, status and consumptions. Has this service been terminated? Any other ways to connect through the python library?

Hi! I believe you are hitting 404 because you are fetching an invalid URL via API. Path / on https://iotx-eu.meross.com is invalid. You should point to valid API paths. For instance: https://iotx-eu.meross.com/v1/Auth/signIn where the path is /v1/Auth/signIn.

The library has been working flawlessly for me. If you still are experiencing the issue, can you please post the error logs provided by the library? Thanks.

— Reply to this email directly, view it on GitHub https://github.com/albertogeniola/MerossIot/issues/363#issuecomment-2025843002, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGXJ63LUIKZLRLCGC2FQQRLY2RGRFAVCNFSM6AAAAABEN56AOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVHA2DGMBQGI . You are receiving this because you authored the thread.Message ID: @.***>

-- Jürg Maier Trungerstrasse 33 9543 St. Margarethen Schweiz @.***

albertogeniola commented 2 months ago

Hi @MaierJuerg ,

the latest version of thje library does not show that... Quite the opposite: handles the error and redirect to the correct domain reported by the API:

image

image

Which version of the library are you using? Can you please upgrade to the latest stable (0.4.6.2) and check if that still occurs?

unixtall commented 2 months ago

I have problems too.

`INFO:Login successful against https://iotx-eu.meross.com ERROR:Received non-ok API status code: INVALID_PARAMETER. Failed request to API. Response was: {'apiStatus': 20101, 'sysStatus': 0, 'info': 'Invalid parameter', 'timestamp': 1711990706, 'data': {}} Traceback (most recent call last): File "C:\Users\unixtall\Documents\Trabajo\pythonProject\prueba.py", line 57, in loop.run_until_complete(main()) File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.11_3.11.2288.0_x64__qbz5n2kfra8p0\Lib\asyncio\base_events.py", line 654, in run_until_complete return future.result() ^^^^^^^^^^^^^^^ File "C:\Users\unixtall\Documents\Trabajo\pythonProject\prueba.py", line 17, in main http_api_client = await MerossHttpClient.async_from_user_password(email=EMAIL, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\unixtall\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\meross_iot\http_api.py", line 130, in async_from_user_password await cls._async_log(creds=creds, File "C:\Users\unixtall\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\meross_iot\http_api.py", line 458, in _async_log return await cls._async_authenticated_post(url=url, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\unixtall\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.11_qbz5n2kfra8p0\LocalCache\local-packages\Python311\site-packages\meross_iot\http_api.py", line 388, in _async_authenticated_post raise HttpApiError(error) meross_iot.model.http.exception.HttpApiError: ErrorCodes.INVALID_PARAMETER

Process finished with exit code 1 `

The method i am using is this: http_api_client = await MerossHttpClient.async_from_user_password(email=EMAIL, password=PASSWORD, api_base_url="https://iotx-eu.meross.com")

MaierJuerg commented 2 months ago

Thanks Alberto updating to your latest version works for me now. In the meantime I have purchased tuya switches and can control them with my python program using requests. The tinytuya app did not work for me as it did not find devices in different wlan areas. Took a while however to make them work... Opens a chance to control more stuff in my house :) Regards Juerg

Am Sa., 30. März 2024 um 18:17 Uhr schrieb Alberto Geniola < @.***>:

Hi @MaierJuerg https://github.com/MaierJuerg ,

the latest version of thje library does not show that... Quite the opposite: handles the error and redirect to the correct domain reported by the API:

image.png (view on web) https://github.com/albertogeniola/MerossIot/assets/4648843/f84f752d-5ef4-433b-89bd-671124ddca47

image.png (view on web) https://github.com/albertogeniola/MerossIot/assets/4648843/7ab0465e-129b-45ca-be02-57eebc6eeefc

Which version of the library are you using? Can you please upgrade to the latest stable (0.4.6.2) and check if that still occurs?

— Reply to this email directly, view it on GitHub https://github.com/albertogeniola/MerossIot/issues/363#issuecomment-2028317644, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGXJ63NSDUILLHZKVCSI2IDY23QTPAVCNFSM6AAAAABEN56AOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYGMYTONRUGQ . You are receiving this because you were mentioned.Message ID: @.***>

-- Jürg Maier Trungerstrasse 33 9543 St. Margarethen Schweiz @.***