linuxha/node-red-contrib-mytimeout issues and pull requests

#32 - Feature/dev test

Pull Request - State: closed - Opened by linuxha almost 3 years ago - 1 comment

#31 - unwanted starting of countdown

Issue - State: closed - Opened by tita2000 over 3 years ago - 6 comments

#30 - strange behaviour, does not turn off , or even turns on instead

Issue - State: open - Opened by Dakhaasje about 4 years ago - 3 comments

#29 - Tick interval

Issue - State: open - Opened by tvlada73 about 5 years ago - 4 comments

#28 - Add topic to 2nd output

Issue - State: open - Opened by andreypopov about 5 years ago - 5 comments

#27 - Topic Using Mustache

Issue - State: open - Opened by dcplaya about 5 years ago - 10 comments

#26 - Warning sent when setting countdown to low value eg. `3` and warning param to 0 in GUI

Issue - State: closed - Opened by iRonin about 5 years ago - 4 comments

#25 - Feature/no on payload

Pull Request - State: closed - Opened by linuxha over 5 years ago

#24 - Warning output doesn't contain extra attributes like the on and off messages do.

Issue - State: open - Opened by linuxha over 5 years ago
Labels: bug

#23 - A msg.warning of 0 doesn't override the GUI setting to cancel sending a warning message

Issue - State: open - Opened by linuxha over 5 years ago - 3 comments
Labels: bug

#22 - Feature Request: Allow the "Timer On Payload" to work like the "Warning state payload"

Issue - State: open - Opened by obbers over 5 years ago - 3 comments
Labels: enhancement

#21 - Feature Request: Allow the Timer On Payload

Issue - State: closed - Opened by obbers over 5 years ago - 1 comment

#20 - Fix for issue #16 - topic name

Pull Request - State: closed - Opened by brammh over 5 years ago - 2 comments

#19 - Should I pass in a JSON string or a javascript object?

Issue - State: closed - Opened by colinl over 5 years ago - 9 comments

#18 - Run different instances of timer based on msg.topic

Issue - State: closed - Opened by sriramsv over 5 years ago - 3 comments

#17 - First countdown msg is a string !

Issue - State: closed - Opened by ipa64 over 5 years ago - 7 comments

#16 - Output Topic - not coming out

Issue - State: closed - Opened by tsprivate over 6 years ago - 5 comments
Labels: bug

#15 - L495: newMsg(inMsg): RangeError: Maximum call stack size exceeded

Issue - State: open - Opened by Unpuertomex over 6 years ago - 13 comments

#14 - Pause

Pull Request - State: open - Opened by readeral over 6 years ago - 24 comments

#13 - Pause?

Issue - State: open - Opened by readeral over 6 years ago - 6 comments
Labels: enhancement

#12 - Time remaining (Output 2) is not in msg.payload

Issue - State: closed - Opened by linuxha over 6 years ago - 1 comment

#11 - "TypeError: node.warn is not a function"

Issue - State: closed - Opened by Unpuertomex over 6 years ago - 4 comments

#10 - Timer does not stop for FLOAT timeout values

Issue - State: open - Opened by tsprivate over 6 years ago - 3 comments

#9 - The workspace contains some nodes that are not properly configured ...