Closed chenchen119 closed 5 years ago
:wave: Thanks for opening your first issue here! If you're reporting a :bug: bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be usefull.
This seems to be fixed on updating the add-on to 0.9.2.
Thanks!
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
Problem/Motivation
Addon crashes supervisor / hassio when accessed using webui. New installation of HassOS on Tinker Board.
Expected behavior
Not crash the system. I have a similar installation with same hardward. It was running addon 0.7.1 I believe and there was no issues. I updated that installation to 0.9.1 as well, then immediately saw this error (I am using the controller as device tracker and set verify_ssl: false):
As this installation is remote, I do not want to access web ui afraid it might crash the system. I also have the same addon 0.9.1 running on a Raspberry Pi 3 B, no issues.
Actual behavior
This is a new install. Installed 0.9.1 fresh. During first start up of addon, then accessing through the Web UI of the addon. Hassio itself became unresponsive. At first I did not realize it was caused by the addon. Ping worked but getting some request timeouts. SSH did not work. Web UI of lovelace is inaccessible.
Had to unplug the tinker board. Everything back to normal, then I loaded a backup to the controller. Crashed again. Same behavior as above. There's no extra logs on supervisor. Unfortunately I cannot see any additional logs from the addon as the UI becomes instantly unresponsive.
Another hard unplug, I was able to get into the Web UI of the addon, the backup should be restored. I can login with username and pw. But then a couple clicks in (trying to adopt AP), same freeze happens again.
This and the above behavior with another installation leads me to believe it might be an issue with 0.9.1 and Tinker board..
Just running the addon does not seem to do anything. Only accessing the web ui does.
Steps to reproduce
Is there any other way to troubleshoot this issue? Any recommendation is appreciated.