I’ve been asked questions about output from my Node-Red-Contrib-BigTimer in the 2.06 update and also the new(ish) “timer X” option. Here is a working demo, I’ve added a timer to my desk with a Sonoff BASIC attached and a lamp to test. Output 1 is as you can see working fine in this demo.
There it is. Set to come on at dusk (it is currently morning). I can do a simple manual override (using an inject for test purposes) until the next ON time or just have a quick 15 minute burst.
Here is the setup in the node itself… set to work all months and days by default.
The injects have “1”, “0”, “auto” and “timer 15 mins” in them, respectively.
And the short answer is, yes you can see the remaining time in the “timer” option and you now have a “timeoff” alternative.
I also tested the second output to ensure that 00:00/00:00 works as does a short morning burst.
Incidentally, second output – msg.precision – tells you how much time in seconds is left before the “timer” and “timeoff” modes runs out.
And YES, in 2.07 I’ve added “timeoff” so now you can have a temporary burst of ON or OFF time and YES I’ve also added the countdown to the visual status.
I wonder how many realise the amount of work and concentration these “little” changes take to put in and more importantly test and re-test. That’s the entire morning gone. Done.
Below: my initial setup controlling various items via BigTimer with optional overrides both onscreen for testing (injects) and using Blynk – often the VERY useful Blynk Segmented Switch – and a LED at the bottom showing heat off the bathroom heater. I don;t need a thermostat on that as it is NEVER warm enough in that bathroom. Having said that our new Air Source Heat Pump heating system is being fitted today. We’re going green (kind of). No more oil for us.