The changes for history are welcome as it’s unusable <0.112. I can view a single day easily now but 2+ days freezes again. Is it possible to include an entity filter? I have many entities but only usually need to see the history on one and I think that’s the big hurtle as why history is still very slow. Thanks!
1 Like
Both the recorder and logbook integration have include/exclude filters. The documentation describes those and allows you to pre-filter what gets recorded or shown.
No doubt this is great improvement!
Unfortunately I cannot enjoy it with the current setup.
My database is MySql, stored on network shared drive.
Until this upgrade, it was working fine. Now, it takes almost 1 hour to start HA, with the following error
If I remove
db_url: mysql://homeassistant:XXXX@[email protected]/homeassistant?charset=utf8
which means I go back to SQLite stored on the DS card, everythign is up and running in no time.
Since I do not want to keep the database on the SD, seems I’ll have to downgrade back to previous version and wait for this improvement to be fine-tuned for externaly stored databases.
Anyway, good improvement!
Yes, I am noticing the same after updating to 0.112. I am still using the default UI and I have hid quite a few. Now it all returned.
Thanks so much for making the logbook work again! It was unuseable before.
In my opinion the logbook really could use better filters and more info.
Filters I would use:
- Filter by device instead of entity
- Filter by string
- Filter by area
- Checkbox to show everything related of the selected entitiy. E.g. automations that switch my selected light.
Info that would help alot:
- show what did the state change (if automation/script or from device itself/external)
3 Likes
My 3H does has stopped working as well.
Im not sure where to log this issue?
0.112.1 made an attempt to fix this. Not quite there yet. Dates selected are right but start and end dates on calendar are not highlit if you straddle a monthend.
just updated from 0.111.4 to 0.112.1 and all good expect for the Air Visual - the lovelace card is now erroring now with
Custom element doesn't exist: air-visual-card.
any suggestions?
UPDATE:
So to fix this i found i had to update the .js file location in the lovelace resources from what it was
Was - /hacsfiles/air-visual-card/air-visual-card.js
To - /local/community/air-visual-card/air-visual-card.js
Was there something hidden in 112.x that changed in this area?
Has anyone else using the “HomeKit Bridge” Integration have a problem with it not working after the update to 0.112?
My bridge will not start no matter what.
I’m on iOS 13 and using the “Supervised Generic Linux” Install.
WHY OH WHY move MQTT and Log tabs.
These are integral to developer tools. You trigger a newly developed automation or other service and you want to see why it didn’t behave as expected so you refer to the Log. Or if MQTT is involved you leave MQTT listening as you have your automation have a dialog with a device.
PLEASE PLEASE PUT THEM BACK.
4 Likes
I just use the version sensor to let me know when an update hits.
sensor.yaml:
- platform: version
name: Installed Version
source: local
- platform: version
name: Latest Available Version
beta: false
image: default
source: docker
The history frontend isn’t virtualized yet like logbook. The backend can now deliver the data quickly but we still have another step to make the history UI with all the graphs at once zippy.
There’s a great workaround for this from the master.
Not for mqtt, but better than nothing.
It looks like your database schema failed to upgrade and it’s stuck trying again. I opened https://github.com/home-assistant/core/pull/37384 to handle this state.
If it’s not fixed by https://github.com/home-assistant/core/pull/37384 please open an issue with the full log output
There is only one browser on iOS - Safari. All other browsers, Firefox / Chrome / Home Assistant companion app / etc, are simply using the Safari browser to display their content. Apple does not allow any other browsers. That is why they all behave the same.
1 Like
Very good upgrade! Thank you so much!
Same problem. Any solution yet?
Thanks guys. Great update.
