2021.11: Icon picker, device links and entity categories

i didnt reply to your post

1 Like

Oops, my bad had a night shift so I am not that sharp at the moment, sorry.

all good, i know the feeling well

Fritz or SyncWorker (?) is now writing debug-log

2021-11-04 10:39:08 DEBUG (SyncWorker_3) [fritzconnection] <?xml version="1.0"?>
etc.
etc.

Any reason for this or way to switch this off? There are now thousends of lines (99%) in the log because of this.

there is already a ticket open

as a workaround add this to your configuration

logger:
  default: info
  logs:
    fritzconnection: info
1 Like

For those with the Media Control issue: if you remove the integration displaying the Media Control, all the missing pieces seems to be back on the dashboard.

But, if you add the integration back, Sonos in my case, everything close to the Media Control disappear againā€¦

So far Iā€™m not able to find what happened exactly with the Media Controlā€¦

Same for me ā€¦ found any solution? It has always worked before for me.
Does it has anything to do with the datacenter selection ?

Hi, I have the same problem.

Same here.
Tuya login error response: {ā€˜codeā€™: 1106, ā€˜msgā€™: ā€˜permission denyā€™ā€¦

1 Like

Hi, receive now this warning:

WARNING (MainThread) [homeassistant.helpers.template] Template warning: 'int' got invalid input 'None' when rendering template '{{ ( state_attr('sensor.xxx', '4503') | int(base=16) / 90 * 255 ) | int }}' but no default was specified. Currently 'int' will return '0', however this template will fail to render in Home Assistant core 2022.1

This is the code:

level_template: "{{ ( state_attr('sensor.xx', '4503') | int(base=16) / 90 * 255 ) | int }}"

if i change to below, i still see the error, what am i missing?

level_template: "{{ ( state_attr('sensor.xx', '4503') | int(base=16) / 90 * 255 ) | int(default=0 }}"

same here. canā€™t add (again, since it is gone with the update) tuya, that was added in prev version.

Same here , previously working well on Hassio-coreā€¦

I do notice that Smart life region is isle of man/United Kingdom and Hassio fields only offer United Kingdom but think that probably a red herring as Everyone reporting this complete failure is not from UK.

The New Tuya core is having a very rough start despite some Sterling efforts from the developers , Iā€™m afraid the update is going to bite most with a completely broken Tuya.

Despite completely re-installing everything I now have no Tuya integration as the Tuya-core will not get past 1106 error despite all Username/Passwords and regions being correct.

There is also an entity which you can use to check: binary_sensor.home_assistant_operating_system_update_available

did anyone having a same problem with me? where the lovelace dashboard (some) is just vanish. The original yaml is still there but cant edit nor retype, it just gone.

2 Likes

It has been reported here already

For me the Media Control Card fails to load because of the custom card Atomic Calendar Revive:

https://github.com/totaldebug/atomic-calendar-revive

It seems to do with the definition of a custom element. Depending whcih card loads first, it will prevent the other from loading. This is from the debug window in Firefox v93.0:

Uncaught (in promise) DOMException: CustomElementRegistry.define: 'mwc-linear-progress' has already been defined as a custom element

Removing Atomic Calendar Revive fixes the issue of the Media Control Card not loading. Iā€™ll post an issue on the ACR cardā€™s git-hub.

4 Likes

Others are saying itā€™s media_control thatā€™s causing that. Also can be caused by custom cards

Oh my! Youā€™re a lot better than me in debugging!

I have also this custom card, which I like a lot!

Can you give us the link to the issue? Maybe we can help to fix this?

1 Like

Can someone who has the medi-control issue write it up on GitHub please? I would write it up but I do not have the issue and I cannot replicate it. Thanks.

EDIT: Please make sure to include screenshots of the developer window in chrome. To access it, hit F12 on your keyboard, then make sure the bottom tab is displaying the console. Make sure to take a screenshot of the console. Thanks.

True, but that was for the core 2021.10.6 and I did not have that problem with 2021.10.6, it even logged in with 2021.11.0 for a good half hour, till I restarted HA and then integration couldnā€™t login anymore. But it is active in that report again.

I am configuring LocalTuya again, but I couldnā€™t get the local keys either CLI Wizard has also login error, finally I found my old document with all the keys, so adding everything one by one, to be honest I would love to go with core version of the integration, we will see, it will be solved at the end I think.