<![CDATA[Home Assistant 中文网]]> 2017-09-30T19:08:02+08:00 http:/// Octopress <![CDATA[0.54: Todoist, DoorBird, Abode cameras]]> 2017-09-23T08:11:05+08:00 http:///blog/2017/09/23/release-54

We’re approaching the end of September and that means that it was our birthday! We are now officially 4 years old and are getting more amazing with every release. This release too will include some great new stuff and tons of bugfixes. Included is a bug fix by @fanthos that should fix the frontend in some browsers. If you had issues with your browser before, make sure to check out this release.

This release we’ve started the work to make our Xiaomi integrations more robust. This meant that we’ve had to rename the components to make it more clear which of the Xiaomi protocols are being used. We have some developers working on making this very affordable home automation solution a first class citizen in the Home Assistant ecosystem, stay tuned for more integrations!

Another cool thing in this release is the new mqtt_statestream component to export state changes to MQTT. Each entity will be exported on their own topic which makes it very easy to subscribe to individual entity updates.

New Platforms

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.

Breaking Changes

  • Sensor - OneWire: This update changes the names of the sensors from <sensor_name> to <sensor_name> <Sensor_type> (@tcastberg - #9404) (sensor.onewire docs) (breaking change)
  • Renamed Xiaomi platforms to include their protocol names. xiaomi -> xiaomi_aqara, xiaomi_aqara.switch, xiaomi_aqara.light, xiaomi_aqara.binary_sensor, … and vacuum.xiaomi, xiaomi_philipslight -> xiaomi_miio, vacuum.xiaomi_miio, light.xiaomi_miio (@danielhiversen - #9426) (breaking change)
  • Swiss Public Transport sensor: All times handled by the Swiss Public Transport sensor are now in ISO 8601 format. Please update your templates sensors and automations. (@fabaff - #9129) (sensor.swiss_public_transport docs) (breaking change)
  • iOS: All category identifiers need to be lowercase. If you do not update, it will break actionable notifications to IOS devices sent by scripts/automations. (@rbflurry - #9427) (breaking change)
  • Fitbit: Put endpoints behind /api like the other oauth-using components (@happyleavesaoc - #9460) (sensor.fitbit docs) (breaking change)
  • Version 0.53 introduced a bug in the HomeMatic component which breaks the usage of system variables on the CCU / Homegear. This has not been fixed yet. If you are using these variables in your automations you should skip updates until the bug has been resolved. Upgrading is safe however if you only interact with devices.

All changes

]]> <![CDATA[Hassbian 1.3 - A bit of a stretch]]> 2017-09-16T23:00:00+08:00 http:///blog/2017/09/16/hassbian-1.3-a-bit-of-a-stretch This new release finally brings us the release of Hassbian based on the release of Raspbian Stretch. The most significant change with this is that we now run Home Assistant on Python 3.5. Other than that the changes are mostly to our tool hassbian-config.

Hassbian-config

To allow you to customize your installation further, we have made a few additions to our tool called hassbian-config. Majority of these changes where contributed by @Ludeeus.

Upgrade scripts

@Ludeeus contributed the possibility to run upgrade scripts to the hassbian-config tool.

  • Upgrade Hassbian: Upgrades packages of the base operating system. Contributed by @Landrash.
  • Upgrade Hassbian-script: Downloads and upgrades the latest release of Hassbian-scripts. Contributed by @Ludeeus.
  • Upgrade Home-assistant: Upgrades the Home Assistant installation to the latest release. Contributed by @Ludeeus.

To follow discussions about the development of the HASSbian image or to contribute join our Discord chat server.

To get started with the new image, check out the installation instructions on the installing Hassbian page.

]]> <![CDATA[0.53: Tesla, Customize editor, and super fast KNX rewrite]]> 2017-09-09T08:11:05+08:00 http:///blog/2017/09/09/release-53

The Home Assistant community has been super busy in the last two weeks to bring you this amazing release. 60 different contributors have done over a 100 PRs filled with new features, bug fixes and performance improvements.

9 days away from our 4th birthday, we’ve just accomplished a couple of great milestones that I would love to share with you. We’ve hit over 8000 stars 🌟 on GitHub and starting this release we now ship over 800 platforms and components!

Customize editor

Another step in making Home Assistant configurable via the frontend has been contributed by @andrey-git: a customization editor! You are now able to inspect all (possible) customizations of an entity and update them with just a few taps. Want to change the name or icon of an entity? All possible in mere seconds.

Screenshot of the new customize editor.

New Home Assistant configurations will be created correctly automatically. If you are an existing user, make sure you have the config screen enabled and that you include customizations from customize.yaml.

# Example configuration.yaml entry
homeassistant:
  # Include the customizations.
  customize: !include customize.yaml

# Enable the config screen
config:

Tesla

Thanks to the contribution by @zabuldon, you will now be able to control your Tesla car from Home Assistant. You’re able to check the temperature inside and outside your car, control your AC and unlock the car.

Input text

This release introduces a new input component: input_text contributed by @BioSehnsucht. With this component you will be able to set free form from the UI and then let that be used by your automations or templates.

KNX

This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunnelling devices. In the background it uses asyncio communication. Check the climate integration in action here and see the lights in action below:

New Platforms

Release 0.53.1 - September 12

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.

Breaking Changes

  • The new customize editor is using the file customize.yaml in your config folder. If you are using this file today for other config, make sure to rename it before using the new customize UI editor. (@andrey-git - #9134) (config docs) (breaking change) (new-platform)
  • The frontend component now supports loading custom html files when Home Assistant front end starts (@andrey-git - #9150) (breaking change). It could be Javascript, CSS or custom Web Components. Along there was a breaking change in the way Custom UI is used:
    • custom_ui_state_card now specifies the exact element name and not a suffix after state-card. So if you had state_card_custom_ui: custom-ui in your config, you should change it to state_card_custom_ui: state-card-custom-ui
    • custom_ui_state_card no longer makes the html fetch, you should make it separately:
frontend:
  extra_html_url:
    - /local/custom_ui/state-card-custom-ui.html

All changes

]]> <![CDATA[0.52: Scripts editor, Nello.io locks, HipChat and Abode Home Security]]> 2017-08-26T08:11:05+08:00 http:///blog/2017/08/26/release-0-52

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:

# scripts.yaml
turn_on_some_lights:
  alias: Turn on the lights
  sequence:
  - data: {}
    service: light.turn_on

Than update your configuration.yaml to look like this:

# Configuration.yaml example
script: !include scripts.yaml

New Platforms

Release 0.52.1 - August 28

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.

Breaking Changes

  • Remove spaces from Xiami switch attributes (@syssi - #8952) (switch.xiaomi docs) (breaking change)
  • MQTT Switch: command and availability payload are now no longer linked. Command and availability payload default to ON/OFF and must be configured individually if custom values are required. (@timstanley1985 - #8934) (switch.mqtt docs) (breaking change)
 -  platform: mqtt
    name: "Kitchen"
    state_topic: "stat/sonoff_1/POWER"
    command_topic: "cmnd/sonoff_1/POWER"
    availability_topic: "tele/sonoff_1/LWT"
    payload_available: "Online"
    payload_not_available: "Offline"
    retain: true

usps:
  username: user
  password: pass
  name: optional
  • eliqonline: The optional channel_id configuration variable of the Eliqonline sensor needs to be a positive integer. (@molobrakos - #9072) (sensor.eliqonline docs) (breaking change)
  • MySensors: Not a breaking change per se but users that have not been following the mysensors serial API could face dropped messages after this change. Messages are now validated according to the API before being passed along from/to devices. See 0.11 release notes for more info. (@MartinHjelmare - #9069) (mysensors docs) (binary_sensor.mysensors docs) (climate.mysensors docs) (cover.mysensors docs) (device_tracker.mysensors docs) (light.mysensors docs) (notify.mysensors docs) (sensor.mysensors docs) (switch.mysensors docs) (breaking change)
  • Automatic has disabled password authentication on their API. Home Assistant will now use OAuth2 to authenticate accounts. The following steps must be taken to transition your setup: 1) Log in to your Automatic developer account. In the Automatic Developer Apps Manager, specify the OAuth Redirect URL in the developer page. This should be configured to <home-assistant-url>/api/automatic/callback. (Example: http://hassio.local:8123/api/automatic/callback) Note that this URL only needs to be accessible from the browser you use to perform the authentication. 2) Remove username/password from your automatic device tracker configuration in configuration.yaml. 3) If you have authorized your account for scope:current_location, add current_location: true to your automatic device tracker configuration in configuration.yaml. 4) When you restart home assistant, click on the Automatic Configure link in the Configurator card, and follow the instructions to authorize Home Assistant.

    NOTE: Automatic’s API is currently not correctly authorizing with refresh tokens, so Step 4 currently needs to be performed after every restart. (@armills - #8962) (configurator docs) (device_tracker.automatic docs) (breaking change)

All changes

]]> <![CDATA[0.51: Massive history speed up, finished automation editor and official vacuum cleaner support]]> 2017-08-12T08:11:05+08:00 http:///blog/2017/08/12/release-51

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.

Release 0.51 is around the corner and it contains some really great updates.

Database speed up

The first one is more amazing database updates #8748 by @OverloadUT. Every query that has been tested executes in well under 1 second, even on a RPi using MySQL with 6 million rows and around 300 entities. This is true even when you’re getting an unrealistically huge date range!

Updating the database will take some time when you start Home Assistant. During that time, the Home Assistant frontend is not accessible. Please let it complete and do not turn Home Assistant off.

Frontend update

We have finished the migration of our frontend to be powered by Polymer 2. This has given us a big speed boost on Safari/iOS devices and has fixed a wide range of bugs.

We have also finished the automation editor. All triggers and actions are now implemented and so are most conditions (missing are and, or). The automation editor is also no longer Chrome only, it can now also be used in Safari.

Another change to the frontend is that we have reorganized the panels. The Z-Wave and automation configuration panels have been merged into the configuration panel.

Vacuum cleaners

As we have seen more vacuum cleaners land in Home Assistant, it was time to create an official component for them. That’s why @azogue introduced the new vacuum cleaner component in #8623. This allows first class integration of vacuum cleaners in Home Assistant. Out of the box we will have Dyson, Xiamo and Roomba as supported platforms.

New Platforms

Release 0.51.1 - August 12

  • Fixed a bug in the automation editor that would break if no conditions available in the config file. (@balloob)

Release 0.51.2 - August 14

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.

Breaking Changes

  • Efergy sensors: change units from KW to W (@emlt - #8761) (sensor.efergy docs) (breaking change)
  • Xiaomi vacuum is now a platform of new vacuum component derived from ToggleEntity, and services (@azogue - #8623) (breaking change) (new-platform)
vacuum:
- platform: xiaomi
  name: Vacuum cleaner
  host: !secret xiaomi_vacuum_robot_ip
  token: !secret xiaomi_vacuum_robot_token

All changes

]]> <![CDATA[Home Assistant Podcast #5]]> 2017-08-01T08:01:00+08:00 http:///blog/2017/08/01/hasspodcast-ep-5 We cover off AppDaemon/HADashboard and all the fun stuff introduced in 0.49 and 0.50.

Show notes available on the Home Assistant Podcast Website

Listen online

]]> <![CDATA[0.50: Voice control, History improvements, and Xiaomi]]> 2017-07-29T08:11:05+08:00 http:///blog/2017/07/29/release-50

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.

The launch has been crazy successful. The 20 minute introduction video by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.

Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.

Adding the power of voice to integrations

But enough about Hass.io, let’s not forget about Home Assistant. This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.

We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. This release includes a shopping list to show the new functionality. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.

# Example configuration.yaml entry
shopping_list:

To make testing these applications easier, we’ve updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions! Check out the developer docs for more information.

History improvements

@OverloadUT has been recently spending a lot of time on optimizing the history database queries. This release includes PR #8632, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.

The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)

Xiaomi integration

Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. @danielhiversen did an amazing job and we now support sensors, switches, lights and covers.

Velbus integration

Another awesome integration is that of the Velbus home automation system which has been contributed by @thomasdelaet. It integrates their sensors, covers, fans, lights and switches.

Manual alarm with MQTT control

A new version of the manual alarm component is now available with full MQTT control thanks to @colinodell. Using this you can build your own control panel to remotely arm/disarm the alarm. For example, using a Raspberry Pi to create an alarm.

New Platforms

Release 0.50.2 - July 31

Straight to 0.50.2. We released 0.50 as 0.50.1 due to an upload error to PyPi.

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.

Breaking Changes

alexa:
snips:
apiai:

intent_script:
  LightKitchen:
    speech:
      type: plain
      text: I did the work, yay.
    card:
      type: simple
      title: Lights Card
      content: I have turned on the lights.
    action:
      service: light.turn_on
      data:
        entity_id: light.kitchen

conversation:
  intents:
    LightKitchen:
      - The kitchen is magic
  • Switch fritzdect: attributes have been renamed to use underscores and no capital letters (@thomasklingbeil - #8436) (switch.fritzdect docs) (breaking change)
  • Yahoo Weather: no longer allow configuring forecasts but include all instead. (@fanthos - #8626) (weather.yweather docs) (breaking change)
  • The Home Assistant Z-Wave Cover implementation has been updated to support the latest development version of OpenZWave. If you are currently applying a workaround to your OpenZWave installation to support the barrier command class, you’ll need to make sure you update your workaround to the latest development version of OpenZWave. (@firstof9 - #8574) (cover docs) (cover.zwave docs) (breaking change)

All changes

]]> <![CDATA[Talk Python interview with Paulus Schoutsen]]> 2017-07-27T10:00:00+08:00 http:///blog/2017/07/27/talk-python-podcast

Join Michael Kennedy at the Talk Python podcast for an hour long interview with Paulus Schoutsen, the founder of Home Assistant, as they discuss the release of Hass.io and the vision for the perfect home automation.

Visit the episode page on Talk Python

]]> <![CDATA[Introducing Hass.io]]> 2017-07-25T08:02:05+08:00 http:///blog/2017/07/25/introducing-hassio TL;DR: Today we’re introducing Hass.io. Hass.io is an operating system that will take care of installing and updating Home Assistant, is managed from the Home Assistant UI, allows creating/restoring snapshots of your configuration and can easily be extended using Hass.io add-ons including Google Assistant and Let’s Encrypt.

Home Assistant is 2 months away from being 4 years old. In that time the Internet of Things has really taken off and we’ve seen many new devices and services. We saw the introduction of voice assistants like Google Home and new standards like Apple HomeKit.

Some things have been supported natively in Home Assistant, others have been integrated into Home Assistant via third party applications. All these moving parts caused our users to spend a lot of time maintaining their systems and applications instead of automating their homes.

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.

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.

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.

Some frequently asked questions are answered below in the read more section.

Hass.io has been built by Pascal Vizeli, the UI has been made by Paulus Schoutsen and BRUHAutomation made the introduction video. Big thanks to Resin.io for building ResinOS and helping us get started with it. Also a big thanks to the community for early feedback, helping out with the documentation and add-on development ❤️

Will Hass.io be the only way to run Home Assistant?

Hass.io is and will always be optional. You can still run Home Assistant wherever you can run Python.

Which 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.

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.

Can I restore a snapshot on a different device?

Yes, any Hass.io snapshot can be restored on any device.

The Hass.io configuration panel contains powerful tools. Why is there no extra security besides the Home Assistant login?

This is in the works. We have already implemented the backend and plan to release the UI soon.

Is there a roadmap?

We use Pivotal Tracker to track things that are in progress and what we might work on.

]]> <![CDATA[Home Assistant Podcast #4]]> 2017-07-17T08:01:00+08:00 http:///blog/2017/07/17/hasspodcast-ep-4 We quickly cover off a few community items including the move to Discord and Carlo talks with Phil about his use of Floorplan.

Listen online

]]> <![CDATA[0.49: Themes 🎨, kiosk mode and Prometheus.io]]> 2017-07-15T08:02:05+08:00 http:///blog/2017/07/15/release-49

