+ Screenshot of our new configuration panel.
+
+ 0.39: Configuration panel, state restoration and improved docs
+ + + + + +It’s time for 0.39 and this release has some amazing new features!
+ +
T-Shirts
+ +First off, in case you haven’t seen it yet: we have t-shirts now and they are beautiful. All proceeds from the shirts will be donated to the Electronic Frontier Foundation. The first three days all of you have already raised $400! Still waiting for Teespring to get back to me so stay tuned for the EU store.
+ +Configuration panel
+ +Yep, you read that right. We have a configuration panel. It’s just the first of many small steps. Putting in a foundation is important and gives us something to iterate on.
+ +To start, we have three simple configuration panels:
+ +-
+
- Core: allows you to validate config, reload core/group/automation config and restart/stop Home Assistant +
- Group: allows you to rename groups, change type between group/view and reorder entities. +
- Z-Wave: allows you to set device specific configuration settings +
+ 
+ Screenshot of our new configuration panel.
+
As a security measure, the configuration panel will need to be activated in the config file to be activated. This can be done by adding the following to your configuration.yaml:
config:
+Using our configuration panels will require you to structure your groups and Z-Wave device config according to how the configuration panel expects it. This is on purpose as it we will not be aiming to build a system that supports both our extended set of configuration extend hooks and our configuration panels. It’s one or the other.
+ +To activate them in your config, create empty files groups.yaml and zwave_device_config.yaml in your config dir and add the following entries to your config:
groups: !include groups.yaml
+
+zwave:
+ device_config: !include zwave_device_config.yaml
+Note that this is the first release. Things will be missing, things might be broken.
+ +Reorganized documentation
+ +Thanks to Fabian we have a great re-organized documentation. Is it perfect yet? No. But we are getting close. We put a lot of focus on making sure the Raspberry Pi is the main focus of our getting started. The other instructions are still available, just not as part of the main getting started.
+ +State restoration
+ +Ever have some input components or integrations and get annoyed with the fact that their state is lost after a restart? Don’t worry any longer. Johann has added the foundation for state restoration to Home Assistant. For the initial release support has been added to to input_select and input_boolean components. We will be adding this to more integrations in the future.
Breaking changes to customize and Z-Wave “customize”
+ +A couple of releases ago we introduced a new way of doing customize. It became a list that allowed different ways of matching the config to the entity.
We realized that this was leading into a rabbit hole that we had to get out off. Besides making it unnecessarily complicated it also blocked the road to config panels. And who doesn’t like config panels?
+ +So starting this release, we had to make some breaking changes to right the wrong. We will be releasing an online tool to help you convert your config to the new format later today.
+ +Customize has been reverted to it’s original config
+ +The old customize is back. The options to match by domain or using glob have been moved to it’s own options. It will now look like this:
+ +homeassistant:
+ customize:
+ light.kitchen:
+ hidden: true
+ customize_domain:
+ light:
+ icon: mdi:home
+ customize_glob:
+ "light.kitchen_*":
+ icon: mid:description
+Z-Wave customize is now device config
+ +Ever wondered why the Z-Wave customize was called customize? Yeah, so did we. So when migrating this to the new config format, we decided to upgrade the name too:
+ +zwave:
+ device_config:
+ light.kitchen:
+ ignored: true
+ device_config_domain:
+ light:
+ polling_intensity: 2
+ device_config_glob:
+ "light.kitchen_*":
+ polling_intensity: 0
+Speed improvements
+ +And a final shout out to Pascal. He keeps improving the performance of components and platforms all over Home Assistant.
+ + + +All changes
+ +New platforms/components
+ +-
+
- Telegram webhooks (@scipioni) +
- Added Openhome support (@bazwilliams) +
- UPS sensor (@happyleavesaoc) +
- FEDex sensor (@happyleavesaoc) +
- Gstreamer media player (@happyleavesaoc) +
- iTach Remote Platform (@alanfischer) +
- myq cover component (@arraylabs) +
- Support for the Open Energy Monitor Thermostat (@Cadair) +
- Added Fritzbox Netmonitor (@PetePriority) +
- Add platform for Yeelight Sunflower lights (@lindsaymarkward) +
- Support for Pocket Casts (@molobrakos) +
- VolvoOnCall component with support for sensors, heater and lock (@molobrakos) +
- Add pushsafer.com notification service (@appzer) +
- Websocket push notifications for Kodi (@armills) +
- New component ‘insteon_plm’ and related platforms (@nugget) +
- Add aurora sensor (@walkerdb) +
- Add Ebox sensor platform (@titilambert) +
- Mediaplayer clementine remote (@jjmontesl) +
- Add Fido sensor (@titilambert) +
Improvements
+ +-
+
- Tellduslive: Don’t thow exception if connection to server is lost (@molobrakos) +
- Core: Convert config.components to a set (@balloob) +
- Media Player - Apple TV: Handle connection errors when connecting to Apple TVs, re-use aiohttp session , add fake support for turn on/off (@postlund) +
- Zoneminder: Refactoring and JSON decode error handling (@pschmitt) +
- Recorder: Add tests for full schema migration, limit to session scope (@armills) +
- Tests: Add history_stats sensor (@bokub) +
- Device tracker - Tado: Add support for multiple devices to Tado device tracker (@markoudev) +
- Z-Wave: Fix zwave helper getter not to fail on some None results. (@andrey-git) +
- Core:
sensor_classmigrate todevice_class(@armills)
+ - Sensor - Amcrest: Avoid traceback for Amcrest cameras/firmware that does not have the software_information API call (@tchellomello) +
- Media Player - MPD: Adds play URL support to mpd (@jjmontesl) +
- Logbook: Component set add using OR (@kellerza) +
- Config: Add config component and hassbian example panel (@balloob) +
- Proximity: Fixed proximity zone incorrectly using name instead of zone setting (@jjmontesl) +
- Z-Wave: Add device_class support to cover component (@armills) +
- Config: Add check_config API (@balloob) +
- Media player: Add media_image to media_player component (@postlund) +
- Sensor- Vasttrafik.py: vasttrafik: update token on read error (@persandstrom) +
- Z-Wave.py: force_update zwave sensors (@andrey-git) +
- Core: Two stage shutdown (@pvizeli) +
- Z-Wave: Rename customize to device_config (@balloob) +
- Thingspeak: Use the correct API key (@fabaff) +
- Lock - Nuki: Reduce battery drain on Nuki Lock (@pschmitt) +
- Notify - Webostv: Only try to pair notify.webostv when not paired (@andersonshatch) +
- KNX: Fix slow status updates from the knx bus (@keerts) +
- HDMI CEC: HDMI_CEC customization [Breaking change] (@balloob, @andrey-git) +
- Sensor - Moon: Remove unit of measurement (@fabaff) +
- Z-Wave: Add initial Z-Wave config panel (@balloob) +
- History: Allow printing the number of states returned by history and time it took to extract and add day (@andrey-git) +
- MQTT: Enable sensor for discovery (@fabaff) +
- Light - Limitlessled: Added limitlessled support for bridge v6 and RGBWW bulbs. (@soldag) +
- Config - Hassbian: Update hassbian component with real output (@balloob) +
- Media Player -Sonos: Bugfix sonos favorite_source after lost connection (@pvizeli) +
- Sensor - SenseHAT: Add flag to declare if SenseHAT is attached (@nodinosaur) +
- RFLink: Reconnect robustness, expose connection state. (@aequitas) +
- Media player - CMUS: Remove IO from properties (@armills) +
- Light - Litejet: Lights should have the option to dim in the UI. (@joncar) +
- Light - Hue: Add effect_list to hue light (@armills) +
- Meida player - Liveboxplaytv: Update liveboxplaytv and catch connection errors (@pschmitt) +
- Llight - Lifx: Fix colortemp conversion for lifx lights (@kitcorey) +
- Light - Flux_LED: Update FLUX_LED by adding Effects (@dramamoose) +
- Alarm control panel - Simplisafe: SimpliSafe updates (@w1ll1am23) +
- Cover Add supported_features to cover component (@armills) +
- Wink: Added tamper detection to Wink devices. (@w1ll1am23) +
- Sensor - onewire: Add support for aliased owfs sensors (@normakm) +
- Weather: Forecast (@Tommatheussen) +
- Device tracker - ASUSwrt: Added support for alternate SSH ports in AsusWRT (@swbradshaw) +
- Zoneminder: Add camera mjpeg stream support (@mnoorenberghe) +
- Restore: Restore_state helper to restore entity states from the DB on startup (@kellerza) +
- Sensor - Darksky: Add ‘entity_picture’ to Darksky component (@aronsky) +
- Media Player - Samsungtv: Add support for waking up Samsung TVs over the network (@justin8) +
- MQTT: Convert MQTT platforms to async (@pvizeli) +
- tests/components/device_tracker/test_init.py: Restore for device_tracker (@kellerza) +
- Discovery: Make it possible to ignore platforms in discovery (@postlund) +
- Image processing: Add
device_class(@pvizeli)
+
Breaking changes
+-
+
- VolvoOnCall has been extended with more features and had to be converted to a component +
- Limitlessled support for Bridge v6 and RGBWW bulbs require users to specify
versionand `port
+ - hdmi_cec config now requires users to set the types in the hdmi_cec config instead of using
customize:
+
hdmi_cec:
+ types:
+ hdmi_cec.hdmi_5: media_player
+Bugfixes:
+@pvizeli, @LinuxChristian, @molobrakos, @balloob, @rytilahti, @fabaff, @andrey-git, @aequitas, @konikvranik, @Danielhiversen, @colinodell, @pschmitt, @bachp, @bachp,@w1ll1am23, @valentinalexeev, @robbiet480, @MartinHjelmare, @happyleavesaoc, @tdickman, @arraylabs, @lwis, @titilambert
+ +If you need help…
+…don’t hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it’s preferred if you use the former communication channels. Thanks.
+ +Reporting Issues
+Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
+
- The Christmas tree in action.
-
-
-
-In this tutorial I will explain how you can activate Tasker tasks from Home Assistant command line switches. We are going to set up a switch that when toggled will make your Android device say either “On” or “Off”.
Sonos support has been added by 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
+
+ 
service developer tools, select the service 
+