2021.11: Icon picker, device links and entity categories

francisp · November 4, 2021, 2:45pm

Did you restart HA after removing Tuya v2 ? I think it is still active.

OmerAn · November 4, 2021, 2:48pm

Before tuya v2 upgrade, I took the pictures I removed specifically so that I would make the names the same. After upgrading to 2021.11 I rebooted and added it as tuya. The devices shown in the pictures were taken over Tuya v2 in the previous version.

francisp · November 4, 2021, 2:53pm

Ah, now I understand.

KenCote · November 4, 2021, 2:57pm

The MSSQL deprecation seems to have come rather suddenly and without much warning. This is kinda
a big deal for me personally. Is there a roadmap that we can see where this sorta stuff is shown? What’s the rationale behind this decision?

kksligh · November 4, 2021, 3:07pm

Since the update, all my media remotes, including Roku Card, Harmony Card, Mini Media Player and Fire TV Card…now dont visibly show most of the buttons. I’ve cleared my cache, tried different cards, changed from Light to Dark and even different themes - none of that fixes the issue. If I scroll over the card, you can see the functioning buttons are still there but they are not visible. See examples

kksligh · November 4, 2021, 3:10pm

Since the update, my Tuya integration stopped working. I tried to delete and re-log back in, and that didnt work. Here are the error logs:

Logger: homeassistant
Source: components/switchbot/entity.py:41
First occurred: 10:02:44 AM (1 occurrences)
Last logged: 10:02:44 AM

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 134, in _handle_refresh_interval
await self._async_refresh(log_failures=True, scheduled=True)
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 265, in _async_refresh
update_callback()
File “/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py”, line 325, in _handle_coordinator_update
self.async_write_ha_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 486, in async_write_ha_state
self._async_write_ha_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 519, in _async_write_ha_state
state = self._stringify_state()
File “/usr/src/homeassistant/homeassistant/helpers/entity.py”, line 492, in _stringify_state
if (state := self.state) is None:
File “/usr/src/homeassistant/homeassistant/components/sensor/init.py”, line 273, in state
value = self.native_value
File “/usr/src/homeassistant/homeassistant/components/switchbot/sensor.py”, line 96, in native_value
return self.data[“data”][self._sensor]
File “/usr/src/homeassistant/homeassistant/components/switchbot/entity.py”, line 41, in data
return self.coordinator.data[self._idx]
KeyError: ‘f232704d4231’

mgwright · November 4, 2021, 3:11pm

It is the same for my FireTV remote card (GitHub - marrobHD/firetv-card: 📺 FireTV Remote Card)

The buttons are there because you get a grey shadow if you hover over them but they don’t show up normally.

Ildar_Gabdullin · November 4, 2021, 3:20pm

Cannot add a simple test automation - getting “Response error: 500”, what could it be?

HA Docker.

OmerAn · November 4, 2021, 3:33pm

I finally made it. I did the operations on the Tuya Api side again, then I added it again via Home assistant. But the temperature sensor, siren sensor etc. is not supported. sample pictures;

Stooovie · November 4, 2021, 3:34pm

After a day of working fine on 2021.11, Tuya V2 stopped working.


Logger: homeassistant.config_entries
Source: components/tuya/__init__.py:66 
First occurred: 16:32:41 (1 occurrences) 
Last logged: 16:32:41

Error setting up entry [email protected] for tuya
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 304, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/tuya/__init__.py", line 66, in async_setup_entry
    hass.data[DOMAIN].pop(entry.entry_id)
KeyError: '4322beed26a09ecf05b8855bab1a92a3'

Stooovie · November 4, 2021, 3:36pm

Same. But it was NOT after the update. It worked fine for almost a full day on 2021.11, stopped working now.

shukkar · November 4, 2021, 3:45pm

My Tuya integration started giving me “1106” error (permission deny) after the update. Upon further digging, I found that I had chosen “Eastern America Data Center” when I created my cloud project on Tuya website. Apparently, Tuya has changed something so that my “Tuya Smart” Android app, doesn’t recognize “Eastern America Data Center” as valid data center. I had to change my cloud project to use “Western America Data Center”. For some reason, the old setting worked before the HASS upgrade. Not sure if the timing of upgrade and Tuya making some backend changes were co-incidental or that new integration uses different APIs and hence the issue appeared after the upgrade. Also, just adding “Western America Data Center” to the cloud project did not do the trick - I had to remove the “Eastern America Data Center”.

