I’ve noted that after 0.64 update the home assistant process is getting killed its running for a few hours. Could find any information on log to understand what is going on. Is anybody else facing a similar issue? I’ve also noted that same issue occurs on 0.65, and returning to 0.63.3 solves the problem.
Same here! Came home and it wasnt responding anymore.
I was looking wondering how can report a bug, since I only have that “the process was no longer running after a few hours”
Hi,
Finally I have a root cause. It seems that changes of Speedtest component introduced on PR #12377 are responsible for this behaviour. To reproduce the issue I just need to call the sensor.update_speedtest service, and in few seconds the homeassistant process is dead. As an example, these are the last line printed on log (no error at all):
2018-03-23 08:54:49 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 2801811024: Received {‘type’: ‘call_service’, ‘domain’: ‘sensor’, ‘service’: ‘update_speedtest’, ‘service_data’: {}, ‘id’: 11}
2018-03-23 08:54:49 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=sensor, service=update_speedtest, service_data=, service_call_id=3048441552-6>
2018-03-23 08:54:49 DEBUG (SyncWorker_9) [homeassistant.components.sensor.speedtest] Executing speedtest…
2018-03-23 08:54:56 INFO (SyncWorker_0) [homeassistant.components.device_tracker.nmap_tracker] No MAC address found for 192.168.0.41
2018-03-23 08:54:56 INFO (SyncWorker_0) [homeassistant.components.device_tracker.nmap_tracker] nmap scan successful
2018-03-23 08:54:59 DEBUG (MainThread) [homeassistant.components.websocket_api] WS 2801811024: Sending {‘id’: 11, ‘type’: ‘result’, ‘success’: True, ‘result’: None}
2018-03-23 08:55:00 INFO (SyncWorker_12) [homeassistant.components.sensor.command_line] Running command: curl --max-time 10 -s http://REDACTED:[email protected]:82/get_status.cgi | grep -oP alarm_status=. | tail -c 2
Maybe @fabaff could help us on confirming this issue…