Does core show those pages? My dev box isn’t running, so I can’t check.
I haven’t had a chance to update to 2022.5(.x), but Backup is present in Core on 2022.4. If @cyn is not using default_config, then backup will have to be added to configuration.yaml manually:
I wouldn’t expect Storage or Hardware to be present on Core, on the other hand, as I’m fairly certain they are both provided only by Supervisor.
2 Likes
Thank you, that fixed the missing Backup and explained Storage & Hardware.
Maybe keep the ui, but creating an export/import function?
Nailed it. Browser cache was reset but had to reset cloudflare cache. That’s twice the cloudflare cache has gotten me in the past month lol
My attempt to upgrade to 2022.5.3 was unsuccessful. I run HA Container and it crashes shortly after start.
However, 2022.5.2 runs just fine.
I get the following output :
2022-05-10 14:35:51 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Home for smartthings
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/smartthings/__init__.py", line 121, in async_setup_entrytoken = await api.generate_tokens(
File "/usr/local/lib/python3.9/site-packages/pysmartthings/smartthings.py", line 209, in generate_tokens
result = await self._service.generate_tokens(
File "/usr/local/lib/python3.9/site-packages/pysmartthings/api.py", line 424, in generate_tokens
raise APIInvalidGrant(data.get("error_description"))
pysmartthings.errors.APIInvalidGrant: Invalid refresh token: 482ca6b2-a299-488b-8faa-f683a4c1f36a
[finish] process exit code 256
[finish] process received signal 11
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Any advice is appreciated.
[Edit]
-
If I disable the SmartThings integration, I no longer get any error messages in the log, but HA still terminates.
-
Then I deleted the SmartThings integration, but to no avail. HA still terminates
-
Then I emptied the DB completely (external Maria-DB), but to no avail. HA still terminates.
So, it doesn’t seem to have anything to do with the SmartThings Integration.
i got same error upon each restart , please look below and if anyone can help about it
[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] waiting for services.
2022-05-10 23:18:27 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /homeassistant/restart request
Found 2 non-daemonic threads.
[finish] process exit code 0
s6-svscanctl: fatal: unable to control /var/run/s6/services: supervisor not listening
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] done.
[services.d] starting services
[services.d] done.
It seems that in the may release the log has been changed so it shows the last lines of the logs from the server was restarted. I can see the idea. If the server crashes and HA restarts you can see the last messages that can give a clue of what caused the crash. But when you manually restart we seem to see some artifacts when the different processes get killed.
In my case ALL the lines in the upper part of the log belong to the previous run…
Restarted at 23:37 (checked event “start” in trigger), all messages in the upper part are at 23:11…23:12.
I Agree, it seems very random / limited … thou if you look at in file-editor, the home-assistant.log is even more “weird” intact, but limited entries,in what also appears to be in a random pattern , that was the first i checked, after viewing the “new” log location after the release … guess one will get use to this also.
any idea how to solve it ? the home assistant working so well but the details of log is full of this on every restart got (fatal: unable to control /var/run/s6/services: supervisor not listening) and ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /homeassistant/restart request
After updating to 2022.5.03 my ‘Database size’ became unavailable.
Below has been automatically been imported into the integration.
- platform: sql
db_url: !secret mariadb_url
queries:
- name: 'DataBase size'
query: 'SELECT table_schema "database", Round(Sum(data_length + index_length) / 1024 / 1024, 1) "value" FROM information_schema.tables WHERE table_schema="home_assistant" GROUP BY table_schema;'
column: 'value'
unit_of_measurement: MB
Error:
Logger: homeassistant.components.sensor
Source: components/sql/sensor.py:97
Integration: Sensor (documentation, issues)
First occurred: 08:18:03 (2 occurrences)
Last logged: 08:57:00
Error while setting up sql platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
await asyncio.shield(task)
File "/usr/src/homeassistant/homeassistant/components/sql/sensor.py", line 97, in async_setup_entry
name: str = entry.options[CONF_NAME]
KeyError: 'name'
Which ‘name’ is meant in the KeyError?
I’m aware of this, sorry I was not clear enough.
Your existing YAML configuration is automatically imported on upgrade to this release; and thus can be safely removed from your YAML configuration after upgrading.
This was both done, existing YAML configuration is automatically imported and I also removed the YAML configuration.
I added the YAML to show what was imported. 
However, do I still overlook something?
Is there anyone that has mastered the usage of the SQL integration in combination with a sqlite database?
I only get an error that my query is incorrect and all attributes I filled in are cleared after that.
It is just a simple SQL:
SELECT * FROM tablename WHERE id = (SELECT MAX(id) FROM tablename);
I get no error for my database url, so I would assume that that is correct.
Or is there something wrong with the SQL integration?
fwiw, this was imported correctly and gave a working sensor:
# - platform: sql
# db_url: !secret db_url
# queries:
# - name: MariaDB size
# query: "SELECT table_schema AS 'db_name', ROUND(SUM( data_length + index_length )
# / 1024 / 1024, 2) AS 'size_mb' FROM information_schema.TABLES WHERE
# table_schema='homeassistant'"
# column: 'size_mb'
# unit_of_measurement: MB
commented now because of UI…check the column maybe?
How are are you monitoring/watching this … given the incredibly useful system-metrics (hassio-system-metrics) view has been disabled/removed ? … (I really want this to return in some fashion … re Adds hassio-system-metrics by ludeeus · Pull Request #7105 · home-assistant/frontend · GitHub … having to setup System Monitor - Home Assistant is … only so good).
While the new “streamlined settings” might seem better there are the following problems …
- It is (still) really confusing to find specific settings - e.g. for energy things (I gave up and used the keyboard to find the energy settings …)
- It is now harder to view logs/they seem to have less visibility vs othe old system overview display (imho)
- The easy controls to say reboot or shutdown a system from the webui have been removed ?
1 Like
No they haven’t
Yes I have to agree, this is probably the hardest configuration to find. IMO it should be a main item in settings. Alas, it’s located
Settings → Dashboards → Energy
Sorry, I have to disagree. The logs are now all in 1 place. Before you had to hunt and peck for each log. It’s simply now just
Settings → System → Logs → upper right corner dropdown to access whatever log you want.
Settings → System → Hardware → Reboot or Shutdown buttons at the bottom.
Settings → System → upper right corner restart
1 Like
Love it, same as for Hardware , the 3 dots in right corner, Show all Hardware