0.112: Making things faster; Logbook & History

I am using mariadb and I am pleased to advise that the database seems to have updated just fine. I still have data back to well before updating to 0.112. Well done on upgrading the database schema to get these speed improvements. Love your work.

Same on the rest of the update, all working fine.

is https://github.com/home-assistant/core/pull/37268 in 112.2 too, or do we have to wait for 113? Would be very nice to have this asap… :wink: #fingerscrossed

This looks similar to my issue, where during the migration it says it loses connection to DB, but the DB remains up, then it’ll start and Recorder won’t work.

Got this message while trying to update to 112.1
HomeAssistant update fails -> rollback!

20-07-03 07:21:56 INFO (SyncWorker_19) [supervisor.docker.interface] Update image homeassistant/intel-nuc-homeassistant:0.112.0 to homeassistant/intel-nuc-homeassistant:0.112.1
20-07-03 07:21:56 INFO (SyncWorker_19) [supervisor.docker.interface] Pull image homeassistant/intel-nuc-homeassistant tag 0.112.1.
20-07-03 07:22:56 ERROR (MainThread) [supervisor.utils] Can't execute update while a task is in progress
20-07-03 07:23:07 INFO (SyncWorker_19) [supervisor.docker.interface] Stop homeassistant application
20-07-03 07:23:08 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Received message 8:1000 is not str
20-07-03 07:23:08 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API connection is closed
20-07-03 07:24:08 INFO (SyncWorker_19) [supervisor.docker.interface] Clean homeassistant application
20-07-03 07:24:08 INFO (MainThread) [supervisor.homeassistant] Update pulse/client.config: /data/tmp/homeassistant_pulse
20-07-03 07:24:08 INFO (SyncWorker_8) [supervisor.docker.homeassistant] Start homeassistant homeassistant/intel-nuc-homeassistant with version 0.112.1
20-07-03 07:24:13 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation in progress
20-07-03 07:24:28 INFO (MainThread) [supervisor.homeassistant] Updated Home Assistant API token
20-07-03 07:25:08 INFO (MainThread) [supervisor.homeassistant] Home Assistant pip installation done
20-07-03 07:35:10 WARNING (MainThread) [supervisor.homeassistant] Don't wait anymore of Home Assistant startup!
20-07-03 07:35:10 CRITICAL (MainThread) [supervisor.homeassistant] HomeAssistant update fails -> rollback!
20-07-03 07:35:10 INFO (MainThread) [supervisor.homeassistant] Update Home Assistant to version 0.112.0

System is okay, however I could not upgrade to 112.1

Whenever i update, the update seems to go through fine, everything boots up and is working fine, shows on the latest version number then after a few mins home assistant restarts and never comes back up. I have to manually power cycle and when it starts up its back on the old version? Anyone else seen this happen?

Hello, I will need some help please. Namely after upgrade to 0.112 my xiaomi philips lamps are not working. Can you point me in which direction to go.
Thank you very much.
BR

I have a question about multiple entities in condition.
Is this:

condition:
  condition: and
  conditions:
    - condition: time
      after: "00:30:00"
      before: "06:00:00"
    - condition: or
      conditions:
        - condition: state
          entity_id: light.bulbs_salon
          state: "on"
        - condition: state
          entity_id: light.leds_salon
          state: "on"
        - condition: state
          entity_id: light.lamp_salon
          state: "on"

can be shortened to this:

condition:
  condition: and
  conditions:
    - condition: time
      after: "00:30:00"
      before: "06:00:00"
    - condition: or
      conditions:
        - condition: state
          entity_id:
            - light.bulbs_salon
            - light.leds_salon
            - light.lamp_salon
          state: "on"

You never needed the condition: and since conditions are logic ‘and’ by default

Yes I know that. So the list of entities works with or condition?

It doesn’t appear to be documented. Give it a try and let us know :slight_smile:

No. All those lights have to be on for the condition you have to be true.

2 Likes

Another great release, thank you. No issues with DB, and snappy.

I have three Denon receivers, updated to the new integration. The log now include houndreds of:

Input function SOURCE is not known
(time) - components/denonavr/media_player.py

I do query the source (via sensor) and it reports correctly, and I can select the source.

Can I help with more information?

Looking at it again, Tom is certainly right. That ‘or’ would ‘or’ against another item in the list, ie:

    - condition: or
      conditions:
        - condition: state
          entity_id:
            - light.bulbs_salon
            - light.leds_salon
            - light.lamp_salon
          state: "on"
        - condition: state
          entity_id: switch.something
          state: 'on'

