Software-update: Home Assistant 0.94

Home Assistant logo (75 pix) Versie 0.94 Home Assistant is kort geleden uitgebracht en inmiddels is er ook alweer een kleine update vertschenen. Home Assistant 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 releasenotes voor deze uitgave zijn hieronder te vinden.

0.94: SmartHab, Watson TTS, Azure Event Hub

It is time for the 0.94 release and there is some seriously good stuff in this release. We’re working hard on polishing everything and getting ready for the big Home Assistant 1.0 release. And we’re getting closer. So close actually, that this is the first release that can be installed and configured without touching a text editor! Onboard, configure integrations, manage automations and scripts all from the UI.

This milestone has been achieved thanks to the hard work by @emontnemery who contributed the ability to store the core config in storage: name, location, unit system, time zone. We still allow users to store their core configuration in configuration.yaml, which will take precedent when defined. This means that it is a non-breaking change. Core config is now set during onboarding and can be edited in the general page of the config panel.

Another cool new feature is the total revamp of how you manage which entities are exposed to Google Assistant via Home Assistant Cloud. From the cloud UI you can now click “Manage Entities” and you are brought to the Google Assistant entity manager. From here you can enable which entities are exposed and, if you deem appropriate, choose to disable the two factor authentication on your garage door (the asking for a pin).

Discovery

Discovery has been modernized thanks to @Kane610 and with the input from @Jc2k. Each integration is now able to specify how they can be discovered in their manifest, and the new zeroconf and ssdp integrations will do the rest. The new discovery is non-obtrusive: no devices are set up without approval by the user. Instead, you will need to approve each discovered integration. You can find them in the discovered section of the integrations page in the config. Only a handful of integrations have been migrated to the new approach in this release: Hue, LIFX, Deconz, Trådfri, Axis, ESPHome, HomeKit Controller.

The new discovery is now part of the default config. If you are not using the default config, add ssdp: and zeroconf: to your configuration.yaml.

Deprecating Python 3.5 support

This release has deprecated support for the almost 4 year old version 3.5 of Python. The first Home Assistant release after August 1 will drop support. This is part of our newly adopted Python support approach.

This will only impact you if you are running a custom installation of Home Assistant. This will not impact anyone using Hass.io or Docker. If you are using hassbian, you can upgrade Python by following these instructions.

Modernizing the device tracker

This release also introduces a long overdue overhaul of how the device tracker works. We are introducing this overhaul piece by piece, focusing first on device tracker platforms that push their updates to Home Assistant: mobile app, OwnTracks, GeoFency, GPSLogger and Locative.

These integrations will no longer use known_devices.yaml but instead use entities, like all other integrations in Home Assistant. You can change the name and entity ID via the UI. It is no longer posible to merge the devices with other device tracker entities. This was flaky at best. You should now use the new person integration for this.

Improved hass.io builds

We have been working hard on improving Hass.io builds. It’s our goal to make the update process faster and more predictable. A build can now be online in as little as 30 minutes after a new release has been tagged. This is thanks to a new wheel-based infrastructure build by @pvizeli with input from @frenck. With Python wheels, we will build all the requirements of integrations ahead of time, and so a new version of Home Assistant is now just putting pieces together.

Because of this, we changed how packages are installed when running Home Assistant inside a Docker container. It will now install the packages into the Python environment inside the container, instead of storing them in the config/deps folder, which lived outside the container.

Note: Because of the new way packages are installed, Home Assistant on Hass.io will take longer to start the first time it is launched after an upgrade. Don’t worry and let it finish! We are working on making this process faster in the future.

Note 2: If you are using Hass.io or a dockerized version of Home Assistant, this release will one time clear the deps folder in your config folder.

New Integrations New Platforms Release 0.94.1 - June 7

Versienummer 0.94
Website Home Assistant
Download https://home-assistant.io/getting-started/
Licentietype GPL

Reacties (7)

7
6
5
1
0
0
Wijzig sortering
Nog mensen zoekend naar een lovelace setup? Hier een link naar mijn huidige setup, veel plezier:

https://github.com/jimz011/homeassistant/
Thanks, een lovelace setup lijkt me een enorm werk, bedankt voor de inspiratie!
Ik wist niet dat er een hoop 3rd party "plugins" beschikbaar zijn. Ik heb dat nergens op de officiële HA site teruggevonden.
Klopt op de officiele site staat alleen in hoe je zelf custom components kunt maken. Niet echt weggelegd voor non-developers. Maar je zou eens kunnen kijken op de Home Assistant community forums. (Die is ook officieel). Er is heel veel mogelijk en ben zelf ook nog altijd aan het experimenteren. Had eerst 22.000 regels code en dat is nu zo’n 10.000 minder. Ben nog aan het proberen daar de helft van te maken door slimmer gebruik te maken van templates.

Uiteraard kun je verwachten dat ik mijn github repo update zodra ik klaar ben met de volgende release.

90% van alle custom cards zitten in mijn setup en alle links daarvoor vind je in de readme op github. (De link die ik eerder deelde).
Wat?! Dat ziet er fantastisch uit! Goed gedaan!

Nog meer dank voor de tutorial, ik ga hier op een vrije dag eens rustig naar kijken om te zien wat ik hier voor mezelf uit kan halen. Dank!
Graag gedaan.
Inmiddels is 0.94.1 te downloaden op de website

Op dit item kan niet meer gereageerd worden.