ReadTimeout Error while running automation #214
Comments
|
I faced the same 2 days ago in a script opening the watering valves of the gardena smart irrigation control: domain: switch |
|
Same for me! |
|
Same issue. Any news? |
|
Same issue for me in version 2024.6.4
|
|
Same issue. Effected device: Gardena smart Water Control Environment: Home Assistant version: 2024.6.4 |
|
Same here It´s a bit hit and miss. Sometimes the integration works without any problems and sometimes it does not ... |
|
To avoid missed opening/closing of watering valves I created (manual trick until the problem is hopefully solved) a slave script that only open/close valve (and allowed to fail) and a master script that keeps trying to open/close the valve until successful (by re-triggering the slave script). With 5 sec delay between each try. Until now worked with # of attempts between 1 and 3 ! But we still need a proper correction of the Gardena integration. |
|
Could you please share how you set up this workaround using a slave script? |
|
I use a single script for all valves, with a variable like 1,2,3,4 to open the valve 1,2,3,4 and 11,22,33,44 to close valve 1,2,3,4 Code for the slave script that "can" crash (duplicate for the other valves 2,3,4...) : alias: Centrale Gardena on-off
sequence:
- choose:
- conditions:
- condition: template
value_template: "{{ choix == 1 }}"
sequence:
- type: turn_on
device_id: 90eeefd7db817d489a7686dae7357730
entity_id: 30050e150937b6f9a9853c4f43a8097c
domain: switch
- conditions:
- condition: template
value_template: "{{ choix == 11 }}"
sequence:
- type: turn_off
device_id: 90eeefd7db817d489a7686dae7357730
entity_id: 30050e150937b6f9a9853c4f43a8097c
domain: switch
icon: mdi:waterThe master script looks like: alias: Centrale Gardena on-off Master
sequence:
- choose:
- conditions:
- condition: template
value_template: "{{ choixm == 1 }}"
sequence:
- repeat:
sequence:
- service: script.turn_on
target:
entity_id: script.centrale_gardena_on_off
data:
variables:
choix: 1
- delay:
hours: 0
minutes: 0
seconds: 5
milliseconds: 0
- if:
- condition: template
value_template: "{{ repeat.index >= 2 }}"
then:
- service: notify.mobile_app
metadata: {}
data:
message: choixm {{ choixm }} tentative {{ repeat.index }}
until:
- condition: or
conditions:
- condition: device
type: is_on
device_id: 90eeefd7db817d489a7686dae7357730
entity_id: 30050e150937b6f9a9853c4f43a8097c
domain: switch
- condition: template
value_template: "{{ repeat.index == 4 }}"
- conditions:
- condition: template
value_template: "{{ choixm == 11 }}"
sequence:
- repeat:
sequence:
- service: script.turn_on
target:
entity_id: script.centrale_gardena_on_off
data:
variables:
choix: 11
- delay:
hours: 0
minutes: 0
seconds: 5
milliseconds: 0
- if:
- condition: template
value_template: "{{ repeat.index >= 2 }}"
then:
- service: notify.mobile_app
metadata: {}
data:
message: choixm {{ choixm }} tentative {{ repeat.index }}
until:
- condition: or
conditions:
- condition: device
type: is_off
device_id: 90eeefd7db817d489a7686dae7357730
entity_id: 30050e150937b6f9a9853c4f43a8097c
domain: switch
- condition: template
value_template: "{{ repeat.index == 4 }}"
icon: mdi:waterThe masterscript is called in the regular watering script instead of opening the valve directly, like to open valve 1: - service: script.turn_on
target:
entity_id: script.centrale_gardena_on_off_master
data:
variables:
choixm: 1Maybe not very academic code but it works and this sends a notification if a 2nd, 3rd or 4th attempt was needed. It always went to max a second attempt ! |
|
Great, thanks a lot, I'll give it a try! |
|
Maybe some good news guys!
Result: It works smooth. No Loops in my scripts after a few tries. I hope this helps fro you, too. |
|
Maybe I’m too pessimistic, but I don’t know if it might solve it completely. I started my setup 5 days ago. And there are still these time out errors. |
|
I have the same issue: Command to valve - open - error after a few seconds, so the first valve is opened for 30 minutes (standard in the irrigation control), while the other 5 won't get a single drop of water.... Problem obtains not every time the automation is running.... Already installed version 1.1.0 (this number is NOT shown in the Integration overview though having it uninstalled before in HACS and reinstalled it with restarts. It shows version 1.0.0) This error occurs since 2023.... please help |
Yes you are right. The fails are less, but not gone. @Developers team: It would be nice to get a short info if you are plannning to look on this and also other topics or if you decided to stop the development. |
|
Hello everyone !
There is no real team behind the library/integration ;) I try to maintain
it ads much as I can, but I have been quite busy in the past few months
with my work.
I am currently on holidays abroad and I will try to solve as many issues as
possible when I come back to france.
I am sorry for the lag in solving this issues and I ll do my best to update
everything to make it work again
Enjoy the summer,
Jérémie
Le dim. 11 août 2024, 08:19, Stoffl17 ***@***.***> a écrit :
… Maybe I’m too pessimistic, but I don’t know if it might solve it
completely. I started my setup 5 days ago. And there are still these time
out errors.
Yes you are right. The fails are less, but not gone.
@Developers <https://github.com/Developers> team: It would be nice to get
a short info if you are plannning to look on this and also other topics or
if you decided to stop the development.
—
Reply to this email directly, view it on GitHub
<#214 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAARGI5ACJAWJSZADNZFTJDZQ366PAVCNFSM6AAAAABJNKNLK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSGY2DAMZZG4>
.
You are receiving this because you are subscribed to this thread.Message
ID: <py-smart-gardena/hass-gardena-smart-system/issues/214/2282640397@
github.com>
|
|
We know of course that you developers do this in your free time and without pay. So thank you in advance for your help. If you need any logs or more information people here are willing to help for sure. |
Dear @grm, thanks for your positive feedback. I really appreciate. Best regards! |
|
Hello, malkie |
|
Unfortunately, I guess that recreating the application in the gardena API solvee a kind if issue like this. I'll think about something about it. Please tell me how do often it happens and if doing nothing also solvees sometimes the issue ? |
|
Thanks for looking into this! Following oliskippy's advice I set up scripts and called them in a loop until the valve is open. Nevertheless, in my case this also fails as it seems that HA's |
|
Hello,I use the HACS Integration "retry" and there are no problems any more - knock on wood...Am 02.09.24, 22:30 schrieb "Jérémie Klein" ***@***.***>:
Unfortunately, httpx.ReadTimeouterrors comes from network error with the gardena API.
There is a retry mechanism that should handle these kind of issues, but it may not. be implemented or there is a hole in the implementation.
Maybe we could try with a loop too retry, but. that seems like a little overkill and rough.
I guess that recreating the application in the gardena API solvee a kind if issue like this.
I'll think about something about it.
Please tell me how do often it happens and if doing nothing also solvees sometimes the issue ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
I also tried the integration "retry" but, unfortunately, in my case it did not work reliably |
|
Hi all, are there any updates on this topic? Or any ideas how to avoid these issues? Thanks |
|
Although the watering season slowly comes to an end, I'm still curious if there are any new ideas to solve this issue? |
and others
I am experiencing a ReadTimeout error with my Gardena integration in Home Assistant. This issue occurs while executing my automation, which is designed to start a new valve every 20 minutes. The error consistently occurs when starting the first valve, causing the entire automation to fail despite continue_on_error: true being set.
Effected device:
Environment:
Additional Information:
Automation looks like:
The text was updated successfully, but these errors were encountered: