![]() The “moonrise” code in module sunCalc seems less than perfect so although I added the moonrise and moonset properties in 2.1.3 BigTimer, there were issues resolved in moonrise and moonset (from version 2.17 on) thanks to adding my own checking to the sunCalc module. Second function node: if (msg.state="off") Įasy – I have a ton of variations on that for different scenarios.īack in February 2018 I added moonrise and moonset – as well as improving the layout and docs. Blynk might be controlling the lighting or the grey manual overrides, OR BigTimer may be running a schedule – it is important that all 3 methods are compatible and that they stay in SYNC.įirst function node: if (msg.payload="1") msg.payload="off" Įlse if (msg.payload="2") msg.payload="auto" ![]() Note the Blynk “Write Event” node on the left and the Blynk “Write” node on the right. A simple function node on either side of BigTimer sorts out that problem. ![]() Let me give an example, the segmented switch in BLYNK, assuming 3 outputs for this example – gives and needs values “1”, “2” and “3” – which I use for “off” “auto” and “on” states in BigTimer. I’ve had the odd comment about BigTimer not giving the output someone wants… if the msg.payload from output 1 isn’t what you need, change it. There is also real-time status information displayed below each BigTimer node.Īs always, the latest node-red-contrib-bigtimer is available at node-red-flows and at – put “scargill” in the search and you’ll see all my nodes and flows. The third output presents a message which could be used for speech or debugging. The second of three outputs offers a simple 1 or 0 every minute in the output “payload” and also presents additional information reflecting the status message in msg.state, message.time and others – see the entire msg object output in debug for more. You can also manually over-ride the UTC time setting on the host computer if required. The node offers outputs suitable for MQTT, speech and databases (but you don’t HAVE to use any of these). Full support is provided for dusk/sunset dawn/sunrise and variations also for day/week/month (and special days) control.īigTimer has three outputs, the first of which updates when there is a change of state and presents one of two messages (for, for example, MQTT or other control mechanism) ON and OFF TEXT fields are optional – for speech or whatever use you have in mind.īigTimers can be used singly or in groups. The MQTT-compatible payload (ON and OFF msg) is the main output and you should put a value in there even if not using MQTT. If you need something to happen at or near midnight – I’ve now added a DAY END option to the OFF dropdown boxes – equating to 23:59 or one minute before “midnight” (the latter is in fact is the beginning of the next day).Īt it’s simplest, BigTimer is a single block which can be used as the equivalent of a simple mechanical timer, seeding other Node-Red nodes or directly manipulating devices by, for example, MQTT protocol. The panel on the right is quite out of date now with many additional items in the actual panel.įor clarity: BigTimer works in minutes – in a DAY which consists of hours and minutes 00:00 to 23:59, where minute 1439 is the last minute of the day – that is why there is no MIDNIGHT in the settings. In version 2.5.0 I added separate on-off randomisation options. I do not plan to spend any more time hunting through Node-Red forums for BigTimer queries, sorry… and the source is NOT in GITHUB – you have the full source when you have BigTimer itself – the whole thing is only 2 files (a. V2.8.1 fixed bug introduced in 2.8.0 to 2nd output payload. Also, one helpful blog subscriber pointed out an issue – special day included – month 9 was faulty – fixed – many thanks to everyone for you feedback on this very popular timer). Update February 2023įixed a mistake in the July-December exclusion months Update January 9, 2022Īdded new “away” command – in minutes for now (away X) which can be as long as you like and will hold the first output off until you clear it with (away 0) or it runs out – this should be fully tested before deploying and you MUST have “repeat” ticked in the dialog for this to work. I’m currently pondering how to add winter and summer options for on-off times without making the setup page more cluttered – ideas welcome. ![]() Questions about BigTimer should be placed in the comments section here. BigTimer is my own creation and is (IMHO) the most powerful and best-ever, most comprehensive timing node for Node-Red, providing a general purpose timer as well as handling summer/winter correctly as well as (importantly) lighting-up time (for which you should provide your longitude and latitude from Google maps or similar).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |