Also upgraded, but when I access the logbook, I don’t see any events anymore? Is this changed?
Are events excluded form the recorder?
No before I saw events like… Light.xxx turned on by Google assistant…
Now logbook is just empty
The Overkiz Somfy integration uses the cloud api .
This will shutdown in a few weeks.
Is there work going on the local api ?
If yes, when will it be released ?
See also my question here:
2022.6 release Somfy switch to Overkiz and local access - what am I missing?
EDIT: Got confirmed through Github that the Overkiz API is not the same as the one being taken down. This one will keep working.
regarding Energy-Dashboard “Self consumed solar energy” is still more or less useless. pls add AUTARKIE / autarchy / self-sufficiency
1 Like
“Lots of you asked for it; the “YAML” tab is now the first tab shown in the developer tools.”
Well that’s annoying. Do people really use the YAML tab more than the state, services,templates,events tabs? lol
3 Likes
Good thing you have months to do it.
Logger: homeassistant.components.google_assistant.helpers
Source: components/google_assistant/helpers.py:343
Integration: Google Assistant (documentation, issues)
First occurred: 3:49:10 PM (1 occurrences)
Last logged: 3:49:10 PMLocal SDK version is too old (None), check documentation on how to update to the latest version
Hmmm… I didn’t see anything related to this in breaking. Something we need to do?
EDIT: Just an app.js upgrade.
2 Likes
Maybe a future release might let people order these sorts of tabs however they want?
5 Likes
I tried to comment the YAML out and still didn’t work
Not sure that’s a viable option. Getting into product verification and assurance is a costly business that would have to be passed on to us lot. In order to keep HA as open and private as possible, we need to keep big business at arms length. Also, The Chinese will simply slap the logo on everything regardless of if it’s actually certified, then HA(NC) would need to spend money protecting it, or certification would become a joke. Online notation through integration is far simpler, cheaper and a more reliable option, if one is needed at all…
Been an issue for a while:
Looks like there’s an issue with the fix
I think this might be a bug. My Logbook is now empty as well. If you have a look in the log file, you might see an error. Mine shows the following:
2022-06-01 16:22:27 ERROR (MainThread) [homeassistant.setup] Error during setup of component logbook
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 235, in _async_setup_component
result = await task
File "/usr/src/homeassistant/homeassistant/components/logbook/__init__.py", line 123, in async_setup
recorder_filter = extract_include_exclude_filter_conf(recorder_conf)
File "/usr/src/homeassistant/homeassistant/components/recorder/filters.py", line 37, in extract_include_exclude_filter_conf
return {
File "/usr/src/homeassistant/homeassistant/components/recorder/filters.py", line 38, in <dictcomp>
filter_type: {
File "/usr/src/homeassistant/homeassistant/components/recorder/filters.py", line 39, in <dictcomp>
matcher: set(conf.get(filter_type, {}).get(matcher, []))
TypeError: 'NoneType' object is not iterable
2022-06-01 16:22:30 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of default_config. Setup failed for dependencies: logbook
2022-06-01 16:22:30 ERROR (MainThread) [homeassistant.setup] Setup failed for default_config: (DependencyError(...), 'Could not setup dependencies: logbook')
Cyclic reboots of my HA Container, and I cant even downgrade, with the recorder module spouting junk 
2022-06-01 22:17:23 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-01 22:17:23 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration svt_play which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-06-01 22:17:23 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=logger, service=set_default_level>
2022-06-01 22:17:23 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event service_registered[L]: domain=logger, service=set_level>
2022-06-01 22:17:23 INFO (MainThread) [homeassistant.setup] Setup of domain logger took 0.0 seconds
2022-06-01 22:17:23 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=system_log>
2022-06-01 22:17:23 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=logger>
2022-06-01 22:17:23 DEBUG (Recorder) [awesomeversion] Comparing '10.2.0' against '10.8.3' with 'compare_handler_container'
2022-06-01 22:17:23 DEBUG (Recorder) [awesomeversion] Comparing '10.2.0' against '10.8.3' with 'compare_handler_simple'
2022-06-01 22:17:23 DEBUG (Recorder) [awesomeversion] Comparing '10.3.0' against '10.8.3' with 'compare_handler_container'
2022-06-01 22:17:23 DEBUG (Recorder) [awesomeversion] Comparing '10.3.0' against '10.8.3' with 'compare_handler_simple'
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Connected to recorder database
2022-06-01 22:17:23 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=630 from 2022-06-01 20:17:16)
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:05:00+00:00-2022-06-01 19:10:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:10:00+00:00-2022-06-01 19:15:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:15:00+00:00-2022-06-01 19:20:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:20:00+00:00-2022-06-01 19:25:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:25:00+00:00-2022-06-01 19:30:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:30:00+00:00-2022-06-01 19:35:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:35:00+00:00-2022-06-01 19:40:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:40:00+00:00-2022-06-01 19:45:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:45:00+00:00-2022-06-01 19:50:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:50:00+00:00-2022-06-01 19:55:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 19:55:00+00:00-2022-06-01 20:00:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 20:00:00+00:00-2022-06-01 20:05:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 20:05:00+00:00-2022-06-01 20:10:00+00:00
2022-06-01 22:17:23 DEBUG (Recorder) [homeassistant.components.recorder] Compiling missing statistics for 2022-06-01 20:10:00+00:00-2022-06-01 20:15:00+00:00
2022-06-01 22:17:23 INFO (MainThread) [homeassistant.setup] Setup of domain recorder took 0.0 seconds
2022-06-01 22:17:23 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event component_loaded[L]: component=recorder>
2022-06-01 22:17:23 ERROR (Recorder) [root] Uncaught thread exception
Traceback (most recent call last):
File "/usr/local/lib/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
File "/usr/src/homeassistant/homeassistant/components/recorder/__init__.py", line 989, in run
if self._wait_startup_or_shutdown() is SHUTDOWN_TASK:
File "/usr/src/homeassistant/homeassistant/components/recorder/__init__.py", line 966, in _wait_startup_or_shutdown
return asyncio.run_coroutine_threadsafe(
File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 443, in result
raise CancelledError()
concurrent.futures._base.CancelledError
^C
I even tried removing my mariadb config, trying to make it use sqlite, but even that fails?
Shouldnt it be possible to start from scratch with sqlite?
Hmm, don’t see that error, bit there is indeed some issue with the logbook
I got the same error. Logbook + default_config 
So I rolled back for a while.
Does the new Google Calendar trigger offset survive a restart?
Ie. All day event triggers at 12am, offset set for 7:30 and system restarted at 6am. Does trigger start the automation at 7:30am?
Cc: @allenporter
Ty!
Thank you for the Update!
I have a strange behaviour since the update today. My Kodi media player disappears after shutdown to be not available anymore. Can’t turn it on anymore after shutdown.
The automation with the turn on Skript works when triggering manually. Can’t see what the reason is. All other WOL integrations work.
Thanks again!
1 Like
The reason was that loading the “State” tab can take a long time depending on the size of your HA instance. With the “YAML” tab being the first that mitigates that somewhat. But either way, HA remembers on which tab you were last (already did that in the previous HA releases) and will show that to you once you go back to the dev tools. So if you don’t use the “YAML” tab, you will rarely actually see it.
2 Likes