Closed ruimarinho closed 5 years ago
Had a quick look at the changelogs (0.65 to 0.67) and did not see something that could have break the component Was this config working previously ?
Update : did upgrade to 0.67.1 --> everything is working fine with release 0.13.post2 (just released with latest commits if you want to try)
Thanks @elric91 - to be clear, the component itself works (0.67.1 works fine for me as well), it's just the check_config
command that isn't loading the component correctly. I have other custom components working fine, so my guess is that it's something related to the way to the component is setup.
See https://travis-ci.org/ruimarinho/home-assistant-config/builds/369629737 for the test build using 0.13.post2.
Strange .. I tested a fresh build (0.67.1 / 0.13.post2)
hass --config ~/.homeassistant/ --script check_config Testing configuration at /home/zzz/.homeassistant/
no complaints from the script ... don't know just a guess : are the authorizations on your custom_component/sensor/zigate.py OK from the perspective of the user who launches the test in travis ?
Hi,
Same problem here with HASS 0.71.0 and the last version of component
Build : https://travis-ci.org/acesyde/Home-Assistant/builds/394987048 Repo : https://github.com/acesyde/Home-Assistant
Latest version of the component and latest version of HASS... No issues here.
Tested with HASS 0.82.1 without issues. If issues appear again reopen or create new issue.
My config loads and runs fine on HASS but testing config has been broken since the installation of zigate as a custom component.
If I run:
The output is:
The custom sensor file is available at
custom_components/sensor/zigate.py
. Any ideas whycheck_config
isn't picking up the custom version?