Aseko Pool Failed setup, will retry: 403

[falinka]

The problem

Few days ago, aseko pool integration stopped working. I have tried with reconfiguration, removal, adding, but no luck. In the logs, in returns the following error: Failed setup, will retry: 403, message='Forbidden', url='https://graphql.acs.prod.aseko.cloud/graphql' It is possible that something was changed server-side, but there were no new updates for the application, that might indicate some modifications.

What version of Home Assistant Core has the issue?

core-2024.10.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Aseko Pool Live

Link to integration documentation on our website

https://www.home-assistant.io/integrations/aseko_pool_live

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.aseko_pool_live.coordinator
Source: helpers/update_coordinator.py:354
integration: Aseko Pool Live (documentation, issues)
First occurred: 30 October 2024 at 21:54:38 (738 occurrences)
Last logged: 14:13:37

Unexpected error fetching aseko_pool_live data
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/gql/transport/aiohttp.py", line 331, in execute
    result = await resp.json(content_type=None)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1260, in json
    return loads(stripped.decode(encoding))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/gql/transport/aiohttp.py", line 319, in raise_response_error
    resp.raise_for_status()
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1121, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 403, message='Forbidden', url='https://graphql.acs.prod.aseko.cloud/graphql'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 354, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/aseko_pool_live/coordinator.py", line 34, in _async_update_data
    units = await self._aseko.get_units()
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aioaseko/aseko.py", line 246, in get_units
    units = await self.get_all_units()
            ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aioaseko/aseko.py", line 136, in get_all_units
    ds = await self._schema()
         ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aioaseko/aseko.py", line 110, in _schema
    async with self._client() as session:
  File "/usr/local/lib/python3.12/site-packages/gql/client.py", line 814, in __aenter__
    return await self.connect_async()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/gql/client.py", line 795, in connect_async
    await self.session.fetch_schema()
  File "/usr/local/lib/python3.12/site-packages/gql/client.py", line 1661, in fetch_schema
    execution_result = await self.transport.execute(parse(introspection_query))
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/gql/transport/aiohttp.py", line 338, in execute
    await raise_response_error(resp, "Not a JSON answer")
  File "/usr/local/lib/python3.12/site-packages/gql/transport/aiohttp.py", line 321, in raise_response_error
    raise TransportServerError(str(e), e.status) from e
gql.transport.exceptions.TransportServerError: 403, message='Forbidden', url='https://graphql.acs.prod.aseko.cloud/graphql'

Additional information

No response

[home-assistant[bot]]

Hey there @milanmeu, mind taking a look at this issue as it has been labeled with an integration (aseko_pool_live) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `aseko_pool_live` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign aseko_pool_live` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

aseko_pool_live documentation aseko_pool_live source _{^{(message by IssueLinks)}}

[Datel01]

Hi same issue here as reported above. Appreciate looking into this and fix it. Thank you!

[maxdet]

Same issue here. Really appreciate your help @milanmeu!

[tokroth]

same issue here

[kernest]

+1

[crewo15]

+1 - since 2-3 weeks, at the same time, the app stopped working for 1-2 days, too.

[linussweden]

Same story for me here.

Also, I contacted Aseko a few weeks before they released their new App and new API (September 6 2024) regarding the posibility of the new API/App allowing remote control of their ASIN AQUA Salt system to witch they basicly replied that they would not allow this for security purpose as overdosing could lead to harm, and they also though most setpoint are of typ set and forget. But I would have loved to be able to control pump speed relays and pool heating setpoint from home assistant for example.

They also made this comment about Home Assistant in the same reply:

"Regarding Home Assistant, it will unfortunately no longer work with our new systems. It was not developed by Aseko but was instead an open-source solution. However, we plan to release official Home Assistant integration by the beginning of next year."

Thought it might be of interest here.

[marvin78]

Same issue

[falinka]

Same story for me here.

Also, I contacted Aseko a few weeks before they released their new App and new API (September 6 2024) regarding the posibility of the new API/App allowing remote control of their ASIN AQUA Salt system to witch they basicly replied that they would not allow this for security purpose as overdosing could lead to harm, and they also though most setpoint are of typ set and forget. But I would have loved to be able to control pump speed relays and pool heating setpoint from home assistant for example.

They also made this comment about Home Assistant in the same reply:

"Regarding Home Assistant, it will unfortunately no longer work with our new systems. It was not developed by Aseko but was instead an open-source solution. However, we plan to release official Home Assistant integration by the beginning of next year."

Thought it might be of interest here.

While i do agree with 'safety concerns', they could easily hide them from being able to be modified remotely. However, they could allow us to modify when filtration can start/stop, or, hear me - NTP sync. So i don't have to go down the shaft every time device starts time drifting :) They are selling their overprices "remote control" which is nothing but a fancy set of remotely controlled relays (using their own application, which also cannot be synced with the main solinator). But, let's wait and see what does this new promises for HA next year will bring.