We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
After the changes that no long show the log on the website, I can't figure out how to get it back :(
I have this in config file:
advanced: log_level: info log_debug_to_mqtt_frontend: true
I have tried 'log level: debug' as well.
But on the website, I only get log entries, if i select debug, but then I get to much info.
I would just like to have the same info as before, where I can see the events as they happen.
Anyone who can help?
Thanks
No response
1.37.1 commit: ea39d86
Coordinator type zStack3x0 Coordinator revision 20230507
Sonoff Zigbee Sensor | Zigbee 3.0
Zigbee2mqtt running on Pi4
The text was updated successfully, but these errors were encountered:
You might want to have a look here : #22522 (comment)
Sorry, something went wrong.
Thanks LaurentChardin
No branches or pull requests
What happened?
After the changes that no long show the log on the website, I can't figure out how to get it back :(
I have this in config file:
advanced:
log_level: info
log_debug_to_mqtt_frontend: true
I have tried 'log level: debug' as well.
But on the website, I only get log entries, if i select debug, but then I get to much info.
I would just like to have the same info as before, where I can see the events as they happen.
Anyone who can help?
Thanks
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.37.1 commit: ea39d86
Adapter firmware version
Coordinator type zStack3x0 Coordinator revision 20230507
Adapter
Sonoff Zigbee Sensor | Zigbee 3.0
Setup
Zigbee2mqtt running on Pi4
Debug log
No response
The text was updated successfully, but these errors were encountered: