Closed brianjking closed 7 years ago
Yes. it works for me instantly in the realtime logs. sudo journalctl home-assistant -fu
@CCOSTAN
pi@hasspi3:~ $ sudo journalctl home-assistant -fu
journalctl: option requires an argument -- 'u'
sudo journalctl -u home-assistant -f
Apr 24 14:51:18 hasspi3 hass[11467]: 17-04-24 14:51:18 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1798708208: Sending {'id': 2, 'type': 'event', 'event': {'data': {'old_state': <state input_select.log_level=warn; friendly_name=Log Level, options=['critical', 'fatal', 'error', 'warning', 'warn', 'info', 'debug', 'notset'] @ 2017-04-24T14:35:28.560626-05:00>, 'entity_id': 'input_select.log_level', 'new_state': <state input_select.log_level=critical; friendly_name=Log Level, options=['critical', 'fatal', 'error', 'warning', 'warn', 'info', 'debug', 'notset'] @ 2017-04-24T14:51:18.319714-05:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2017, 4, 24, 19, 51, 18, 319886, tzinfo=<UTC>), 'event_type': 'state_changed'}}
Apr 24 14:51:18 hasspi3 hass[11467]: 17-04-24 14:51:18 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 1820938192: Sending {'id': 2, 'type': 'event', 'event': {'data': {'old_state': <state input_select.log_level=warn; friendly_name=Log Level, options=['critical', 'fatal', 'error', 'warning', 'warn', 'info', 'debug', 'notset'] @ 2017-04-24T14:35:28.560626-05:00>, 'entity_id': 'input_select.log_level', 'new_state': <state input_select.log_level=critical; friendly_name=Log Level, options=['critical', 'fatal', 'error', 'warning', 'warn', 'info', 'debug', 'notset'] @ 2017-04-24T14:51:18.319714-05:00>}, 'origin': 'LOCAL', 'time_fired': datetime.datetime(2017, 4, 24, 19, 51, 18, 319886, tzinfo=<UTC>), 'event_type': 'state_changed'}}
Apr 24 14:51:18 hasspi3 hass[11467]: 17-04-24 14:51:18 INFO (MainThread) [homeassistant.components.automation] Executing Log Level
Apr 24 14:51:18 hasspi3 hass[11467]: 17-04-24 14:51:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event logbook_entry[L]: message=has been triggered, entity_id=automation.log_level, name=Log Level, domain=automation>
Apr 24 14:51:18 hasspi3 hass[11467]: 17-04-24 14:51:18 INFO (MainThread) [homeassistant.helpers.script] Script Log Level: Running script
Apr 24 14:51:18 hasspi3 hass[11467]: 17-04-24 14:51:18 INFO (MainThread) [homeassistant.helpers.script] Script Log Level: Executing step call service
Apr 24 14:51:18 hasspi3 hass[11467]: 17-04-24 14:51:18 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_data=homeassistant.components=critical, service_call_id=1978632720-12, domain=logger, service=set_level>
@CCOSTAN -- I saw this log level automation in your repo and implemented it, however, it doesn't seem to actually change the log level. Is yours working?
home-assistant.log
My Configuration for Log Level Input Select