Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: export logs #265

Merged
merged 1 commit into from
Jan 19, 2021
Merged

docs: export logs #265

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/_sidebar.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@
- Troubleshooting

- [Exporting Node Json](troubleshooting/node_export.md)
- [Exporting Logs](troubleshooting/logs_export.md)

- [Screenshots](screenshots.md)
- [Thanks](thanks.md)
Expand Down
14 changes: 14 additions & 0 deletions docs/troubleshooting/logs_export.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Logs export

The are two main loggers, one for zwavejs2mqtt and one for zwave-js module.

To help us finding what's going on, when reporting a bug, you should attach the logs coming from both loggers.

Both loggers options are configurable from the UI in `Settings`:

1. The ZwaveJS logger can be confgured in `Zwave` section, enable `Log enabled` switch and `Log To File` and set `Log Level` to `silly`
2. The zwavejs2mqtt logger can be confgured in `General` section, enable `Log enabled` switch and `Log To File` and set `Log Level` to `silly`

Now press on `SAVE` button to store the new settings and your logs will be stored in separeted files inside `store` folder. The zwavejs2mqtt log output file will be named `zwavejs2mqtt.log` and the zwavejs one `zwavejs_<processid>.log`

If you are using docker you can ssh inside the running container and/or use the `docker cp` command to download the files in the local filesystem.