0.102: Official Android App, almond, scene editor
Home Assistant 0.102 is here ! It was quite the trip we invited you to our annual State of the Union last week, which has a lot of energy away from our Version. This does not mean that we have nothing to share, only that the notes polished, maybe a little less.
First, we had our State of the Union at the ING office in Amsterdam! It was great. You can see it again on YouTube or keep an eye out for the blog post coming soon, which is a summary of the announcements.
Alright, so what’s new? A Lot.
Android App released!
On the state of the Union, we have announced that we released the first version of the official Home-Assistant-Android app. It is still a work in progress, but the basic version is already working.
It was developed by @CedrickFlocon and the source code is available on GitHub. We have already seen how some other developer step, so this is great! Keep it coming.
We’ve teamed up with the Stanford tight Integration with its open, under the protection of the privacy of a virtual assistant almond in Home Assistant. For more information, see the separate blog post.
allow Some companies to integrate with their products via cloud APIs. These cloud APIs often use the OAuth2 specification, the link to the accounts. The problem with this specification is that it does not treat correctly, not with the public and / or remote installations.
So if you link a integration using OAuth2 ago today, you would have to account for a developer, you configure the Home-wizard, and you have to put your instance in the public before it to the part where you link to your account. This is not good!
Home Assistant Cloud, the introduction of a new account-linking service that will be freely available to all-no cloud account is required. With this service, Home-wizard, the developer controls the account, and the user only has to/the connection of your accounts.
The first integration to use this new service is Somfy. A manual installation is also possible. This integration is based on our new OAuth2 framework. We expect that more integration developers OAuth2 integrations in the future.
Create automations with natural language
As an experimental feature we have added a new way to create automations. With the help of almond, can we change the natural language in the Home-Assistant automation.
Screenshot create automation dialog box.
If the + in the automation editor to add a new automation, you will see a new dialog box where you can enter what you want to do your automation in natural language. Like:
Turn off the light when I come home. We will try to convert you in a automation. We will check if you need to specify, devices, or people that ask for this automation, and you, for you. You can then check the generated automation in the editor and save it.
note that not all devices are supported, yet, and, the almond needs more training for better answers. You check the almond-how you can help make almonds better.
Screenshot of the scene editor.
We will also be introducing a scene editor. With the scene editor you can simply save the States of devices in a scene. You simply select the devices (and/or facilities, if you are in advanced mode), you want to include in your scene, and set the conditions as you would like it, when the scene is activated.
to use the scene editor on your scene config should be in the File
scenes.yaml in your config directory and in the
configuration.yaml. Each scene should have a unique id for the editor.
# scenes.yaml id: my_unique_id # < work-- is Required for editor. name: Romantic People: Light.tv_back_light: on Light.Ceiling: Condition: on xy_color: [0.33, 0.66] Brightness: 200
configuration.yaml as follows:
# configuration.yaml example Scene: !You the scenes.yaml
In other news
Andrew learned, Swift, and creates a new mini-app for Mac:
With my new Swift skills, the I button is a tiny Mac-menu to app switch bar on @home_assistant https://t.co/N7wl2gXd2O
Save me, reach behind the printer for the embarrassing power.
Consider it alpha, I have a lot to learn, both swift and HA! pic.twitter.com/o6Wm7Le5nm
— Andrew Jackson (@AndrewCodeChimp) November 18, 2019
Our Android app is not the only new app on the block. @tuanha2000vn Hasskit, a new app has been released, with a Flap that can be used on both Android and iOS.
And finally, Brad has a video on Reddit shows off his amazing use of picture elements in Lovelace. Check it out:
users of Xiaomi vacuum cleaner, you can now use this great custom-Lovelace-map:
This custom card for Xiaomi vacuum cleaner allows you to say exactly in what part of the house to clean with your vacuum cleaner ?https://t.co/NJtrRLKvDZ pic.twitter.com/iNOOwt5Wxd
— Home Assistant (@home_assistant) 8. November 2019
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.
Huawei LTE – configuration consolidated under
huawei_lte. Device tracker is no longer used known_devices.yaml but entity registry. – (@scop – #26675) (huawei_lte docs)
huawei_lte: url: http://192.168.100.1/ User name: admin Password: something
Ikea Tradfri – This removes the battery sensor that was for the signal repeater. The sensor would never have a Status, and after some testing, it looks like the device will present all of the important metrics. – (@ludeeus – #28181) (tradfri docs)
/UPNP IGD – All of the UPNP/IGD sensors are in one device. You need to remove and re-integration, to add, to get rid of the previous devices. (@escoand – #27517) upnp (docs)
standby. Relates to user defined scripts, automations, etc.. (@ktnrg45 – #28261) (ps4 docs)
ssdpin the manifest.json has changed; it is now a list of dicts, and how we agree now with the UPnP device description of the fields directly,
device_typewas renamed to
device type. Not included integrations to use it at the moment, nor will they be broken by changing this. If you are functions, any custom Integra to use it, you need to adjust this accordingly. (@scop – #28285) ssdp (docs)
HomematicIP Cloud – The attribute naming between Homematic IP
HmIP-FSM/HmIP-PSM(switch) was different and in the case of light is not correct. The attributes for
have been renamed:
- energy_counter_kwh –> today_energy_kwh
- power_consumption –> current_power_w
Please check your automations, scripts, scenes, etc., if you are using the old parameters in templates and replace them with new ones. – (@SukramJ – #28271) (homematicip_cloud docs)
Plugwise – proof of a legacy-Anna (firmware 1.8.x) is not automatic: the owner of the legacy-Anna provide info in the configuration.yaml, on the last line. This change was necessary to fix the location issue #26520. – (@bouwew – #28237) (plugwise-docs)
climate: Platform: plugwise name: your_device_name Password: your_password host: your_anna_ip legacy_anna: true
Android TV – The
sources_list– the attributes for the Fire TV devices, use-friendly app name instead of app ID (e.g. “Netflix” instead of “com”.netflix.ninja”). If you have these attributes in automations, sensors, etc., you will need to update it.
- If you need to check that the
source– attribute of a Fire TV device to a specific app ID, you have two options:
- Check the
- Replace this app ID with the friendly name for the app.
- Check the
- When you check currently, the
sources_listattribute, then you need to check for the friendly app name instead of app-IDs.
continue.select_source service. – (@JeffLIrion – #28417) (TV dongle docs)
- If you need to check that the
Homekit thermostats supported by the Homekit Controller component, they reported “from” for the status to running when the HVAC was powered on but not actively heating or cooling. The
hvac_action– attribute is now correctly “empty run” instead of off. Any logic that tests for the
idle. There is no change to all other States. – (@GaryOkie – #28625) (homekit_controller docs)
OpenALPR local – The “alp_bin” option has been corrected to “alpr_bin”, as described in the documentation. User you should check your config” and update them if necessary. (@HexF – #28746) (openalpr_local docs)
Release 0.102.1 – 21. November
All of the changes
Released on Wed, 20 Nov 2019 00:41:02 +0000