If it is only 5 minutes coding, you have no doubt done it locally, and are submitting a PR.
4 Likes
From user feedback it doesn’t look like you can generate V3 keys anymore. I know this is a bummer, I will get V4 support added as soon as I can
3 Likes
Well check the addon instructions because UTF8 is incorrect and maybe the reason for your problem.
I commented out the URL in recorder.yaml to make it use the inbuilt sqllite, restarted HA, deleted the addon and readied it and edited the url in recorder again and restarted and had no more issues.
This is my config and it works with utf8 
maria_db: mysql://xxxxxxxx@xxxxxxxx@core-mariadb/homeassistant?charset=utf8
It’s still wrong. I had an issue a little while back that the recorder stopped recording. I believe the issue was with emoji characters… but check the docs and it’s clearly wrong.
I can see it’s changed since I originally set up, but still working, so idk.
I never noticed it had changed until I saw my history graphs screwing up…
I have this in:
db_url: mysql://homeassistant:password@core-mariadb/homeassistant?charset=utf8mb4
Needed to change it a while back in order to get rid of some issue in the log.
1 Like
I am getting the below error from the Nuki integration:
2021-03-05 08:16:05 ERROR (MainThread) [homeassistant.components.nuki.config_flow] Unexpected exception
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/nuki/config_flow.py”, line 92, in async_step_validate
info = await validate_input(self.hass, user_input)
File “/usr/src/homeassistant/homeassistant/components/nuki/config_flow.py”, line 39, in validate_input
data[CONF_HOST],
KeyError: ‘host’
On the top of that I see 4 times the integration on the integration’s tab. 3 pending of configuration and one perfectly configured. I tried to remove all and add the integration manually and it did not work. YAML related confirguration has been deleted.
And last but not least, the integration works well 
Thank you both for your answers.
It works perfectly with previous core version, but stop working after a few minutes with 2021.3 core version (it works for a few minutes though, which is bizarre…). Maybe some specific data that raises an error yeah, could be.
I will change the url.
If I can’t get it to work, I will give sqlite another chance. I have optimized my recorder settings and my templates, my db does not get bigger than 70Mb for a 7-days retention policy, so I guess sqlite should not have any trouble to handle it and MariaDB may not be a big improvement anymore in my case. I will try.
I will keep the topic informed !
Tanks again for the help.
Got this error message in my supervisor.
Restart didn’t help.
Translation Error: The intl string context variable “naam” was not provided to the string “Weet u zeker dat u {naam} opnieuw wilt starten?”
And yes, I also see the drops of connection in Safari and Chrome on Mac desktop. so this seems a core issue
I do see these new errors at startup, maybe already indicate some timing issues:
021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /supervisor/info request
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /supervisor/info -
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /info request
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /info -
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /core/info request
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /core/info -
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /network/info request
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /network/info -
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /resolution/info request
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /resolution/info -
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /os/info request
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /os/info -
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /addons request
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /addons -
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /store request
2021-03-05 09:16:36 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /store -
HA OS 2021.3.1
Same here. I leave like the new view and hope to see it working. Is there any investigation going on already? If not may it would be helpful to raise an issue.
In my case it occurred in developer tools as well as UI automation view.
Make sure you delete the addon and add it back as I describe.
I asked what your URL was because it sounded similar to the error I had previously
I had/have the same issue. Since supervisor-2021.03.4 this issue pops up. The links in the supervisor- system tabs are not correct:
Thanks, I will.
I already tried 2 or 3 times yesterday to uninstall/reinstall, but I did not change the url. I will today.
Wondeful to see all the nice and helpful new features, thanks to everybody who contributed. The only thing that wonders me is whether there will be a point that so many support / easifying features and functions will be available, that they will actually make things worse rather than better. As a developer of complex measurement gear I know that such things can become a real culprit of inconvenient user experience. The great thing of HA is that the contibuters are also actual users, which is often not the case.
Anyway, a minor little translation thingy that just showed up in my instance when updating:
3 Likes
