That happened last month https://www.home-assistant.io/blog/2021/10/06/release-202110/#farewell-to-the-following
1 Like
Hmm, thought I searched the site extensive enough⊠Missed that one completely.
Same here having issue with Tuya integration after update.
All my bulb lights stopped working as configured devices became orphan.
Tried:
- removing Tuya integration
- clearing cache
- rebooting
- reinstalling Tuya integration
- clearing cache again
- 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
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.
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âŠ?
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
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
And what is your timezone set to?
My timezone is set to Europe/Prague
Iâm right there with you. I have 82mil rows in dbo.states and am well settled into MSSQL.
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!
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.
Anthem AV integration still does not work. Entity is unavailable.
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
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.
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.
There is a breaking change in this release affecting several custom integrations:
This is affecting Magic Areas, Adaptive Lighting, Programmable thermostat and several others.
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?
September. Iâm sorry