I have created this flow to be triggered whenever a chromecast device gets stuck, to wait for 5mins (so corrective action doesn’t get triggered too many times if two chromecasts go down in succession), then to restart the chromecast app in homey pro.
For some reason this flow gets auto-disabled for running too many times. I can’t imagine why would it run too many times if it can only be triggered by a failing chromecast, and they don’t fail every second or every minute.
Thoughts?
I would add and AND card between the top card and second card to make sure the timer is not running already.
Third card from above: Maybe use the card for Timer has stopped?
Are you using a static IP for the Google devices?
Post a notification to the timeline whenever the flow triggers, perhaps it’s triggering more often than you think.
The first card triggers the timer to start (second card). How would an AND between them work?
Testing the second idea. I’m afraid it might increase triggers not reduce them (any stop in the timer vs only when it countdowns to zero). Still worth testing.
Yes, all of them have fixed IPs.
Done. Let’s see what it brings up.
When…
-device x became unavailable
And…
-timer “chromecast offline” is not running
Then…
-start timer “chromecast offline” with 300s runtime
this prevents the timer from being started before 300s have passed
Note: Chronograph has timer cards like “start and replace timer” and “start and resume timer”
This prevents for the same timer started multiple times, which could be the cause of your flow getting disabled.
(“60 triggered times and still running flows limit”: I was told to be sort of the only one with this issue according to Athom 
[Timeline] Flow disabled because it runs 60 times - #21 by Peter_Kawa)
Thank you for the reminder that we have chronograph 
I tend to stick to simpler apps where possible but here the upgrade is worth it.
So the automation is being triggered 11times in the same minute (pattern repeats once an hour but not same minute of the hour). Sometimes only 1-2 times.
I have only 6 chromecast devices. 3 Nest Max and 2 Nest displays and 1 android TV. Only 4 of them run in flows including the flow shown at the start of this thread.
What can I do to limit the flow being triggered 11 times every hour? should I just set up a simple timer to restart the chromecast app every 30mins (might not catch every chromecast failing in time, but I’m not using them for anything mission critical to start with).
Perhaps you should contact Athom to ask why a flow like that gets disabled, 11 times per minute doesn’t seem at all unreasonable.
No, I would only restart it when a device becomes unavailable.
I use it like this, without any issues.
I would like to know more about the problem 
before acting on it. I am using a flow similar to the one Peter Kawa posted. Since I adjusted some settings in my router it happens not even once a week a Google device is not available.
But it happened some time ago every day. This until I discovered that it always happened when my router was switching channels, So i turned this off and since then it is very rare that a device is unavailable.
First thing to know is if the device is really unavailable for Homey?
Is the device working in Google Home when unavailable in Homey?
Could there be something in your network which could cause the behaviour?
Like:
Ok, then I would recommend a flow like the one from Peter to restart the app Maybe add a extra action card to mention somewhere (like in the timeline) the app has been restarted. This so you know when it happened and how often.
I wonder if 11 times in one minute will also happen when you use a flow like the one from Peter (without using Device capabilities).
I think the “11 times in one minute” was a typo and should be “11 times an hour”, like TS wrote next. I can’t imagine the Chromecast getting unavailable every 9s…
Thanks for the network hints, Hielke!
I’ll check the Wifi settings. I’ve a dedicated 2.4GHz separate wifi SSID with fixed channel for Homey; I think i’m going to add the Chromecast devices to that same SSID as well.
Now they’re connected to a wifi6 3 AP system…
It’s one to two times a day unavailable here, so I’m having less Homey-with-wifi issues I guess :
2024-08-25T23:12:35.086Z,Info,Flow,Discover paused or crashed apps,"A HubHub was in error and Chromecast app was restarted. Error: Flow card is not available."
2024-08-25T00:48:37.653Z,Info,Flow,Discover paused or crashed apps,"A HubHub was in error and Chromecast app was restarted. Error: Flow card is not available."
2024-08-24T01:24:41.224Z,Info,Flow,Discover paused or crashed apps,"A HubHub was in error and Chromecast app was restarted. Error: Flow card is not available."
2024-08-23T00:54:37.411Z,Info,Flow,Discover paused or crashed apps,"A HubHub was in error and Chromecast app was restarted. Error: Flow card is not available."
It is in fact 11 in a minute “when it occurs”.
I didn’t mention this before: the error message that the flow has been disabled occurs as many times in a single minute.
The burst happens a few times a day.
