I don’t have any errors in my log yet it doesn’t work. Restarted Maria db and ha several times.
I hadn’t a question, I had an answer. As I mentioned there is a solution in the issue I linked (which was yesterday the second-top issue right under the one PickOne opened…).
But thanks anyway, help is always appreciated!
Since the update to 2021.6.0, I am unable to edit scripts using the UI. I get a message saying:
The page at http://192 168.1.93 says
This is on both the Android app and on Firefox/Opera on Windows. Oddly, I am able to edit automations.
It looks as if I’m getting banned:
Logger: homeassistant.components.http.ban
Source: components/http/ban.py:116
Integration: HTTP (documentation, issues)
First occurred: 13:43:19 (1 occurrences)
Last logged: 13:43:19
Login attempt or request with invalid authentication from 192.168.1.201 (192.168.1.201). (Mozilla/5.0 (Android 11; Mobile; rv:88.0) Gecko/88.0 Firefox/88.0)
But only when I try to edit a script in the UI - odd surely?
Blank error messages are… Really. Not. Helpful.
I’m struggling here - any ideas?
It is working now, thanks for your help.
Working now, the integration had disappeared but it’s back.
Is this update doing anything special with the database? It’s been several hours now that I cannot restart the system but get:
homeassistant.exceptions.HomeAssistantError: The system cannot restart while a database upgrade is in progress.
The MariaDB log doesn’t show anything special. CPU load by the database is at 0%. The last log entry was an error from yesterday:
2021-06-02 12:00:54 395 [Warning] Aborted connection 395 to db: 'homeassistant' user: 'homeassistant' host: '172.30.32.1' (Got timeout reading communication packets)
One of my Kindle tablets that I use as a panel with Fully Kiosk is doing this same thing. At first it wouldn’t load anything. After clearing the cache in Fully Kiosk, it’s stuck at “Initializing” I have another (I thought) identical Kindle that is working fine. Using Chrome on the same device loads fine as well
Do we know why this is happening?
OK, well, turns out one panel had FireOS 7.1.2. Updated to 7.1.9 and now the dashboards load…That took a minute to figure out.
Using the check HA configuration add-on gave this (twice):
[16:42:13] ERROR: The configuration check did not pass!
[16:42:13] ERROR: See the output below for more details.
Testing configuration at /tmp/config
ERROR:homeassistant.helpers.check_config:Unexpected error validating config
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/homeassistant/helpers/check_config.py", line 155, in async_check_ha_config_file
await config_validator.async_validate_config( # type: ignore
File "/usr/local/lib/python3.8/site-packages/homeassistant/components/automation/config.py", line 127, in async_validate_config
await asyncio.gather(
File "/usr/local/lib/python3.8/site-packages/homeassistant/components/automation/config.py", line 104, in _try_async_validate_config_item
config = await async_validate_config_item(hass, config, full_config)
File "/usr/local/lib/python3.8/site-packages/homeassistant/components/automation/config.py", line 72, in async_validate_config_item
config[CONF_TRIGGER] = await async_validate_trigger_config(
File "/usr/local/lib/python3.8/site-packages/homeassistant/helpers/trigger.py", line 49, in async_validate_trigger_config
conf = await platform.async_validate_trigger_config(hass, conf)
File "/usr/local/lib/python3.8/site-packages/homeassistant/components/device_automation/trigger.py", line 21, in async_validate_trigger_config
return await getattr(platform, "async_validate_trigger_config")(hass, config)
I don’t know how to interpret this. Safe to proceed?
For info, the check config button on the server control page returns that all is fine in my current version (2021.5.5).
Looks like the Custom Component for Alarm.com with Ajax just broke. I am reading through the notes, but cannot seem to figure out why it broke. This is a fantastic custom component, as it makes alarm.com function fully with Home Assitant:
Anyone seeing an issue with the Jandy integration? I updated to 2021.6 this morning and didn’t look to see if jandy was having an issue beforehand. There are a few others here that have indicated that they’re experiencing issues also, but they didnt give away the HA version that they were on.
I’m getting a “Forbidden” in the logs for it.
Write up an issue against the custom integration.
so I did a little more testing. my history graphs are still gone.
I restarted MariaDB and HomeAssistant multiple times. I uninstalled and reinstalled the MariaDB Addon. I restored the Addon from a snapshot before the update. I get no errors in any log. I see the schema migration from 14 to 15 to 16, it finishes without issue. My DB size sensor still reports a size. Am I the only one with this issue?
Update on the template-entity-row issue.
It is a cache issue. Somehow these custom component js files are heavily cached by the browsers. Even control F5 does not refresh them
You can enable developer mode in Chrome based browsers and then right click on the refresh button and select a hard refresh reloading all cache.
In IOS you cannot refresh cache unless you clear everything and live a miserable life with cookie warning popups.
There is trick. If you load the updated js file directly as a URL and then refresh a few times even IOS safari reloads the file. URL will look like
https://MY-HA-URL/hacsfiles/lovelace-template-entity-row/template-entity-row.js
1 Like
I just checked.
It takes the browser 2.5 minutes to load a logbook where 3 hours has 2500 entries.
And Bram hinted to look at the Network part of the developer tools in Chrome and it seems all the waiting time is loading the data from the backend. It is not the browser that cannot render the data fast.
Something has slowed down HA collecting data from the database. I run on a Home Assistant Blue. I have no other high loads on that machine. I have no loading addons. Even my Deconz, and Mosquitto runs on another server. Something has made the process very slow.
MY remote console stopped working with the upgrade, the Core log is filled with
2021-06-03 19:32:08 WARNING (MainThread) [hass_nabucasa.cloud_api] Fetched https://remote-sni-api.nabucasa.com/snitun_token (400)
2021-06-03 19:32:08 ERROR (MainThread) [hass_nabucasa.remote] Can't refresh the snitun token
Have reloaded, restarted, rebooted, no change.
using Chrome’s developer tools I narrowed it down further. the history graph uses this call to fetch the data and gets a 404 response. the Initiator is app.cdb4df30.js:36059
Have another problem. My Google home mini tts not say anything. Only hear the clank sound and no voice. Something changed with it? Before working good.
Get this error : * Failed to cast media https://xxxxxx.yyyyyyy.zzzzzz.me/local/1sec.mp3 from external_url (https://xxxxxx.yyyyyyy.zzzzzz.me). Please make sure the URL is: Reachable from the cast device and either a publicly resolvable hostname or an IP address