Don’t add anything, just wait for it to magically fix itself for this one 
When I try to install component, I’m receiving following error into the log (during configuration validation):
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
resp = await task
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/app/homeassistant/components/http/real_ip.py", line 33, in real_ip_middleware
return await handler(request)
File "/usr/src/app/homeassistant/components/http/ban.py", line 68, in ban_middleware
return await handler(request)
File "/usr/src/app/homeassistant/components/http/auth.py", line 216, in auth_middleware
return await handler(request)
File "/usr/src/app/homeassistant/components/http/view.py", line 115, in handle
result = await result
File "/usr/src/app/homeassistant/components/config/core.py", line 21, in post
errors = await async_check_ha_config_file(request.app['hass'])
File "/usr/src/app/homeassistant/config.py", line 785, in async_check_ha_config_file
check_ha_config_file, hass)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/app/homeassistant/scripts/check_config.py", line 332, in check_ha_config_file
component = loader.get_component(hass, domain)
File "/usr/src/app/homeassistant/loader.py", line 148, in get_component
comp = _load_file(hass, comp_or_platform, LOOKUP_PATHS)
File "/usr/src/app/homeassistant/loader.py", line 183, in _load_file
module = importlib.import_module(path)
File "/usr/local/lib/python3.7/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
File "<frozen importlib._bootstrap>", line 983, in _find_and_load
File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 724, in exec_module
File "<frozen importlib._bootstrap_external>", line 860, in get_code
File "<frozen importlib._bootstrap_external>", line 791, in source_to_code
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "/config/custom_components/breaking_changes/__init__.py", line 7
<!DOCTYPE html>You do not have python files, if you download directly from github you need to use the RAW format.
I’m running in HA in docker. Could you please advice how to use RAW format?
Thanks! This solve the issue
Just today I started getting these entries in the log at about once a minute:
2019-05-16 04:44:25 ERROR (MainThread) [custom_components.breaking_changes] Could not update data - Expecting value: line 1 column 1 (char 0)
2019-05-16 04:45:30 ERROR (MainThread) [custom_components.breaking_changes] Could not update data - Expecting value: line 1 column 1 (char 0)
2019-05-16 04:46:36 ERROR (MainThread) [custom_components.breaking_changes] Could not update data - Expecting value: line 1 column 1 (char 0)
2019-05-16 04:47:42 ERROR (MainThread) [custom_components.breaking_changes] Could not update data - Expecting value: line 1 column 1 (char 0)
2019-05-16 04:48:48 ERROR (MainThread) [custom_components.breaking_changes] Could not update data - Expecting value: line 1 column 1 (char 0)
Any idea’s why?
According to the custom_updater the component is up to date (0.1.0) and I’m on HA v92.2.
thanks for the link. At least I know it’s not just me.
What a great add-on. I can see that it is working and now I can upgrade to 0.93 from 0.92.2 without being disappointed like I did when I upgraded to 0.91.4 with serious breaking changes.
Now the add-on shows this fine description of possible breaking changes:
1 Like
Hey, is there any reason the binary sensor was removed in the latest update?
I am guessing, but the binary_sensor doesn’t tell you anything the sensor does.
As in your example I copied all files into “custom_components / breaking_changes /” and made the entry “breaking_changes” in the configurations.yaml.
However, the entity “sensor.potential_breaking_changes” always outputs only the value 0. I currently use hassio 0.94.1. But I have the problem a bit longer.
Do I have to add or add something else somewhere?
When you are on the latest version it is expected to show 0
Can you provide a good way to display the breaking changes on lovelace.
Currently I am using something like this, which should look good in theory but not in practice. As I have yet to show the information inside json. Thank you.
- type: custom:fold-entity-row
head: sensor.potential_breaking_changes
title: Breaking Changes
items:
- type: custom:entity-attributes-card
entity: sensor.potential_breaking_changes
heading_name: ID
heading_state: Changes
filter:
include:
- sensor.potential_breaking_changes.*
exclude:
- sensor.potential_breaking_changes.icon
- sensor.potential_breaking_changes.friendly_nameI may be the worst person to ask.
My UI
There are some amazing folks that usually hang out in the #lovelace channel on Discord, that might be able to help
https://discord.gg/c5DvZ4e
1 Like
Ok, but at the latest when 0.94.2 comes out soon, then I would have to see something?
no, there are no breaking changes in a point release.
Okay, then I see something again at 0.95.