node-red-contrib-schedex
node-red-contrib-schedex copied to clipboard
biddster
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 offs...
Maybe not the best title, but here goes: I'm using ontime: dusk and off time 22:00. Works great in the winter, but here in the summer, dusk is actually later...
Bumps [y18n](https://github.com/yargs/y18n) from 4.0.0 to 4.0.1. Changelog Sourced from y18n's changelog. Change Log All notable changes to this project will be documented in this file. See standard-version for commit guidelines....
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [ssri](https://github.com/npm/ssri) from 8.0.0 to 8.0.1. Changelog Sourced from ssri's changelog. 8.0.1 (2021-01-27) Bug Fixes simplify regex for strict mode, add tests (76e2233) Commits 3eec7a3 chore(release): 8.0.1 2083289 chore: update...
Hello! I found something. Example The on time is set to 6:00 am The off time is set to 6:00 pm Now 1:00 pm 1. I make a request -...
Was happy to find this node, just was I needed ! Maybe I'am missing something (english is not my native language), but it's not working ... Input of ON/OFF works...
I'm having an issue with the following settings: `ON`: `sunset` `offset`: `240` In this case, the time/date is correctly calculated as 12:30am the next day -- at least -- according...
I successful integrated schedex to my project - many thanks for this nice flow. The only limitation I see so far is, that I can only set one on and...
I have confirmed that the Latitude and Longitude are correct but the solar times are considerably off. Set the On time to “solarNoon” and the display is stating that ON...
Hello I was debugging as to why the time was off by about 30 minutes to my sunset and sunrise. While I was debugging. I thought I would try using...
When the node is first deployed, the status shown in the editor under the node is correct, but that caught by the `status` node is not. You can see this...
