2021.3: My Oh My

finity · March 9, 2021, 12:11am

And unfortunately from the lack of “official” responses here after asking a few times it looks like we’re on our own.

And again, why would the speed controls be deprecated? They seem to be working fine together right now. Why the need to remove that functionality?

Let the people who want to use the percentages or presets use those and let the people who want to use speeds use those. I haven’t tested the new version with my Echo’s yet (not home) so I don’t know if there will be an issue there with the current functionality.

cybergrimes · March 9, 2021, 1:07am

Someone got a working fan template for those of us that are based on the brightness attribute of a light entity in another thread. It works but it complains about the off position (because no brightness data when light is off). I was told to add a default to the operation but it still complains in the log. It would be nice to just have the regular speed list back (in addition to the new percentage slider too of course)

If there’s a way to still have drop down in our case… examples would be very appreciated

mnl1121 · March 9, 2021, 1:08am

This update broke controlling my zwave fans with Alexa. Saying “set office fan to low” sets the my GE fan control switch to 33%, but to it, that is medium, not low. Why was the fan presets removed and the percentages added? Percentages should have been added and the presents left intact.

Can we get a fix please?

Tarass_Gribuks · March 9, 2021, 1:21am

Yes, I have opened the one, but with new update the problem still there… Without proper editor I cannot use new version.

walaj · March 9, 2021, 1:38am

@mirekmal - did you resolve your issue with ConditionErrorMessage(“zone”, “no zone specified”) ?

I’m getting a similar error, but for a different geo system:

2021-03-09 10:09:50 ERROR (MainThread) [homeassistant.helpers.event] Error while processing event <Event state_changed[L]: entity_id=geo_location.rfs_wallgrove_rd_eastern_creek, old_state=None, new_state=<state geo_location.rfs_wallgrove_rd_eastern_creek=26.7; latitude=-33.81448, longitude=150.85146, source=nsw_rural_fire_service_feed, external_id=https://incidents.rfs.nsw.gov.au/api/v1/incidents/409965, category=Not Applicable, location=Wallgrove Rd, Eastern Creek, NSW 2766, attribution=State of New South Wales (NSW Rural Fire Service), publication_date=2021-03-09T09:58:00+11:00, council_area=Blacktown, status=Out of control, type=MVA/Transport, fire=False, size=0 ha, responsible_agency=Fire and Rescue NSW, unit_of_measurement=km, friendly_name=Wallgrove Rd, Eastern Creek, icon=mdi:alarm-light, hide_attributes=['templates'] @ 2021-03-09T10:09:50.263905+11:00>> for domain geo_location
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/helpers/event.py", line 416, in _async_dispatch_domain_event
    hass.async_run_hass_job(job, event)
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/core.py", line 435, in async_run_hass_job
    hassjob.target(*args)
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/components/geo_location/trigger.py", line 55, in state_change_listener
    to_match = condition.zone(hass, zone_state, to_state) if to_state else False
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/helpers/condition.py", line 668, in zone
    raise ConditionErrorMessage("zone", "no zone specified")
homeassistant.exceptions.ConditionErrorMessage: In 'zone' condition: no zone specified
2021-03-09 10:09:50 ERROR (MainThread) [homeassistant.helpers.event] Error while processing event <Event state_changed[L]: entity_id=geo_location.rfs_wallgrove_rd_eastern_creek, old_state=None, new_state=<state geo_location.rfs_wallgrove_rd_eastern_creek=26.7; latitude=-33.81448, longitude=150.85146, source=nsw_rural_fire_service_feed, external_id=https://incidents.rfs.nsw.gov.au/api/v1/incidents/409965, category=Not Applicable, location=Wallgrove Rd, Eastern Creek, NSW 2766, attribution=State of New South Wales (NSW Rural Fire Service), publication_date=2021-03-09T09:58:00+11:00, council_area=Blacktown, status=Out of control, type=MVA/Transport, fire=False, size=0 ha, responsible_agency=Fire and Rescue NSW, unit_of_measurement=km, friendly_name=Wallgrove Rd, Eastern Creek, icon=mdi:alarm-light, hide_attributes=['templates'] @ 2021-03-09T10:09:50.263905+11:00>> for domain geo_location
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/helpers/event.py", line 416, in _async_dispatch_domain_event
    hass.async_run_hass_job(job, event)
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/core.py", line 435, in async_run_hass_job
    hassjob.target(*args)
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/components/geo_location/trigger.py", line 55, in state_change_listener
    to_match = condition.zone(hass, zone_state, to_state) if to_state else False
  File "/srv/homeassistant/lib/python3.8/site-packages/homeassistant/helpers/condition.py", line 668, in zone
    raise ConditionErrorMessage("zone", "no zone specified")
