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.
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?
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.
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
I use Zigbee curtains (covers) from Lonsonho. They get properly exposed via zigbee2mqtt plugin panel with the “open” and “close” states. But in HA it became unavailable. I can’t operate my covers in 2021.6. What have changes? Should I restore to 2021.5 or is there a quick fix to that?
snitun issue happens to me about twice a year. Never got help. Fortunately restart of HA always helped. Recently when it happened to me on I noticed snitun related change in NC github a few days back. Maybe coincidence.
if you check github it’s know but never resolved because of lack of evidences. In short devs require debug logs, which obviously nobody can provide since it would require to have debug logs enabled for a whole year.
Hi all, I found this in the log usin external mysql…
Logger: homeassistant.components.recorder.util
Source: components/recorder/util.py:68
Integration: Recorder (documentation, issues)
First occurred: 8:51:30 PM (1 occurrences)
Last logged: 8:51:30 PM
Error executing query: (MySQLdb._exceptions.OperationalError) (1071, 'Specified key was too long; max key length is 1000 bytes') [SQL: CREATE INDEX ix_statistics_statistic_id_start ON statistics (statistic_id, start)] (Background on this error at: http://sqlalche.me/e/14/e3q8)
that really is too bad, and cant reproduce here (3 instances all Pi3/4)
that being said, I feel somewhat relieved that I am not the only one experiencing ‘network issues’. On 1 of my 3 instances I see connection errors regarding the image files in my www folder (only certain files though, so I don’t understand it at all, and can’t put a finger on it) On the 2 other instances that are almost empty except for the MQTT add-on and the ZwaveJS add-on respectively, I see my customizations being loaded sometimes after a few seconds (up to 12) while they are immediate on the other instance and have always been before the last couple of updates…
So I would tend to agree there is something in the backend frustrating that. (I do serve all my instances over duckdns, so there is actual networking going on. most of the files do render immediate though, making the exceptions really hard to understand)
I have the same issue. It appears to be associated with a custom card that uses Lit, which has moved to V2.0. The custom card will need to be updated to accommodate the new version. If the card hasn’t been maintained, you might need to find an alternative.
