Open Markswanepoel opened 1 year ago
Hi @Markswanepoel, based on what you've shared, I'm not sure how this integration is impacting your restart times or how it relates to the controller's docker container. Can you elaborate further on your issue?
Hi @zachcheatham I am new at this so beg your pardon for me not explaining this properly.
If i reboot my Homeassistant it can take up to 5 min to to display the logon screen , on investigation the log files , I noticed that the controller software at 2drunc-moby-c37df2f37c6770292423039f4f30cdd146def5091e88f8ccfb446f986f5a954f-runc.78yuE0, which is my docker container for the omada controller has an entry in my "host log file" as below
May 01 01:22:17 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-c37df2f37c6770292423039f4f30cdd146def5091e88f8ccfb446f986f5a954f-runc.78yuE0.mount: Deactivated successfully.
May 01 01:28:55 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-c37df2f37c6770292423039f4f30cdd146def5091e88f8ccfb446f986f5a954f-runc.zCOLvH.mount: Deactivated successfully.
This seems to coincide with my HA boot time, this might be coincidence only , not sure. Was wondering if this could cause a slow reboot as the system is waiting for response from the Omada container? .
Hi , I am having an issue when rebooting my HA, it seems to take forever , on inspection I found the following in the log file of "host" Omada Integration version 5.9 This log point to the docker that houses the omada controller
May 01 01:22:17 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-c37df2f37c6770292423039f4f30cdd146def5091e88f8ccfb446f986f5a954f-runc.78yuE0.mount: Deactivated successfully. May 01 01:28:55 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-c37df2f37c6770292423039f4f30cdd146def5091e88f8ccfb446f986f5a954f-runc.zCOLvH.mount: Deactivated successfully.