WE HAVE THEMES 🎨👩‍🎨

Our already amazing frontend just got even more amazing thanks to @andrey-git. With the new theme support you can be in control of the primary color, accent color and a whole bunch more.

You can specify themes using new configuration options under frontend.

frontend:
  themes:
    green:
      primary-color: "#6CA518"

Once 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 Screenshot of a green dashboard

Not all parts of the user interface are themable yet. Expect improvements in future releases.

Kiosk mode

Another great new improvement for the frontend is the addition of a kiosk mode. When the frontend is viewed in kiosk mode, the tab bar will be hidden.

To activate kiosk mode, navigate to https://hass.example.com:8123/kiosk/group.living_room_view. Note that for default_view the url is just https://hass.example.com:8123/kiosk

This feature has also been brought to you by @Andrey-git! Big shout out to him for his continuous efforts to bring Home Assistant to the next level.

New Platforms

Release 0.49.1 - July 24

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.

Breaking Changes

apple_tv:
  - name: Apple TV
    host: 10.0.10.20
    login_id: 00000000-1234-5678-9012-345678901234
    start_off: true
    credentials: 8660DEA5154FB46B:20B94847926112B3F46F85DB3A7311830463BF65570C22C3786E27F38C3326CF

amcrest:
  - host: !secret amcrest_living
    name: "Living Room"
    username: !secret amcrest_living_username
    password: !secret amcrest_living_password
    resolution: low
    stream_source: snapshot
    sensors:
      - motion_detector
      - ptz_preset

All changes

]]> <![CDATA[Home Assistant Podcast #3]]> 2017-07-05T08:01:00+08:00 http:///blog/2017/07/05/hasspodcast-ep-3 The third episode of the Home Assistant Podcast is out. Paulus joins to talk about some stats and the release of 0.47 and Petar tells all about his Floorplan project for Home Assistant.

Listen online

]]> <![CDATA[Home Assistant is moving to Discord]]> 2017-07-04T07:28:01+08:00 http:///blog/2017/07/03/home-assistant-is-moving-to-discord Communities grow, things change. We understand that some people don’t like change, and that is why we are trying to make our chat transition from Gitter to Discord as smooth as possible for everyone. Join us now with just a click!

Click Read on → to find out more about why we’re moving.

Easy to join

Discord is a very easy platform to join. New users can immediately jump into the conversations without first having to create an account. Just provide your name and you’re in!

This is incredibly valuable for us and will make Home Assistant even more accessible than before.

Great apps

One of our least favorite things about Gitter is the quality of apps that they provide for iOS and Android devices. Discord, on the other hand, has the fastest and most feature-rich mobile apps that we’ve tried! For those of you who like to post pictures to the chatrooms directly from your phone…now you can. It doesn’t stop there; they also provide well-polished clients for Windows, macOS and even Linux. If you’re more of a browser-based chat client person, their web client will be perfect for you.

