gablau / node-red-contrib-bigtimer Goto Github PK

As stated on official BigTimer developer webpage, some users has problem with working Timer2.

I think the problem occurs when 2nd timer has this same value for On and Off (e.g. 18:00 or Dusk in both fields) regardless of the Offset.

E.g.
DON’T works: On Time2 = 18:00, On Offset2 = 0, Off Time2 = 18:00, Off Offset2 = 15
DO works: ……On Time2 = 18:00, On Offset2 = 0, Off Time2 = 18:15, Off Offset2 = 0

Hi,
this is just a "Unofficial source code mirror of bigtimer NPM package".

• I'm not the original author.
• I put the original source code here, because the original author does not have a repository.
• I need it because I made the changes you find on week-override branch

I can't support the original code, sorry.
For any other requests go to: https://tech.scargill.net/big-timer

Regards

After ending timer, on output #2 msg.time and msg.exState shows incorrect data. It doesn't take into account the start of the second timer, just show the next time of start this timer.

e.g.
When
On Time parameter is set to "22:00" and Off Time for "1 minutes" and
On Time2 parameter is set to "10:00" and Off Time for "1 minutes"

msg.time which is (or I suppose it is) responsible for next switching on BigTimer, reports "23hrs 59mins" and
msg.exState do reports "Off for 23hrs 59mins" (in fact not sure why it is called exState

Expecting "11hrs 59mins" and "Off for 11hrs 59mins" respectively, or, better "Last ON at 10:00"

EDIT IMPORTANT:
The above problem occurs only for timers settings exactly as in above example. When switched (On Time = 10:00, OnTime2 = 22:00), it shows ok.
Moreover, it only occurs when checking it at the end of the day (past 22:10). At the morning, e.g. 10:20, for both timers settings (10:00 / 22:00 and 22:00 / 10:00) it does indicate OK.

When I use timer x to override the bigtimer schedule it sends the payload every seconds until the timer is finished.
Normally it should send it only once like the rest, right ?

I am using version 2.2.5 of bigtimer

Hi i see, that the bigtimer sends multiple message on the one message port.