Well that experience was the final push to remove my last few tuya devices and replace them with zigbee 
1 Like
Same here, both missing.
The update has caused my Tuya devices statuses not update. I can toggle my switches, but the state never updates in Home Assistantā¦ Will have to push to replace my Tuya switches faster š¤¦
This is because they messed up the instructions.
Look at Tuya - Home Assistant
Configuration of the Tuya IoT Platform
Step six is missing instructions and messing everyone up.
As it says it does copy over the smart stuff but they forget to mention that its not all you need.
If you look at the picture below six you also need authorizationā¦iot device analytics and device status notification .
When you created the project one of more of those was missing.
1 Like
To go from S0 to S2? No.
1 Like
So, the tuya2 custom (eg via HACS) integration does support energy, but the new official tuya integration does not. I have to assume that it will be supported sometime in the futureā¦ Iāve moved everything over as it was a nice to have, not a showstopper, and am just hoping it is supported sooner rather than later along with a few of the other tuya devices I have that arenāt supported yet.
Iām having the same problem too. Looking for a solution.
After Upgrading my Node Red disconnects every 30min or so with problems communication to the Supervisor.
Anyone experiencing this issue also?
10 Oct 08:57:53 - [info] [server:Home Assistant] Connecting to http://supervisor/core
10 Oct 08:57:53 - [info] [server:Home Assistant] Connected to http://supervisor/core
(node:500) UnhandledPromiseRejectionWarning: #<Object>
(node:500) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 97)
10 Oct 09:12:43 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
10 Oct 09:12:43 - [error] [ha-entity:GenshinCodes] Entity API error.
edit: also filed a issue, as no one seems to have this bug too. https://github.com/hassio-addons/addon-node-red/issues/1136
Iām having the mustache and dot as well. Not really a nice look on my dashboard to be honest. It only appears on the badge on a dashboard. When opening the person the icon is correct. Please fix this.
Absolutely 
Looks like the default picture gets rendered together with the uploaded avatar.
4 Likes
Hi guys,
Is anyone having issue with ShellyForHass custom integration?
Upgrading from 2021.9.7 lead to all my Shelly devices being unavailable, rolling back to 2021.9.7 alla fine again.
I did see another post from someone with that problem. (Unless it was you).
I ask genuinely, why does one need to use shellyforhass now that there is s shelly integration in core?
There is a.pr to fix that I believe
I will leave it like this for the time being. My wife looks great with that mustache (and she has not even noticed it yet) 
3 Likes
Because it has dozens of more options to adjust.
Has anyone had any issues with the unifi integration since this upgrade? I have a switch which controls the DPI traffic restrictions for the network my kids connect to (enables/disables access to Youtube and some other stuff). This switch no longer works.
I guess it was me.
Your point is correct: I am using the custom component since a long time and moving to the official integration will be a quite long work.
Maybe time to tackle it
Hello,
same probelm for me the statistics doesnt work anymore āno history foundā.
are we only 2 guys with this problem???
i revert to history-graph, hope there is a fix, i am used to statistic-graph nowā¦so bad to revert the old styleā¦
Hello,
same problem for me the statistics doesnt work anymore āno history foundā.
are we only 2 guys with this problem???
i revert to history-graph, hope there is a fix, i am used to statistic-graph nowā¦so bad to revert the old styleā¦
and dont understand but seems we need to create a new sensor for each entity to stat :
sensor:
- platform: statistics
entity_id: sensor.cpu
name: cpu sensor stat