Socket
Socket
Sign inDemoInstall

node-red-contrib-schedex

Package Overview
Dependencies
3
Maintainers
1
Versions
41
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    node-red-contrib-schedex

Scheduler for node-red which allows you to enter on/off times as 24hr clock (e.g. 01:10) or suncalc events (e.g. goldenHour). It also allows you to offset times and randomise the time within the offset.


Version published
Weekly downloads
257
decreased by-35.59%
Maintainers
1
Created
Weekly downloads
 

Readme

Source

Schedex

Scheduler for node-red which allows you to enter on/off times as 24hr clock (e.g. 01:10) or suncalc events (e.g. goldenHour). It also allows you to offset times and randomise the time within the offset.

Inspired by Pete Scargill's BigTimer

Installation

Change directory to your node red installation:

$ npm install node-red-contrib-schedex

Configuration

Suspending scheduling

The 'Suspend scheduling' checkbox allows you to disable time scheduling. If scheduling is suspended, Schedex will only generate output events upon receipt of input 'on' and 'off' events (see below).

This setting is provided for the situation where you temporarily don't want time based activation and don't want to rewire your Node-RED flow.

Times

The times can be a 24 hour time or a suncalc event:

TimeDescription
00:00 ... 23:5924hr time
sunrisesunrise (top edge of the sun appears on the horizon)
sunriseEndsunrise ends (bottom edge of the sun touches the horizon)
goldenHourEndmorning golden hour (soft light, best time for photography) ends
solarNoonsolar noon (sun is in the highest position)
goldenHourevening golden hour starts
sunsetStartsunset starts (bottom edge of the sun touches the horizon)
sunsetsunset (sun disappears below the horizon, evening civil twilight starts)
duskdusk (evening nautical twilight starts)
nauticalDusknautical dusk (evening astronomical twilight starts)
nightnight starts (dark enough for astronomical observations)
nadirnadir (darkest moment of the night, sun is in the lowest position)
nightEndnight ends (morning astronomical twilight starts)
nauticalDawnnautical dawn (morning nautical twilight starts)
dawndawn (morning nautical twilight ends, morning civil twilight starts)

Offsets

The on and off time can have an offset. This is specified in minutes:

  • -ve number brings the time forward. E.g. if the time is dusk and offset is -60, a message will be generated 60 minutes before dusk.
  • +ve number delays the time by the specified number of minutes

Randomisation of times

Both on and off times can be randomised by ticking "Use random time within offset period". For example, if you specify dusk with an offset of -60 minutes, every day a message will be generated at a random time in a 60 minute window before dusk.

Inputs

You can wire inject nodes to the input of this node. To turn on manually, simply send a payload of 'on'. To turn off manually, send a payload of 'off'. Injecting on or off causes this node emit the configured topic and payload. The manual mode is reset when the next on or off time is reached.

Programmatic Control

This node supports programmatic time control as well as configuration via the NodeRED UI.

It is very important to note that properties set programmatically in this manner are transient. They will not persist over a NodeRED restart or redeploy!

You can set the following:

PropertyType
msg.payload.suspendedBoolean: true will suspend scheduling, false will resume scheduling
msg.payload.ontimeString value as specified in the table above for time configuration
msg.payload.ontopicString value emitted as the topic for the on event
msg.payload.onpayloadString value emitted as the payload for the on event
msg.payload.onoffsetNumber value as specified above for Offset configuration
msg.payload.onrandomoffsetBoolean value as specified above in Randomisation of Times
msg.payload.offtimeString value as specified in the table above for time configuration
msg.payload.offtopicString value emitted as the topic for the off event
msg.payload.offpayloadString value emitted as the payload for the off event
msg.payload.offoffsetNumber value as specified above for Offset configuration
msg.payload.offrandomoffsetBoolean value as specified above in Randomisation of Times

Alternatively, you can send msg.payload as a string with the following values:

Example msg.payloadDescription
suspended truetrue will suspend scheduling, false will resume scheduling
ontime 12:00Time as specified in the table above for time configuration
ontopic my_topicOverride the topic for the on event (no spaces)
onpayload my_payloadOverride the payload for the on event (no spaces)
onoffset 30Override the offset for the on event
onrandomoffset trueOverride the random offset for the on event
offtime duskTime as specified in the table above for time configuration
offtopic my_topicOverride the topic for the off event (no spaces)
offpayload my_payloadOverride the payload for the off event (no spaces)
offoffset -30Override the offset for the off event
offrandomoffset falseOverride the random offset for the off event
ontime 16:30 onoffset 60 onrandomoffset trueOverride the time, offset and random offset for the on event

Keywords

FAQs

Last updated on 04 Jan 2017

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc