You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 27, 2021. It is now read-only.
I'm opening this again because while it's similar to #18, it's not identical to #18, and the workaround for #18 doesn't work here.
Same basic symptoms: error in the log reading
2021-03-02 13:58:53 ERROR (MainThread) [homeassistant.config] Package office_package setup failed. Integration o365 No module named 'O365' (See /config/packages/office365.yaml:3).
However, I can confirm that the O365 module has been downloaded and installed in the /config/deps folder, at /config/deps/deps/lib/python3.8/site-packages/O365, as per the manifest.json, so it is not that HA is failing to install it. Also, the config validates fine despite this error at runtime.
Environment: latest O365-HomeAssistant, installed via HACS, on HA 2021.2.3, running inside a Kubernetes pod (i.e., not under the Hass.io supervisor). Restarting the pod (i.e., a second reboot) does not work as a workaround this time.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm opening this again because while it's similar to #18, it's not identical to #18, and the workaround for #18 doesn't work here.
Same basic symptoms: error in the log reading
However, I can confirm that the O365 module has been downloaded and installed in the /config/deps folder, at
/config/deps/deps/lib/python3.8/site-packages/O365
, as per the manifest.json, so it is not that HA is failing to install it. Also, the config validates fine despite this error at runtime.Environment: latest O365-HomeAssistant, installed via HACS, on HA 2021.2.3, running inside a Kubernetes pod (i.e., not under the Hass.io supervisor). Restarting the pod (i.e., a second reboot) does not work as a workaround this time.
The text was updated successfully, but these errors were encountered: