madzharov

Members
  • Posts

    2
  • Joined

  • Last visited

madzharov's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. It is working, no complains here, but since I am using a password manager with a rather complex password - is there a way to send that password to the login screen as I didn't see the clipboard feature working for that use case? Also can the default user be changed?
  2. Similar problem as of some others. Happens at least twice in 24 hours: [32m20-05-21 09:55:43 INFO (MainThread) [supervisor.supervisor] Update Supervisor to version 222[0m [32m20-05-21 09:55:43 INFO (SyncWorker_3) [supervisor.docker.interface] Pull image homeassistant/amd64-hassio-supervisor tag 222.[0m [32m20-05-21 09:55:45 INFO (MainThread) [supervisor.supervisor] Fetch AppArmor profile https://version.home-assistant.io/apparmor.txt[0m [32m20-05-21 09:55:46 INFO (MainThread) [supervisor.host.apparmor] Add or Update AppArmor profile: hassio-supervisor[0m [32m20-05-21 09:55:51 INFO (MainThread) [__main__] Stopping Supervisor[0m [32m20-05-21 09:55:51 INFO (MainThread) [supervisor.hwmon] Stop Supervisor hardware monitor[0m [32m20-05-21 09:55:51 INFO (MainThread) [supervisor.api] Stop API on 172.30.32.2[0m [32m20-05-21 09:55:51 INFO (MainThread) [supervisor.misc.forwarder] Stop DNS forwarding[0m [32m20-05-21 09:55:51 INFO (MainThread) [supervisor.core] Supervisor is down[0m [32m20-05-21 09:55:51 INFO (MainThread) [__main__] Close Supervisor[0m [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. The update part is wrong though. The version in the UI is stated to be 223 so I understand why no update happens, but at the very least I'd expect for the container to attempt starting. I can start manually the supervisor afterwards and it works fine though, but if that goes on, I should be the one called "assistant"