Replies: 5 comments 1 reply
-
Hi Rob |
Beta Was this translation helpful? Give feedback.
-
Yup.. my bad... the timer thing was at the top in big technicoloured writing! Timers work great. A couple of observations. If I simply say 'set a timer for x minutes', all works fine, but I can actually do that multiple times, and although HASS only shows the remaining time for the first timer you set, it actually keeps track of all the timers you've set. For example, I could set a timer (in this order), for 2 minutes, 1 minute and then 30 seconds. Each will then trigger. Also... how do I set a timer for the second timer... I've tried using the phrase "set timer 2 for x minutes' but it doesnt recognise it. |
Beta Was this translation helpful? Give feedback.
-
at the moment the tracking only supports tracking the first timer, however you can set multiple timers, I still have this to add to support viewing the other timers. it is still a bit of a work in progress :) But the code is all in the config if you can figure it out ;) |
Beta Was this translation helpful? Give feedback.
-
Been playing around with the s3 this afternoon, amazing what you have managed to get it to do. Maybe the cleaner approach would be for the timer menu item to take the user to the timer finished page if the timer_ringing is on. After I typed that reply, I decided I preferred the menu option and added this to the on_click for the timer page:-
|
Beta Was this translation helpful? Give feedback.
-
yes that is a good point , i hadn't come across that issue - so thanks for pointing it out 👍 I will add that condition in Cheers 😃 |
Beta Was this translation helpful? Give feedback.
-
So, after re-designing my idle page (docs were super useful), I want to be able to set a timer via the device.
If I simply say 'set a timer for x minutes', HASS replies with a message, saying that devices are not supported on this device.
So I thought about writing an automation to do it. This in itself is not difficult, but having hass respond to the device when the timer has ended, is.
If I simply use a wait for trigger (timer.idle) in my automation to send message when the timer has finished, it all works, but because the automation doesn't then end until the wait for trigger condition is met, it basically holds the box3 on the listening screen for as long as the timer is running.
The other way is to have another automation listen for the timer.idle trigger, but how would it then know which media player to send the notification back to, using the 'set conversation response' action (which takes no parameters).
Looking on the community forums, there are a ton of posts, with some huge code examples for what should be a relatively simple thing.
TLDR:- How do a tell the box3 that an action has happened if its not immediate (like turning on a light).
Beta Was this translation helpful? Give feedback.
All reactions