Yeah ok, it’s only an issue if this was a problem:
That is unlikely to have caused an issue in my case - unless memory use on the external system I am monitoring shoots up from its usual 27% to over 75% during a restart of home assistant or within the 60 seconds or so that it takes for the sensor to update.
But at least now I don’t have errors cluttering up my log hiding other issues I should be taking notice of.
Getting this message when I want to upgrade:
<html>
<head><title>504 Gateway Time-out</title></head>
<body>
<center><h1>504 Gateway Time-out</h1></center>
<hr><center>nginx/1.16.1</center>
</body>
</html>
When I try a second time I get:
Unknown error, see supervisor
At the Core Log I see:
2021-03-04 15:28:44 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [1630670752] Error handling message: Unauthorized
2021-03-04 15:28:44 ERROR (MainThread) [frontend.js.latest.202101277] https://xxxx.duckdns.org/hacsfiles/button-card/button-card.js:1:38791 NotSupportedError: Cannot define multiple custom elements with the same tag name
2021-03-04 15:28:44 ERROR (MainThread) [frontend.js.latest.202101277] https://xxxx.duckdns.org/dwains_dashboard/js/dwains-dashboard.js:90:19835 TypeError: undefined is not an object (evaluating 'e.config')
2021-03-04 15:28:44 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [1630670752] Error handling message: Unauthorized
2021-03-04 15:29:05 WARNING (MainThread) [homeassistant.components.automation.battery_sensor_from_attributes] battery_sensor_from_attributes: Already running
2021-03-04 15:29:05 WARNING (MainThread) [homeassistant.components.automation.battery_sensor_from_attributes] battery_sensor_from_attributes: Already running
2021-03-04 15:29:05 WARNING (MainThread) [homeassistant.components.automation.battery_sensor_from_attributes] battery_sensor_from_attributes: Already running
2021-03-04 15:29:05 WARNING (MainThread) [homeassistant.components.automation.battery_sensor_from_attributes] battery_sensor_from_attributes: Already running
2021-03-04 15:29:05 WARNING (MainThread) [homeassistant.components.automation.battery_sensor_from_attributes] battery_sensor_from_attributes: Already running
2021-03-04 15:29:05 WARNING (MainThread) [homeassistant.components.automation.battery_sensor_from_attributes] battery_sensor_from_attributes: Already running
2021-03-04 15:29:05 WARNING (MainThread) [homeassistant.components.automation.battery_sensor_from_attributes] battery_sensor_from_attributes: Already running
2021-03-04 15:33:23 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [1667809752] Error handling message: Unauthorized
2021-03-04 15:33:23 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [1667809752] Error handling message: Unauthorized
I am just a user. I don’t understand those messages. Can someone point me a simple direction where to solve the problem so I can update to the latest HA version.
Maybe try clearing cookies and cache, and then log in again?
To the people complaining that if they change their SMB password then they have to update it for multiple other devices on their LAN. Please… NEVER save your passwords for SMB shares! If you get a cryptovirus (or many different varieties of trojan) - you will lose everything on any network share that you have saved the password for.
Nah not for me. Too much hassle for such a small risk - and I keep offsite backups.
Reply on my own message 
It seemed that the update was processing in the back after all. I cleared the cache (activated the update from the iPad app) then closed the app and used safari to login and it said “reconnecting”. When everything was loaded, I saw the latest version was installed.
The update processes on HA doesn’t show any progress bar, so you don’t know what’s happening or if it’s finished or not. So sometimes I press “update” again, because I think nothing is happening. Maybe a good idea for the developers to add a progress bar on all updates within HA.
It can only tell you while it’s connected to WiFi. Once it reboots, it won’t be able to tell you the progress.
The docs for fans aren’t very informative with the new fan speed percentages.
How does the integration handle a fan that only understands low (1) medium (2) or high (3) (such as ifan03 mqtt fan)?
Or in the integration of my zigbee fan (that I have zero control over) that has a low/medium/high setting?
where does the translation happen between “low” and “33%”?
that’s a good question…
So you have verified that it no longer works with the new percentages?
You have verified that the controls still work after the update for fans now using percentages instead of speeds?
(just wanting to know how much work I have to do to get it working again if not 
)
But why tell people about something in a log that they have never noticed before because it has never been an issue for them? Or they did notice but understood that it would be corrected once the entities complete initializing in a few minutes?
all it does is end up with…
for no real benefit.
Especially if the only thing they can do to get rid of the log entry is to rework the code to hide the issue that the entity is temporarily unavailable (that wasn’t really an issue in the first place or they would have noticed it before now… 
)?
is there going to be a log entry for every other trigger platform/entity that hasn’t initialized completely yet or just for numeric_state triggers?
Again a great release. Thanks so much to everyone making this possible.
One question to @raman325 - is there any more information what exactly changed for the universal media player ?
I looked at the sources, seems that now more (all ?) of the services can be overwritten. This was one of the things I was looking for to make it useful for me. The other thing that would be handy is to be able to call more then one service per command - that would save additional scripts to be needed.
Yes depending on which I click it’s going to the right percentage-- 0, 33, 67 or 100
I haven’t changed anything, it’s interpreting my original template to those values automatically
Which fan platform are you using (mqtt/zha/etc)?
It’s a template fan from a zwave device (Inovelli LZW36)
After the upgrade none of the sensors on my mobile devices via the companion app are now updating?!?!? including location!!
Hi!
I run both HA and Z-Wave JS MQTT as Docker containers.
With the 2021.3.0 version HA incorrectly identifies the Z-Wave JS server version. See the screenshots below, where the Z-Wave JS version info in the first and the HA error message from the log in the second.
I also tried to update Z-Wave MQTT to the latest version with the same result
Best regards,
Jonas
https://my.home-assistant.io/redirect/supervisor_addon_store/ was added to to supervisor, but not the my site, all good now 
Yeah seeing the same thing. All “unknown”.
I think you need to update the app (from app store) too.
The ClimaCell integration seems to work off the V3 API so you need that key version…you prob are trying to use the V4 key/token which the integration doesn’t recognise…
Everything listed in green here: https://github.com/home-assistant/core/pull/44711/files
Unfortunately this integration isn’t documented well, otherwise I would refer to the docs. Might be a good exercise for someone with some free time who has an interest in the integration.
I definitely did not add support to call more than one service per command. I think the right approach here is to use a script and to call that script as a service (which it sounds like you are already doing). It’s the most flexible way to handle this without adding unnecessary complexity to the integration itself
I’ve got the same, I’m guessing they’re unavailable on boot. Maybe these checks can be done once HA has fully started?
