0.103: Happy Holidays, Service calls, StarLine, GeoNet NZ, and Proxmox
Here it is! Home Assistant 0.103 is released, and this is the last major release
for this year. For the last piece of this year, we have focused
Cleaning Things. This Version contains a lot of things that were
in progress (e.g. due to hacking upper), many bugfixes, especially
Things that help improve the stability and experience of the Home-the wizard.
We wish you a merry Christmas! As always, we dispense with a release cycle to the end
of the year, so this is the final major release of 2019. This is all
the time to enjoy the holidays with our families.
The first Version of 2020, are on 15. January.
In addition, we would like to take the opportunity to thank all of our contributors,
no matter how small or large the contribution, code, documentation,
Problem reporting, beta testing, supporters in our
the forum and chat.
We salute and thank you and wish you the best for the new decade
as we are in 2020! free to play game.
Services have been moved to their respective integration namespaces
0.103, an extensive cleanup has already taken place, the names of the
services. We realize this affects a lot of users; therefore, we have taken care of all these
changes in this Version.
This change was driven by @raman325, who has an excellent work
this is the time to 0.103.
We have used services that were provided, in other domains,
this was not always the case, and, therefore, inconsistent.
So, for example, the service to add an item to Todoist was actually a service
with This release, all of the services not correctly placed, moved, in their
appropriate integration domain. So, for the example above
calendar.todoist_new_task was todoist renamed in
We hope this brings a streamlined experience of the use of the services,
for now and in the future. For a complete list of old vs. new-service-name,
Move imports of Python packages
Internally, the Home Assistant used a lot of Python packages that our integrations
use. In the last few weeks, the places where all of these imports
The place has changed. These are not directly in resonance with the system
and, above all, internal cleansing is action.
A big shout out to the following employees who are jointly responsible
to help for the production of hundreds posts the last couple of weeks, to us:
@Bouni, @briglx, @djpremier, @exxamalte, @javicalle, @Michsior14,
@Misiu, @mnigbur, @Quentame, @spring Stan @thaohtp, @tulindo
Python-3.6-support is deprecated
has been deprecated Since version 0.101, support for Python 3.6. We are
currently support work on Python, 3.8 -, which is expected soon.
Therefore, this release is the last Version that supports Python 3.6.
If you not yet updated your system to Python 3.7, it will,
to do so, to ensure that you can keep up with the Home Assistant in the future.
If you are using Docker or hatred.io, you don’t need to worry about,
we offer a matching and working version of Python for you.
Frenck joins the Nabu Casa
As previously announced, during the state of the Union 2019,
Frenck has Nabu-Casa.
Today is the first day of my full-time open-source adventure! ? Heading into my office this morning, full of energy and a lot of gratitude for this opportunity! I feel blessed to be able to work on @home_assistant for @NabuCasa ? pic.twitter.com/mjkMYeCNaz
— Franck Nijhof (@Frenck), 2. December, 2019
We have some love and attention to the automation editor,
Fixing some bugs and adding a few useful features.
< / h3>
Natural language improvements
We add support for automations, providing you with natural language,
and we try to find the right surface or the device for you, if you mentioned the name.
So, you can say now: “Turn on the light in the living room,” and she adds, all
the slight devices in your living room, automation.
By clicking on the
Select each device allows you to add or remove devices.
Screenshot of the result of the above query.
< / h3>
you can now edit each trigger, condition or action, such as YAML.
This makes it possible, even very complex automation in the
the automation editor allows you to copy parts of your automation system quickly.
Screenshot of the automation YAML editor.
< / h3>
We also added the ability to change the order of the actions, so that you don’t have to start
all of the above, if you want, add a delay between 2 service calls.
Talk about the service-call to action, now has a firm picker
you have to help the search for the right.
Screenshot of the automation of actions.
In other news
looking for a gift for the holidays? T-shirts with our rainbow logo are now available in our online Shop. ?
EU: https://t.co/KiTDuOFgG2 you
US: https://t.co/OdtILXBoDh pic.twitter.com/BG5mDWhwYN
— Home Assistant (@home_assistant), 5. December, 2019
[email protected]_assistant for the iOS version, 2019.1/2.0 is now (finally) available in the App Store near you! Also releasing today: beautiful new documentation for the app! Check it out on https://t.co/4RhY8tOand. pic.twitter.com/YkuhhdRjwu
— Robbie Trencheny (@Robbie) November 26, 2019
Home Assistant: Controlling Addressable LEDs like all of the other light! (WLED-integration) https://t.co/bJJMkZbdn9 @home_assistant @Frenck #home assistant #wled #ws2812b #tutorial #howto
— Intermittent.Tech (@Intermittent Tech) November 25, 2019
The following integrations have been added in this Version:
The following platforms have been added to existing integrations:
If you are an existing user, be sure to read update in this section, ” before,
this helps you to understand the changes and avoids problems when upgrading.
< / h3>
will move All the services for use in the Home Assistant, your integration naming space.
the list below shows The service calls and platforms have been moved to their own integrations – @raman325
the Local file:
the Elk-M1 controller:
the alarm decoder Alarm:
the blue sound:
the sound touch:
the Xiaomi Miio:
the Xiaomi Miio:
< / h3>
Other important Changes
Mobile App – Download the Mobile App no longer causes the Cloud integration will be loaded. If you relied on this, add
cloud:in your configuration.yaml. – (@balloob – #29373) (mobile_app docs)
Samsung TV – The behavior for next and previous track commands to the Samsung TV has changed. Before the change, the Samsung TV integration responded to the two above-mentioned commands, the KEY_FF and KEY_REWIND send commands. While doing TV programs, these two commands have nothing to. After the change, the Person, instead of sending the KEY_CHUP and KEY_CHDOWN commands, allowing the user to change the channel with the media player-standard-Lovelace-interface. The user does not need to change anything in the configuration. – (@tulindo – #28213) (samsungtv docs)
Wake on LAN – The configuration key
mac_address:was renamed to
mac:in sync with the service. (@fabaff – #28830) (wake_on_lan docs)
PulseAudio Loopback switch – The default port was set incorrectly 4712, however, the official documentation States that the default port 4713. So, the port was changed and all the previously configured network switches must now on port 4713. – (@spring Stan – #28857) (pulseaudio_loopback docs)
Z-Wave – This changes the primary command class z-wave thermostats in the discovery schema of
COMMAND_CLASS_THERMOSTAT_MODE. Thus, a typical dual is displayed-setpoint thermostat correctly, as a single unit. – (@oandrew – #27040) (z-docs)
Transmission – added the host field,
add_torrentservice, in order to support multiple Transmission instances. (@engrbm87 – #28653) (transfer docs)
Opentherm Gateway – Adds support for the device. This change breaks enabled,
binary_sensorentities, which are now disabled by default and can be enabled through the devices panel. It is also
entity_idthe air-conditioning unit in some configurations, to break. To ensure that the
gateway_idinstead of configured
namefor uniqueness. – (@mvn23 – #28722) (opentherm_gw docs)
intention – If the
configuration is the built-in intentions, for the shopping list, cover, or light, you must.yaml. – (@balloob – #29280) (interview docs) (cover docs) (intent-docs) (light-docs) (shopping_list docs)
Emulates Hue – As the previous
entityidis not Hue-compatible,
emulated_hue_ids.jsonmust be deleted and the devices are re-detected and configured Alexa / Google homepage. This is a necessary growing pain, the integration to the front in a Hue-compatible fashion. – (@Noble kangaroo – #28317) (emulated_hue docs)
Miflora – values for a non-responsive device is not reported any more, as if they were valid, so it is possible to send an Alarm. – (@available – #29276) (miflora docs)
- id: plant_unreachable alias: system not reachable trigger: - entity_id: the sensor.plant_moisture for: 01:00:00 Platform: Condition to: not available Action:
Entity ID – It is no longer possible, and addressed to all persons not to pass by, both
area_idto your service data. This feature was previously deprecated and print warnings. The right way to the goal, to set all the people, is
entity_id: all– (@balloob – #29178)
Heatmiser-Thermostat – The Heatmiser was updated integration to the latest version of the heatmiserV3 library, which means less code, in HA, and more influence on the library. The current version of the Heatmiser integration was deprecated with the introduction of sensual. This has now been fixed, but it is the old config syntax breaks easily. You can find the updated documentation for the new config format. – (@andylockran – #29006) (heatmiser docs)
If you are in need of help…
…do not hesitate and use our own very active forums, or join us for a little chat.
problems introduced in this Version? Please log in our issue tracker. Make sure you fill in all the fields, the Problem template.
All of the changes
Released on Thu, 11 Dec 2019 17:00:00 +0000