Moderation tools

We have been quite lucky so far as to not have much inappropriate behavior (spammers, trolls, etc) in our chatrooms. However, as our community continues to grow, this common issue might come up. Discord has the features that will help us shut this behavior down before it gets out of hand.

Great multiple server support

Do you already have a Discord account? Great! You can use that account to join in on the conversation now. One Discord account works with every Discord server. It is extremely easy to switch between servers or join new ones. Discord messages also work across servers, so your personal conversations are not scoped to a single server.

It’s hosted

We are big fans of self-hosted apps and services, but everyone knows they require a fair amount of maintenance and attention to keep them running smoothly. Discord is hosted on its own servers, so it’s better to let them maintain the service while we keep busy improving Home Assistant to bring you new and exciting features!

Plenty of features

Syntax highlighting, voice chats, ability to search chatrooms, private messaging, and even custom emoji! Discord has a great set of features that will keep us all happy for a long time to come. (Pssst…after you join our server, check out the :ponder: emoji!)

Join us!

Are you convinced and ready to make the switch? Join us, we’re just one click away!

Not convinced? Please take a moment to reach out to us in the comments below to provide your feedback on this change so that we can help make the switch easier for you and everyone else.

The fine print…

In the process of switching chat platforms we have decided to create what we feel is a very fair set of rules for our chat community. As growth continues, these rules might change. Also be sure to check the #welcome-rules channel for the most up-to-date rules for our chat server.

The rules…

Rules:

Please carefully read through these rules before engaging in conversation.

  1. New members: Welcome! Start by reading over the FAQ. Feel free to introduce yourself, as we are all friends here!

  2. If you have a question, please check the FAQ and relevant documentation before posting.

  3. Do not insult, belittle, or abuse your fellow community members. Any reports of abuse will not be taken lightly and will lead to a ban.

  4. Our moderators are kind enough to volunteer their time to help keep this a great community for everyone. Any inappropriate or unconstructive comments toward or about them will result in a ban.

  5. #devs is for development discussion only. #general is for common discussion, support questions, and lending help to others. Please use the appropriate channel as it pertains to the nature of your discussion.

  6. Spam will not be tolerated, including but not limited to: self-promotion, flooding, codewalls (longer than 15 lines) and unapproved bots.

These rules are not to be interpreted how you like, there are no “loopholes.” Anyone claiming not to be breaking the rules due to it “not being in the rules” will result in the according consequence. If you are unsure about something, please ask either myself (@dale3h) or the community.

If you have any issues with anything or anyone on the server please PM me (@dale3h) with any relevant details. I cannot help anyone if I am unaware of any issues.

Infractions and Bans:

Bans will be issued after one serious infraction or failing to acknowledge warnings of minor infractions. This is non-negotiable.

Sincerely,

Dale Higgs
Community Leader, Home Assistant

]]> <![CDATA[0.48: Snips.ai, Shiftr.io and a massive History query speed up]]> 2017-07-02T08:02:05+08:00 http:///blog/2017/07/02/release-48

It’s time for a great new release!

We’ve started the process of upgrading our frontend technology. If you notice something not working that did work before, please open an issue.

Pascal 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.

zwave:
  new_entity_ids: false

Big speed up in querying the history

Thanks to the work by @cmsimike in #8255 you’ll see a significant speed up when using the history view. In his local tests queries went from 1 minute to 90ms! ⚡️

Snips.ai component

Snips has contributed a component to integrate with their Snips.ai local voice assistant. This will allow you to hook a speaker and a microphone into your Raspberry Pi and make your own local Amazon Echo quickly. See the docs for further instructions.

Also a shoutout to @michaelarnauts for keeping an eye on our Docker build and once again reducing the file size 👍

Release 0.48.1 - July 5

New Platforms

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.

Breaking Changes

  • We have added a new option to whitelist folders that can be used as sources for sending files. You will need to use this option if you are using files with the telegram component. (@pvizeli - #8189) (breaking change)
homeassistant:
  whitelist_external_dirs:
    - /tmp
    - /home/kenji/data

notify:
  - name: mail
    platform: smtp
    server: !secret smtp_server
    sender: !secret mail_alert
    username: !secret mail_username
    password: !secret mail_password
    recipient: !secret mail_admin
    encryption: tls  # Or starttls, none
  • Light - LIFX: The lifx_effect_breathe call was deprecated in version 0.47 and has now been removed. You can use lifx_effect_pulse with mode: breathe for 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:
  platform: limitlessled
  bridges:

    - host: !secret limitless_v6_ip
      port: 5987
      version: 6
      groups:

      - number: 1
        type: rgbww
        name: Safari Glow
        fade: none

All changes

]]> <![CDATA[[Update: fixed] A frank and serious warning about X]]> 2017-06-20T09:04:05+08:00 http:///blog/2017/06/20/things-you-should-know-about-senic-covi Update June 21: Senic has removed our name from their materials and have issued an apology. We wish them best of luck with the launch of COVI.

Update June 28: Removed the brand name from the title to reduce the search ranking.

Original post:

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.

Take some of the following quotes from their Kickstarter campaign:

COVI is built on an open source platform. The Senic team, along with outside developers, contributes to this platform to create the integrations for COVI.

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.

Here is a quote that their CEO Tobias Eichenwald gave to Forbes:

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.

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.

Sincerely,

Paulus Schoutsen
Founder, Home Assistant

Robbie Trencheny
Core Developer, Home Assistant

]]> <![CDATA[0.47: Python Scripts, Sesame Smart Lock, Gitter, Onvif cameras]]> 2017-06-17T09:04:05+08:00 http:///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!

Python Scripts

The biggest change is a new type of script component: Python scripts. This new component will allow you to write scripts to manipulate Home Assistant: call services, set states and fire events. Each Python script is made available as a service. Head over to the docs to see how to get started.

