layout: post

title: "0.30: More Async, HASSbian, Digital Ocean, statistics, REST"

description: "More asynchronous, HASSbian image, Support for Digital Ocean, statistics, Västtrafik public transport, and Hacktoberfest."

date: 2016-10-08 03:04:05 +0000

date_formatted: "October 08, 2016"

author: Fabian Affolter & Paulus Schoutsen

author_twitter: fabaff

comments: true

categories: Release-Notes

Yes, after only nine days comes 0.30. Don't worry, we will try to keep our usual release cycle and not start to release every day.

We guess that you already know: The [Raspberry Pi image][pi-image] is available now. For Hassbian, [@Landrash] has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to recieve [feedback][hassbian-forum], [issue report][hassbian-forum], and [suggestions][hassbian-forum] to improve it.

A large amount of resources of the development are still focusing on the effort to move Home Assistant further to asynchronous programming. It's a labor-intensive task, comes with segmentation faults, and unstable instances when certain combinations of sensors are used. The benefit will be more speed in the near future.

To reduce the run-time of your tests, [@balloob] did a lot of tweaking. For now the RFXtrx tests are excluded which cut the needed time for running on your Pull Request in half.

All configuration sample entries are now minimized. This should help to avoid problem for starters and newbies as they only get what's needed and not a full sample with all optional entries. If there is an issue with an entry in your `configuration.yaml` file the error message will provide you an URL that point to the documentation.

<p class='img'>

<img src='{{site_root}}/images/screenshots/config-validation-url.png' />

</p>

As soon as the [Hacktoberfest] started there were a lot of incoming Pull Requests for the documentation. A huge "Thank you" to all participants. Especially, we would like to give a cookie to [@hillaryfraley]. She created around a dozen Pull Requests so far and didn't only fix typos but complete sections. The [Hacktoberfest] is still on-going and we are looking forward to get more Pull Requests.

With the [statistics sensor][stats-sensor] we would like to introduce a new sensor that is similar to the [template sensor][template-sensor] or the [trend sensor][trend-sensor]. This sensor is consuming values from another sensor and is doing some statistical analysis of the data. Over a group of samples is the average/mean, the min/max, the total, the standard deviation, and the variance calculated which can be used in your automation rules. If the source is a binary sensor then the state changes are counted.

<p class='img'>

<img src='{{site_root}}/images/screenshots/stats-sensor.png' />

</p>

As the results are processed on-the-fly you still need to use the data from your database for a in-depth analysis of your stored information. Check the latest [notebook] for doing statistics with your Home Assistant database.

There was a lot of work done on our implementation which are working with RESTful APIs. [@w1ll1am23] extended the [aREST] platforms to display if an aREST unit is available or not. The aREST is now covered by the configuration check as well. Please check the Breaking changes section for more details.

The [REST sensor][rest-sensor] supports now HTTP authentication (basic and digest) and custom header. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.

- platform: rest

resource: https://api.github.com/repos/home-assistant/home-assistant/releases/latest

username: YOUR_GITHUB_USERNAME

password: YOUR_GITHUB_ACCESS_TOKEN

authentication: basic

value_template: '{% raw %}{{ value_json.tag_name }}{% endraw %}'

headers:

Accept: application/vnd.github.v3+json

Content-Type: application/json

User-Agent: Home Assistant REST sensor

- Minor features and bug fixes by [@tchellomello], [@pavoni], [@fabaff], [@pvizeli], [@lwis], [@turbokongen], [@Danielhiversen], [@persandstrom], [@balloob], [@robbiet480], [@sam-io], [@bbangert], and you if you are missing here.

- All deprecated condition options from `automation` have been removed (deprecated since May and have printed warnings to your console):

- `use_trigger_values` is gone. You have to copy your triggers to conditions and adjust for the correct config.

- `condition_type` is gone. Use `condition: or` instead.

- To specify the type of a condition, use `condition:` instead of `platform:`.

- The [Forecast.io][forecast] was renamed to [Dark Sky][darksky]. Replace your `- platform: forecast` with `- platform: darksky`.

- The [aREST][arest] configuration between the [sensor][arest-sensor] and the [switch][arest-switch] platform was aligned.

...don't hesitate to use our [Forum](https://community.home-assistant.io/) or join us for a little [chat](https://gitter.im/home-assistant/home-assistant). The release notes have comments enabled but it's preferred if you the former communication channels. Thanks.

[@balloob]: https://github.com/balloob

[@bbangert]: https://github.com/bbangert

[@capellini]: https://github.com/capellini

[@Danielhiversen]: https://github.com/Danielhiversen

[@danielperna84]: https://github.com/danielperna84

[@fabaff]: https://github.com/fabaff

[@gwendalg]: https://github.com/gwendalg

[@hillaryfraley]: https://github.com/hillaryfraley

[@jawilson]: https://github.com/jawilson

[@justweb1]: https://github.com/justweb1

[@kellerza]: https://github.com/kellerza

[@KlaasH]: https://github.com/KlaasH

[@Landrash]: https://github.com/Landrash

[@lwis]: https://github.com/lwis

[@MartinHjelmare]: https://github.com/MartinHjelmare

[@molobrakos]: https://github.com/molobrakos

[@mweinelt]: https://github.com/mweinelt

[@OttoWinter]: https://github.com/OttoWinter

[@pavoni]: https://github.com/pavoni

[@persandstrom]: https://github.com/persandstrom

[@pvizeli]: https://github.com/pvizeli

[@robbiet480]: https://github.com/robbiet480

[@sam-io]: https://github.com/sam-io

[@simonszu]: https://github.com/simonszu

[@tchellomello]: https://github.com/tchellomello

[@turbokongen]: https://github.com/turbokongen

[@w1ll1am23]: https://github.com/w1ll1am23

[arest]: https://arest.io/

[arest-sensor]: /components/sensor.arest/

[arest-switch]: /components/switch.arest/

[darksky]: /components/sensor.darksky/

[do-bin-sensor]: /components/binary_sensor.digital_ocean/

[do-switch]: /components/switch.digital_ocean/

[forecast]: /components/sensor.forecast/

[forum]: https://community.home-assistant.io/

[Hacktoberfest]: /blog/2016/10/02/hacktoberfest/

[hassbian-forum]: https://community.home-assistant.io/c/hassbian

[mention-bot]: https://github.com/mention-bot

[mysensors-cover]: /components/cover.mysensors/

[notebook]: http://nbviewer.jupyter.org/github/home-assistant/home-assistant-notebooks/blob/master/database-statistics.ipynb

[pi-image]: /blog/2016/10/01/we-have-raspberry-image-now/

[pushetta]: /components/notify.pushetta/

[pwrctrl-switch]: /components/switch.pwrctrl/

[rest-sensor]: /components/sensor.rest/

[stats-sensor]: /components/sensor.statistics/

[ted5000]: /components/sensor.ted5000/

[template-sensor]: /components/sensor.template/

[trend-sensor]: /components/binary_sensor.trend/

[vasttrafik]: /components/sensor.vasttrafik/

[Volvo]: /components/device_tracker.volvooncall/