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
2018-01-16 08:08:52 ERROR (MainThread) [homeassistant.loader] Unable to find component broadlink
2018-01-16 08:08:52 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/home/hass/homeassistant/lib/python3.5/site-packages/homeassistant/components/websocket_api.py", line 473, in get_services_helper
descriptions = yield from async_get_all_descriptions(self.hass)
File "/home/hass/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/service.py", line 153, in async_get_all_descriptions
yaml_file = domain_yaml_file(domain)
File "/home/hass/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/service.py", line 137, in domain_yaml_file
component_path = path.dirname(get_component(domain).__file__)
AttributeError: 'NoneType' object has no attribute '__file__'
Additional info:
Worked with 0.60.1, now I cant get the UI to load at all if I have the broadlink component in the config
The text was updated successfully, but these errors were encountered:
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (
hass --version
): 0.61Python release (
python3 --version
): 2.7.13Component/platform:
Description of problem: HA won't load if broadlink component is in the config
Expected: Expected HA to start up normally
Problem-relevant
configuration.yaml
entries and steps to reproduce:Traceback (if applicable):
Additional info:
Worked with 0.60.1, now I cant get the UI to load at all if I have the broadlink component in the config
The text was updated successfully, but these errors were encountered: