Open Seexelas opened 10 months ago
Thanks for reporting!
Indeed, there's a hard limit of 30 seconds in the activity execution (log entry: started activity with timeout of 30s
) and the individual delay steps are not accounted for.
I've also discovered some UI issues while testing this.
We'll fix this.
Release 1.4.3 increases the timeout from 30 to 60s as a quick "workaround". However, the UI might still show an error. A real fix is in the works.
Is there an existing issue for this?
Description
Hi,
I have done a Zidoo activity where I need a delay of more than 20 secs to let my Zidoo media player start so I can after this set the input.
It seems that a delay superior of 20 seconds freeze the activity start and the only way to exit is by power off or restart the remote.
How to Reproduce
Create an activity with different entities : (in my case Panasonic Tv, then go to HDMI 2, then my AVR, input to Zidoo, then Zidoo starts and then a delay of 30 secs before setting the Zidoo to input on Home Theater.
Launch the activity
When the delay of 30 secs arrives, the activity freeze and do nothing.
Expected behavior
The activity starts with the predefine settings.
System version
1.4.2
What part of the system affected by the problem?
Overall system
Additional context
UCR2_logs_2023-10-18.txt