where the first 3 are still a logic ‘and’ group and then they logic ‘or’ against the one below them

2 Likes

Thank you everybody who is involved for the continuing amazing work!

I got a failure and my Logbook just shows the loading indicator:

Logger: aiohttp.server
Source: core.py:118
First occurred: 10:30:41 AM (1 occurrences)
Last logged: 10:30:41 AM

Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py”, line 418, in start
resp = await task
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py”, line 458, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py”, line 119, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/real_ip.py”, line 39, in real_ip_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 73, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 127, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 129, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/logbook/init.py”, line 195, in get
return await hass.async_add_job(json_events)
File “/usr/local/lib/python3.7/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/usr/src/homeassistant/homeassistant/components/logbook/init.py”, line 192, in json_events
_get_events(hass, self.config, start_day, end_day, entity_id)
File “/usr/src/homeassistant/homeassistant/components/logbook/init.py”, line 376, in _get_events
entity_ids = _get_related_entity_ids(session, entities_filter)
File “/usr/src/homeassistant/homeassistant/components/logbook/init.py”, line 335, in _get_related_entity_ids
result = [row.entity_id for row in query if entity_filter(row.entity_id)]
File “/usr/src/homeassistant/homeassistant/components/logbook/init.py”, line 335, in
result = [row.entity_id for row in query if entity_filter(row.entity_id)]
File “/usr/src/homeassistant/homeassistant/helpers/entityfilter.py”, line 167, in entity_filter_2
domain = split_entity_id(entity_id)[0]
File “/usr/src/homeassistant/homeassistant/core.py”, line 118, in split_entity_id
return entity_id.split(“.”, 1)
AttributeError: ‘NoneType’ object has no attribute ‘split’

I checked my MariaDB and it looks like the upgrade went well

I just put in a netgate/pfsense firewall as well as 4 unify UAP-AC-M-US mesh AP’s a couple weeks ago replacing all my other various ap’s. The Ubiquity management server caused me a bit of grief at first and one unit was stubborn about adopting but its all stable now that it’s on my NUC. I was on a FaceTime call w my sis tonite and walked around my property and the AP roaming/handoff function was Simply flawless. It was so good, I didn’t even realize it at the time. No way I could do that before. Its certainly got my vote.

This last update to supervisor 228 was an unmitigated disaster as my install is on Supervised on generic Linux/Docker (recently un-deprecated, thankfully) on my NUC but a full reinstall/restore fix it. After moving off my Pi, I’m Loving Ubuntu. What a Slick OS.

Jeff

wow, this is awkward. seeing this for all my scripts rendering the integration script invalid, which of course makes my complete HA instance useless:

Package package_printers setup failed. Integration script cannot import name 'EVENT_SCRIPT_STARTED' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py) (See /config/packages/package_printers.yaml:5).

It only mentions the packages because the script is declared there. All scripts are gone…

I am testing the new script integration as a custom component, so that might be it (it worked flawlessly on 111.4) but taking it out also causes issues, rendering the script integration not to be setup.

Anyone else having script issues?
Paulus, if you see this please chime in, you know all about the script integration Phil is working on (not tagging here…:wink: )
could this cause the error, and if not what could?
where have these services gone: https://github.com/home-assistant/core/blob/ab4687d914b600fb678bd93fbcaf4ae94f5abdb3/homeassistant/const.py#L184

Yes has now been added in again on documentation about 30 mins ago. Tks

I’m with you on this one. 90+% of the time I use home assistant from iPads/iPhone. History flashes briefly on safari, but nothing on chrome. Very annoying. At least let me remove the link When I’m on iOS to free up some Menu real estate.

Oh yes, I got MQTT too !
Add in the HACS sidebar-order feature and I have made space for what I need to add too.
Thanks @VDRainer

  - name: panel-redirect
    # url_path needs to be unique for each panel_custom config
    url_path: redirect-mqtt-controls
    sidebar_title: MQTT
    sidebar_icon: mdi:lan-pending
    module_url: /local/panel-redirect.js
    config:
      # Where you want to redirect to
      target: /config/mqtt?config_entry=88d8fc6108a64d61a78bf7236a21b7c9
1 Like

I’m trying to decide if I move to openZwave beta or I wait for the migration room/automated process.

Do we have an ETA on that? I mean ballpark wise, are we taking days, weeks or months?

Thanks!