homeassistant.exceptions.ConditionErrorMessage: In 'zone' condition: no zone specified

cybergrimes · March 9, 2021, 2:01am

Thanks again for the help in the other thread.
Here’s what my fan looks like in Alexa now

I don’t recall the interface in the app before so don’t know if these sliders were always here before but using voice commands it’s only responding to “set fan to number” with number being the percent. There’s a slider on the bottom for fan speed 0 - 3 but it’s not controlling anything, just updating after the fact…

finity · March 9, 2021, 2:23am

So if you say “set fan to low” it doesn’t work and makes you set a percentage value?

That’s what I was hoping against.

cybergrimes · March 9, 2021, 2:49am

Right, fan does nothing which makes sense there’s no speed list anymore.

the logbook shows this

Amazon Alexa send command Alexa.RangeController/SetRangeValue for Living room fan by Home Assistant Cloud

and the log shows it’s using fan.set_speed, complains about it being deprecated

walaj · March 9, 2021, 3:56am

Replying to myself, found the issue.

My code for handling zones referenced a zone that didn’t actually exist. 2021.3 has https://github.com/home-assistant/core/pull/46253 which now raises an error that was silently ignored in the past. Fixed my code, and going to recommend the error be “enhanced” to say which zone doesn’t actually exist.

sparkydave · March 9, 2021, 7:03am

At we at the point of tagging the major players for attention to this fan issue?
I won’t be updating until there is a solution, which I’m not happy about because I like meeting things up to date

Eltjo_de_Waard · March 9, 2021, 7:09am

Thanx for another update! But when I did the update I see the following " Translation Error: The intl string context variable “naam” was not provided to the string “Herstart {naam}”

Translation Error: The intl string context variable “naam” was not provided to the string “Weet u zeker dat u {naam} opnieuw wilt starten?”"

This was also with the previous update.

Update was executed.

jjdave2020 · March 9, 2021, 7:30am

yes, I do get daily error message due to troubles with snapshot --> tar.file.

Any idea how to solve this? Thx

mirekmal · March 9, 2021, 7:51am

Thanks a lot for the hint! Indeed I was doing some housekeeping on entities names recently and I changed the name of one zone, that I forgot to rename also in automation… now the log is clear of these messages!

jeanbart · March 9, 2021, 9:54am

Got ‘Unknown error’ see supervisor log…

this happened every update since 2021.3. manageged to update anyway trough 2021.3.1 and 2021.3.2 but getting stuck at 2021.3.3 any solution?

(edit: It seems when i disable the snapshot option at the update… I still get the error, but manage to update somehow)

tom_l · March 9, 2021, 9:57am

Please open an issue.

Tuxinator94 · March 9, 2021, 12:29pm

Not sure if this is the same problem. This solved my problem by defining fields in my script. Documentation: https://www.home-assistant.io/integrations/script#fields
My ticket that lead to the above: https://github.com/home-assistant/frontend/issues/8591

Tarass_Gribuks · March 9, 2021, 12:43pm

This has nothing to do with the scrolling bug by the editor…

finity · March 9, 2021, 1:22pm

The problem with opening an issue is that it’s not an issue. It’s a feature.

In order to get it changed it needs to be a feature request. And almost nobody looks at those.

I hope that wasn’t too “critical” and gets flagged too.

tom_l · March 9, 2021, 1:36pm

I would say this is an issue:

petro · March 9, 2021, 1:53pm

If low does not set it to 33% it’s an issue