0.112: Making things faster; Logbook & History

Blog
268

I had to reinstall a couple of my cards from hacs.

269

Hi

after upgrading to 0.112.x I noticed a delay, sometimes very long, for MQTT messages.
I’ve always had the Mosquitto Broker addon and it’ was working fine before.

What can I check?

Thanks

270

I alone am not happy with the 0.112 update. Now I can’t use the custom_components xiaomi_aqara for my converted motion sensors, a trigger time every 12 seconds. Why didn’t you leave the possibility of the old configuration? Now I can not update HA’

271

My database is 3.2Gb. It is running mariadb in docker on the same machine as ha core (also in docker). It is a nuc. Intel® Core™ i5-5250U CPU @ 1.60GHz. 8G ram.

272

There is no aqara relay support again (

273

why not wait for the author to update the custom component or ask them to update it?

1 Like
274

My Xiaomy Awara Gateway didnt connet on 0.112.

  1. Comment out in configuration.yaml xiaomi_aqara.
  2. Xiaomi Aqara Gateway does not show up automatically.
  3. Trying to add with xiaomi_aqara Integrations.
  4. Didnt find it.

xiaomi_aqara host: 192.168.1.40
HA host: 192.168.2.34

And they connet to different routers.

P.S. “Xiaomi Miio: Gateway” integration see my gateway…

275

Instead of any for network interface on the integration screen try the IP for the device HA is running on.

276

Same here. I have had to update from the command line since 0.110.

277

I was talking about the update binary sensor.

278

’ve been experiencing issues with the the Lutron Caseta after upgrading to 112, my occupancy sensors are no longer detected. They were working fine on 111.4. I tried removing the integration and reinstalling and nothing. The lights work fine, in HA and the app, the sensors only work on the app.

Error while setting up lutron_caseta platform for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 186, in _async_setup_platform
    await asyncio.gather(*pending)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 292, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 343, in _async_add_entity
    device_info = entity.device_info
  File "/usr/src/homeassistant/homeassistant/components/lutron_caseta/__init__.py", line 134, in device_info
    "identifiers": {(DOMAIN, self.serial)},
  File "/usr/src/homeassistant/homeassistant/components/lutron_caseta/__init__.py", line 123, in serial
    return self._device["serial"]
KeyError: 'serial'
279

Ive skimmed through these posts but haven’t seen anyone asking if its possible to disable the frontend refresh. it seems to be messing with my RSTP camera streams. RSTP stream hasnt been the greatest but now its pretty unusable …Hope someone can help thanks

280

update to 0.112.1 and check the user profile on the device to disable the refresh

281

Yep same here - Xiaomi Air Purifiers have stopped working

282

Hi Yoinkz, i have added three aqara gateways in HA and they work without a problem.
I have problems with xiaomi philips light bulbs. After update to 0.112 they are not visible to HA, and they work normal in Mihome app. I even did reset one of the lamp for new token, but again no success.
Any ideas?
Thank you
BR

283

I tryed, but this dont work for me.

284

So you are across different subnets. Perhaps the new config method doesn’t support that?

285

Router 1 -> Router 2(lan) -> HA Pi3b+(lan)
Router 1 -> Xiaomi Gateway(WiFi)

286

I really like how fast history and logbook are after upgrade :+1: ! I do not like though the default settings that are applied to views :frowning: Every time I check history I have to reconfigure view from calendar selector to see exactly what I want to see.
Would it be possible to have some sort of default view configuration paramenetrs in history component to be added? Sort of:

default_view: 
  show: 24 h # number of hours to show
        2 d # number of days to show
  start: flex # start at exact number of hours/days back from now()
         day_start # start at midninght of first full inclusive day

So the old behaviour from pre 0.112 (show up to 24 hours from midnight) would be then configured as:

default_view: 
  show: 24 h
  start: day_start

and my preferred view (show last 48 hours) would be:

default_view: 
  show: 48 h
  start: flex

Obvioulsy just an idea, actual implementation could be done perhaps somehow smarter…

5 Likes
287

HIYerum, how did you fix the Toon Call back url issue? I can´t make it work with mine…
Thanks,