Updater

The updater has received a new opt-in option to let us know which components you use. This will allow us to focus development efforts on the components that are popular.

updater:
  include_used_components: true

And as a reminder. We will never share gathered data in a manner that can be used to identify anyone. We do plan on making aggregate data public soon. This will include total number of users and which hardware/software platform people use to run Home Assistant.

Z-Wave

Z-Wave is also getting a big update in this release. The confusing entity_ids will be on their way out. There is a zwave blog post that gives more detail, but the upgrade steps will be as follows:

  1. Run Home Assistant as normal and the old IDs will still be used.
  2. The new entity IDs will be shown in the more-info dialog for each entity. Check to make sure none of them will have conflicts once the new names are applied.
  3. Rename entities using the ui card as described in the blog post to avoid conflicts. Restart Home Assistant to observe the changes.
  4. Update all places mentioning IDs (groups, automation, customization, etc.) in configuration.yaml.
  5. Add new_entity_ids: true to your zwave config.
  6. Restart Home Assistant to run with new IDs.
  7. The old entity IDs will be available in the more info dialog to trace down any remaining errors.

Monkey Patching Python 3.6

Some people have noticed that running Home Assistant under Python 3.6 can lead to segfaults. It seems to be related to the earlier segfault issues that we experienced when we released the asyncio-based core. We thought that those issues would have been fixed when Python bug 26617 was resolved. Although we see less reports compared to the old bug, there are still users experiencing them (gdb stacktrace points at PyObject_GC_Del()).

Since Python 3.6, the Task and Future classes have been moved to C. This gives a nice speed boost but also prevents us from monkey patching the Task class to avoid the segfault. Ben Bangert managed to brew up another monkey patch to stop Python 3.6 from using the C classes, falling back to the Python versions instead. This allows us to apply the original monkey patch again.

Both monkey patches are now active by default starting version 0.47 to avoid our users experiencing segfaults. This comes at a cost of not being able to benefit from all optimizations that were introduced in Python 3.6.

To run without the monkey patch, start Home Assistant with HASS_NO_MONKEY=1 hass. We will further investigate this issue and try to fix it in a future version of Python.

Release 0.47.1 - June 21

New platforms

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.

Breaking changes

image_processing:
  - platform: opencv
    name: OpenCV
    source:
      - entity_id: camera.front_door
    classifier:
      faces:
        file: /path/to/classifier
        name: Husband
        neighbors: 4
        min_size: (40, 40)
        scale: 1.1

lutron:
  host: IP_ADDRESS
  username: lutron
  password: integration

mailgun:
  domain: !secret mailgun_domain
  api_key: !secret mailgun_api_key
  sandbox: False

