Versie 0.112 van Home Assistant Core is uitgebracht. Home Assistant Core is een opensourceplatform voor home-automation dat draait onder Python 3. Het draait via Hassbian op een Raspberry Pi 3 of een Linux-, macOS- of Windows-computer. Het ondersteunt het detecteren van apparaten, zoals Nest-thermostaten, Philips Hue, Belkin WeMo-schakelaars, Mr. Coffee-koffiezetapparaten, de slimme schakelaars van IKEA en het mqtt-protocol. Daarnaast kan het waar mogelijk deze apparaten aansturen en automatisering toepassen. Voor meer informatie verwijzen we naar deze pagina en ons Forum. De aankondiging voor deze uitgave is hieronder te vinden.
0.112: Making things faster; Logbook & HistoryAnd another three weeks passed! Home Assistant Core 0.112!
At this point, I almost feel like “Making things easier” as the motto for our current development is replaced by: Making things faster!
The last couple of releases, tons of performance improvements where made, most notably the frontend starting sooner in the previous 0.111 release.
This release is no exception, bringing absolutely game-changing performance improvements to the logbook and history panels. Honestly, I avoided using the logbook in the past because of the slowness it had.
Personally, I feel like Home Assistant is growing up. Slowly things become more reliable, faster, easier to use, slick, more fine-grained? I might be biased a bit… What do you think? What is your favorite improvement that was made lately?
Enjoy the release!
../Frenck
Important upgrade notice!Let’s start with an important notice for upgrading to Home Assistant Core 0.112.
This release has changes to the database format of Home Assistant. On upgrade, it will be migrated to the new format.
Depending on the size of your database and the performance of the hardware you run Home Assistant on, this migration process could add additional time to the first time starting after the upgrade. For most of us, this adds just a couple of minutes, but if you have an enormous database (for example, 30+ GiB), it might take an hour or maybe even two.
So, don’t panic if Home Assistant doesn’t come up immediately.
Logbook and HistoryThe reason for the above-mentioned database change can be found in the Logbook & History. Thanks to @bdraco, who has been improving this part of Home Assistant the past weeks.
As a result of his effort, the History & Logbook are now lightning fast. ⚡️
Not a tiny bit faster, but a whole new experience compared to how it used to be. Fantastic work there @bdraco!
Logbook and History now have a date/time range pickerSo, @bramkragten stepped on the Logbook & History train and made the logbook and history panels a lot more flexible.
You no longer have to choose between a fixed period to show, but can define the period you want to see data for yourself.
Select a start and end date and time window and it will show just that data.
By default it no longer shows a full day of data, but just a couple of hours so it is even quicker to load. As most of the time, one would look at recent events anyways.
The user that made a change visible in the logbookTalking about the logbook, you can now also see who made a change in the logbook! No more discussion about who changed the temperature!
Multiple entities and states in YAML automationsAre you writing your automations in YAML? You might appreciate this one:
A single condition rule can now test if multiple entities match the condition. Furthermore, states and zones now also accept a list in a condition. That helps testing if the entity matches any of the ones listed.
Integration specific panels are now on the integrations pageSome integrations, like ZHA, Z-Wave and MQTT have their own panels or dev tools. For things like pairing devices or publishing MQTT messages.
These used to be on the configuration page or development tools, which was weird because the integration settings would be on the integrations page. ZHA also had a lot of device settings in its own panel, resulting in a lot of duplicate functionality spread across the Home Assistant interface.
These panels and tools are now moved to the integrations pages, directly within the integration that provides those. You can find them on the card of the integration at the
Configurebutton.The device-specific settings are now available on the device page, so we now have 1 place to go for information and settings for devices.
In the process, we also cleaned some things ups, like adding a device in ZHA. If you change the name of the device while adding it, the entities and entity IDs are named accordingly.
New home for the logs and information pagesMore moving this release, the logs and information pages used to be in the development tools panel, but they didn’t really belong there. They aren’t really tools for developing, they provide information on your set up.
We moved them to the configuration page where they are joined with server management and the general configuration.
Automatically disconnect if a tab has been hidden for 5 minutesAn improvement in the battery of your device and your data cap are going to like:
When the Home Assistant UI is not visible for longer than 5 minutes, it disconnects from your Home Assistant server. This means you no longer get data or camera streams and your device can optimize resource and power consumption.
Of course, when showing the browser (or browser tab) again, it will automatically reconnect.
We now show all automation/scenes/scriptsAutomations, scenes and scripts in the configuration panel are no longer hidden when they have the
hiddenattribute. This was erroneously added in the past and has now been undone.Talking about the old
Other noteworthy changeshiddenattributes. They have been slowly deprecated over time, as they originate from the previous Home Assistant UI. As of this release, this attribute has been completely removed from the system.New Integrations
- @balloob has shaved of a couple of seconds from the Home Assistant startup again.
- Entities that originate from MQTT will now become “unavailable” when the integration is not connected to the MQTT broker. Thanks @elupus!
- If you have a Xiaomi vacuum cleaner, @jthure added a service to send it to specific places using a new goto service.
- The Smappee integration has been fully rewritten, by @bsmappee themselves!
- Auto discovery has been added to the NUT integration. Please note that some NAS devices might be discovered as they support adding an external battery.
New Platforms
- Add notify_events notify integration (@papajojo - #36049) (notify_events docs) (new-integration)
- Add HVV integration (Hamburg public transportation) (@vigonotion - #31564) (hvv_departures docs) (new-integration)
- Add new Remote Python Debugger integration (@frenck - #36960) (debugpy docs) (new-integration)
- Add new humidifier entity integration (@Shulyaka - #28693) ([humidity docs]) (new-integration)
Integrations now available to set up from the UI
- Add devolo binary_sensor devices (@2Fake - #36370) (devolo_home_control docs) (new-platform)
- Add sensor platform for vicare integration (heatpump) (@crazyfx1 - #34385) (vicare docs) (breaking-change) (new-platform)
- Add Withings webhooks (@vangorra - #34447) (withings docs) (new-platform)
- Light control support to Axis devices (@Kane610 - #36611) (axis docs) (new-platform)
- Fix/Rewrite of Toon integration (@frenck - #36952) (toon docs) (breaking-change) (new-platform)
- Part 2: Add signal sensor (@ocalvo - #34406) (sms docs) (new-platform)
- Part 3: Add support for incoming sms events (@ocalvo - #37015) (sms docs) (new-platform)
- Add smappee binary_sensor platform (@bsmappee - #37023) (smappee docs) (new-platform)
- Add devolo sensor devices (@2Fake - #37049) (devolo_home_control docs) (new-platform)
The following integrations are now available via the Home Assistant UI:
- Arcam, done by @elupus
- Avri, done by @timvancann
- Awair, done by @ahayworth
- DenonAVR, done by @starkillerOG
- MetOffice, done by @MrHarcombe
- Plum Lightpad, done by @prystupa
- Smappee, done by @bsmappee
- SMS notifications via GSM-modem, done by @ocalvo
- Speedtest.net, done by @engrbm87
- Squeezebox, done by @rajlaud
- Tile, done by @bachya
- Xiaomi Aqara, done by @starkillerOG
:fill(white):strip_exif()/i/2006976478.jpeg?f=thumbmedium)
/u/482160/crop5f2d01c062aaa_cropped.png?f=community){kind=small}
