home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.34k stars 29.88k forks source link

Config checker reports sqlalchemy is missing #30040

Closed uphillbattle closed 4 years ago

uphillbattle commented 4 years ago

Home Assistant release with the issue: 0.103.0

Config checker version: 3.1

Last working Home Assistant release (if known): 0.102.3

Operating environment (Hass.io/Docker/Windows/etc.): Hass.io (Docker on Debian on Intel NUC)

Integration:

Description of problem: The configuration check from 0.102.3 to 0.103.0 reports that 'sqlalchemy' is missing.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

starting version 3.2.8
[08:50:10] INFO: Don't worry, this temporary installation is not overwriting your current one.
[08:50:10] INFO: Installing Home Assistant: latest...
[08:50:10] INFO: Please be patient, this might take a few minutes...
WARNING: You are using pip version 19.2.2, however version 19.3.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
[08:50:36] INFO: Installed Home Assistant 0.103.0
[08:50:36] INFO: Making a copy of your configuration for checking...
[08:50:37] INFO: Checking your configuration against this version...
[08:52:27] ERROR: The configuration check did not pass!
[08:52:27] ERROR: See the output below for more details.
INFO:homeassistant.util.package:Attempting install of colorlog==4.0.2
Testing configuration at /tmp/config
INFO:homeassistant.util.package:Attempting install of aiohttp_cors==0.7.0
INFO:homeassistant.util.package:Attempting install of pymyq==2.0.1
INFO:homeassistant.util.package:Attempting install of ring_doorbell==0.2.3
INFO:homeassistant.util.package:Attempting install of ha-ffmpeg==2.0
INFO:homeassistant.util.package:Attempting install of hbmqtt==0.9.5
INFO:homeassistant.util.package:Attempting install of paho-mqtt==1.5.0
INFO:homeassistant.util.package:Attempting install of xmltodict==0.12.0
INFO:homeassistant.util.package:Attempting install of zeroconf==0.24.0
INFO:homeassistant.util.package:Attempting install of home-assistant-frontend==20191204.1
INFO:homeassistant.util.package:Attempting install of aioharmony==0.1.13
INFO:homeassistant.util.package:Attempting install of spotipy-homeassistant==2.4.4.dev1
INFO:homeassistant.util.package:Attempting install of pyfttt==0.3
INFO:homeassistant.util.package:Attempting install of hass-nabucasa==0.30
INFO:homeassistant.util.package:Attempting install of av==6.1.2
INFO:homeassistant.util.package:Attempting install of pywebpush==1.9.2
INFO:homeassistant.util.package:Attempting install of sqlalchemy==1.3.11
INFO:homeassistant.util.package:Attempting install of distro==1.4.0
INFO:homeassistant.util.package:Attempting install of python-nmap==0.6.1
INFO:homeassistant.util.package:Attempting install of getmac==0.8.1
INFO:homeassistant.util.package:Attempting install of google-api-python-client==1.6.4
INFO:homeassistant.util.package:Attempting install of httplib2==0.10.3
INFO:homeassistant.util.package:Attempting install of oauth2client==4.0.0
INFO:homeassistant.util.package:Attempting install of PyNaCl==1.3.0
INFO:homeassistant.util.package:Attempting install of homeassistant-pyozw==0.1.7
INFO:homeassistant.util.package:Attempting install of netdisco==2.6.0
INFO:homeassistant.util.package:Attempting install of mutagen==1.43.0
INFO:homeassistant.util.package:Attempting install of gTTS-token==1.1.3
Failed config
  General Errors: 
    - Platform error sensor.filter - No module named 'sqlalchemy'

Successful config (partial)

Additional information:

probot-home-assistant[bot] commented 4 years ago

Hey there @dgomes, mind taking a look at this issue as its been labeled with a integration (filter) you are listed as a codeowner for? Thanks!

dgomes commented 4 years ago

This is probably related to https://github.com/home-assistant/home-assistant/pull/29932

uphillbattle commented 4 years ago

Additional information: The configuration checking reported above was started from a Chrome web app on a Windows 10 PC.

I have also run the configuration checker from the Android companion app. When starting the configuration checker from the app, the result is this:

starting version 3.2.8
[14:17:23] INFO: Don't worry, this temporary installation is not overwriting your current one.
[14:17:23] INFO: Installing Home Assistant: latest...
[14:17:23] INFO: Please be patient, this might take a few minutes...
WARNING: You are using pip version 19.2.2, however version 19.3.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
[14:17:49] INFO: Installed Home Assistant 0.103.0
[14:17:49] INFO: Making a copy of your configuration for checking...
[14:17:50] INFO: Checking your configuration against this version...
[14:19:40] INFO: Configuration check finished - no error found! :)

I found this strange, so I started the configuration checker a third time - again from the Chrome web app on the Win10 machine. The result: 'sqlalchemy' missing.

Starting the configuration checker a fourth time - from the Android companion app - I got the 'no error found'.

I can't explain this, but I thought it might be useful information for anyone investigation this issue.

uphillbattle commented 4 years ago

Additional information 2: Tested some more:

Starting the config checker from Android or iOS companion app: 'no error found'

Starting the config checker from a Chrome browser (accessing the front end via the Nabu Casa remote link) on Android or Win10: 'sqlalchemy' missing.

It appears that the result of the config checker depends on from where the config checker is started, which does not make sense to me as I assume the config checker actually runs on the Intel NUC regardless of from where I start it.

uphillbattle commented 4 years ago

No error reported by the config checker for HA version 0.103.2

dgomes commented 4 years ago

Does that mean we can close the issue :) ?

uphillbattle commented 4 years ago

It is no longer a problem for me, but in case you felt that the inexplicable behavior reported above warrants further investigation, I did not close the issue myself but left it up to you. ;)

dgomes commented 4 years ago

I still think it was related to the issue I mentioned. Closing it for now