You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under the Zigbee2Mqtt GUI / Logs , selecting Log Level both "warning" as well as "warn" exists in the dropdown menu.
Selecting "warn" seems to crash the zigbee2mqtt addon with the following message shown in stacktrace.
This is most likely only a GUI issue that needs to be adjusted.
Remove warn level or change it to some other syslog level actually intended
I have both 1.42.0 as well as 2.0.2 installation and it exists in both.
If the addon crashed a workaround is to change the log level in the zigbee2mqtt configuration.yaml file
log_level: warn
to perhaps info instead and for me the addon starts again without crashing
log_level: info
What browsers are you seeing the problem on?
Microsoft Edge
Relevant stacktrace
Starting Zigbee2MQTT without watchdog.
AssertionError [ERR_ASSERTION]: 'warn' is not valid log_level, use one of 'error, warning, info, debug'
at Logger.init (/app/lib/util/logger.ts:41:15)
at new Controller (/app/lib/controller.ts:79:16)
at start (/app/index.js:159:18)
Did you download state.json.zip?
I will not attach state.json.zip
The text was updated successfully, but these errors were encountered:
What happened?
Under the Zigbee2Mqtt GUI / Logs , selecting Log Level both "warning" as well as "warn" exists in the dropdown menu.
Selecting "warn" seems to crash the zigbee2mqtt addon with the following message shown in stacktrace.
This is most likely only a GUI issue that needs to be adjusted.
Remove warn level or change it to some other syslog level actually intended
I have both 1.42.0 as well as 2.0.2 installation and it exists in both.
If the addon crashed a workaround is to change the log level in the zigbee2mqtt configuration.yaml file
log_level: warn
to perhaps info instead and for me the addon starts again without crashing
log_level: info
What browsers are you seeing the problem on?
Microsoft Edge
Relevant stacktrace
Did you download state.json.zip?
I will not attach state.json.zip
The text was updated successfully, but these errors were encountered: