Using the Light-Scheduler in the middle of a flow about node-red-contrib-light-scheduler HOT 7 OPEN

Just pushed v0.0.14 that adds a new filter-node with this functionality. Please try it out and report any issues.

Have a nice week end!
/Niklas

from node-red-contrib-light-scheduler.

@rhoddan that's correct. It does currently don't care about the overrides.

Since I used msg.payload for the overrides, that would mean that I have to block these msg from being forwarded to the outputs and since the override keywords are so basic that could have a problem if you for exmaple want a msg.payload of 'stop' to be forwarded to the correct output based on the schedule.

I'm going to add the override functionality back, but will move it to msg.override so that it's easy to determine if it's a override msg or a "normal" one.

/Niklas

from node-red-contrib-light-scheduler.

Absolutely. I think that one will need to use both msg.payload and msg.override initially to not cause to many breaking setups.

/N

from node-red-contrib-light-scheduler.

I have the same used @brammh .. but I have setup a dedicated flow with your node which is switching a global variable (eg. global.Light =true/false or ON/OFF) .. I check now the my flow on the variable to pass-through the sensor-trigger or not

from node-red-contrib-light-scheduler.

perfect! Maybe it can be good to change (or complement) the standard node (not the filter node) so it uses msg.override as well (just to have a standard behavior)?

from node-red-contrib-light-scheduler.

Hi,

I have actually done this myself as well, but have not decided to release it since it has it's problems.
If you have the code available, please make a pull request so that I can look into it in more detail!

/Niklas

from node-red-contrib-light-scheduler.

Really good function with the filter. It seems not to be possible to send override codes to the filter node.

from node-red-contrib-light-scheduler.