2021.11: Icon picker, device links and entity categories

Blog
369

Hmm, thought I searched the site extensive enough
 Missed that one completely.

370

Same here having issue with Tuya integration after update.
All my bulb lights stopped working as configured devices became orphan.
Tried:

  1. removing Tuya integration
  2. clearing cache
  3. rebooting
  4. reinstalling Tuya integration
  5. clearing cache again
  6. rebooting again

Tuya now is just showing my lightbulbs as “atmosphere (unsupported)”.

so in my specific case I got 7 devices (3 lights + 1 remote + 1 zigbee gateway + 2 plugs) and 2 entities (plugs)

is there any workaround to get trough this rather than downgrading Home assistant to 2021.10?
thank you in advance

1 Like
371

I had an MQTT issue prior to the upgrade and after the daylight changes of the last weekend in Europe. After restart everything it disappeared and not happened again, so for me it is not linked with the update.

372

Great to see the Tuya integration has been updated to support so much more! This made me finally do the feared upgrade from 2021.9.6. I did notice the state of the covers isn’t getting updated. Is that just me or
?

373

Is anyone else having Homekit integration issues? I tried adding a new device to one of my bridges via the UI and noticed each domain under the domain selector is repeated twice. (see photo). I hit submit and select the new entity (zha switch) in “include” mode. If I hit submit again, I get a “User Import malformed error” and cannot proceed to the next step. Neither integration reloads nor core restarts solve the issue. Any ideas? Looks like others are having the same issue: https://community.home-assistant.io/t/homekit-error-user-input-malformed/353390
Screen Shot 2021-11-06 at 6.24.49 PMScreen Shot 2021-11-06 at 6.24.34 PM

374

Hello, petro, via usb debugging Ifound I have the same issue as in this issue: Lovelace hangs due to "Uncaught (in promise) RangeError: Invalid timeZoneName"

Uncaught RangeError: Invalid timeZoneName
at Function.a.DateTimeFormat.__setDefaultTimeZone (:8123/frontend_latest/94a4fdf6.js:1)
at Array.<anonymous> (:8123/frontend_latest/app.707ed561.js:1243)
at s (:8123/frontend_latest/core.bba75532.js:1)
at n (:8123/frontend_latest/core.bba75532.js:1)
at Object.callback (:8123/frontend_latest/core.bba75532.js:1)
at n._handleMessage (:8123/frontend_latest/core.bba75532.js:1)
at WebSocket.<anonymous> (:8123/frontend_latest/core.bba75532.js:1)

and

Uncaught (in promise) RangeError: Invalid timeZoneName
at Function.a.DateTimeFormat.__setDefaultTimeZone (:8123/frontend_latest/94a4fdf6.js:1)
at Array.<anonymous> (:8123/frontend_latest/app.707ed561.js:1243)
at Object.s [as setState] (:8123/frontend_latest/core.bba75532.js:1)
at :8123/frontend_latest/core.bba75532.js:1

375

And what is your timezone set to?

376

My timezone is set to Europe/Prague

377

I’m right there with you. I have 82mil rows in dbo.states and am well settled into MSSQL.

378

here is the solution: After core-2021.11.0 & core-2021.11.1 Update, HA Mobile & Fully Browser on tablets, stuck on "Loading Data" · Issue #59085 · home-assistant/core · GitHub

it®s a bug of TimeZone format and for me solution was to change time zone to Europe/Oslo
 have a nice time!

379

solution: After core-2021.11.0 & core-2021.11.1 Update, HA Mobile & Fully Browser on tablets, stuck on "Loading Data" · Issue #59085 · home-assistant/core · GitHub

380

Are there any known issues with the AVM Fritzbox Tools Integration? Since the update, some device_tracker entities just vanished and some were disabled, even though they werelactive before Ive updated from 2021.10.6 to 2021.11.1

Some of my automations donÂŽt work anymore, since I made some conditions wether the device_tracker entity is connected to wifi or not.

I guess I could simply remove and readd the integration, but maybe itÂŽs some kind of bug.

381

Anthem AV integration still does not work. Entity is unavailable.

382

Posting in this thread will not net any changes or fixes to code. If you have an issue, open it up on github and follow the directions. Right now, you’ve provided nothing useful in regards to fixing any error. Simply saying “XYZ does not work” does not help anyone figure out what’s wrong. So please write an issue on github with a longer description than “Does not work”. This can be done simply by supplying logs from config\homeassistant.log with some screenshots showing the issues.

1 Like
383

I did. In August. I provided my logs and a detailed description of the issue on Reddit and Github. I have received no responses. On Reddit I got one comment that said I have the same issue. So if somebody wants to assume HA users don’t know how to ask for help I can assume nobody cares about fixing the issue.

384

Then you have to wait until a developer of that integration picks up the issue and fixes it. If that integration has no code owner, you have to wait. You’re always welcome to bump the issue to get more eyes on it. Posting here or reddit will get you none of that. The people making changes use github.

385

There is a breaking change in this release affecting several custom integrations:

This is affecting Magic Areas, Adaptive Lighting, Programmable thermostat and several others.

386

I see no issues on github linked to anthem av or any combination of letters that make up anthem av. Are you sure you created an issue? Did you create the issue against core?

387

September. I’m sorry

388

Wrong location for the support issue (GitHub Support Community forum is for issues with Github). You should probably create one here:

1 Like