Core: check_config failing with "platform not found" device_tracker.nmap_tracker

[aneisch]

Home Assistant release with the issue: 0.96

Last working Home Assistant release (if known): N/A

Operating environment (Hass.io/Docker/Windows/etc.):
Centos 7
Python 3.6.8
Travis-ci

Component/platform: Core script check_config

Description of problem: hass -c . --script check_config -i -f reports "platform not found" for built-in components. I _suspect_ this is due to check_config not installing the required dependencies.

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

device_tracker:
  - platform: nmap_tracker
    home_interval: 10
climate:
  platform: radiotherm
  host:
    - 10.0.1.29
  hold_temp: True

Traceback (if applicable):

Failed config
  General Errors: 
    - Platform not found: device_tracker.nmap_tracker
    - Platform not found: climate.radiotherm

Additional information:
Additional details can be seen in travis log https://travis-ci.org/aneisch/home-assistant-config/builds/560537477

[Limych]

The same error with my config. This part of the code has not changed for a long time and has never caused errors before. Errors began to appear with HA version 0.96.0

https://travis-ci.org/Limych/HomeAssistantConfiguration/builds/560355096

[fronzbot]

Yep, I'm having the same issue. Specifically with climate.radiotherm. Removing the climate section from my config allows the config checker to pass. I should note, my home assistant install with radiotherm works perfectly fine and this is definitely an issue with the config checker script.

Here's my failing travis build --> https://travis-ci.org/fronzbot/githass/jobs/561038310
And my now passing travis build with the band-aid --> https://travis-ci.org/fronzbot/githass/jobs/561059805

Current iteration of my travis script --> https://github.com/fronzbot/githass/blob/master/.travis.yml

@frenck - you changed the title, but it's not quite correct. It's an issue with both device_tracker.nmap_tracker and climate.radiotherm according to OP's logs.

[Midnitte]

Still experiencing this in 0.96.2.

Just upgraded from 0.95.4 and get

Failed config
  General Errors:
    - Platform not found: device_tracker.nmap_tracker

[bieniu]

pip install getmac==0.8.1 fix this issue. I don't know why HA doesn't install this package automatically.

[Midnitte]

Looks like that fixed my issues with nmap, thanks!

[Limych]

Even if some additional commands correct situation, this error will cause problems with the installation HA for new users. That shows via testing on Travis - the system is put there from scratch every time.

Therefore, I consider it relatively serious error.

[eifinger]

I encountered the same problem with a custom component and found out:

• The check_config script only fails if homeassistant is installed via pip, not if installed from source (git)
• Starting homeassistant does not throw this error when it was installed via pip
• hass.io users do have an error when starting. This can be fixed by restarting a second time
• I could only see this behaviour after I changed my component to use top level imports instead of at function/class level

[HtownTexans]

My Hass.io installed in Ubuntu 18.04 docker receives this message and a restart does not fix it. I don't see it causing any errors to my actual nmap and only see the error if I run the config checker.

[aneisch]

The check_config script only fails if homeassistant is installed via pip, not if installed from source (git)

@eifinger can you expound upon this?

[eifinger]

@aneisch

Prerequisite

Have a config directory with the custom_component configured lets call it /my_conf

Installation with pip

```bash
cd /hass
python3 -m venv venv
source venv/bin/activate
pip install homeassistant
hass -c ../my_conf --script check_config --info all
````

-> platform not found error

Installation from source

```bash
git clone https://github.com/home-assistant/home-assistant/ /hass
cd /hass
python3 -m venv venv
source venv/bin/activate
script/setup
hass -c ../my_conf --script check_config --info all
````

-> all is well

[fronzbot]

@eifinger the errors with climate.radiotherm I posted earlier on this thread are not associated with a custom component. The problem you had is likely related, but not the same. Either way, just because it's fixed by changing the installation method doesn't mean it's not a bug.

[shortbloke]

nmap issue appears to be fixed in 0.97
At least I was able to do a config check, a TravisCI build with my config and an update from 0.95.4 to 0.97.0 without issue now.

[aneisch]

My travis build shows this now. No more entries about nmap though:
- Unable to install all requirements: homeassistant-pyozw==0.1.4, pydispatcher==2.0.5

[fronzbot]

Try adding the following in the before_install section of .travis.yml:

sudo apt-get update && sudo apt-get install -y libudev-dev 

Fixed the issue for me when I saw that crop up.

[aneisch]

Try adding the following in the before_install section of .travis.yml:

sudo apt-get update && sudo apt-get install -y libudev-dev 

Fixed the issue for me when I saw that crop up.

Worked perfect. My custom component is still failing but I will just comment the component line out in before_install.

[aneisch]

This appears to now be resolved in 0.97.