I have run check_config on all 2012.3.x releases and have what appear to be 2 failures. I have raised an issue against the second one but I’m not technical to understand the errors. I have not upgraded. I’d like to understand if anyone else is seeing the issues and what can be done about them please:
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
aiohttp 3.7.4 requires chardet<4.0,>=2.0, but you'll have chardet 4.0.0 which is incompatible.
[08:32:23] ERROR: The configuration check did not pass!
[08:32:23] ERROR: See the output below for more details.
Testing configuration at /tmp/config
WARNING:homeassistant.components.http:The 'base_url' option is deprecated, please remove it from your configuration
ERROR:homeassistant.helpers.check_config:Unexpected error validating config
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/homeassistant/helpers/check_config.py", line 147, in async_check_ha_config_file
await config_validator.async_validate_config( # type: ignore
File "/usr/local/lib/python3.8/site-packages/homeassistant/components/automation/config.py", line 103, in async_validate_config
await asyncio.gather(
File "/usr/local/lib/python3.8/site-packages/homeassistant/components/automation/config.py", line 85, in _try_async_validate_config_item
config = await async_validate_config_item(hass, config, full_config)
File "/usr/local/lib/python3.8/site-packages/homeassistant/components/automation/config.py", line 63, in async_validate_config_item
config[CONF_TRIGGER] = await async_validate_trigger_config(
File "/usr/local/lib/python3.8/site-packages/homeassistant/helpers/trigger.py", line 49, in async_validate_trigger_config
conf = await platform.async_validate_trigger_config(hass, conf)
File "/usr/local/lib/python3.8/site-packages/homeassistant/components/device_automation/trigger.py", line 21, in async_validate_trigger_config
Following David’s response to my post I took the plunge and upgraded. It was successful, which is a relief. I am a little concerned about the first message in my previous post (repeated below) and what needs to be done to avoid issues in the future, does anyone know?
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
aiohttp 3.7.4 requires chardet<4.0,>=2.0, but you'll have chardet 4.0.0 which is incompatible.
With the fans changing to percentages, will integrations have to map them to the set speeds the fans require? Most fans have set speeds because they hum if treated like a dimmer. So I’m uncertain if you set to 25%, if that is intended now to just map to the closest speed for that particular device?
ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.
We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.
It’s not an error. Pip is just trying to get attention by calling it an error. It’s really just a info or a warning.
And for
aiohttp 3.7.4 requires chardet<4.0,>=2.0, but you'll have chardet 4.0.0 which is incompatible.
It’s a common thing, from my knowledge. Another package requires a newer version of the library chardet, but aiohttp wants an older version. Of course, it could be a problem, but chances are that HA doesn’t use the functionality that works better with the older version.
I asked a similar question above and got no response.
I’m not really sure who thought that it was easier to remember which fan speeds now correlate to which percentages (use “set fan to 20%” instead of “set fan to low”) but I think I know what my fans speeds are.
Now I have to figure out which percentages correlate to which speeds and then set up my fan templates to use those percentages instead. Or even worse I need to figure out what the correct percentages are for fan integrations I don’t set up (like my ZHA fan) to get it to work.
For example the mqtt fan still has a “speeds:” list. What happens if I now use the new “fan.set_percentage” service and set the fan to 50%? What speed will my fan be set to? low or medium? Or if I use 75%? Medium or high? At what percent is “off”? if I set the fan to 10% will the fan be off or low.
What constrains me (or anyone else who didn’t actually program anything - wife, kids, guests) from giving a fan a percentage that it doesn’t “know”? or knowing what percentages equal which speeds?
I don’t get the new “all or nothing” mentality that seems to be setting in.
Why can’t there be both - speeds and percentages - to maintain backwards compatibility between the existing integrations and those who want or need the percentages? We already have similar functionality with lights (set “brightness” or “brightness_pct”) and covers (value_template or position_template). There should be some way to keep speeds if you want or use the percentages if you want.
I use to paste as it is very long.
Before the update there was no problem showing it, but i am having a big headache trying to understand why it is not shown in the frontend. I doubled checked all the entries, all the entities, all the cards and all the sensors, but nothing to do, i also cleared cache too many times…
Users should have to click that they have read and understood it. It is basic tech forum know-how, but this often seems to be the first tech forum for many users.
In fairness a lot of the new ‘target audience’ aren’t even capable of copying and pasting, so the idea of them complying with most of the suggestions to ‘ask a good question’ is a stretch
So I don’t think you have to worry about this but I’m not familiar with mqtt fan so it may be different. I had a few template fans in my setup and all I did was this:
Replace any reference to speed with preset_mode (literally just find and replace, clean switch)
Remove off from the list of preset_modes. You turn the fan off using turn_off, any preset mode is condiered on
Adjust my preset_mode_template to ignore the removed off option (just return '' when that is what is selected)
I didn’t add a percentage_template or acknowledge it in anyway and my fans now work fine. I just use preset_mode like I used to use speed.
It was nicer to have a dropdown of all the options instead of having a dropdown of all the on options and a nameless turn_off option. But its not much different in the end.
Although one thing I’m not doing currently is exposing any of the fans I have to google assistant. I would hope you would still be able to address the preset modes in a voice assistant and not have to know the percentages otherwise that would not be a good experience for the reasons you outlined.
The concern about the voice control was caused by this from the breaking changes:
Additionally, it’s a lot easier to ask your voice assistant to set the fan to 20% then remember that medium-low is actually low-medium or have to learn and remember how to say the speeds for every fan model you want to control.
Yep, good point, forgot it said that. So I decided to test it and exposed one of my fans to google assistant just now to see what happened. Looks like I’m only able to turn it on and off, can’t figure out any way to change to a preset mode (even manually typing in commands). I also couldn’t change the percentage, maybe if you don’t provide a percentage_template it tells google its an on/off only fan?
I can’t make a before and after comparison here since I didn’t have a fan exposed to google assistant prior to this. Also behavior could be different on other voice assistants, not sure which you use.
That does seem like a potential pain point though. Definitely much easier to use names if your fan doesn’t actually support setting to a specific percent speed.
me too, please help as i have many devices use this feature to send V_TEXT message.
i use Node-red to send notify.mysensors but now i get “Call-service API error. Error Message: Service not found.”