notify:
  - name: mailgun
    platform: mailgun
    recipient: !secret mailgun_recipient
  • Z-Wave node and scene activated trigger events now use the full entity ID (@armills - #7786) (zwave docs) (breaking change) ```yaml automation:
    • alias: Button 1 trigger: platform: event event_type: zwave.scene_activated event_data: entity_id: living_room_remote_13 scene_id: 1 yaml automation:
    • alias: Event 1 trigger: platform: event event_type: zwave.node_event event_data: entity_id: zwave.living_room_remote_13 basic_level: 1 ```
  • LIFX: add multiple modes to pulse effect. The lifx_effect_breathe call has been deprecated. Use lifx_effect_pulse with the new mode: breathe attribute instead. (@amelchio - #8016) (light.lifx docs) (breaking change)
  • Use standard entity_ids for zwave entities. This also introduces a small API breakage, where EVENT_SCENE_ACTIVATED and EVENT_NODE_EVENT will no longer supply an object_id. They will now be tied to the node entity_id. (@armills - #7786) (zwave docs) (light.zwave docs) (breaking change)
  • Fix attribute entities. Home Assistant will no longer filter out entities that are ‘falsey’. So you might see more entity attributes show up. (@pvizeli - #8066) (breaking change)

All changes

]]> <![CDATA[ZWave Entity IDs]]> 2017-06-15T20:00:00+08:00 http:///blog/2017/06/15/zwave-entity-ids ZWave entity_ids have long been a source of frustration in Home Assistant. The first problem we faced was that depending on the order of node discovery, entity_ids could be discovered with different names on each run. To solve this we added the node id as a suffix to the entity_id. This ensured that entity_ids were generated deterministically on each run, but additional suffixes had to be added to handle edge cases where there would otherwise be a conflict. The resulting entity_ids worked, but have been difficult to work with and makes ZWave a strange exception among other Home Assistant components.

Thanks to the awesome work of @turbokongen, a growing number of ZWave configuration options are now available from the new ZWave panel in the Home Assistant frontend. Among these new features is support for renaming of ZWave nodes and their underlying values. (These renames are persisted in zwcfg_*.xml) This is important, because these items are combined to form the Home Assistant entity name, which is used to generate the entity_id. Now that these options are available, ZWave users can rename nodes and values, influencing the entity_ids that are generated by Home Assistant.

Now that users are able to control these names, we will be making changes to how the entity_ids are generated for ZWave entities. The ZWave entity_ids are going to switch back to using the standard entity_id generation from Home Assistant core, based on the entity names. Moving forward, if there is a conflict when generating entity_ids, a suffix will be added, and it will be the responsibility of the user to rename their nodes and values to avoid the conflict. This is the same as any other platform in Home Assistant where two devices are discovered with the same name.

With the release of 0.47, this feature will be opt-in. Setting new_entity_ids: true under zwave: in your configuration.yaml will enable the new generation. After 0.48 this feature will become opt-out. From 0.48 onward, unless you’ve declared new_entity_ids: false you will switch to the new entity_id generation. At an undecided point in the future, the old entity_id generation will be removed completely.

I’m sure all ZWave users understand that the current entity_ids aren’t easy to use. They’re annoying to type in configuration.yaml, and break if a node needs to be re-included to the network. We know that breaking changes are painful, and so we’re doing what we can to roll this change out as smoothly as possible. The end result should be a dramatic simplification of most ZWave configurations. We hope that this change will ultimately make ZWave much easier to work with, and bring ZWave configuration just a little closer to the rest of the Home Assistant platforms.

]]> <![CDATA[Linux Action Show special about Home Assistant]]> 2017-06-10T09:04:05+08:00 http:///blog/2017/06/10/interview-with-jupiter-broadcasting Our founder Paulus Schoutsen is interviewed by Chris Fisher for a Linux Action Show special about home automation, Hass.io and the new Home Assistant podcast.

]]> <![CDATA[0.46: Rachio sprinklers, Netgear Arlo cameras and Z-Wave fans]]> 2017-06-04T09:04:05+08:00 http:///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.

New platforms

Release 0.46.1 - June 9

Breaking changes

  • The USPS sensor entity names have changed as there are now two. One for packages and one for mail. Config will now also use scan_interval instead of update_interval (@happyleavesaoc - #7655) (sensor.usps docs) (breaking change)
  • Automation state trigger: From/to checks will now ignore state changes that are just attribute changess (@amelchio - #7651) (automation.state docs) (breaking change)
  • Redesign monitored variables for hp_ilo sensor. monitored_variables is now a list of name and sensor_type values (@Juggels - #7534) (sensor.hp_ilo docs) (breaking change)
sensor:
  - platform: hp_ilo
    host: IP_ADDRESS or HOSTNAME
    username: USERNAME
    password: PASSWORD
    monitored_variables:
      - name: SENSOR NAME
        sensor_type: SENSOR TYPE
  • Automation - time: The after keyword for time triggers (not conditions) has been deprecated in favor of the at keyword. This resembles better what it does (old one still works, gives a warning) (@armills - #7846) (automation.time docs) (breaking change)
  • Automation - numeric_state: above and below will no longer trigger if it is equal. (@armills - #7857) (breaking change)
  • Broadlink switches: Entity ids will change for switches that don’t have a default name set. In this case the object_id is now used. (@abmantis - #7845) (switch.broadlink docs) (breaking change)
  • Disallow ambiguous color descriptors in the light.turn_on schema. This means that you can no longer specify both xy_color and rgb_color. (@amelchio - #7765) (breaking change)

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.

All changes

]]> <![CDATA[Home Assistant Podcast 1]]> 2017-06-02T14:00:00+08:00 http:///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.

]]>