+ 
-Although the summer is in full progress, the development hasn’t stalled. This release brings bug fixes, clean ups and another 8 new integrations. On top of that we are also introducing a new script editor!
+Although the summer is in full progress, the development hasn’t stalled. This release brings bug fixes, clean ups and another 8 new integrations. On top of that we are also introducing a new script editor!
To use the scripts editor, create a new file in your config directory named scripts.yaml and copy your existing scripts over:
+ 
This release has to do a one time database migration which can take a long time on big databases (20 minutes). During this time the frontend will not work. Do not stop Home Assistant while it is in progress.
@@ -411,7 +411,7 @@
+ 
Last Wednesday we released Hass.io, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
@@ -639,7 +639,7 @@@@ -649,23 +649,23 @@
So we decided to take a step back from day-to-day Home Assistant development and see if we could offer a solution that makes updating a breeze for our users. A solution that you can flash to your Raspberry Pi and no longer worry about. A solution that would still be local first and respect the user’s privacy.
-And this is how Pascal Vizeli came up with Hass.io, an operating system based on ResinOS and Docker. Hass.io will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows taking/restoring snapshots of your configuration and can easily be extended using Hass.io add-ons.
+And this is how Pascal Vizeli came up with Hass.io, an operating system based on ResinOS and Docker. Hass.io will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows taking/restoring snapshots of your configuration and can easily be extended using Hass.io add-ons.
-
+
Hass.io dashboard
To install add-ons, a user can browse the built-in add-on store and install, configure and update any available application. Want to turn your device into a Google Assistant or make your configuration accessible via Samba/Windows networking? Both are a couple of clicks away! (Video demo - 38s, no audio)
-At launch we have included a couple of built-in add-ons like Google Assistant, Let’s Encrypt and Duck DNS. Besides our internal add-ons, it is also possible to create and share your own add-on repositories. During our beta period we’ve already seen some great add-ons being shared: Homebridge, InfluxDB, HASS Configurator and AppDaemon.
+At launch we have included a couple of built-in add-ons like Google Assistant, Let’s Encrypt and Duck DNS. Besides our internal add-ons, it is also possible to create and share your own add-on repositories. During our beta period we’ve already seen some great add-ons being shared: Homebridge, InfluxDB, HASS Configurator and AppDaemon.
As we strongly believe in the openness of technology, we are releasing Hass.io as open source under the Apache 2.0 license. That way any user can make sure that the code that runs in their homes is secure and safe.
-
-
- Learn more about Hass.io -
- Install Hass.io -
- Available add-ons +
- Learn more about Hass.io +
- Install Hass.io +
- Available add-ons
Some frequently asked questions are answered below in the read more section.
@@ -684,11 +684,11 @@ Hass.io dashboardWhich devices are supported at launch?
-Initially we support the Raspberry Pi 1, 2, 3 and Intel NUC. Advanced users can also install Hass.io on a Linux server.
+Initially we support the Raspberry Pi 1, 2, 3 and Intel NUC. Advanced users can also install Hass.io on a Linux server.
Can I install packages or scripts on the machine?
-No, this is not possible as we’re using stateless Docker containers. To install a package you’ll have to write a local add-on that interacts with Home Assistant. See our tutorial.
+No, this is not possible as we’re using stateless Docker containers. To install a package you’ll have to write a local add-on that interacts with Home Assistant. See our tutorial.
Can I restore a snapshot on a different device?
@@ -722,7 +722,7 @@ Hass.io dashboard
+ 
WE HAVE THEMES 🎨👩🎨
@@ -740,7 +740,7 @@ Hass.io dashboardOnce a theme is defined, use the new frontend service frontend.set_theme to activate it. More information in the docs.
-
+
Screenshot of a green dashboard
+ 
It’s time for a great new release!
@@ -1066,7 +1066,7 @@ Community Leader, Home AssistantPascal has added a new option to Home Assistant core to set a list of whitelisted folders that Home Assistant can read from. When a component allows to send files (like Telegram), it will only be allowed to send files from those directories. The only default whitelisted folder is the public <config>/www directory.
Z-Wave will, as announced in the last release, be defaulting to generate the new entity ids. More info in the blog post. You can still opt-in for the old style.
+Z-Wave will, as announced in the last release, be defaulting to generate the new entity ids. More info in the blog post. You can still opt-in for the old style.
zwave:
new_entity_ids: false
@@ -1098,21 +1098,21 @@ Community Leader, Home Assistant
New Platforms
- - Add initial support for Shiftr.io (@fabaff - #7974) (shiftr docs) (new-platform)
- - Upnp properties (@dgomes - #8067) (upnp docs) (sensor.upnp docs) (new-platform)
- - Add support for Insteon FanLinc fan (@jawilson - #6959) (insteon_local docs) (fan.insteon_local docs) (new-platform)
- - add knx cover support (@tiktok7 - #7997) (knx docs) (cover.knx docs) (new-platform)
- - Add I2c BME280 temperature, humidity and pressure sensor for Raspberry Pi (@azogue - #7989) (sensor.bme280 docs) (new-platform)
- - Add I2c HTU21D temperature and humidity sensor for Raspberry Pi (@azogue - #8049) (sensor.htu21d docs) (new-platform)
- - Add new BH1750 light level sensor (@azogue - #8050) (sensor.bh1750 docs) (new-platform)
- - Rfxtrx binary sensor (@ypollart - #6794) (rfxtrx docs) (binary_sensor.rfxtrx docs) (new-platform)
- - Add ClickSend notify service. (@omarusman - #8135) (notify.clicksend docs) (new-platform)
- - Add device tracker for Linksys Smart Wifi devices (@mortenlj - #8144) (device_tracker.linksys_smart docs) (new-platform)
- - Openhardwaremonitor (@depl0y - #8056) (sensor.openhardwaremonitor docs) (new-platform)
- - WIP: Verisure app api (@persandstrom - #7394) (verisure docs) (alarm_control_panel.verisure docs) (binary_sensor.verisure docs) (sensor.verisure docs) (switch.verisure docs) (new-platform)
+ - Add initial support for Shiftr.io (@fabaff - #7974) (shiftr docs) (new-platform)
+ - Upnp properties (@dgomes - #8067) (upnp docs) (sensor.upnp docs) (new-platform)
+ - Add support for Insteon FanLinc fan (@jawilson - #6959) (insteon_local docs) (fan.insteon_local docs) (new-platform)
+ - add knx cover support (@tiktok7 - #7997) (knx docs) (cover.knx docs) (new-platform)
+ - Add I2c BME280 temperature, humidity and pressure sensor for Raspberry Pi (@azogue - #7989) (sensor.bme280 docs) (new-platform)
+ - Add I2c HTU21D temperature and humidity sensor for Raspberry Pi (@azogue - #8049) (sensor.htu21d docs) (new-platform)
+ - Add new BH1750 light level sensor (@azogue - #8050) (sensor.bh1750 docs) (new-platform)
+ - Rfxtrx binary sensor (@ypollart - #6794) (rfxtrx docs) (binary_sensor.rfxtrx docs) (new-platform)
+ - Add ClickSend notify service. (@omarusman - #8135) (notify.clicksend docs) (new-platform)
+ - Add device tracker for Linksys Smart Wifi devices (@mortenlj - #8144) (device_tracker.linksys_smart docs) (new-platform)
+ - Openhardwaremonitor (@depl0y - #8056) (sensor.openhardwaremonitor docs) (new-platform)
+ - WIP: Verisure app api (@persandstrom - #7394) (verisure docs) (alarm_control_panel.verisure docs) (binary_sensor.verisure docs) (sensor.verisure docs) (switch.verisure docs) (new-platform)
- telegram_bot platform to only send messages (@azogue - #8186) (new-platform)
- - Comfoconnect fan component (@michaelarnauts - #8073) (comfoconnect docs) (fan.comfoconnect docs) (sensor.comfoconnect docs) (new-platform)
- - Implement templates for covers (@PhracturedBlue - #8100) (cover.template docs) (new-platform)
+ - Comfoconnect fan component (@michaelarnauts - #8073) (comfoconnect docs) (fan.comfoconnect docs) (sensor.comfoconnect docs) (new-platform)
+ - Implement templates for covers (@PhracturedBlue - #8100) (cover.template docs) (new-platform)
- Snips ASR and NLU component (@michaelfester - #8156) (snips docs) (new-platform)
@@ -1138,8 +1138,8 @@ Community Leader, Home Assistant
-
-
- Vera battery levels will no longer have the percent sign appended (@philhawthorne - #8069) (vera docs) (breaking change) -
- Notify - SMTP: Added SMTP SSL/TLS support so now you should specify which encryption to use. (@sn0oz - #7960) (notify.smtp docs) (breaking change) +
- Vera battery levels will no longer have the percent sign appended (@philhawthorne - #8069) (vera docs) (breaking change) +
- Notify - SMTP: Added SMTP SSL/TLS support so now you should specify which encryption to use. (@sn0oz - #7960) (notify.smtp docs) (breaking change)
notify:
@@ -1155,8 +1155,8 @@ Community Leader, Home Assistant
-
-
- Light - LIFX: The
lifx_effect_breathecall was deprecated in version 0.47 and has now been removed. You can uselifx_effect_pulsewithmode: breathefor the same effect. (@amelchio - #8222) (light.lifx docs) (breaking change)
- - LimitlessLED: No longer automatically fades the lights when turning the light off. Can be restored with a new config option. (@SmilyOrg - #7369) (light.limitlessled docs) (breaking change) +
- Light - LIFX: The
lifx_effect_breathecall was deprecated in version 0.47 and has now been removed. You can uselifx_effect_pulsewithmode: breathefor the same effect. (@amelchio - #8222) (light.lifx docs) (breaking change)
+ - LimitlessLED: No longer automatically fades the lights when turning the light off. Can be restored with a new config option. (@SmilyOrg - #7369) (light.limitlessled docs) (breaking change)
light:
@@ -1178,124 +1178,124 @@ Community Leader, Home Assistant
All changes
- - Update numpy 1.13.0 (@pvizeli - #8059) (image_processing.opencv docs)
+ - Update numpy 1.13.0 (@pvizeli - #8059) (image_processing.opencv docs)
- No update in MQTT Binary Sensor #7478 (@pezinek - #8057)
- - Use standard entity_ids for zwave entities (@armills - #7786) (zwave docs) (light.zwave docs) (breaking change)
- - Fix some warnings found by quantifiedcode (@andrey-git - #8027) (insteon_hub docs) (tellduslive docs) (calendar.google docs)
+ - Use standard entity_ids for zwave entities (@armills - #7786) (zwave docs) (light.zwave docs) (breaking change)
+ - Fix some warnings found by quantifiedcode (@andrey-git - #8027) (insteon_hub docs) (tellduslive docs) (calendar.google docs)
- Always enable monkey patch (@balloob - #8054)
- - Remove % sign from Vera Battery Levels (@philhawthorne - #8069) (vera docs) (breaking change)
- - Allow config of latitude and longitude (@jshore1296 - #8068) (sensor.wunderground docs)
- - Failed to parse response from WU API: ‘record’ (and ‘recordyear’) #7747 (@pezinek - #8058) (sensor.wunderground docs)
- - Add initial support for Shiftr.io (@fabaff - #7974) (shiftr docs) (new-platform)
- - Add option to set language of openweathermap sensor, and handle updating errors (@azogue - #8046) (sensor.openweathermap docs)
- - Bump pyEmby version to account for API changes (@mezz64 - #8070) (media_player.emby docs)
- - bump ups (@happyleavesaoc - #8075) (sensor.ups docs)
- - bump usps version (@happyleavesaoc - #8074) (sensor.usps docs)
+ - Remove % sign from Vera Battery Levels (@philhawthorne - #8069) (vera docs) (breaking change)
+ - Allow config of latitude and longitude (@jshore1296 - #8068) (sensor.wunderground docs)
+ - Failed to parse response from WU API: ‘record’ (and ‘recordyear’) #7747 (@pezinek - #8058) (sensor.wunderground docs)
+ - Add initial support for Shiftr.io (@fabaff - #7974) (shiftr docs) (new-platform)
+ - Add option to set language of openweathermap sensor, and handle updating errors (@azogue - #8046) (sensor.openweathermap docs)
+ - Bump pyEmby version to account for API changes (@mezz64 - #8070) (media_player.emby docs)
+ - bump ups (@happyleavesaoc - #8075) (sensor.ups docs)
+ - bump usps version (@happyleavesaoc - #8074) (sensor.usps docs)
- Add to zwave services descriptions (@andrey-git - #8072)
- Fix attribute entity (@pvizeli - #8066) (breaking change)
- - Added ‘all_plants’ group and support for plant groups state. (@aronsky - #8063) (group docs) (plant docs)
+ - Added ‘all_plants’ group and support for plant groups state. (@aronsky - #8063) (group docs) (plant docs)
- Fix EntityComponent handle entities without a name (@balloob - #8065)
- - Update pyunifi component to use APIError passed from pyunifi 2.13. Better accommodate login failures with wrapper in pyunifi 2.13. (@finish06 - #7899) (device_tracker.unifi docs)
- - Stopping the logfile spam by piping STDERR to /dev/null (@madpilot - #8081) (switch.wake_on_lan docs)
- - mpd: implement support for seek, shuffle, and clear playlist (@auchter - #8090) (media_player.mpd docs)
+ - Update pyunifi component to use APIError passed from pyunifi 2.13. Better accommodate login failures with wrapper in pyunifi 2.13. (@finish06 - #7899) (device_tracker.unifi docs)
+ - Stopping the logfile spam by piping STDERR to /dev/null (@madpilot - #8081) (switch.wake_on_lan docs)
+ - mpd: implement support for seek, shuffle, and clear playlist (@auchter - #8090) (media_player.mpd docs)
- Cleanup .coveragerc (@michaelarnauts - #8088)
- - update pywebpush to 1.0.5 (@perosb - #8084) (notify.html5 docs)
- - media player Kodi: handle TransportError exceptions when calling JSONRPC API methods (@azogue - #8047) (media_player.kodi docs)
- - Upnp properties (@dgomes - #8067) (upnp docs) (sensor.upnp docs) (new-platform)
- - Add support for Insteon FanLinc fan (@jawilson - #6959) (insteon_local docs) (fan.insteon_local docs) (new-platform)
- - add knx cover support (@tiktok7 - #7997) (knx docs) (cover.knx docs) (new-platform)
+ - update pywebpush to 1.0.5 (@perosb - #8084) (notify.html5 docs)
+ - media player Kodi: handle TransportError exceptions when calling JSONRPC API methods (@azogue - #8047) (media_player.kodi docs)
+ - Upnp properties (@dgomes - #8067) (upnp docs) (sensor.upnp docs) (new-platform)
+ - Add support for Insteon FanLinc fan (@jawilson - #6959) (insteon_local docs) (fan.insteon_local docs) (new-platform)
+ - add knx cover support (@tiktok7 - #7997) (knx docs) (cover.knx docs) (new-platform)
- More updates to zwave services.yaml file (@andrey-git - #8083)
- - Fix lights issue #8098 (@tsvi - #8101) (light.vera docs)
- - increase timeout for setWebhook to 10s (@azogue - #8102) (telegram_bot.webhooks docs)
- - Added SMTP SSL/TLS support (@sn0oz - #7960) (notify.smtp docs) (breaking change)
- - Fix Dyson async_add_job (@CharlesBlonde - #8113) (fan.dyson docs) (sensor.dyson docs)
- - Update InfluxDB to handle datetime objects and multiple decimal points (@philhawthorne - #8080) (influxdb docs)
- - Remove config details (see docs) (@fabaff - #8119) (cover.knx docs)
- - Only mark active DHCP clients as present (@cyberplant - #8110) (device_tracker.mikrotik docs)
- - Add option to specify the location of the API (fixes #8115) (@fabaff - #8118) (sensor.pi_hole docs)
- - Fixed iTach command parsing with empty data (@alanfischer - #8104) (remote.itach docs)
- - Upgrade mutagen to 1.38 (@fabaff - #8126) (tts docs)
- - Upgrade paho-mqtt to 1.3.0 (@fabaff - #8125) (mqtt docs) (shiftr docs)
- - Upgrade sqlalchemy to 1.1.11 (@fabaff - #8124) (recorder docs)
+ - Fix lights issue #8098 (@tsvi - #8101) (light.vera docs)
+ - increase timeout for setWebhook to 10s (@azogue - #8102) (telegram_bot.webhooks docs)
+ - Added SMTP SSL/TLS support (@sn0oz - #7960) (notify.smtp docs) (breaking change)
+ - Fix Dyson async_add_job (@CharlesBlonde - #8113) (fan.dyson docs) (sensor.dyson docs)
+ - Update InfluxDB to handle datetime objects and multiple decimal points (@philhawthorne - #8080) (influxdb docs)
+ - Remove config details (see docs) (@fabaff - #8119) (cover.knx docs)
+ - Only mark active DHCP clients as present (@cyberplant - #8110) (device_tracker.mikrotik docs)
+ - Add option to specify the location of the API (fixes #8115) (@fabaff - #8118) (sensor.pi_hole docs)
+ - Fixed iTach command parsing with empty data (@alanfischer - #8104) (remote.itach docs)
+ - Upgrade mutagen to 1.38 (@fabaff - #8126) (tts docs)
+ - Upgrade paho-mqtt to 1.3.0 (@fabaff - #8125) (mqtt docs) (shiftr docs)
+ - Upgrade sqlalchemy to 1.1.11 (@fabaff - #8124) (recorder docs)
- Upgrade aiohttp to 2.2.0 (@fabaff - #8121)
- - Upgrade RestrictedPython dependency (@balloob - #8132) (python_script docs)
- - Added RFXTRX UV badge (@lunar-consultancy - #8129) (rfxtrx docs)
- - Do not call update() in constructor (@fabaff - #8120) (sensor.netdata docs)
- - Change Error Message when Turning off ISY994 Light (@SConaway - #8131) (light.isy994 docs)
- - Allow iteration in python_script (@balloob - #8134) (python_script docs)
- - Add current balance to hydroquebec sensor (@titilambert - #8138) (sensor.hydroquebec docs)
- - Decora light: Fix brightness level in UI (@titilambert - #8139) (light.decora docs)
- - Add I2c BME280 temperature, humidity and pressure sensor for Raspberry Pi (@azogue - #7989) (sensor.bme280 docs) (new-platform)
- - Upgrade libsoundtouch to prevent Python3.6 errors with enum. #7733 #8103 (@CharlesBlonde - #8143) (media_player.soundtouch docs)
- - Adds CPU temp monitoring, and allow startup when endpoint is not yet available. (@jjmontestl - #8093) (sensor.glances docs)
- - Add I2c HTU21D temperature and humidity sensor for Raspberry Pi (@azogue - #8049) (sensor.htu21d docs) (new-platform)
- - Add new BH1750 light level sensor (@azogue - #8050) (sensor.bh1750 docs) (new-platform)
- - LimitlessLED: Configurable fade-out behavior (@SmilyOrg - #7369) (light.limitlessled docs) (breaking change)
+ - Upgrade RestrictedPython dependency (@balloob - #8132) (python_script docs)
+ - Added RFXTRX UV badge (@lunar-consultancy - #8129) (rfxtrx docs)
+ - Do not call update() in constructor (@fabaff - #8120) (sensor.netdata docs)
+ - Change Error Message when Turning off ISY994 Light (@SConaway - #8131) (light.isy994 docs)
+ - Allow iteration in python_script (@balloob - #8134) (python_script docs)
+ - Add current balance to hydroquebec sensor (@titilambert - #8138) (sensor.hydroquebec docs)
+ - Decora light: Fix brightness level in UI (@titilambert - #8139) (light.decora docs)
+ - Add I2c BME280 temperature, humidity and pressure sensor for Raspberry Pi (@azogue - #7989) (sensor.bme280 docs) (new-platform)
+ - Upgrade libsoundtouch to prevent Python3.6 errors with enum. #7733 #8103 (@CharlesBlonde - #8143) (media_player.soundtouch docs)
+ - Adds CPU temp monitoring, and allow startup when endpoint is not yet available. (@jjmontestl - #8093) (sensor.glances docs)
+ - Add I2c HTU21D temperature and humidity sensor for Raspberry Pi (@azogue - #8049) (sensor.htu21d docs) (new-platform)
+ - Add new BH1750 light level sensor (@azogue - #8050) (sensor.bh1750 docs) (new-platform)
+ - LimitlessLED: Configurable fade-out behavior (@SmilyOrg - #7369) (light.limitlessled docs) (breaking change)
- Harmony auto discovery via netdisco (@tony2nite - #7741) (remote.harmony docs)
- - Rfxtrx binary sensor (@ypollart - #6794) (rfxtrx docs) (binary_sensor.rfxtrx docs) (new-platform)
- - Add support of Zone2 and Zone3 (@scarface-4711 - #8025) (media_player.denonavr docs)
- - Upgrade python-telegram-bot to 6.1.0 (@fabaff - #8151) (telegram_bot docs)
- - Upgrade libsoundtouch to 0.6.2 (@fabaff - #8149) (media_player.soundtouch docs)
- - Switch rachiopy to pypi (@andrey-git - #8040) (switch.rachio docs)
+ - Rfxtrx binary sensor (@ypollart - #6794) (rfxtrx docs) (binary_sensor.rfxtrx docs) (new-platform)
+ - Add support of Zone2 and Zone3 (@scarface-4711 - #8025) (media_player.denonavr docs)
+ - Upgrade python-telegram-bot to 6.1.0 (@fabaff - #8151) (telegram_bot docs)
+ - Upgrade libsoundtouch to 0.6.2 (@fabaff - #8149) (media_player.soundtouch docs)
+ - Switch rachiopy to pypi (@andrey-git - #8040) (switch.rachio docs)
- ubus: Refresh session on Access denied (@glance- - #8111)
- Added invert flag for position for actuators that uses 100% for fully closed position (@open-homeautomation - #8147)
- - add telegram_bot service: delete_message (@azogue - #8153) (telegram_bot docs)
- - Fixed rfxtrx binary_sensor off command (@basschipper - #8160) (rfxtrx docs) (binary_sensor.rfxtrx docs)
- - Use version 1.3 of radiotherm (@twilde - #8164) (climate.radiotherm docs)
- - Tado climate device (@wmalgadey - #8041) (tado docs) (climate.tado docs)
- - Add ClickSend notify service. (@omarusman - #8135) (notify.clicksend docs) (new-platform)
+ - add telegram_bot service: delete_message (@azogue - #8153) (telegram_bot docs)
+ - Fixed rfxtrx binary_sensor off command (@basschipper - #8160) (rfxtrx docs) (binary_sensor.rfxtrx docs)
+ - Use version 1.3 of radiotherm (@twilde - #8164) (climate.radiotherm docs)
+ - Tado climate device (@wmalgadey - #8041) (tado docs) (climate.tado docs)
+ - Add ClickSend notify service. (@omarusman - #8135) (notify.clicksend docs) (new-platform)
- Add libboost-python1.62-dev (fixes #7851) (@fabaff - #7868)
- Uninstall enum34 in python3.6 docker image (@jeanregisser - #8103)
- Revert “Add libboost-python1.62-dev (fixes #7851)” (@balloob - #8182)
- - Add device tracker for Linksys Smart Wifi devices (@mortenlj - #8144) (device_tracker.linksys_smart docs) (new-platform)
- - Update buienradar.py (@lrmate - #8173) (sensor.buienradar docs)
- - Fix radiotherm model CT50 (@tubaman - #8181) (climate.radiotherm docs)
- - Throw exception if _convert_for_display called on non Number (@sdague - #8178) (climate docs) (climate.mysensors docs)
- - Added buienradar precipitation forecast average & total sensors (@basschipper - #8171) (sensor.buienradar docs) (weather.buienradar docs)
- - Axis service vapix call (@Kane610 - #7794) (axis docs) (camera.axis docs)
+ - Add device tracker for Linksys Smart Wifi devices (@mortenlj - #8144) (device_tracker.linksys_smart docs) (new-platform)
+ - Update buienradar.py (@lrmate - #8173) (sensor.buienradar docs)
+ - Fix radiotherm model CT50 (@tubaman - #8181) (climate.radiotherm docs)
+ - Throw exception if _convert_for_display called on non Number (@sdague - #8178) (climate docs) (climate.mysensors docs)
+ - Added buienradar precipitation forecast average & total sensors (@basschipper - #8171) (sensor.buienradar docs) (weather.buienradar docs)
+ - Axis service vapix call (@Kane610 - #7794) (axis docs) (camera.axis docs)
- added optional node_id to MQTT discovery (@AlexMekkering - #8096)
- Add offset option to sensor.gtfs (@Kernald - #7980)
- - Switch to new zwave entity ids by default (@armills - #8192) (zwave docs)
- - Pushed to version 0.5.1 of the library (@scarface-4711 - #8190) (media_player.denonavr docs)
- - Fix MySensors climate (@balloob - #8193) (climate.mysensors docs)
+ - Switch to new zwave entity ids by default (@armills - #8192) (zwave docs)
+ - Pushed to version 0.5.1 of the library (@scarface-4711 - #8190) (media_player.denonavr docs)
+ - Fix MySensors climate (@balloob - #8193) (climate.mysensors docs)
- Fix plants calling async methods from sync context (@balloob - #8200)
- Split mock_service (@balloob - #8198)
- add option to set content_type in camera.generic to support ‘svg cameras’ (@azogue - #8188)
- Remove unnecessary thread_ident assignment (@armills - #8194)
- - Openhardwaremonitor (@depl0y - #8056) (sensor.openhardwaremonitor docs) (new-platform)
+ - Openhardwaremonitor (@depl0y - #8056) (sensor.openhardwaremonitor docs) (new-platform)
- Add security layer to send file output things (@pvizeli - #8189) (breaking change)
- - Fix Plex component to use port number in discovery. (@voltagex - #8197) (media_player.plex docs)
+ - Fix Plex component to use port number in discovery. (@voltagex - #8197) (media_player.plex docs)
- EntityComponent to retry platforms that are not ready yet (@balloob - #8209)
- - WIP: Verisure app api (@persandstrom - #7394) (verisure docs) (alarm_control_panel.verisure docs) (binary_sensor.verisure docs) (sensor.verisure docs) (switch.verisure docs) (new-platform)
- - guess the content_type in local_file cameras (@azogue - #8217) (camera.local_file docs)
+ - WIP: Verisure app api (@persandstrom - #7394) (verisure docs) (alarm_control_panel.verisure docs) (binary_sensor.verisure docs) (sensor.verisure docs) (switch.verisure docs) (new-platform)
+ - guess the content_type in local_file cameras (@azogue - #8217) (camera.local_file docs)
- Improve executor pool size / speedup python 3.5 (@pvizeli - #8215)
- - LIFX: Move light effects to external library (@amelchio - #8222) (light.lifx docs) (breaking change)
+ - LIFX: Move light effects to external library (@amelchio - #8222) (light.lifx docs) (breaking change)
- Fixed mqtt subscription filter on sys $ topics (@natemason - #8166) (mqtt docs)
- telegram_bot platform to only send messages (@azogue - #8186) (new-platform)
- - add percentage (DPT_Scaling) KNX sensors (@tiktok7 - #8168) (sensor.knx docs)
+ - add percentage (DPT_Scaling) KNX sensors (@tiktok7 - #8168) (sensor.knx docs)
- Fix homeassistant.start trigger (@azogue - #8220)
- Cleanup automations yaml (@balloob - #8223)
- - Do not call update() in constructor (@fabaff - #8148) (sensor.glances docs)
- - KNX Cover tilt control (@open-homeautomation - #8159) (cover.knx docs)
- - Comfoconnect fan component (@michaelarnauts - #8073) (comfoconnect docs) (fan.comfoconnect docs) (sensor.comfoconnect docs) (new-platform)
- - Upgrade python-digitalocean to 1.12 (@fabaff - #8241) (digital_ocean docs)
- - update i2csense requirement (@azogue - #8242) (sensor.bh1750 docs) (sensor.bme280 docs) (sensor.htu21d docs)
- - Update docstrings (@fabaff - #8244) (comfoconnect docs) (fan.comfoconnect docs)
- - Do not call update() in constructor (@fabaff - #8247) (binary_sensor.arest docs) (sensor.arest docs)
- - better logging to debug when a message is not sent (@azogue - #8248) (telegram_bot docs)
- - LIFX: Small code cleanups (@amelchio - #8228) (light.lifx docs)
- - Use ‘hass.data’ instead of global (@fabaff - #8245) (digital_ocean docs) (binary_sensor.digital_ocean docs) (switch.digital_ocean docs)
- - Use constant and update ordering (@fabaff - #8246) (arlo docs) (camera.arlo docs)
- - Add PlatformNotReady support for Sensibo (@andrey-git - #8252) (climate.sensibo docs)
- - verisure component names (@persandstrom - #8251) (binary_sensor.verisure docs) (camera.verisure docs) (lock.verisure docs) (switch.verisure docs)
+ - Do not call update() in constructor (@fabaff - #8148) (sensor.glances docs)
+ - KNX Cover tilt control (@open-homeautomation - #8159) (cover.knx docs)
+ - Comfoconnect fan component (@michaelarnauts - #8073) (comfoconnect docs) (fan.comfoconnect docs) (sensor.comfoconnect docs) (new-platform)
+ - Upgrade python-digitalocean to 1.12 (@fabaff - #8241) (digital_ocean docs)
+ - update i2csense requirement (@azogue - #8242) (sensor.bh1750 docs) (sensor.bme280 docs) (sensor.htu21d docs)
+ - Update docstrings (@fabaff - #8244) (comfoconnect docs) (fan.comfoconnect docs)
+ - Do not call update() in constructor (@fabaff - #8247) (binary_sensor.arest docs) (sensor.arest docs)
+ - better logging to debug when a message is not sent (@azogue - #8248) (telegram_bot docs)
+ - LIFX: Small code cleanups (@amelchio - #8228) (light.lifx docs)
+ - Use ‘hass.data’ instead of global (@fabaff - #8245) (digital_ocean docs) (binary_sensor.digital_ocean docs) (switch.digital_ocean docs)
+ - Use constant and update ordering (@fabaff - #8246) (arlo docs) (camera.arlo docs)
+ - Add PlatformNotReady support for Sensibo (@andrey-git - #8252) (climate.sensibo docs)
+ - verisure component names (@persandstrom - #8251) (binary_sensor.verisure docs) (camera.verisure docs) (lock.verisure docs) (switch.verisure docs)
- further document add_node_secure (@kentcalero - #8229)
- - Upgrade libnacl to 1.5.1 (@fabaff - #8259) (device_tracker.owntracks docs)
+ - Upgrade libnacl to 1.5.1 (@fabaff - #8259) (device_tracker.owntracks docs)
- Docker cleanup. (@michaelarnauts - #8226)
- - Implement templates for covers (@PhracturedBlue - #8100) (cover.template docs) (new-platform)
- - Adding done_message to alert (@karlw00t - #8116) (alert docs)
+ - Implement templates for covers (@PhracturedBlue - #8100) (cover.template docs) (new-platform)
+ - Adding done_message to alert (@karlw00t - #8116) (alert docs)
- Camera services arm disarm including Netgear Arlo (@viswa-swami - #7961) (camera.arlo docs)
- - Update modbus.py (@lrmate - #8256) (binary_sensor.modbus docs)
- - components.knx - KNXMultiAddressDevice corrections (@tiktok7 - #8275) (knx docs)
+ - Update modbus.py (@lrmate - #8256) (binary_sensor.modbus docs)
+ - components.knx - KNXMultiAddressDevice corrections (@tiktok7 - #8275) (knx docs)
- Snips ASR and NLU component (@michaelfester - #8156) (snips docs) (new-platform)
- Create an index on the states table to help hass startup time (@cmsimike - #8255)
@@ -1319,7 +1319,7 @@ Community Leader, Home Assistant
TL;DR: We are not affiliated with Senic or their COVI product. We will not support their users and you will get a subpar Home Assistant experience by using their product. Furthermore, we cannot guarantee stability or security if you use Senic products.
-Recently Home Assistant has been made aware of a product by Senic that will be launching later today on Kickstarter (screenshot). Senic is not new in the IoT business, we have had support for their first product (Nuimo) since last September. Their new product, COVI, uses Home Assistant as its core home automation codebase. This is great, that is what open source is all about. However, they also use our name and logo in their Kickstarter, with the press and in their developer documentation (screenshot) to give the appearance of being affiliated with Home Assistant, against our wishes. Which is not great, at all.
+Recently Home Assistant has been made aware of a product by Senic that will be launching later today on Kickstarter (screenshot). Senic is not new in the IoT business, we have had support for their first product (Nuimo) since last September. Their new product, COVI, uses Home Assistant as its core home automation codebase. This is great, that is what open source is all about. However, they also use our name and logo in their Kickstarter, with the press and in their developer documentation (screenshot) to give the appearance of being affiliated with Home Assistant, against our wishes. Which is not great, at all.
Take some of the following quotes from their Kickstarter campaign:
@@ -1331,7 +1331,7 @@ TL;DR: We are not affiliated with Senic or their COVI product. We will not suppo
With COVI, we have built upon an open platform called Home Assistant that anyone can contribute to alongside our engineers and the Home Assistant community.
-Although those quotes are technically correct, they are very misleading. The Senic team contributes only to their own platform, they have not contributed to Home Assistant, its integrations or related projects. We did receive 1 contribution from them for Netdisco, our network discovery package. It included a memory leak and required us to publish a hotfix release for the 0.39 series. Their contribution has since been reverted. A third party contributor had contributed support for their Nuimo controller.
+Although those quotes are technically correct, they are very misleading. The Senic team contributes only to their own platform, they have not contributed to Home Assistant, its integrations or related projects. We did receive 1 contribution from them for Netdisco, our network discovery package. It included a memory leak and required us to publish a hotfix release for the 0.39 series. Their contribution has since been reverted. A third party contributor had contributed support for their Nuimo controller.
Here is a quote that their CEO Tobias Eichenwald gave to Forbes:
@@ -1339,9 +1339,9 @@ TL;DR: We are not affiliated with Senic or their COVI product. We will not suppo
Unlike many larger companies who build closed automation platforms, COVI is built on an open source platform called Home Assistant that includes 500+ contributors. This allows COVI to be integrated into any ecosystem or platform with an open API.
-They reached out to us on April 7 (screenshot). We replied on April 11 and told them they should not use our name as we do not want to be affiliated with them because we do not want to support their users. After that one e-mail we had never heard from them again until Forbes accidentally published an article about it before the Kickstarter launched. We did not get any chance to give feedback on their Kickstarter campaign content and they went ahead and used our name and logo without authorization or permission.
+They reached out to us on April 7 (screenshot). We replied on April 11 and told them they should not use our name as we do not want to be affiliated with them because we do not want to support their users. After that one e-mail we had never heard from them again until Forbes accidentally published an article about it before the Kickstarter launched. We did not get any chance to give feedback on their Kickstarter campaign content and they went ahead and used our name and logo without authorization or permission.
-If you want an open source and constantly evolving product, get yourself a $35 Raspberry Pi, install our hub Hass.io for free and buy yourself some cheap and reliable IKEA Trådfri lights to get yourself a basic home automation setup. If you want a $250 talking lamp, go buy the COVI. Just know that we are not affiliated with Senic, we will not support their users and you will get a subpar Home Assistant experience by using their product. Furthermore, we cannot guarantee stability or security if you use Senic products.
+If you want an open source and constantly evolving product, get yourself a $35 Raspberry Pi, install our hub Hass.io for free and buy yourself some cheap and reliable IKEA Trådfri lights to get yourself a basic home automation setup. If you want a $250 talking lamp, go buy the COVI. Just know that we are not affiliated with Senic, we will not support their users and you will get a subpar Home Assistant experience by using their product. Furthermore, we cannot guarantee stability or security if you use Senic products.
Senic, we know that this is probably not what you wanted to wake up to on the first day of your Kickstarter but you left us no choice. Please reach out to us to help make this right. We will always do everything in our power to protect the best interests of the Home Assistant community, our 500+ contributors and 250,000+ users. If we don’t hear from you by Wednesday, June 21st, we will be forced to consider further actions.
@@ -1361,7 +1361,7 @@ Core Developer, Home Assistant
2017-06-17T01:04:05+00:00
https://home-assistant.io/blog/2017/06/17/release-47
- 
+ 
In this release a ton of new stuff! And who doesn’t like new stuff? This release we’re passing the 700 integrations for Home Assistant. As of today we’re 1369 days old, which means that roughly every two days a new integration gets added!
@@ -1678,7 +1678,7 @@ trigger:
2017-06-04T01:04:05+00:00
https://home-assistant.io/blog/2017/06/04/release-46
- 
+ 
It’s time for 0.46! This release does not have too many new integrations, instead it focussed on bug fixes.
@@ -1848,7 +1848,7 @@ trigger:
2017-06-02T06:00:00+00:00
https://home-assistant.io/blog/2017/06/02/home-assistant-podcast-1
- The first podcast by Home Assistant Podcast contains an introduction and covers the 0.45 release of Home Assistant.
+ The first podcast by Home Assistant Podcast contains an introduction and covers the 0.45 release of Home Assistant.
- Listen online: https://hasspodcast.io/ha001/
@@ -1863,14 +1863,14 @@ trigger:
2017-05-20T13:00:00+00:00
https://home-assistant.io/blog/2017/05/20/automation-editor-zwave-panel-ocr
- 
+ 
Welcome to another great release of Home Assistant! While some of contributors and users are gathering at PyCon US 2017, we still managed to get a great release together!
First thing for this release is a feature that has been requested a lot: an automation editor! It’s still experimental - and many things are still in progress - but it works! You can create new automations and edit existing ones. If you start a new config, you’re all good to go. Otherwise check these instructions to get your automations ready for editing in the UI.
- 
+ 
Check this video by Ben from BRUHautomation to see the new release in action.
@@ -1884,7 +1884,7 @@ trigger:
On the Z-Wave front a lot has happened. The biggest one is that we have a major extension of the Z-Wave panel thanks to @turbokongen! You will now be able to change config parameters and manage your devices.
- 
+ 
Thanks to the work by the Python Open Z-Wave team we are now able to install it on demand from PyPi! There is no longer a need to pre-compile it yourself. This should give us the guarantee that we work with the Python Open Z-Wave version that the code expects.
@@ -1897,7 +1897,7 @@ If you have a security key set in your Open Z-Wave file sensor and the seven_segments OCR image processing platform. The first simply reads a plain-text file which was created by a logger or alike. The latter one extracts the value from a captured image that shows a seven-segments display.
- 
+ 
And last, but not least, our Docker image is now based off Python 3.6. This version is faster and uses less memory than Python 3.5. Win!
@@ -2073,10 +2073,10 @@ If you have a security key set in your Open Z-Wave 2017-05-13T09:00:00+00:00
https://home-assistant.io/blog/2017/05/13/home-assistant-on-orange-pi-zero
- This blog post is about the setup of Home Assistant on an Orange Pi Zero. Like the setup on a Raspberry Pi Zero it will only take a couple of minutes to get a fully functional super cheap (less than 18 Euro incl. casing and power supply) Home Assistant hub. The reasons to use an Orange Pi Zero beside the prize are the built-in Ethernet port and the availability.
+ This blog post is about the setup of Home Assistant on an Orange Pi Zero. Like the setup on a Raspberry Pi Zero it will only take a couple of minutes to get a fully functional super cheap (less than 18 Euro incl. casing and power supply) Home Assistant hub. The reasons to use an Orange Pi Zero beside the prize are the built-in Ethernet port and the availability.
- 
+ 
@@ -2179,7 +2179,7 @@ Reading package lists... Done
Those steps to install Home Assistant are described in the documentation and the guide for venv as well. Switch to the create user ha and perform the remaining installation steps which are reduced to the minimum below:
Those steps to install Home Assistant are described in the documentation and the guide for venv as well. Switch to the create user ha and perform the remaining installation steps which are reduced to the minimum below:
ha@orangepizero:~$ pyvenv-3.5 homeassistant
ha@orangepizero:~$ cd homeassistant && source bin/activate
@@ -2190,10 +2190,10 @@ Reading package lists... Done
- 
+ 
To make it ready for daily usage, don’t forget to enable autostart.
+To make it ready for daily usage, don’t forget to enable autostart.
]]>