The most powerful, high performing and highly polished Z-Wave node for Node-RED based on Z-Wave JS. If you want a fully featured Z-Wave framework in your Node-RED instance, you have found it.
MIT License
47
stars
6
forks
source link
[Feature]: Allow zwave logs to pipe to controller node output #100
Would like to see the options for zwjs logs to be piped to a second output on controller node.
Might need a check box for both "to file" and "to second output" - I'm planning only to enable the second output as I don't always want the text file saved. Log level could be the same between "to file" and "to second output" or could be different detail.
Perhaps just a new drop-down for "log to 2nd output" would do the trick. We can enable and set the log file the same as ever but have a new drop-down to enable 2nd output and choose log level.
Any more details?
Screenshot of how the NR debug could look:
Version
5.0.0
Node-RED Version
2.0.5
What hardware are you using?
Raspberry Pi
Any code to add?
// format should be json:
format: Winston.format.json()
Contact Details (optional)
goosegoosegoose@duck.com
What is your idea?
Would like to see the options for zwjs logs to be piped to a second output on controller node.
Might need a check box for both "to file" and "to second output" - I'm planning only to enable the second output as I don't always want the text file saved. Log level could be the same between "to file" and "to second output" or could be different detail.
Perhaps just a new drop-down for "log to 2nd output" would do the trick. We can enable and set the log file the same as ever but have a new drop-down to enable 2nd output and choose log level.
Any more details?
Screenshot of how the NR debug could look:
Version
5.0.0
Node-RED Version
2.0.5
What hardware are you using?
Raspberry Pi
Any code to add?