0.36: ISS, USPS, Image processing, Insteon

five minutes reading time
  • Release-Notes

Welcome to 2017 and 0.36. We are proud to announce the first release for this year. While we are still migrating parts to async but 0.36 is focusing on new features and a lot of bug fixes.


Packages are providing a new way to organize different component’s configuration parts together. With packages we offer the option to include different components or parts of configuration using any of the !include directives.

InfluxDB export

The InfluxDB component was causing problems in a wide variety of use cases. @titilambert improved our InfluxDB exporter feature. It might be that you need to run the migration script to update your InfluxDB database.

$ hass --script influxdb_migrator \

International Space Station (ISS)

No, unfortunately we are not going to space. The iss sensor is tracking the position of the International Space Station and gives you some details.

Insteon local

The support for Insteon was removed due to issues a while ago. With the insteon_local component support for Insteon is back and let one work locally with an Insteon setup.

Image processing

The new image processing component currently works with number plates. But this could level the way to integrate feature like facial recognition, motion detection, or gestures control.

All changes

Release 0.36.1 - January 17

Breaking changes

  • APNS service was moved to the notify domain. Use notify.apns_NOTIFIER_NAME instead of apns.NOTIFIER_NAME.
  • InfluxDB component has a new schema to store values in the InfluxDB database. You may require to run the influxdb_migrator script. You have to note:
    • There will not be any tags/fields named time anymore.
    • All numeric fields (int/float/bool) will be stored as float inside influx db.
    • All string fields corresponding to state attributes will be renamed as FIELDNAME_str, where FIELDNAME is the state attribute, to avoid type conflicts.
    • All string fields corresponding to a state will be renamed as state (former value).
    • Fields named value will always be stored as float.
    • Fields named state will always be stored as string.
  • TTS cache files use now the language abbreviation as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. HASH_PLATFORM.xxx -> HASH_LANG_PLATFORM.xxx.

If you need help…

…don’t hesitate to use our Forum 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.