Anyway, hope this helps someone.

arganto · November 4, 2021, 3:51pm

Is this “More” new as well? Didn’t see this before and didn’t find this in the changelog

And secondly: Is the defaulting of int equal to float from the .10 now mandatory as well. Only found the breaking change for float in the release notes from .10, but neither for int there nor now in .11

In Home Assistant Core 2021.12 the template will fail to render if no default value is specified. You can specify a default value by passing to the filter like this: {{ "abc" | float(default=0) }}.

gonzotek · November 4, 2021, 3:51pm

Here’s where the conversation about the change took place:

github.com/home-assistant/architecture

ADR: Supported databases

home-assistant:master ← home-assistant:emontnemery-patch-1

opened 02:20PM - 20 Oct 21 UTC

emontnemery

+53 -0

We currently have no restrictions on supported database engines for the recorder…, and the documentation states: > Home Assistant uses SQLAlchemy, which is an Object Relational Mapper (ORM). This means that you can use any > SQL backend for the recorder that is supported by SQLAlchemy, like MySQL, MariaDB, PostgreSQL, or MS SQL Server. This claim is not correct, SQLAlchemy will behave differently on different databases, and features relied on by the recorder may work differently, or not at all, in different databases. We advertise a lot of different databases being supported, without version limitation mentioned. This causes the end-user to think their database and version of choice will work with Home Assistant. Unfortunately, that is not always the case; the user experience for those using a less popular database engine or an outdated version is very poor, with frequent issues preventing the recorder from working after an upgrade of Home Assistant. This ADR is limiting the supported databases in order to improve the experience, testability, maintenance, and provide clarity.

And the resulting Architecture Decision Record:

github.com

home-assistant/architecture/blob/3331ea0255844a46d2830f3d780672b37b5793ff/adr/0018-supported-databases.md

# 0018. Supported databases

Date: 2021-10-20

## Status

Accepted

## Context

We currently have no restrictions on supported databases for the recorder, and the documentation states:

 > Home Assistant uses SQLAlchemy, which is an Object Relational Mapper (ORM). This means that you can use any 
 > SQL backend for the recorder that is supported by SQLAlchemy, like MySQL, MariaDB, PostgreSQL, or MS SQL Server.

This claim is not correct, SQLAlchemy will behave differently on different databases, and features relied
on by the recorder may work differently, or not at all, in different databases. 

As a matter of fact, we have a lot of special handling for the different databases out there, which makes
maintenance and implementing changes really hard. For contributors, it is impossible to test changes against

This file has been truncated. show original

oldpizza · November 4, 2021, 3:52pm

After seeing covers were supported again in Tuya i bothered to try and setup the new integration as i only have a cover so didnt bother last month.

Unfortunately, when asking alexa to open/close the curtains, while it does work, the request must be made backwards, so open to close them and close to open them.

Via google no action can be made and i simply get told that the mode isn’t available for the device.

Not sure why the functionality would be exposed differently, both assistants were happy before the new integration, but i wouldnt have expected them to know/care about how home assistant controls the entity anyway.

andremain · November 4, 2021, 4:00pm

When are you guys planning to fix the alexa slow and unreliable response issues??

petro · November 4, 2021, 4:00pm

What are you talking about? Alexa works fine.

Stooovie · November 4, 2021, 4:06pm

Yes it is new.

Nameless · November 4, 2021, 4:16pm

I don’t think there are any official reports of problems that I’ve read, but I have experienced slow responses or no response for about a month now using Alexa as well. Google has been much more reliable, so I chalked it up to an Alexa issue.

I figured this was an issue on my end, so have been troubleshooting what I can. I also suspect it could be Amazon with an issue.

I’m biting my tongue and not calling it an HA issue until I know for sure.

petro · November 4, 2021, 4:19pm

Been working great on my end, but I’ve noticed that adblock home has been causing issues with it. I believe amazon has been moving the server endpoints around via updates.