core
core copied to clipboard
home-assistant
Latest fix to IAquakink (2023.2.4) has not resolved issue
The problem
Logger: homeassistant.components.iaqualink Source: components/iaqualink/init.py:151 Integration: Jandy iAqualink (documentation, issues) First occurred: 11:54:33 AM (189 occurrences) Last logged: 12:41:33 PM
Failed to refresh system XXXXXXXXXXX state: <ConnectionTerminated error_code:ErrorCodes.NO_ERROR, last_stream_id:961, additional_data:None>
(actual system ID has been replaced with "X"s.)
What version of Home Assistant Core has the issue?
2023.2.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Logger: homeassistant.components.websocket_api.http.connection
Source: components/iaqualink/utils.py:14
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 12:27:54 PM (1 occurrences)
Last logged: 12:27:54 PM
[139775231935392] <ConnectionTerminated error_code:ErrorCodes.NO_ERROR, last_stream_id:961, additional_data:None>
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/h2/connection.py", line 224, in process_input
func, target_state = self._transitions[(self.state, input_)]
KeyError: (<ConnectionState.CLOSED: 3>, <ConnectionInputs.SEND_HEADERS: 0>)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/http2.py", line 106, in handle_async_request
await self._send_request_headers(request=request, stream_id=stream_id)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/http2.py", line 203, in _send_request_headers
self._h2_state.send_headers(stream_id, headers, end_stream=end_stream)
File "/usr/local/lib/python3.10/site-packages/h2/connection.py", line 766, in send_headers
self.state_machine.process_input(ConnectionInputs.SEND_HEADERS)
File "/usr/local/lib/python3.10/site-packages/h2/connection.py", line 228, in process_input
raise ProtocolError(
h2.exceptions.ProtocolError: Invalid input ConnectionInputs.SEND_HEADERS in state ConnectionState.CLOSED
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/httpx/_transports/default.py", line 60, in map_httpcore_exceptions
yield
File "/usr/local/lib/python3.10/site-packages/httpx/_transports/default.py", line 353, in handle_async_request
resp = await self._pool.handle_async_request(req)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 253, in handle_async_request
raise exc
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 237, in handle_async_request
response = await connection.handle_async_request(request)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/connection.py", line 90, in handle_async_request
return await self._connection.handle_async_request(request)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/http2.py", line 139, in handle_async_request
raise RemoteProtocolError(self._connection_error_event)
httpcore.RemoteProtocolError: <ConnectionTerminated error_code:ErrorCodes.NO_ERROR, last_stream_id:961, additional_data:None>
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 200, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1787, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1824, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 680, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 968, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 720, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 571, in async_handle_light_on_service
await light.async_turn_on(**filter_turn_on_params(light, params))
File "/usr/src/homeassistant/homeassistant/components/switch_as_x/entity.py", line 80, in async_turn_on
await self.hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1787, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1824, in _execute_service
await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 680, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 968, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 720, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/iaqualink/__init__.py", line 192, in wrapper
await func(self, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/components/iaqualink/switch.py", line 59, in async_turn_on
await await_or_reraise(self.dev.turn_on())
File "/usr/src/homeassistant/homeassistant/components/iaqualink/utils.py", line 14, in await_or_reraise
await awaitable
File "/usr/local/lib/python3.10/site-packages/iaqualink/systems/iaqua/device.py", line 130, in turn_on
await self._toggle()
File "/usr/local/lib/python3.10/site-packages/iaqualink/systems/iaqua/device.py", line 147, in _toggle
await self.system.set_aux(self.data["aux"])
File "/usr/local/lib/python3.10/site-packages/iaqualink/systems/iaqua/system.py", line 174, in set_aux
r = await self._send_session_request(aux)
File "/usr/local/lib/python3.10/site-packages/iaqualink/systems/iaqua/system.py", line 72, in _send_session_request
return await self.aqualink.send_request(url)
File "/usr/local/lib/python3.10/site-packages/iaqualink/client.py", line 98, in send_request
r = await self._client.request(
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1533, in request
return await self.send(request, auth=auth, follow_redirects=follow_redirects)
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1620, in send
response = await self._send_handling_auth(
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1648, in _send_handling_auth
response = await self._send_handling_redirects(
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1685, in _send_handling_redirects
response = await self._send_single_request(request)
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1722, in _send_single_request
response = await transport.handle_async_request(request)
File "/usr/local/lib/python3.10/site-packages/httpx/_transports/default.py", line 352, in handle_async_request
with map_httpcore_exceptions():
File "/usr/local/lib/python3.10/contextlib.py", line 153, in __exit__
self.gen.throw(typ, value, traceback)
File "/usr/local/lib/python3.10/site-packages/httpx/_transports/default.py", line 77, in map_httpcore_exceptions
raise mapped_exc(message) from exc
httpx.RemoteProtocolError: <ConnectionTerminated error_code:ErrorCodes.NO_ERROR, last_stream_id:961, additional_data:None>
Additional information
No response
Hey there @flz, mind taking a look at this issue as it has been labeled with an integration (iaqualink) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of iaqualink can trigger bot actions by commenting:
-
@home-assistant closeCloses the issue. -
@home-assistant rename Awesome new titleChange the title of the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign iaqualinkRemoves the current integration label and assignees on the issue, add the integration domain after the command.
(message by CodeOwnersMention)
iaqualink documentation iaqualink source (message by IssueLinks)
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
Looks like I missed one. Will try and set a fix later.
Thanks @flz ... very much appreciate your efforts to support this integration..
Highly valued integration in our house. Looking forward to the fix and thanks again.
Thank you @flz! Really appreciate you all of the work you do to maintain this.
Just want to say that I'm thankful for everyone here. I did the update earlier and found it wasn't working, too - and then here we are, a fix already in the works. Amazing.
BTW, it works for a while upon restart of HomeAssistant, but within a few hours loses synch with the iaqualink cloud due to error. So, you may want to test for a day or so, and ensure that throughout your test period you can control pool pump or pool lights. My personal experience is that after some time it stops responding and then see errors in the log.
Yes - I believe got same issue here. Thank you for your efforts!
Yeah, I'm finding the same error. If I reboot Home Assistant, the iAqualink component works fine, but then stops working within a day or so.
When I try to toggle something like the Pool Light, which I have as part of a daily automation for my yard lighting...
Here's the error I get inside the Home Assistant UI.
Sending some more love to the team! This integration is core to my HA setup, so thank you for your efforts!
Same symptoms.
So, I am curious. Overall, is this an issue with the Jandy API, the implementation within python, or what?
Thank you!
Sent from my iPad
On Feb 16, 2023, at 12:10 PM, Noodleheader @.***> wrote:
Sending some more love to the team! This integration is core to my HA setup, so thank you for your efforts!
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/88033#issuecomment-1433425079, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARBHCMFU3ZA7FY4EANFE6V3WXZNQTANCNFSM6AAAAAAU2XPYHU. You are receiving this because you commented.Message ID: @.***>
For the record, updated yesterday to 2023.2.5 and still no dice. I know @flz didn't say the last fix was uploaded, but I did see a comment in the release notes. Just like @devMarcus, still experiencing same symptoms.
Definitely - Thank you….
Anything you need from us? Chocolates, tea, doritos? Developers like doritos…
Sent from my iPad
On Feb 16, 2023, at 5:28 PM, Michael York @.***> wrote:
Thanks for your help @flzhttps://github.com/flz! 🙏
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/88033#issuecomment-1433800359, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARBHCMBTEIXIPKU3FB667G3WX2SXFANCNFSM6AAAAAAU2XPYHU. You are receiving this because you were mentioned.Message ID: @.***>
Same symptoms. So, I am curious. Overall, is this an issue with the Jandy API, the implementation within python, or what?
I am interested to know this too. For me, when the integration fails, reloading the integration just puts it in an unavailable state and subsequent attempts to reload the integration cause a UI popup saying "Restart Home Assistant to finish reloading this integration". So the entire Home Assistant needs to be restarted to get the integration back (until it fails again).
I also updated to 2023.2.5 and am still getting the error. A reboot fixes it for a little while, but for me it stops working a couple of hours later.
Just wanted to note something to the group that I just realized regarding automations after scratching my head for a few days- I have an automation that turns off my pool lights at 10:15pm every day, and the action to turn off the pool lights is ~#25 in a list of ~30 actions. So once the automation reached the pool lights and errored out, the remaining actions did not trigger. For now I have moved the pool light action to the end of the list.
Guys,
I do not have any automations or anything, and just let it sit and it will error out. My hunch is that it looses its connection to the cloud. Not 100% certain. If needed I can troubleshoot to the nth degree. But have not done that as it seemed that @FLZ was working on a fix.
Sent from my iPhone
On Feb 19, 2023, at 12:14 PM, smshapiro85 @.***> wrote:
Just wanted to note something to the group that I just realized regarding automations after scratching my head for a few days- I have an automation that turns off my pool lights at 10:15pm every day, and the action to turn off the pool lights is ~#25https://github.com/home-assistant/core/pull/25 in a list of ~30 actions. So once the automation reached the pool lights and errored out, the remaining actions did not trigger. For now I have moved the pool light action to the end of the list.
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/88033#issuecomment-1436041804, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARBHCMBDCTYTUD6P5XH2CWDWYJIFNANCNFSM6AAAAAAU2XPYHU. You are receiving this because you were mentioned.Message ID: @.***>
My limited analysis is that this is a result of an authentication issue. Jandy used to keep alive for a ridiculous amount of time the auth token, and now it expires within what I am guessing to be 12 or so hours. Can’t remember how long I had my C# code running. It might have been as little as 3-4 hours.
This change on the cloud infrastructure is a step towards better security! Guessing that the integration does not attempt to get a new token – or that it chokes when the cloud infrastructure gives it {"status":"Service"},{"response":"Error"}.
Thinking that all you need to do is re-login and authenticate, and use the new auth token for all subsequent requests until the cloud requires re-authentication again?
Am I on the right track? I’ll have to use network analysis tools to confirm this hypothesis.
I noticed after enable debug logging that the integration was calling the aqualink API every 5 seconds. Even after just restarting HA, i would see that every few calls to the API would fail and i wondered if it was trying to call before the prior call had completed. Checking in const.py i see that the update interval is set to 15 seconds so it shouldn't update every 5 seconds. I manually changed the update interval in init.py and i'm not seeing the random connection errors. I'm going to let it run like this for the next 24 hours and see if still has an issue.
Well after just an hour, its not working again so the update interval isn't the issue. I did managed to hit the login REST API and in the response object, under the "UserPoolOAuth" section, along with the Access Token, there's a key called "ExpiresIn" and the value is set to 3600. Assuming this is likely seconds, that equates to 1 hour at which point the token expires. So it appears the fix is to reauthenticate every hour to refresh the access token.
Yep - that is what I thought.. Auth issue and that Jandy changed the token expiration to a shorter time where before it was a very long time. I would think that someone with python skills should be able to fix this - at least on a temporary basis to complete the proof of concept.
Curious - where are these files CONST.PY, etc located on the device?
Sent from my iPad
On Feb 20, 2023, at 2:44 PM, rcork @.***> wrote:
Well after just an hour, its not working again so the update interval isn't the issue. I did managed to hit the login REST API and in the response object, under the "UserPoolOAuth" section, along with the Access Token, there's a key called "ExpiresIn" and the value is set to 3600. Assuming this is likely seconds, that equates to 1 hour at which point the token expires. So it appears the fix is to reauthenticate every hour to refresh the access token.
— Reply to this email directly, view it on GitHubhttps://github.com/home-assistant/core/issues/88033#issuecomment-1437481273, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARBHCMHGYMIXPQPJ5JNNQLTWYPCQBANCNFSM6AAAAAAU2XPYHU. You are receiving this because you were mentioned.Message ID: @.***>
I'm running in a docker image so it might be different but i found them under /usr/src/homeassistant/homeassistant/components/iaqualink
I'm editing the code directly to try to log back in when it gets the connection error. If that works i'll post back my results. I'm not great at python but know enough to hack my way around.
The integration source code is here: https://github.com/home-assistant/core/tree/dev/homeassistant/components/iaqualink
The integration offloads the actual work for talking to the iaqualink API to this library: https://github.com/flz/iaqualink-py
Interestingly there is an open PR for refreshing the access token: https://github.com/flz/iaqualink-py/pull/19 But this was opened Feb '22, mentions an 8 hour expiry, and it's unclear if the PR works as intended.
@rcork if it's easier you can create your own custom component - a copy of the existing iaqualink - using steps here: https://github.com/home-assistant/core/issues/82336#issuecomment-1383011017
I'm not sure if this was a change by Jandy or if it is the result of a change to use the httpx library. @flz mentioned something about that in some of the previous attempts to fix this.
In the mean time, I've been able to mitigate this by using an automation to have HA reload the configuration once an hour.
alias: Reload Jandy iAqualink every hour
description: ""
trigger:
- platform: time_pattern
hours: "*"
minutes: "10"
seconds: "0"
condition: []
action:
- service: homeassistant.reload_config_entry
data:
entry_id: 78756025d03c7b811db07b8be7a9ed12
mode: single
I'm not sure if the config_entry_id is the same for everyone but you can find yours here.
That doesn't do the trick for me. When I reload the config entry all the iAqualink functions become unavailable in lovelace.
From: Greg Doerr @.> Sent: Monday, February 20, 2023 3:57 PM To: home-assistant/core @.> Cc: ffpllc @.>; Comment @.> Subject: Re: [home-assistant/core] Latest fix to IAquakink (2023.2.4) has not resolved issue (Issue #88033)
I'm not sure if this was a change by Jandy or if it is the result of a change to use the httpx library. @flzhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fflz&data=05%7C01%7C%7C4d5f16a1ff174f9497ef08db13852393%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125234785438274%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=w3vFbXBJr3Xod1CxITHw3jeDFQ%2Fd6l%2Bbh4iziefI%2B6Q%3D&reserved=0 mentioned something about that in some of the previous attempts to fix this.
In the mean time, I've been able to mitigate this by have HA reload the configuration once an hour. `alias: Reload Jandy iAqualink every hour description: "" trigger:
- platform: time_pattern hours: "*" minutes: "10" seconds: "0" condition: [] action:
- service: homeassistant.reload_config_entry data: entry_id: 78756025d03c7b811db07b8be7a9ed12 mode: single `
I'm not sure if the config_entry_id is the same for everyone but you can find yours herehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.home-assistant.io%2Ft%2Fhow-to-find-config-entry-id-to-reload-via-service-call%2F451053%2F2&data=05%7C01%7C%7C4d5f16a1ff174f9497ef08db13852393%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125234785438274%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UsS56k02jVjNYo86l9qykjENR4TyE18Un2BYJ2fo4AQ%3D&reserved=0.
— Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhome-assistant%2Fcore%2Fissues%2F88033%23issuecomment-1437535569&data=05%7C01%7C%7C4d5f16a1ff174f9497ef08db13852393%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125234785594512%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cdYfud%2BurO4d4CSW0XjkS73wIFXtNqYBhPxtkjVMLfI%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXQVQUHSFA267OLBCNV6OQTWYPLFFANCNFSM6AAAAAAU2XPYHU&data=05%7C01%7C%7C4d5f16a1ff174f9497ef08db13852393%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125234785594512%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ty0yjc2Bw5j9PKayCcL2e0y5xs%2B3W%2FvxJr5K85BVw5s%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>
I'm not sure if this was a change by Jandy or if it is the result of a change to use the httpx library. @flz mentioned something about that in some of the previous attempts to fix this.
In the mean time, I've been able to mitigate this by using an automation to have HA reload the configuration once an hour.
alias: Reload Jandy iAqualink every hour description: "" trigger: - platform: time_pattern hours: "*" minutes: "10" seconds: "0" condition: [] action: - service: homeassistant.reload_config_entry data: entry_id: 78756025d03c7b811db07b8be7a9ed12 mode: singleI'm not sure if the config_entry_id is the same for everyone but you can find yours here.
Thank you I am going to try this out as well. My config_entry_id is different FWIW.
Also it looks like you have it set to refresh every 10 minutes? I am not really familiar with automations so maybe the "*" in the hours field means something different.
That doesn't do the trick for me. When I reload the config entry all the iAqualink functions become unavailable in lovelace. … ________________________________ From: Greg Doerr @.> Sent: Monday, February 20, 2023 3:57 PM To: home-assistant/core @.> Cc: ffpllc @.>; Comment @.> Subject: Re: [home-assistant/core] Latest fix to IAquakink (2023.2.4) has not resolved issue (Issue #88033) I'm not sure if this was a change by Jandy or if it is the result of a change to use the httpx library. @flzhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fflz&data=05%7C01%7C%7C4d5f16a1ff174f9497ef08db13852393%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125234785438274%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=w3vFbXBJr3Xod1CxITHw3jeDFQ%2Fd6l%2Bbh4iziefI%2B6Q%3D&reserved=0 mentioned something about that in some of the previous attempts to fix this. In the mean time, I've been able to mitigate this by have HA reload the configuration once an hour.
alias: Reload Jandy iAqualink every hour description: "" trigger: * platform: time_pattern hours: "*" minutes: "10" seconds: "0" condition: [] action: * service: homeassistant.reload_config_entry data: entry_id: 78756025d03c7b811db07b8be7a9ed12 mode: singleI'm not sure if the config_entry_id is the same for everyone but you can find yours herehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcommunity.home-assistant.io%2Ft%2Fhow-to-find-config-entry-id-to-reload-via-service-call%2F451053%2F2&data=05%7C01%7C%7C4d5f16a1ff174f9497ef08db13852393%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125234785438274%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=UsS56k02jVjNYo86l9qykjENR4TyE18Un2BYJ2fo4AQ%3D&reserved=0. — Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhome-assistant%2Fcore%2Fissues%2F88033%23issuecomment-1437535569&data=05%7C01%7C%7C4d5f16a1ff174f9497ef08db13852393%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125234785594512%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=cdYfud%2BurO4d4CSW0XjkS73wIFXtNqYBhPxtkjVMLfI%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAXQVQUHSFA267OLBCNV6OQTWYPLFFANCNFSM6AAAAAAU2XPYHU&data=05%7C01%7C%7C4d5f16a1ff174f9497ef08db13852393%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638125234785594512%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ty0yjc2Bw5j9PKayCcL2e0y5xs%2B3W%2FvxJr5K85BVw5s%3D&reserved=0. You are receiving this because you commented.Message ID: @.***>
Yea unfortunately I am seeing the same thing.
You might try calling the config reload service manually through "Dev Tools" when the iAqualink service isn't working. If that works, then an automation will work. If that doesn't work, then I'm at a loss. It does work for me.
For the time_pattern, minutes: 10 means run when the time unit, minutes in this case, equals 10. Asterisk matches all hours. You can also omit the hours reference which is the same thing. minutes: /10 would match every 10 minutes