I have Raspberry P3+, HA 64-bit version, and all latest two upgrades went well without no errors.
I have only one problem to run Glances but finally it works.
I have the same issue. Either the limitlessled or the scene config is the cause.
Have you figured out any solution?
The scene config has changedâŚ
Use brightness: instead of brightness_pct,
use color_temp: (in mireds) instead of kelvin:,
use rgb_color: instead of color_name:,
and dont use transition:. If you want to specify a transition you will have to use a script instead of a scene.
I had the same experience and this is what I did to restore my last working version:
With 18 Potential breaking changes in hass.io 0.101.2 that broke down my working Hassio:
Things to do when restoring from SSH:
- Always make a full snapshot before upgrading and save it externally
- Read logs after failing - hassio ha logs
- If database error then delete db file - rm /config/home-assistant_v2.db
- Stop hassio - hassio hassos stop
- Find latest working snapshop no. - hassio snapshot
- Restore latest working snapshot - hassio snapshot restore âxxxxxxâ
- Wait until Web UI is back up
1 Like
Thanks a lot, I will save your message for next update.
I was able to restore to 0.100.3, still unable to update to 0.101.2
I can only with a basic configuration, not my regular one. I think itâs a weird issue, not easy to find the cause
Can you please elaborate, just checking clues for my problem of mot bering able to upgrade
Am I invisible? 
Look at the post directly below Davidâs.
1 Like
not sure if Ive missed it above, so please forgive me for asking if we still need to use the
device_class: battery
on the Ikea remotes and motion sensors. I hd that set through customize, to have the icon change according to the battery_level.
Do the changes in 101 also apply to the wireless dimmer, next to the mentioned remote and motion sensor?
thanks for having a look
does anyone else see failed logins and bans for 192.168.1.1 again on 101? after upgrading I get this:
while my config is using:
auth_providers:
- type: homeassistant
- type: trusted_networks
trusted_networks:
- 127.0.0.1
- 192.168.1.0/24
Thanks for pointing out the scene breaking changes, I missed that.
I made changes in my config, but still no luckâŚ
If I check my config against the the next version (v0.101.2) the same error stayed. Iâm in v0.100.3.
ERROR:homeassistant.scripts.check_config:BURB
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/homeassistant/scripts/check_config.py", line 206, in check
async_check_ha_config_file(hass)
File "/usr/local/lib/python3.7/asyncio/base_events.py", line 579, in run_until_complete
return future.result()
File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/check_config.py", line 140, in async_check_ha_config_file
p_validated = component_platform_schema(p_config)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 272, in __call__
return self._compiled([], data)
File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 205, in _run
return self._exec(self._compiled, value, path)
File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 285, in _exec
v = func(path, v)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
return schema(data)
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/scene/__init__.py", line 46, in _platform_validator
return platform.PLATFORM_SCHEMA(config)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 272, in __call__
return self._compiled([], data)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
return base_validate(path, iteritems(data), out)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 386, in validate_mapping
cval = cvalue(key_path, value)
File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 205, in _run
return self._exec(self._compiled, value, path)
File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 285, in _exec
v = func(path, v)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 635, in validate_sequence
cval = validate(index_path, value)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 594, in validate_dict
return base_validate(path, iteritems(data), out)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 386, in validate_mapping
cval = cvalue(key_path, value)
File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 205, in _run
return self._exec(self._compiled, value, path)
File "/usr/local/lib/python3.7/site-packages/voluptuous/validators.py", line 285, in _exec
v = func(path, v)
File "/usr/local/lib/python3.7/site-packages/voluptuous/schema_builder.py", line 817, in validate_callable
return schema(data)
File "/usr/local/lib/python3.7/site-packages/homeassistant/components/homeassistant/scene.py", line 37, in _convert_states
if isinstance(states[entity_id], dict):
KeyError: 'light.teglafal'
Fatal error while loading config: 'light.teglafal'
Failed config
General Errors:
- 'light.teglafal'
and my corrected scene config now:
scene:
##NAPPALI VILĂGĂTĂS SCENE##
- name: Livingroom normal
entities:
light.Teglafal:
state: on
#transition: 3
rgb_color: [255, 227, 213]
brightness: 255
light.Bar:
state: on
#transition: 1
rgb_color: [228, 202, 255]
brightness: 255
light.Vaszon:
state: on
#transition: 1
rgb_color: [255, 234, 210]
brightness: 255
light.Kanape:
state: on
#transition: 1
rgb_color: [255, 234, 210]
brightness: 255
input_select.light_scene:
option: NormĂĄl
- name: Livingroom dim
entities:
light.Teglafal:
state: on
#transition: 5
brightness: 1
rgb_color: [255, 234, 210]
light.Bar:
state: on
#transition: 2
brightness: 1
rgb_color: [228, 202, 255]
light.Vaszon:
state: on
#transition: 2
brightness: 1
rgb_color: [255, 234, 210]
light.Kanape:
state: on
#transition: 2
brightness: 1
rgb_color: [255, 234, 210]
input_select.light_scene:
option: Minimal
- name: Livingroom movie
entities:
light.Teglafal:
state: on
#transition: 10
brightness: 1
rgb_color: [15, 0, 150]
light.Bar:
state: on
#transition: 2
brightness: 1
rgb_color: [0, 136, 36]
light.Vaszon:
state: on
#transition: 2
brightness: 1
rgb_color: [15, 0, 150]
light.Kanape:
state: on
#transition: 2
brightness: 1
rgb_color: [15, 0, 150]
input_select.light_scene:
option: Mozi
- name: Livingroom off
entities:
light.Teglafal:
state: off
light.Bar:
state: off
light.Vaszon:
state: off
light.Kanape:
state: off
light.Bridgeled:
state: off
input_select.light_scene:
option: Ki
- name: Livingroom 50
entities:
light.Teglafal:
state: on
#transition: 3
brightness: 127
rgb_color: [255, 234, 210]
light.Bar:
state: on
#transition: 2
brightness: 127
rgb_color: [228, 202, 255]
light.Vaszon:
state: on
#transition: 2
brightness: 127
rgb_color: [255, 234, 210]
light.Kanape:
state: on
#transition: 2
brightness: 127
rgb_color: [255, 234, 210]
input_select.light_scene:
option: 50%
What am I missing?
Your entity ids should not have capital letters in them.
1 Like
Thank you for that tip. This did solve it for me.
I had 1 scene file which I changed ONLY the uppercase letter to lowercase as below.
FROM
name: All OFF
entities:
group.Livingroom:
state: off
group.Kitchen:
state: off
TO:
name: All OFF
entities:
group.livingroom:
state: off
group.kitchen:
state: off
After this 0.101.2 installed and upgraded successfully.
Thank you, it worked for me too!
I had to change my input_select part too, from option: to state:
After that the upgrade went fine.
Hi, what is this?
IS the below input_select wrong?
marantz_video_select:
name: 'Source:'
options:
- Firestick
- Chromecast
- Games
- Internet Radio
- TUNER
initial: Firestick
icon: mdi:speaker-wireless
No, itâs fine.
I use input_select in a scene, I had to change there like this:
scene:
- name: Livingroom normal
entities:
light.Teglafal:
state: on
#transition: 3
rgb_color: [255, 227, 213]
brightness: 255
input_select.light_scene:
state: Minimal
still puzzled by the now called âimproved scene supportâ, which truly feels like the opposite. Why are all these nice features deprecated now? Transition, profile, brightness_pct⌠No reason or outlook for the better is presented unfortunately.
checking https://github.com/home-assistant/home-assistant/pull/27182 mentions workarounds, but they are not to be found. Especially the transition, which is deeply missed.
Sure we can write scripts, by the ease of scenes was to not having to write scriptsâŚ
3 Likes
Light scene support will temporarily support the turn_on service attributes with the release of 0.101.3 but will print deprecation warnings. This should make the transition smoother. These attributes will be removed in the future.
If you were using a scene as you would have used a script, you should use a script. The ease of scenes is that you take any current existing state and can reproduce it at a later point. This will be made even easier with the new scene editor.
How is using kelvin: (a much more easy to understand unit than mireds) using a scene âas I would a scriptâ?
2 Likes
I feel the same way, how is this not a breaking change, my scenes are now⌠broken.
1 Like