I’m having a similar issue.
recorder is working in config yaml but all my sensors have stopped working.
I have the sensors in their own yaml but with the same url to the mariadb.
I’ve checked from mysql workbench and data is still feeding into mysql maria.
I’ve even restarted the host machine etc etc.
Some graphs are showing but none of the sensors which pull data in from mysql.
After this update I found that the automations are triggered twice…
I hope the problem will be fixed.
Thanks.
For me its this component that is not working:
platform: sql
frenck Upgrade sqlalchemy to 1.3.18 (#37123)
I’ve opened up an issue with this component sensors with sql
make sure browser_mod is up to date, if you use it
Don’t know what it is so … can it be a problem?
then probably not 
I have lots of entities created from sql views and now none are available. 
Rolled back to 0.113 and got all my sensors (sql platform) back.
So obviously a major bug in this version.
So if you have a mysql DB with views as entities this version will break your entities.
Keep getting the message/dialog box everytime i refresh (open) the browser , it also appears on the android app too.
I did read an article for the beta version for 114.0 to remove card-tools from the lovelace . Done
System : synology DS918+ / Docker
no related errors in the log
LeeB
Googling your communication error finds this (and probably many others) https://www.percona.com/blog/2016/05/16/mysql-got-an-error-reading-communication-packet-errors/
I like dark theme but I wish I could make the background colour fully black, that’s my small wish for the future.
Whoever thinks it is funny to keep flagging my posts, just stop it please. Feel free to send me a PM if you have something to say to me.
emulated hue also not working here anymore, anyone else?
I flagged it and it was reviewed by an another moderator, as it was condescending towards another user.
My REST sensors stopped working; had to revert to 113.3.
I got that, as a red-herring - it turned out the error only occurred to my RESTful sensors. But the error implied it was a custom component (the custom button).
You need to setup the Secondary Info Attribute with “humidity”
Strange, but it doesn’t work for me😕
I have Xiaomi Redmi Note 8 Pro, Android 10, MIUI 12. The user profile has Backend-selected Theme and Auto in mode. Just upgraded to latest app 2.1.1-13.
By the way other Android apps are going into Dark mode if system is changed.
Update: After update to latest latest app 2.1.1-17 is going to change to the Dark mode as expected!!
Great work!!!
I had the same error. I rebooted a couple of times and it finally went away and things seem fine.
Can i prevent the shell_command 60s timeout since 0.114.0 ?
I have a led-light fade in/out shell script called by shell_command for my aquariums.
And the fading times (script runtimes) are much longer then 60 seconds.