Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FONCTIONALITIES
Timers on the S3 Boxes, only the micro-wake-word variations, we will deprecate the non-micro-wake-word soon.
The Split was initially done to avoid long compilation times of the micro-wake-word component on a low-powered machine.
OTA fixes that, we do not need to support both variations.
Timer timeline
A timeline will be visible to represent the state of the timer
Where?
How does the timeline work?
Q&A
Timer Widget
Where
How does the widget work?
HH:MM
MM:SS
Q&A
Timer end behavior
When a timer ends, many things happen
Q&A
timer_finished_illustration_file
TODO LIST FOR THIS PR
file
component used does not support remote paths. For now, this PR references local paths for the sound file but this will cause issues when adopting and customizing the firmwareI use the
interrupt_pin
as such:However, on the original box, the
interupt_pin
was working only once, and the touch even was never registered again.So I fell back to a more dirty approach: I used the
update_interval
and updated the touchscreen component every 50ms. If any of you can find out why theinputerp_pin
is not working on the original S3-BOX, that would be great