diff --git a/atom.xml b/atom.xml
index a6aa9a865c..4e6c7a4bff 100644
--- a/atom.xml
+++ b/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Home Assistant]]>
- 2017-07-03T21:16:28+00:00
+ 2017-07-04T01:57:58+00:00https://home-assistant.io/
@@ -13,6 +13,96 @@
Octopress
+
+ <![CDATA[Home Assistant is moving to Discord]]>
+
+ 2017-07-03T23:28:01+00:00
+ https://home-assistant.io/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, and it is extremely easy to switch between your servers quickly, and even 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 on their own servers, so it’s better to let them maintain the service while we keep busy on improving Home Assistant to bring you bigger and better 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 making the switch easier for you and everyone else.
+
+
The fine print…
+
+
In the process of switching chat platforms we have decided to go ahead and 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.
+
+
+
+
New members: Welcome! Start by reading over the FAQ. Feel free to introduce yourself, as we are all friends here!
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.
+
+
+
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.
+
+
+
#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.
+
+
+
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]]>
@@ -65,7 +155,7 @@
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.
+
…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.
@@ -383,7 +473,7 @@ Core Developer, Home Assistant
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.
+
…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.
@@ -678,7 +768,7 @@ trigger:
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.
+
…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.
@@ -879,7 +969,7 @@ If you have a security key set in your Open Z-Wave 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.
+
…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.
…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.
+
…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.
To follow discussions about the development of the HASSbian image or to contribute join the HASSbian gitter chat.
+
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 in the getting started section.
@@ -1682,7 +1772,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
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.
+
…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.
@@ -1967,46 +2057,6 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
As it currently stands, this is going to be the perfect companion hardware to work with Home Assistant: local, affordable, secure. And as cherry on the pie, local push will make us aware of changes right away.
-]]>
-
-
-
- <![CDATA[1 year and 22 days ago I had an idea...]]>
-
- 2017-04-15T08:04:05+00:00
- https://home-assistant.io/blog/2017/04/15/ios
- 1 year and 22 days ago, or 387 days ago, on March 25th, 2016, I started a project to bring Home Assistant to the iPhone.
-
-
I thought the existing notification and location solutions were lacking in one way or another and had wanted for years to have a project I could call my own which would allow me to learn iOS development. What better way then implementing an extremely complex application like Home Assistant?
-
-
I started with a lot of steam. I remember cranking out the initial work that night and showing Paulus who was astounded at how fast the UI was coming together.
-
-
Little would I know how many problems I would create and uncover throughout the process. Writing a mobile app for a project that moves as fast as Home Assistant is… tricky, to say the least. In the time since I started writing the app, Home Assistant had 90 releases. I started writing the day before 0.16 was released. Now we are at 0.42.3. Time flies…
-
-
I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.
-
-
I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.
-
-
I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.
-
-
It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
-
-
Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.
-
-
The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can’t do it all, and I’m still a new iOS developer who doesn’t know all the best practices.
-
-
The app is open source, has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there’s tons to do.
-
-
1 year and 22 days ago, on March 25th, 2016 I began work on Home Assistant for iOS.
-
-
Today, April 16th, 2017, I am extremely excited to announce that Home Assistant for iOS has been approved by Apple and is now available to download for a monthly subscription starting at $9.99 free! (had to get a joke in here somewhere!) on the iOS App Store in every country.
-
-
-
-
Please note, you must have Home Assistant 0.42.4 or later installed for the app to function properly.
-
-
Thanks for everything so far, I’m looking forward to the road that lies ahead for Home Assistant on iOS!
diff --git a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
index fd0d0db3fc..e7963c572b 100644
--- a/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
+++ b/blog/2014/12/26/home-control-home-automation-and-the-smart-home/index.html
@@ -162,6 +162,9 @@ This article will try to explain how they all relate.
diff --git a/blog/2015/02/08/looking-at-the-past/index.html b/blog/2015/02/08/looking-at-the-past/index.html
index 2187fa4768..da91ae0c36 100644
--- a/blog/2015/02/08/looking-at-the-past/index.html
+++ b/blog/2015/02/08/looking-at-the-past/index.html
@@ -150,6 +150,9 @@ Events are saved in a local database. Google Graphs is used to draw the graph. D
diff --git a/blog/2015/03/08/new-logo/index.html b/blog/2015/03/08/new-logo/index.html
index 5ae9c87cc0..80cf9566e7 100644
--- a/blog/2015/03/08/new-logo/index.html
+++ b/blog/2015/03/08/new-logo/index.html
@@ -133,6 +133,9 @@ The old logo, the new detailed logo and the new simple logo.
diff --git a/blog/2015/03/11/release-notes/index.html b/blog/2015/03/11/release-notes/index.html
index 456bd3de83..fd23f93967 100644
--- a/blog/2015/03/11/release-notes/index.html
+++ b/blog/2015/03/11/release-notes/index.html
@@ -158,6 +158,9 @@ An initial version of voice control for Home Assistant has landed. The current i
diff --git a/blog/2015/03/22/release-notes/index.html b/blog/2015/03/22/release-notes/index.html
index 39ec64b84f..435a0281a4 100644
--- a/blog/2015/03/22/release-notes/index.html
+++ b/blog/2015/03/22/release-notes/index.html
@@ -194,6 +194,9 @@ I (Paulus) have contributed a scene component. A user can create scenes that cap
diff --git a/blog/2015/05/14/release-notes/index.html b/blog/2015/05/14/release-notes/index.html
index 5cf545c07c..c545f954b3 100644
--- a/blog/2015/05/14/release-notes/index.html
+++ b/blog/2015/05/14/release-notes/index.html
@@ -216,6 +216,9 @@ Before diving into the newly supported devices and services, I want to highlight
diff --git a/blog/2015/06/10/release-notes/index.html b/blog/2015/06/10/release-notes/index.html
index 4d650daeff..32f54214e3 100644
--- a/blog/2015/06/10/release-notes/index.html
+++ b/blog/2015/06/10/release-notes/index.html
@@ -262,6 +262,9 @@ This switch platform allows you to control your motion detection setting on your
diff --git a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
index 935f00a34d..07dab16a57 100644
--- a/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
+++ b/blog/2015/07/11/ip-cameras-arduino-kodi-efergy-support/index.html
@@ -226,6 +226,9 @@ Fabian has added support for Forecast.io to g
diff --git a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
index 266129db9a..df515d5ad3 100644
--- a/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
+++ b/blog/2015/08/09/mqtt-raspberry-pi-squeezebox-asuswrt-support/index.html
@@ -209,6 +209,9 @@ Support for Temper temperature sensors has been contributed by
diff --git a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
index d2d8b19993..2e56b578c5 100644
--- a/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
+++ b/blog/2015/08/26/laundry-automation-with-moteino-mqtt-and-home-assistant/index.html
@@ -246,6 +246,9 @@ The automation and script syntax here is using a deprecated and no longer suppor
diff --git a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
index 5bde33808d..a3bfb6ff42 100644
--- a/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
+++ b/blog/2015/09/18/monitoring-with-glances-and-home-assistant/index.html
@@ -173,6 +173,9 @@ Glances web server started on http://0.0.0.0:61208/
It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
+
It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
diff --git a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
index 494a567b90..cb602bacc5 100644
--- a/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
+++ b/blog/2015/10/05/home-assistant-goes-geo-with-owntracks/index.html
@@ -152,6 +152,9 @@ Map in Home Assistant showing two people and three zones (home, school, work)
diff --git a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
index 080555be0d..9a5e27a885 100644
--- a/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
+++ b/blog/2015/10/11/measure-temperature-with-esp8266-and-report-to-mqtt/index.html
@@ -337,6 +337,9 @@ Home Assistant will keep track of historical values and allow you to integrate i
diff --git a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
index 928a438860..20337d0b5d 100644
--- a/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
+++ b/blog/2015/10/26/firetv-and-radiotherm-now-supported/index.html
@@ -159,6 +159,9 @@ This makes more sense as most people run Home Assistant as a daemon
Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that’s enough time to have some “only partially representative” data. It’s hard to tell how many Home Assistant users are out there. Currently there are 215 members in our Gitter chat room and last week PyPI counted 5063 downloads.
+
Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that’s enough time to have some “only partially representative” data. It’s hard to tell how many Home Assistant users are out there. Currently there are 215 members on our Discord chat server and last week PyPI counted 5063 downloads.
The idea was to anonymously collect some details about the usage of the different parts of Home Assistant and a little bit about the environment its running in.
Thanks to Python, users are running Home Assistant on the most popular Linux distributions and other operating systems including OS X and Microsoft Windows. One quarter of the operating systems are unknown which leads to the assumption that it is possible to run Home Assistant on most of the available operation systems today. We hope that *BSD users have fun too. The Hardware platform of choice seems to be x86_64 and ARM.
diff --git a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
index 62a855a2c9..3d7f88328f 100644
--- a/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
+++ b/blog/2015/12/10/activating-tasker-tasks-from-home-assistant-using-command-line-switches/index.html
@@ -164,6 +164,9 @@ This is where we’ll configure our task, so select the plus icon to select an a
diff --git a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
index 4eca64786f..ddbabe249b 100644
--- a/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
+++ b/blog/2016/01/30/insteon-lifx-twitter-and-zigbee/index.html
@@ -161,6 +161,9 @@ Example of the new views in the frontend. Learn mor
diff --git a/blog/2016/02/20/community-highlights/index.html b/blog/2016/02/20/community-highlights/index.html
index bab6d80c65..4c93851650 100644
--- a/blog/2016/02/20/community-highlights/index.html
+++ b/blog/2016/02/20/community-highlights/index.html
@@ -163,6 +163,9 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
diff --git a/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html b/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html
index 4e49781856..dc6f240528 100644
--- a/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html
+++ b/blog/2016/03/12/z-wave-pep257-templated-service-calls/index.html
@@ -166,6 +166,9 @@ player state attributes. This change affects automations, scripts and scenes.
In the past the buzz word “Smart mirror” was used a couple of times in our chatroom and even made it into the issue tracker. The existing solutions (Smart mirror, MagicMirror, and HomeMirror) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background.
+
In the past the buzz word “Smart mirror” was used a couple of times in our chatroom and even made it into the issue tracker. The existing solutions (Smart mirror, MagicMirror, and HomeMirror) seems to be overkill if you already have Home Assistant running somewhere in your house or apartment. Why not simple display a web page served by Home Assistant on the tablet? No app and no Raspberry Pi running in the background.
The HBMQTT broker provides websockets support for MQTT and mqttws31.js included in web page gives you access to the MQTT messages. It’s a matter of minutes. OK, it took a little longer because I’m not a Javascript guy to create the software part that will show details about your environment. The source is available at https://github.com/fabaff/home-assistant-display and the screenshot above shows the result. I guess that every person who is familiar with Javascript would be able to reduce the amount of code and to make it more flexible. Well, it’s a only prototype and showcase to include an image in this blog post.
I hope that this little article could give you an idea of extending Home Assistant in an unconventional way.
Until now the focus has been on making a platform that developers love to use. A platform that is simple but customizable. A platform that is both powerful and reliable. But most important: a platform that is local and open. Home Assistant does a great job at all these things.
There will be some major challenges ahead of us to target groups other than developers. Easy installation and easy configuration being the #1. I’m sure that we’ll be able to eventually achieve these goals. I can’t say yet how or when. As with everything Home Assistant, we’ll take tiny steps, gathering feedback along the way to make sure we’re solving the right problems.
I am confident that we will get there because we are set up for success: we have a robust architecture, high test coverage and an active community of world class developers and users. On top of that, we use Python which allows us to move fast and tackle complex problems in elegant ways. It is so easy to learn that it allows any programmer, experienced or not, to contribute support for devices and services. It’s as simple as filling in the blanks.
-
I would like to put out a big thank you to all our contributors who make Home Assistant what it is today. It doesn’t matter if it is form of code, documentation or giving support in our chat room or forums. You. all. rock.
+
I would like to put out a big thank you to all our contributors who make Home Assistant what it is today. It doesn’t matter if it is form of code, documentation or giving support in our chat room or forums. You. all. rock.
diff --git a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
index ed308b8856..9313f02d2d 100644
--- a/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
+++ b/blog/2016/04/30/ibeacons-part-1-making-presence-detection-work-better/index.html
@@ -208,6 +208,9 @@ For example, my wife works next door - and I couldn’t detect whether she’s a
Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our chat room and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.
+
Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our chat room and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.
SceneGen - cli for making scenes
SceneGen is a new command line utility developed by Andrew Cockburn that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states.
diff --git a/blog/2016/07/06/pocketchip-running-home-assistant/index.html b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
index 10cb5f8d85..a1cb0af3f3 100644
--- a/blog/2016/07/06/pocketchip-running-home-assistant/index.html
+++ b/blog/2016/07/06/pocketchip-running-home-assistant/index.html
@@ -161,6 +161,9 @@ Over a year ago I participated in the
diff --git a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
index 43048b651f..1cecffeca2 100644
--- a/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
+++ b/blog/2016/07/23/internet-of-things-data-exploration-with-jupyter-notebooks/index.html
@@ -171,6 +171,9 @@ One of the graphs created with this tutorial.
diff --git a/blog/2016/07/28/esp8266-and-micropython-part1/index.html b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
index 0aafb9d785..716a3a3463 100644
--- a/blog/2016/07/28/esp8266-and-micropython-part1/index.html
+++ b/blog/2016/07/28/esp8266-and-micropython-part1/index.html
@@ -251,6 +251,9 @@ If a module is missing then you need to download it from the
Thanks all for sticking with me to the end. I’ll be taking over a lot of Paulus’s (@balloob) work while he is gone, but as I said, don’t worry because he’ll be back well before 0.28.0 comes out. Hopefully you didn’t find this jovial blog post too jarring from our standard style, I just wrote a lot of this at 2am after being awake for almost 20 hours, so I’m a little loopy hahaha 😴.
Also, thanks as always to our developer contributors, documentation contributors, but most of all our users! This would’ve just been a script that Paulus (@balloob) used to control his lights at home if we didn’t have your enthusiasm.
-
Feel free to let me know what you thought of this blog post and release on Gitter or my Twitter, or even the Home Assistant Twitter. Did I mention we have a brand new Facebook page that you should absolutely Like? There’s a convenient Facebook Like and Twitter follow button right on the sidebar.
+
Feel free to let me know what you thought of this blog post and release on Discord or my Twitter, or even the Home Assistant Twitter. Did I mention we have a brand new Facebook page that you should absolutely Like? There’s a convenient Facebook Like and Twitter follow button right on the sidebar.
I almost forgot about your 🎁 for reading all the way to here: a 🍪! Hope you enjoy it in good health 😄.
-
Talk to you soon on Gitter and in your pull request comments!
+
Talk to you soon on Discord and in your pull request comments!
– Robbie
(p.s. To those of you that scrolled directly to the bottom to get your present, just know that you didn’t earn it like the others did. 😄)
diff --git a/blog/2016/08/31/esp8266-and-micropython-part2/index.html b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
index fe6127bffc..96413d8658 100644
--- a/blog/2016/08/31/esp8266-and-micropython-part2/index.html
+++ b/blog/2016/08/31/esp8266-and-micropython-part2/index.html
@@ -209,6 +209,9 @@ So, part 1 of ESP8266
Custom components extending BaseNotificationService need to be aware that kwargs.get(ATTR_TITLE) will now return None if a title has not been set, and will need to specify kwargs.get(ATTR_TITLE, ATTR_TITLE_DEFAULT) if they always require a title.
If you need help…
-
…don’t hesitate to use our Forum or join us for a little chat.
+
…don’t hesitate to use our Forum or join us for a little chat.
Nest sensor ‘mode’ has been renamed to ‘operation_mode’
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 the former communication channels. Thanks.
+
…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 the former communication channels. Thanks.
The aREST configuration between the sensor and the switch platform was aligned.
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 the former communication channels. Thanks.
+
…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 the former communication channels. Thanks.
…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 the former communication channels. Thanks.
+
…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 the former communication channels. Thanks.
Until next time
Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
…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 the former communication channels. Thanks.
+
…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 the former communication channels. Thanks.
Nest contains changes which will require your attention.
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 these communication channels. Thanks.
+
…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 these 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.
5000 stars on GitHub, 2000 people in out Gitter chatroom and over a million monthly page views. I don’t think we could wish for a better place to be at the end of 2016. Feels like an early Christmas present! Our early one for you is 0.35. It’s not a single thing inside a nice wrapping, more like several little gifts inside the 0.35 box.
+
5000 stars on GitHub, 2000 people in our chatroom and over a million monthly page views. I don’t think we could wish for a better place to be at the end of 2016. Feels like an early Christmas present! Our early one for you is 0.35. It’s not a single thing inside a nice wrapping, more like several little gifts inside the 0.35 box.
This will be the last release of 2016 as our developers are taking a well deserved break. We will be back in 2017!
Text to Speech
With the addition of a text-to-speech component by @pvizeli we have been able to bring Home Assistant to a whole new level. The text-to-speech component will take in any text and will play it on a media player that supports to play media. We have tested this on Sonos, Chromecast, and Google Home.
Call for help with HASSbian (our Raspberry Pi image)
In an effort to make Home Assistant, we’re planning to extend the things that people can do out of the box with HASSbian, our Raspberry Pi image. As you might know, the image is currently maintained by @Landrash. However he also spends a lot of time on improving the docs and helping out with a ton of other things.
So if you know your Linux-foo and would love to contribute to open source, join the developer chat and take a stab at one of our open issues.
VLC media player, Broadlink, and GPSLogger
Let you control VLC media player and play sound on connected speakers.
This Broadlink switch platform allow to you control Broadlink RM2 Pro and RM mini IR+RF devices. This Broadlink sensor platform adds support for Broadlink RM2 and A1 Devices.
@@ -154,7 +154,7 @@
Fix nest component with various KeyError exceptions (@technicalpickles)
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.
+
…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.
diff --git a/blog/2017/01/14/iss-usps-images-packages/index.html b/blog/2017/01/14/iss-usps-images-packages/index.html
index 77e6520165..3dae0631ff 100644
--- a/blog/2017/01/14/iss-usps-images-packages/index.html
+++ b/blog/2017/01/14/iss-usps-images-packages/index.html
@@ -171,7 +171,7 @@ You have to note:
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.
+
…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.
More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we’re introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.
-
Moving forward this Code of Conduct will be active for all projects within the Home Assistant organisation.
+
Moving forward this Code of Conduct will be active for all projects within the Home Assistant organization.
Moving forward we will also require that all contributors to any project have electronically signed our contributor license agreement (CLA). We have adopted the CLA that GitHub uses for their projects (see update at the top). Currently we have no plans to retroactively require a CLA for previous contributions, only those going forward.
@@ -133,7 +133,7 @@
Crediting contributors
We have now mostly automated updating the Credits page so that contributors get their attribution more quickly.
In closing
-
We hope you understand that our desire with these changes is only to help protect the amazing community that has been built around Home Assistant. If you have any questions, please contact us via email, Twitter or Gitter.
+
We hope you understand that our desire with these changes is only to help protect the amazing community that has been built around Home Assistant. If you have any questions, please contact us via email, Twitter or Discord.
TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. HASH_LANG_PLATFORM.xxx -> HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with - on exiting platforms.
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.
+
…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.
diff --git a/blog/2017/02/03/babyphone/index.html b/blog/2017/02/03/babyphone/index.html
index 3e6f85c69f..a97e27ce22 100644
--- a/blog/2017/02/03/babyphone/index.html
+++ b/blog/2017/02/03/babyphone/index.html
@@ -240,6 +240,9 @@ We change the platform name for binary sensor in 0.38 from
diff --git a/blog/2017/02/04/hassbian-toybox/index.html b/blog/2017/02/04/hassbian-toybox/index.html
index e15faa37d3..a687778200 100644
--- a/blog/2017/02/04/hassbian-toybox/index.html
+++ b/blog/2017/02/04/hassbian-toybox/index.html
@@ -123,7 +123,7 @@ To update the hassbian-scripts directory execute the following command as the On the horizon
There’s of course more on the horizon and there’s even more plans and wishes for how this image will function in the future.
On the close horizon from @Landrash there a few more script in the works and for tellstick, emulated_hue and for controlling Home Assistant.
-
To follow discussions about the development of the HASSbian image or to contribute join the HASSbian gitter chat.
+
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 in the getting started section.
@@ -166,6 +166,9 @@ On the close horizon from @Landrash th
The frontend core changes have caused all custom panels to break. Docs have not been updated yet. The gist is that you have to use this.hass.entities, this.hass.callService and this.hass.callApi.
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.
+
…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.
…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.
+
…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.
It’s time for version 0.40 already! For this version, the main focus was on performance and bug fixes. Big thanks to @pvizeli for driving this effort. Startup is now super fast. We have also continued with adding warnings for components and platforms that are slowing down Home Assistant.
Some people have interpreted our recent added warnings as if 0.39 introduced the issues that caused the warning. This is not the case, the platforms and components have been misbehaving for a while but now we are adding warnings so we are able to track down the culprits.
-
Before we continue talking about all the improvements in this release I want to take a moment to thank a few people from the Home Assistant community that are fundamental to the success of Home Assistant. Big thanks to @dale3h, @CCOSTAN, @skalavala, @rrubin0, @brahmafear, @bassclarinetl2, and @torn8o! These are all people that hang out in our main chat channel and help new users get started and help existing users when running into trouble. Home Assistant would not be there without all the effort you put in! 🙇
+
Before we continue talking about all the improvements in this release I want to take a moment to thank a few people from the Home Assistant community that are fundamental to the success of Home Assistant. Big thanks to @dale3h, @CCOSTAN, @skalavala, @rrubin0, @brahmafear, @bassclarinetl2, and @torn8o! These are all people that hang out in our main chat channel and help new users get started and help existing users when running into trouble. Home Assistant would not be there without all the effort you put in! 🙇
And that our community kicks ass is also shown in the numbers. We have already raised together over $700 for the EFF via the sale of our t-shirts! All of you rock! Another number worth mentioning is that this release brings us passed 600 integrations for Home Assistant. All of you rock, again!
Z-Wave is now threadsafe
@andrey-git has spend a lot of time to make Z-Wave perform better. It should no longer cause Home Assistant to run slower or raise warnings about the timer getting out of sync.
@@ -128,7 +128,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
If you are using async custom components, the passed in async_add_devices method is now a callback instead of a coroutine function.
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.
+
…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.
Release 0.40.1 - March 16
@@ -341,6 +341,9 @@ Screenshot of all the different functionality the IP webcam integration offers.
The frontend is now using Shadow DOM and this could break your custom panels (#228).
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.
+
…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.
…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.
+
…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.
diff --git a/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html b/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
index f7c926a8ba..967f144ab3 100644
--- a/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
+++ b/blog/2017/04/17/ikea-tradfri-internet-of-things-done-right/index.html
@@ -196,6 +196,9 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
diff --git a/blog/2017/04/22/ikea-tradfri-spotify/index.html b/blog/2017/04/22/ikea-tradfri-spotify/index.html
index 129aa40e1a..c3303a8d1a 100644
--- a/blog/2017/04/22/ikea-tradfri-spotify/index.html
+++ b/blog/2017/04/22/ikea-tradfri-spotify/index.html
@@ -145,7 +145,7 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
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.
+
…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.
Release 0.43.1 - April 25
@@ -341,6 +341,9 @@ After automatic discovery, Home Assistant will ask the user to finish pairing wi
And finally, for users of the config panel in the UI, we have fixed the issue with the group editor.
Enjoy!
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.
+
…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.
diff --git a/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html b/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
index ee0cd7d7b1..9ad6daf508 100644
--- a/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
+++ b/blog/2017/05/20/automation-editor-zwave-panel-ocr/index.html
@@ -135,7 +135,7 @@ If you have a security key set in your Open Z-Wave @balloob - #7714) (hassio docs)
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.
+
…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
@@ -289,6 +289,9 @@ If you have a security key set in your Open Z-Wave
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.
+
…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.
…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.
+
…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.
…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.
+
…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.
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, and it is extremely easy to switch between your servers quickly, and even 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 on their own servers, so it’s better to let them maintain the service while we keep busy on improving Home Assistant to bring you bigger and better 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 making the switch easier for you and everyone else.
+
The fine print…
+
In the process of switching chat platforms we have decided to go ahead and 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.
+
+
+
New members: Welcome! Start by reading over the FAQ. Feel free to introduce yourself, as we are all friends here!
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.
+
+
+
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.
+
+
+
#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.
+
+
+
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.
diff --git a/blog/categories/community/atom.xml b/blog/categories/community/atom.xml
index 7cb9783b2f..29c1af700b 100644
--- a/blog/categories/community/atom.xml
+++ b/blog/categories/community/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Community | Home Assistant]]>
- 2017-07-03T21:16:28+00:00
+ 2017-07-04T01:57:58+00:00https://home-assistant.io/
@@ -13,6 +13,92 @@
Octopress
+
+ <![CDATA[Home Assistant is moving to Discord]]>
+
+ 2017-07-03T23:28:01+00:00
+ https://home-assistant.io/blog/2017/07/03/home-assistant-is-moving-to-discord
+
+
+### 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][discord] now. One Discord account works with every Discord server, and it is extremely easy to switch between your servers quickly, and even 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 on their own servers, so it's better to let them maintain the service while we keep busy on improving Home Assistant to bring you bigger and better 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][discord]!
+
+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 making the switch easier for you and everyone else.
+
+## The fine print...
+
+In the process of switching chat platforms we have decided to go ahead and 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][discord] 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][docs] 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][discord-devs] is for **development discussion only**. [#general][discord-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
+
+[discord]: https://discord.gg/c5DvZ4e
+[discord-devs]: https://discord.gg/8X8DTH4
+[discord-general]: https://discord.gg/pywKZRT
+[FAQ]: https://home-assistant.io/faq/
+[docs]: https://home-assistant.io/docs/
+]]>
+
+
<![CDATA[Home Assistant at PyCon US 2017]]>
@@ -102,29 +188,6 @@ Keep in mind that you may have to pay the fee for customs handling and the impor
[forum]: https://community.home-assistant.io/c/contest-2017
[twitter]: https://twitter.com/home_assistant
-]]>
-
-
-
- <![CDATA[Workshop at CLT 2017]]>
-
- 2017-02-14T08:04:05+00:00
- https://home-assistant.io/blog/2017/02/14/clt-workshop
-
diff --git a/blog/categories/community/index.html b/blog/categories/community/index.html
index 631b58b403..a38dee2ea7 100644
--- a/blog/categories/community/index.html
+++ b/blog/categories/community/index.html
@@ -79,6 +79,27 @@
diff --git a/blog/categories/organisation/atom.xml b/blog/categories/organisation/atom.xml
index af406fd7c8..83a3ac57aa 100644
--- a/blog/categories/organisation/atom.xml
+++ b/blog/categories/organisation/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Organisation | Home Assistant]]>
- 2017-07-03T21:16:28+00:00
+ 2017-07-04T01:57:58+00:00https://home-assistant.io/
@@ -35,7 +35,7 @@ Starting today we are announcing a few initiatives to help protect our users, co
More people are getting to know and love Home Assistant every day and our community keeps growing. Our community consists of people from all over the world with different backgrounds and we want Home Assistant to be a place where everyone can feel at home. To help with this we're introducing a Code of Conduct. The Code of Conduct describes what type of behavior is unacceptable, how we will enforce it and where to report incidents.
-Moving forward this Code of Conduct will be active for all projects within the Home Assistant organisation.
+Moving forward this Code of Conduct will be active for all projects within the Home Assistant organization.
[Read the Code of Conduct][coc]
@@ -103,12 +103,14 @@ We have now mostly automated updating the [Credits](/developers/credits/) page s
## In closing
-We hope you understand that our desire with these changes is only to help protect the amazing community that has been built around Home Assistant. If you have any questions, please contact us via email, Twitter or Gitter.
+We hope you understand that our desire with these changes is only to help protect the amazing community that has been built around Home Assistant. If you have any questions, please contact us via email, [Twitter][twitter] or [Discord][discord].
[cla]: /developers/cla/
[mjg59]: https://twitter.com/mjg59
[gh-cla]: https://cla.github.com/
[license]: /developers/license/
+[twitter]: https://twitter.com/home_assistant
+[discord]: https://discord.gg/c5DvZ4e
]]>
@@ -198,7 +200,7 @@ Paulus
[gh-ha]: https://github.com/home-assistant/
[filling in the blanks]: /developers/platform_example_sensor/#code
-[chat room]: https://gitter.im/home-assistant/home-assistant
+[chat room]: https://discord.gg/c5DvZ4e
[forums]: https://community.home-assistant.io/
]]>
diff --git a/blog/categories/organisation/index.html b/blog/categories/organisation/index.html
index 01c999452b..c5dae8571c 100644
--- a/blog/categories/organisation/index.html
+++ b/blog/categories/organisation/index.html
@@ -201,6 +201,9 @@
diff --git a/blog/categories/release-notes/atom.xml b/blog/categories/release-notes/atom.xml
index ee23557e9e..6768a853e4 100644
--- a/blog/categories/release-notes/atom.xml
+++ b/blog/categories/release-notes/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Release-Notes | Home Assistant]]>
- 2017-07-03T21:16:28+00:00
+ 2017-07-04T01:57:58+00:00https://home-assistant.io/
@@ -65,7 +65,7 @@ Also a shoutout to [@michaelarnauts] for keeping an eye on our Docker build and
- Snips ASR and NLU component ([@michaelfester] - [#8156]) ([snips docs]) (new-platform)
## If you need help...
-...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. 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][issue]. Make sure to fill in all fields of the issue template.
@@ -516,8 +516,8 @@ light:
[weather.buienradar docs]: /components/weather.buienradar/
[zwave docs]: /components/zwave/
[forum]: https://community.home-assistant.io/
-[gitter]: https://gitter.im/home-assistant/home-assistant
[issue]: https://github.com/home-assistant/home-assistant/issues
+[discord]: https://discord.gg/c5DvZ4e
]]>
@@ -600,7 +600,7 @@ To run without the monkey patch, start Home Assistant with `HASS_NO_MONKEY=1 has
- Add Flexit AC climate platform ([@Sabesto] - [#7871]) ([climate.flexit docs]) (new-platform)
## If you need help...
-...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. 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][issue]. Make sure to fill in all fields of the issue template.
@@ -1078,7 +1078,6 @@ automation:
[zwave docs]: https://home-assistant.io/components/zwave/
[zwave blog post]: https://home-assistant.io/blog/2017/06/15/zwave-entity-ids/
[forum]: https://community.home-assistant.io/
-[gitter]: https://gitter.im/home-assistant/home-assistant
[issue]: https://github.com/home-assistant/home-assistant/issues
[first-commit]: https://home-assistant.io/help/trivia/#first-commit
[#8080]: https://github.com/home-assistant/home-assistant/pull/8080
@@ -1090,6 +1089,7 @@ automation:
[fan.dyson docs]: https://home-assistant.io/components/fan.dyson/
[remote.itach docs]: https://home-assistant.io/components/remote.itach/
[sensor.dyson docs]: https://home-assistant.io/components/sensor.dyson/
+[discord]: https://discord.gg/c5DvZ4e
]]>
@@ -1142,7 +1142,7 @@ sensor:
- 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][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. 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][issue]. Make sure to fill in all fields of the issue template.
@@ -1469,7 +1469,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[zoneminder docs]: https://home-assistant.io/components/zoneminder/
[zwave docs]: https://home-assistant.io/components/zwave/
[forum]: https://community.home-assistant.io/
-[gitter]: https://gitter.im/home-assistant/home-assistant
[issue]: https://github.com/home-assistant/home-assistant/issues
[#7780]: https://github.com/home-assistant/home-assistant/pull/7780
[#7841]: https://github.com/home-assistant/home-assistant/pull/7841
@@ -1484,6 +1483,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[sensor.metoffice docs]: https://home-assistant.io/components/sensor.metoffice/
[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
[media_player.roku docs]: https://home-assistant.io/components/media_player.roku/
+[discord]: https://discord.gg/c5DvZ4e
]]>
@@ -1559,7 +1559,7 @@ If you are using our [experimental Hass.io image][hass.io], we made a breaking c
- Allow fetching hass.io panel without auth ([@balloob] - [#7714]) ([hassio docs])
## If you need help...
-...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. 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][issue]. Make sure to fill in all fields of the issue template.
@@ -1904,7 +1904,6 @@ Experiencing issues introduced by this release? Please report them in our [issue
[zwave docs]: https://home-assistant.io/components/zwave/
[zwave.api docs]: https://home-assistant.io/components/zwave.api/
[forum]: https://community.home-assistant.io/
-[gitter]: https://gitter.im/home-assistant/home-assistant
[issue]: https://github.com/home-assistant/home-assistant/issues
[#7673]: https://github.com/home-assistant/home-assistant/pull/7673
[#7683]: https://github.com/home-assistant/home-assistant/pull/7683
@@ -1916,6 +1915,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
[hassio docs]: https://home-assistant.io/components/hassio/
[media_player.volumio docs]: https://home-assistant.io/components/media_player.volumio/
[telegram_bot.__init__ docs]: https://home-assistant.io/components/telegram_bot.__init__/
+[discord]: https://discord.gg/c5DvZ4e
]]>
@@ -1937,7 +1937,7 @@ And finally, for users of the config panel in the UI, we have fixed the issue wi
Enjoy!
## If you need help...
-...don't hesitate to use our very active [forums][forum] or join us for a little [chat][gitter]. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
+...don't hesitate to use our very active [forums][forum] or join us for a little [chat][discord]. 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][issue]. Make sure to fill in all fields of the issue template.
@@ -2412,7 +2412,6 @@ influxdb:
[wink docs]: https://home-assistant.io/components/wink/
[zha docs]: https://home-assistant.io/components/zha/
[forum]: https://community.home-assistant.io/
-[gitter]: https://gitter.im/home-assistant/home-assistant
[issue]: https://github.com/home-assistant/home-assistant/issues
[#7062]: https://github.com/home-assistant/home-assistant/pull/7062
[#7468]: https://github.com/home-assistant/home-assistant/pull/7468
@@ -2423,6 +2422,7 @@ influxdb:
[@pezinek]: https://github.com/pezinek
[device_tracker.unifi docs]: https://home-assistant.io/components/device_tracker.unifi/
[sensor.wunderground docs]: https://home-assistant.io/components/sensor.wunderground/
+[discord]: https://discord.gg/c5DvZ4e
]]>
diff --git a/blog/categories/release-notes/index.html b/blog/categories/release-notes/index.html
index b3e2f5c010..d4276f14a5 100644
--- a/blog/categories/release-notes/index.html
+++ b/blog/categories/release-notes/index.html
@@ -1462,6 +1462,9 @@
diff --git a/blog/categories/survey/atom.xml b/blog/categories/survey/atom.xml
index 1ad5a64314..ad27c5d7d9 100644
--- a/blog/categories/survey/atom.xml
+++ b/blog/categories/survey/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Survey | Home Assistant]]>
- 2017-07-03T21:16:28+00:00
+ 2017-07-04T01:57:58+00:00https://home-assistant.io/
@@ -18,7 +18,7 @@
2015-11-22T14:51:18+00:00https://home-assistant.io/blog/2015/11/22/survey-november-2015
- Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that's enough time to have some "only partially representative" data. It's hard to tell how many Home Assistant users are out there. Currently there are 215 members in our [Gitter chat room](https://gitter.im/balloob/home-assistant) and last week [PyPI](https://pypi.python.org/pypi/homeassistant/) counted 5063 downloads.
+ Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that's enough time to have some "only partially representative" data. It's hard to tell how many Home Assistant users are out there. Currently there are 215 members on our [Discord chat server](https://discord.gg/c5DvZ4e) and last week [PyPI](https://pypi.python.org/pypi/homeassistant/) counted 5063 downloads.
The idea was to anonymously collect some details about the usage of the different parts of Home Assistant and a little bit about the environment its running in.
diff --git a/blog/categories/survey/index.html b/blog/categories/survey/index.html
index 81ecfbe7b3..545c4b1e6a 100644
--- a/blog/categories/survey/index.html
+++ b/blog/categories/survey/index.html
@@ -136,6 +136,9 @@
diff --git a/blog/categories/technology/atom.xml b/blog/categories/technology/atom.xml
index cface8c06b..eceba23a59 100644
--- a/blog/categories/technology/atom.xml
+++ b/blog/categories/technology/atom.xml
@@ -4,7 +4,7 @@
<![CDATA[Category: Technology | Home Assistant]]>
- 2017-07-03T21:16:28+00:00
+ 2017-07-04T01:57:58+00:00https://home-assistant.io/
@@ -67,15 +67,15 @@ With this image there also quite a bit of cleaning of the base system and the sc
- Added libtool and autoconf package. Dependencies for some of the pip packages.
- Pi ZeroW should now work with the image.
-To follow discussions about the development of the HASSbian image or to contribute join the [HASSbian gitter chat][hassbian-gitter].
+To follow discussions about the development of the HASSbian image or to contribute join our [Discord chat server][discord-devs].
To get started with the new image, check out the installation instructions in the [getting started section][gs-image].
[cec]: /components/hdmi_cec/
[hassbian-repo]: https://github.com/home-assistant/hassbian-scripts/
[hassbian-config-release]: https://github.com/home-assistant/hassbian-scripts/releases/latest
-[hassbian-gitter]: https://gitter.im/home-assistant/hassbian
[gs-image]: /getting-started/installation-raspberry-pi-image/
+[discord-devs]: https://discord.gg/8X8DTH4
]]>
@@ -125,16 +125,16 @@ With this image there also quite a bit of cleaning of the base system and the sc
There's of course more on the horizon and there's even more plans and wishes for how this image will function in the future.
On the close horizon from [@Landrash][landrash-github] there a few more script in the works and for tellstick, emulated_hue and for controlling Home Assistant.
-To follow discussions about the development of the HASSbian image or to contribute join the [HASSbian gitter chat][hassbian-gitter].
+To follow discussions about the development of the HASSbian image or to contribute join our [Discord chat server][discord].
To get started with the new image, check out the installation instructions in the [getting started section][gs-image].
[cec]: /components/hdmi_cec/
[hassbian-repo]: https://github.com/home-assistant/hassbian-scripts
[hassbian-avahi]: hassbian.local
-[hassbian-gitter]: https://gitter.im/home-assistant/hassbian
[landrash-github]: https://github.com/Landrash
[gs-image]: /getting-started/installation-raspberry-pi-image/
+[discord]: https://discord.gg/8X8DTH4
]]>
diff --git a/blog/categories/technology/index.html b/blog/categories/technology/index.html
index ecb1514bb5..ae5aca1b7e 100644
--- a/blog/categories/technology/index.html
+++ b/blog/categories/technology/index.html
@@ -242,6 +242,9 @@
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.
…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.
+
…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.
…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.
+
…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.
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.
+
…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.
Read on →
@@ -465,7 +492,7 @@ If you have a security key set in your Open Z-Wave @balloob - #7714) (hassio docs)
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.
+
…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
@@ -505,35 +532,6 @@ If you have a security key set in your Open Z-Wave
-
-
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.
The core of home automation is knowing what’s going on. The faster we know about a state change, the better we can serve the user. If you want to have your lights to turn on when you arrive at home, it doesn’t help if it only knows about it after you’ve already opened the door and manually (!!) turned on the light.
+
Each smart device consists of the ‘normal’ device and the piece that makes it ‘smart’: the connectivity. The connectivity part of a device can consists of either control, state or both.
+
State describes what a device is up to right now. For example, a light can be on with a red color and a medium brightness.
+
Control is about controlling the smart device by sending commands via an API. These commands can vary from configuring how a device works till mimicking how a user would interact with a device. A media player can allow skipping to the next track and a sensor could allow to configure its sensitivity or polling interval.
+
The Home Assistant APIs are setup to be as convenient as possible. However, a network is always as weak as it’s weakest link. In our case these are the integrations. Take for example controlling a light that does not report state. The only state Home Assistant can report on after sending a command is the assumed state: what do we expect the state of the light to be if the command worked.
+
We want our users to get the best home automation experience out there and this starts with making sure they have devices that work well with Home Assistant. That’s why we will start applying the following classifiers to our integrations:
+
+
+
+
Classifier
+
Description
+
+
+
+
Assumed State
+
+ We are unable to get the state of the device. Best we can do is to assume the state based on our last command.
+
+
+
+
+
Cloud Polling
+
+ Integration of this device happens via the cloud and requires an active internet connection. Polling the state means that an update might be noticed later.
+
+
+
+
+
Cloud Push
+
+ Integration of this device happens via the cloud and requires an active internet connection. Home Assistant will be notified as soon as a new state is available.
+
+
+
+
+
Local Polling
+
+ Offers direct communication with device. Polling the state means that an update might be noticed later.
+
+
+
+
+
Local Push
+
+ Offers direct communication with device. Home Assistant will be notified as soon as a new state is available.
+
+
+
+
The background to how we got to these classifiers can be read after the break.
To update, run pip3 install --upgrade homeassistant.
+
+
+
+
+
+
@@ -120,7 +160,7 @@
-
Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that’s enough time to have some “only partially representative” data. It’s hard to tell how many Home Assistant users are out there. Currently there are 215 members in our Gitter chat room and last week PyPI counted 5063 downloads.
+
Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that’s enough time to have some “only partially representative” data. It’s hard to tell how many Home Assistant users are out there. Currently there are 215 members on our Discord chat server and last week PyPI counted 5063 downloads.
The idea was to anonymously collect some details about the usage of the different parts of Home Assistant and a little bit about the environment its running in.
@@ -372,7 +412,7 @@ Map in Home Assistant showing two people and three zones (home, school, work)
-
It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
+
It’s like someone opened a can of rock solid developers and emptied it above our chat channel because it exploded with great conversations and solid contributions. Featured in release 0.7.3: Sonos, iTunes, Alarm component and Automation upgrade.
Today we announce the release of Home Assistant v0.7.2 which includes brand new support by @sfam to integrate with IFTTT. IFTTT stands for If This, Then That and is a webservice that integrates with almost every possible webservice out there. Adding Home Assistant to this mix means Home Assistant can connect with all via IFTTT.
-
It is now possible to disable your irregation system if it is going to be cloudy tomorrow or tweet if your smoke alarm goes off.
-
-
-
-
Head over to the setup instructions to get started with IFTTT. Click the read more button for some example recipes.
Today we announce the release of Home Assistant v0.7.2 which includes brand new support by @sfam to integrate with IFTTT. IFTTT stands for If This, Then That and is a webservice that integrates with almost every possible webservice out there. Adding Home Assistant to this mix means Home Assistant can connect with all via IFTTT.
+
It is now possible to disable your irregation system if it is going to be cloudy tomorrow or tweet if your smoke alarm goes off.
+
+
+
+
Head over to the setup instructions to get started with IFTTT. Click the read more button for some example recipes.
It’s been a month since the latest update and a lot has happened again. Here a quick overview of the new things.
-
Line Charts
-James has upgraded the history in the frontend to support line graphs. Line graphs will be shown for any entity that has a unit of measurement. The line graphs will also be shown in the more info card of an entity. See the demo for a live example.
-
-
-
-
ISY994 hub support
-Ryan has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.
Logbook
- I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. See the demo for a live example.
-
It’s been a month since the latest update and a lot has happened again. Here a quick overview of the new things.
+
Line Charts
+James has upgraded the history in the frontend to support line graphs. Line graphs will be shown for any entity that has a unit of measurement. The line graphs will also be shown in the more info card of an entity. See the demo for a live example.
+
+
+
+
ISY994 hub support
+Ryan has contributed support to integrate the ISY994 hub by Universal Devices. This allows you to integrate your X10/Insteon sensors, switches and lights.
Logbook
+ I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. See the demo for a live example.
+
One of the things that was missing in Home Assistant for a while was a way to communicate with users. Wouldn’t it be nice to get a message when important events happen like the lights being turned on while no one is home? Since the Home Assistant frontend runs as a web application on the phone, we have no way to bring ourselves to the front. This is where the new notify component comes in, powered by PushBullet.
-
The new notify component will take in messages and tells them to the user. For now this will be powered by the very awesome PushBullet but any other messaging platform can be easily added.
-
-
- A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
-
-
Read on to learn how to enable the notify component and integrate it with other components.
One of the things that was missing in Home Assistant for a while was a way to communicate with users. Wouldn’t it be nice to get a message when important events happen like the lights being turned on while no one is home? Since the Home Assistant frontend runs as a web application on the phone, we have no way to bring ourselves to the front. This is where the new notify component comes in, powered by PushBullet.
+
The new notify component will take in messages and tells them to the user. For now this will be powered by the very awesome PushBullet but any other messaging platform can be easily added.
+
+
+ A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
+
+
Read on to learn how to enable the notify component and integrate it with other components.
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.
And finally, for users of the config panel in the UI, we have fixed the issue with the group editor.
Enjoy!
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.
+
…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.
1 year and 22 days ago, or 387 days ago, on March 25th, 2016, I started a project to bring Home Assistant to the iPhone.
-
I thought the existing notification and location solutions were lacking in one way or another and had wanted for years to have a project I could call my own which would allow me to learn iOS development. What better way then implementing an extremely complex application like Home Assistant?
-
I started with a lot of steam. I remember cranking out the initial work that night and showing Paulus who was astounded at how fast the UI was coming together.
-
Little would I know how many problems I would create and uncover throughout the process. Writing a mobile app for a project that moves as fast as Home Assistant is… tricky, to say the least. In the time since I started writing the app, Home Assistant had 90 releases. I started writing the day before 0.16 was released. Now we are at 0.42.3. Time flies…
-
I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.
-
I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.
-
I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.
-
It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
-
Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.
-
The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can’t do it all, and I’m still a new iOS developer who doesn’t know all the best practices.
-
The app is open source, has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there’s tons to do.
-
1 year and 22 days ago, on March 25th, 2016 I began work on Home Assistant for iOS.
-
Today, April 16th, 2017, I am extremely excited to announce that Home Assistant for iOS has been approved by Apple and is now available to download for a monthly subscription starting at $9.99 free! (had to get a joke in here somewhere!) on the iOS App Store in every country.
-
-
Please note, you must have Home Assistant 0.42.4 or later installed for the app to function properly.
-
Thanks for everything so far, I’m looking forward to the road that lies ahead for Home Assistant on iOS!
1 year and 22 days ago, or 387 days ago, on March 25th, 2016, I started a project to bring Home Assistant to the iPhone.
+
I thought the existing notification and location solutions were lacking in one way or another and had wanted for years to have a project I could call my own which would allow me to learn iOS development. What better way then implementing an extremely complex application like Home Assistant?
+
I started with a lot of steam. I remember cranking out the initial work that night and showing Paulus who was astounded at how fast the UI was coming together.
+
Little would I know how many problems I would create and uncover throughout the process. Writing a mobile app for a project that moves as fast as Home Assistant is… tricky, to say the least. In the time since I started writing the app, Home Assistant had 90 releases. I started writing the day before 0.16 was released. Now we are at 0.42.3. Time flies…
+
I couldn’t have completed the app without help and input from the community. By the end I had 700 beta testers, of which about 500 were very active in testing the app.
+
I received emails and forum posts almost every day, even when the app would go without an update for weeks and sometimes months at a time as my life got busier and busier.
+
I wanted this app to be done 9 months ago, at least, but my drive to add more and more features killed that idea. This really taught me the value of the MVP over the kitchen sink.
+
It may not look the way that I wanted it to initially, with beautiful native UI components, but thats okay. What I really cared about is there. The notification and location engines are some of the most customizable and powerful available in an iOS app if I do say so myself. I made them this way to keep with the spirit of infinite flexibility that is enshrined in Home Assistant.
+
Just because the app is released doesn’t mean we are at the end of the road. It’s only the beginning. There’s plenty of bugs to fix still, improvements to make, features to add. Beta testing will continue, and if anything, be expanded. I do want to have a native UI someday, but that’s pretty hard with how fast the project moves.
+
The biggest request I have is for more developers on the project. As many of you know, I have my hands in many different parts of Home Assistant, from governance and organization to managing the forums to writing this app, managing the Homebridge plugin and even sometimes writing code for the actual core codebase! I can’t do it all, and I’m still a new iOS developer who doesn’t know all the best practices.
+
The app is open source, has been for the last few months when I first prepared to submit it to Apple for review. I invite Swift developers to come and join me in building it. Trust me, there’s tons to do.
+
1 year and 22 days ago, on March 25th, 2016 I began work on Home Assistant for iOS.
+
Today, April 16th, 2017, I am extremely excited to announce that Home Assistant for iOS has been approved by Apple and is now available to download for a monthly subscription starting at $9.99 free! (had to get a joke in here somewhere!) on the iOS App Store in every country.
+
+
Please note, you must have Home Assistant 0.42.4 or later installed for the app to function properly.
+
Thanks for everything so far, I’m looking forward to the road that lies ahead for Home Assistant on iOS!
+
+
+
@@ -216,7 +256,7 @@
The frontend is now using Shadow DOM and this could break your custom panels (#228).
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.
+
…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.
It’s time for version 0.40 already! For this version, the main focus was on performance and bug fixes. Big thanks to @pvizeli for driving this effort. Startup is now super fast. We have also continued with adding warnings for components and platforms that are slowing down Home Assistant.
Some people have interpreted our recent added warnings as if 0.39 introduced the issues that caused the warning. This is not the case, the platforms and components have been misbehaving for a while but now we are adding warnings so we are able to track down the culprits.
-
Before we continue talking about all the improvements in this release I want to take a moment to thank a few people from the Home Assistant community that are fundamental to the success of Home Assistant. Big thanks to @dale3h, @CCOSTAN, @skalavala, @rrubin0, @brahmafear, @bassclarinetl2, and @torn8o! These are all people that hang out in our main chat channel and help new users get started and help existing users when running into trouble. Home Assistant would not be there without all the effort you put in! 🙇
+
Before we continue talking about all the improvements in this release I want to take a moment to thank a few people from the Home Assistant community that are fundamental to the success of Home Assistant. Big thanks to @dale3h, @CCOSTAN, @skalavala, @rrubin0, @brahmafear, @bassclarinetl2, and @torn8o! These are all people that hang out in our main chat channel and help new users get started and help existing users when running into trouble. Home Assistant would not be there without all the effort you put in! 🙇
And that our community kicks ass is also shown in the numbers. We have already raised together over $700 for the EFF via the sale of our t-shirts! All of you rock! Another number worth mentioning is that this release brings us passed 600 integrations for Home Assistant. All of you rock, again!
Z-Wave is now threadsafe
@andrey-git has spend a lot of time to make Z-Wave perform better. It should no longer cause Home Assistant to run slower or raise warnings about the timer getting out of sync.
@@ -349,7 +389,7 @@ Screenshot of all the different functionality the IP webcam integration offers.
If you are using async custom components, the passed in async_add_devices method is now a callback instead of a coroutine function.
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.
+
…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.
Release 0.40.1 - March 16
@@ -514,39 +554,6 @@ Screenshot of all the different functionality the IP webcam integration offers.
There will be a Home Assistant Workshop at the Chemnitzer Linux-Tage 2017. First I will cover the installation, the setup, and the configuration process. The second part will be all about automation. Last but not least, we will talk about the integration of a new platform/component.
There will be a Home Assistant Workshop at the Chemnitzer Linux-Tage 2017. First I will cover the installation, the setup, and the configuration process. The second part will be all about automation. Last but not least, we will talk about the integration of a new platform/component.
Reqistration is required as the places in the room are limited. The deadline for the registration is March, 8th 2017.
+
+
Location: Technische Universität Chemnitz, Reichenhainer Straße 90, 09126 Chemnitz, Germany
+
Date: March, 12th 2017
+
Time: 10:00, Room W2
+
Language: German
+
+
+
+
@@ -211,7 +244,7 @@
The frontend core changes have caused all custom panels to break. Docs have not been updated yet. The gist is that you have to use this.hass.entities, this.hass.callService and this.hass.callApi.
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.
+
…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.
@@ -276,7 +309,7 @@ To update the hassbian-scripts directory execute the following command as the On the horizon
There’s of course more on the horizon and there’s even more plans and wishes for how this image will function in the future.
On the close horizon from @Landrash there a few more script in the works and for tellstick, emulated_hue and for controlling Home Assistant.
-
To follow discussions about the development of the HASSbian image or to contribute join the HASSbian gitter chat.
+
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 in the getting started section.
@@ -460,7 +493,7 @@ On the close horizon from @Landrash th
TTS cache have change for the last time. Files use now also a option hash as part of the name. If you want to use the cache, it need to be renamed or cleared, new created. E. g. HASH_LANG_PLATFORM.xxx -> HASH_LANG_OPTIONS_PLATFORM.xxx, replace OPTIONS with - on exiting platforms.
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.
+
…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.
@@ -638,7 +671,7 @@ You have to note:
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.
+
…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.
@@ -707,101 +740,6 @@ You have to note:
And finally thank you community for being so helpful and awesome 🙇.
We’re taking a well deserved break and we will be back again in 2017 with more awesomeness. Happy holidays!
5000 stars on GitHub, 2000 people in out Gitter chatroom and over a million monthly page views. I don’t think we could wish for a better place to be at the end of 2016. Feels like an early Christmas present! Our early one for you is 0.35. It’s not a single thing inside a nice wrapping, more like several little gifts inside the 0.35 box.
-
This will be the last release of 2016 as our developers are taking a well deserved break. We will be back in 2017!
-
Text to Speech
-
With the addition of a text-to-speech component by @pvizeli we have been able to bring Home Assistant to a whole new level. The text-to-speech component will take in any text and will play it on a media player that supports to play media. We have tested this on Sonos, Chromecast, and Google Home.
Call for help with HASSbian (our Raspberry Pi image)
-
In an effort to make Home Assistant, we’re planning to extend the things that people can do out of the box with HASSbian, our Raspberry Pi image. As you might know, the image is currently maintained by @Landrash. However he also spends a lot of time on improving the docs and helping out with a ton of other things.
Let you control VLC media player and play sound on connected speakers.
-
This Broadlink switch platform allow to you control Broadlink RM2 Pro and RM mini IR+RF devices. This Broadlink sensor platform adds support for Broadlink RM2 and A1 Devices.
-
The GPSLogger now also supports attributes as the speed, direction, altitude, provider, and activity.
Some issues have been reported with TTS that will be addressed by 0.35.1. The TTS component had issues linking the media player to the right media file if you were using Docker or SSL certificates. This can be fixed by exposing to your HTTP config what url you use for hosting Home Assistant:
-
http:
- base_url:example.duckdns.org
-
-
-
-
Fix exit hanging on OS X with async logging (@balloob)
Fix nest component with various KeyError exceptions (@technicalpickles)
-
-
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.
5000 stars on GitHub, 2000 people in our chatroom and over a million monthly page views. I don’t think we could wish for a better place to be at the end of 2016. Feels like an early Christmas present! Our early one for you is 0.35. It’s not a single thing inside a nice wrapping, more like several little gifts inside the 0.35 box.
+
This will be the last release of 2016 as our developers are taking a well deserved break. We will be back in 2017!
+
Text to Speech
+
With the addition of a text-to-speech component by @pvizeli we have been able to bring Home Assistant to a whole new level. The text-to-speech component will take in any text and will play it on a media player that supports to play media. We have tested this on Sonos, Chromecast, and Google Home.
Call for help with HASSbian (our Raspberry Pi image)
+
In an effort to make Home Assistant, we’re planning to extend the things that people can do out of the box with HASSbian, our Raspberry Pi image. As you might know, the image is currently maintained by @Landrash. However he also spends a lot of time on improving the docs and helping out with a ton of other things.
+
So if you know your Linux-foo and would love to contribute to open source, join the developer chat and take a stab at one of our open issues.
+
VLC media player, Broadlink, and GPSLogger
+
Let you control VLC media player and play sound on connected speakers.
+
This Broadlink switch platform allow to you control Broadlink RM2 Pro and RM mini IR+RF devices. This Broadlink sensor platform adds support for Broadlink RM2 and A1 Devices.
+
The GPSLogger now also supports attributes as the speed, direction, altitude, provider, and activity.
Some issues have been reported with TTS that will be addressed by 0.35.1. The TTS component had issues linking the media player to the right media file if you were using Docker or SSL certificates. This can be fixed by exposing to your HTTP config what url you use for hosting Home Assistant:
+
http:
+ base_url:example.duckdns.org
+
+
+
+
Fix exit hanging on OS X with async logging (@balloob)
Fix nest component with various KeyError exceptions (@technicalpickles)
+
+
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.
+
+
+
@@ -203,7 +298,7 @@
Nest contains changes which will require your attention.
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 these communication channels. Thanks.
+
…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 these 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.
…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 the former communication channels. Thanks.
+
…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 the former communication channels. Thanks.
@@ -725,7 +820,7 @@
The Z-Wave entity ID change mentioned above
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 the former communication channels. Thanks.
+
…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 the former communication channels. Thanks.
Until next time
Thanks for reading all of the above, especially since this week was a pretty long post. We should be back with a new post around November 5th announcing the arrival of 0.32.
– Robbie
@@ -852,7 +947,7 @@
The aREST configuration between the sensor and the switch platform was aligned.
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 the former communication channels. Thanks.
+
…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 the former communication channels. Thanks.
Nest sensor ‘mode’ has been renamed to ‘operation_mode’
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 the former communication channels. Thanks.
It’s already time for 0.28 thanks to our super short release cycles. Now, it’ official…we hit 4000 stars on Github. That’s amazing. Sorry, not as amazing as all the stuff that was going on for 0.27 but still pretty awesome.
-
Reload automation rules
-
This release brings you a huge improvement of the automation and group handling. Both can be reloaded without a Home Assistant restart by calling their new reload services. The automations can be controlled directly from the frontend.
-
-
-
-
Raspberry Pi installation guide
-
Singleboard computers are very popular to run Home Assistant. To support this fact, the installation documentation for the Raspberry Pi devices was re-written to get users started as quickly as possible. @Landrash took the lead with on this tasks with help from @kellerza and @MartinHjelmare.
-
Climate and cover
-
There are countless bugfixes included in this release which will make your experience with the climate and the cover platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to @turbokongen, @pvizeli, @djbanks, @danielperna84, and others the improvements on the code and the frontend side is continuing…
-
API documentation
-
The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who whant to get details about the code without actually browsing the code on Github.
-
Configuration validation
-
The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to @kellerza, @fabaff, @Teagan42, and @pvizeli for your effort!
-
All changes
-
-
-
Light: Added bitfield to Flux LED since we are supporting effects (@tchellomello)
OpenweatherMap entity IDs are now like sensor.owm_temperature. Previously they were like sensor.weather_temperature. Apologies for this change, but we needed to make OpenWeatherMap more generic now that we have many weather platforms.
-
Updates of configuration variables due to configuration check or alignment with other platforms. Please update your configuration entries according to the documentation:
-
Custom components extending BaseNotificationService need to be aware that kwargs.get(ATTR_TITLE) will now return None if a title has not been set, and will need to specify kwargs.get(ATTR_TITLE, ATTR_TITLE_DEFAULT) if they always require a title.
-
-
If you need help…
-
…don’t hesitate to use our Forum or join us for a little chat.
+
…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 the former communication channels. Thanks.
It’s already time for 0.28 thanks to our super short release cycles. Now, it’ official…we hit 4000 stars on Github. That’s amazing. Sorry, not as amazing as all the stuff that was going on for 0.27 but still pretty awesome.
+
Reload automation rules
+
This release brings you a huge improvement of the automation and group handling. Both can be reloaded without a Home Assistant restart by calling their new reload services. The automations can be controlled directly from the frontend.
+
+
+
+
Raspberry Pi installation guide
+
Singleboard computers are very popular to run Home Assistant. To support this fact, the installation documentation for the Raspberry Pi devices was re-written to get users started as quickly as possible. @Landrash took the lead with on this tasks with help from @kellerza and @MartinHjelmare.
+
Climate and cover
+
There are countless bugfixes included in this release which will make your experience with the climate and the cover platforms better. Two week ago was the biggest merger of implementations released that ever happened in the history of Home Assistant. Thanks to @turbokongen, @pvizeli, @djbanks, @danielperna84, and others the improvements on the code and the frontend side is continuing…
+
API documentation
+
The Home Assistant API Documentation is a great addition to the already exisiting user documentation. The focus is not end-users but developers who whant to get details about the code without actually browsing the code on Github.
+
Configuration validation
+
The validation of the configuration is still on-going. Approximatly 80 % is done. This means that we will propably talk about this topic in the next release notes again. To align the configuration of components and platforms we needed to break some. Please refer to the Breaking changes section to check if you need to update your configuration or simple check your log for configuration validation errors. Thanks to @kellerza, @fabaff, @Teagan42, and @pvizeli for your effort!
+
All changes
+
+
+
Light: Added bitfield to Flux LED since we are supporting effects (@tchellomello)
OpenweatherMap entity IDs are now like sensor.owm_temperature. Previously they were like sensor.weather_temperature. Apologies for this change, but we needed to make OpenWeatherMap more generic now that we have many weather platforms.
+
Updates of configuration variables due to configuration check or alignment with other platforms. Please update your configuration entries according to the documentation:
+
Custom components extending BaseNotificationService need to be aware that kwargs.get(ATTR_TITLE) will now return None if a title has not been set, and will need to specify kwargs.get(ATTR_TITLE, ATTR_TITLE_DEFAULT) if they always require a title.
+
+
If you need help…
+
…don’t hesitate to use our Forum or join us for a little chat.
Thanks all for sticking with me to the end. I’ll be taking over a lot of Paulus’s (@balloob) work while he is gone, but as I said, don’t worry because he’ll be back well before 0.28.0 comes out. Hopefully you didn’t find this jovial blog post too jarring from our standard style, I just wrote a lot of this at 2am after being awake for almost 20 hours, so I’m a little loopy hahaha 😴.
Also, thanks as always to our developer contributors, documentation contributors, but most of all our users! This would’ve just been a script that Paulus (@balloob) used to control his lights at home if we didn’t have your enthusiasm.
-
Feel free to let me know what you thought of this blog post and release on Gitter or my Twitter, or even the Home Assistant Twitter. Did I mention we have a brand new Facebook page that you should absolutely Like? There’s a convenient Facebook Like and Twitter follow button right on the sidebar.
+
Feel free to let me know what you thought of this blog post and release on Discord or my Twitter, or even the Home Assistant Twitter. Did I mention we have a brand new Facebook page that you should absolutely Like? There’s a convenient Facebook Like and Twitter follow button right on the sidebar.
I almost forgot about your 🎁 for reading all the way to here: a 🍪! Hope you enjoy it in good health 😄.
-
Talk to you soon on Gitter and in your pull request comments!
+
Talk to you soon on Discord and in your pull request comments!
– Robbie
(p.s. To those of you that scrolled directly to the bottom to get your present, just know that you didn’t earn it like the others did. 😄)
Hotfix 0.27.1 - August 30
@@ -594,45 +702,6 @@ The first release of Micropython for ESP8266 was delivered a couple of weeks ago
This is the first blog post by Anton Kireyeu. A new contributor to Home Assistant who will focus on exploring and visualizing Home Assistant data.
-
As we learned in the recent blog post by Fabian, all operational data of your Home Assistant application is stored locally and is available for exploration. Our first steps were querying data with the DB Browser for SQLite, exporting the data extract as a CSV file and graphing in LibreOffice. But what else can be done with this data and what tools are there available?
-
This post will help you get set up using a few popular data scientist tools to allow you to locally process your data:
-
-
Pandas: an open source tool for data analysis for Python
This is the first blog post by Anton Kireyeu. A new contributor to Home Assistant who will focus on exploring and visualizing Home Assistant data.
+
As we learned in the recent blog post by Fabian, all operational data of your Home Assistant application is stored locally and is available for exploration. Our first steps were querying data with the DB Browser for SQLite, exporting the data extract as a CSV file and graphing in LibreOffice. But what else can be done with this data and what tools are there available?
+
This post will help you get set up using a few popular data scientist tools to allow you to locally process your data:
+
+
Pandas: an open source tool for data analysis for Python
@@ -480,7 +519,7 @@ In the past month I was thinking about ways to integrate USB webcams into Home A
-
Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our chat room and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.
+
Our community is amazingly helpful and creative. If you haven’t been there yet, make sure to stop by our chat room and come hang out with us. In this blog post I want to highlight a few recent awesome projects and videos from the community.
SceneGen - cli for making scenes
SceneGen is a new command line utility developed by Andrew Cockburn that helps with creating scene configurations for Home Assistant. To use it, you put your house in the preferred state, run SceneGen and it will print the scene configuration for your current states.
Videos
@@ -499,45 +538,6 @@ In the past month I was thinking about ways to integrate USB webcams into Home A
This post is by Home Assistant contributor Greg Dowling.
-
In Part 1 I talked about using iBeacons to improve presence tracking. In part 2 I’ll talk about how to track things like keys that can’t track themselves by using iBeacons.
-
Tracking things using iBeacons
-
In the first part I mentioned that iBeacons just send out I’m here packets, and we used this to trigger an update when your phone came close to a fixed beacon.
-
But beacons don’t have to be fixed.
-
Your phone knows roughly where it is located (based on mobile phone masts, Wi-Fi networks or GPS). If your phone sees an I’m here message then it knows the beacon is close.
-
If your phone can remember (or tell a server) where it was when it last saw the iBeacon - then it knows where the beacon was. So the result of this is that you can track where an iBeacon was - even though the iBeacon doesn’t have any tracking technology itself.
-
So if you put an iBeacon on your keys or in your car - then you can track them.
-
-
- Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!
-
This post is by Home Assistant contributor Greg Dowling.
+
In Part 1 I talked about using iBeacons to improve presence tracking. In part 2 I’ll talk about how to track things like keys that can’t track themselves by using iBeacons.
+
Tracking things using iBeacons
+
In the first part I mentioned that iBeacons just send out I’m here packets, and we used this to trigger an update when your phone came close to a fixed beacon.
+
But beacons don’t have to be fixed.
+
Your phone knows roughly where it is located (based on mobile phone masts, Wi-Fi networks or GPS). If your phone sees an I’m here message then it knows the beacon is close.
+
If your phone can remember (or tell a server) where it was when it last saw the iBeacon - then it knows where the beacon was. So the result of this is that you can track where an iBeacon was - even though the iBeacon doesn’t have any tracking technology itself.
+
So if you put an iBeacon on your keys or in your car - then you can track them.
+
+
+ Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!
+
Until now the focus has been on making a platform that developers love to use. A platform that is simple but customizable. A platform that is both powerful and reliable. But most important: a platform that is local and open. Home Assistant does a great job at all these things.
There will be some major challenges ahead of us to target groups other than developers. Easy installation and easy configuration being the #1. I’m sure that we’ll be able to eventually achieve these goals. I can’t say yet how or when. As with everything Home Assistant, we’ll take tiny steps, gathering feedback along the way to make sure we’re solving the right problems.
I am confident that we will get there because we are set up for success: we have a robust architecture, high test coverage and an active community of world class developers and users. On top of that, we use Python which allows us to move fast and tackle complex problems in elegant ways. It is so easy to learn that it allows any programmer, experienced or not, to contribute support for devices and services. It’s as simple as filling in the blanks.
-
I would like to put out a big thank you to all our contributors who make Home Assistant what it is today. It doesn’t matter if it is form of code, documentation or giving support in our chat room or forums. You. all. rock.
+
I would like to put out a big thank you to all our contributors who make Home Assistant what it is today. It doesn’t matter if it is form of code, documentation or giving support in our chat room or forums. You. all. rock.
One of the main complaints that we receive is something along the lines “I read that X is possible yet I am unable to find it on the website.”. This post is to announce that we have taken the first steps to improve it by revamping the getting started and developers sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.
-
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and called it a website. Back then we had a whopping 11 components.
-
As Home Assistant grew, so did our documentation. Fabian Affolter does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that’s quite a feat given our frequent releases! But despite all the efforts, the documentation outgrew our existing documentation organisation.
-
Today it has been almost 1.5 years since we started the website. We now have 264 components and platforms under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.
-
Finally, if you see some content that could use more clarifcation or is outdated, don’t hesitate to use the ‘Edit in GitHub’ link that is present on each page.
One of the main complaints that we receive is something along the lines “I read that X is possible yet I am unable to find it on the website.”. This post is to announce that we have taken the first steps to improve it by revamping the getting started and developers sections. It’s still a work in progress but we now have a solid foundation to build on for the future 👍.
+
Our documentation has been going through various phases. Initially it was just the README in our GitHub repository. I discovered Jekyll and GitHub pages in December 2014 and created home-assistant.io. I more or less broke the README in 5 pages and called it a website. Back then we had a whopping 11 components.
+
As Home Assistant grew, so did our documentation. Fabian Affolter does an amazing job in making sure there is at least a documentation stub for each new feature that lands. And that’s quite a feat given our frequent releases! But despite all the efforts, the documentation outgrew our existing documentation organisation.
+
Today it has been almost 1.5 years since we started the website. We now have 264 components and platforms under our belt and have been honored with 1.5 million page views ✨. And hopefully we now also have documentation that our community deserves.
+
Finally, if you see some content that could use more clarifcation or is outdated, don’t hesitate to use the ‘Edit in GitHub’ link that is present on each page.
+
+
+
@@ -523,80 +552,6 @@ Hold your NFC tag against the belly of Garfield to unlock the alarm.
The core of home automation is knowing what’s going on. The faster we know about a state change, the better we can serve the user. If you want to have your lights to turn on when you arrive at home, it doesn’t help if it only knows about it after you’ve already opened the door and manually (!!) turned on the light.
-
Each smart device consists of the ‘normal’ device and the piece that makes it ‘smart’: the connectivity. The connectivity part of a device can consists of either control, state or both.
-
State describes what a device is up to right now. For example, a light can be on with a red color and a medium brightness.
-
Control is about controlling the smart device by sending commands via an API. These commands can vary from configuring how a device works till mimicking how a user would interact with a device. A media player can allow skipping to the next track and a sensor could allow to configure its sensitivity or polling interval.
-
The Home Assistant APIs are setup to be as convenient as possible. However, a network is always as weak as it’s weakest link. In our case these are the integrations. Take for example controlling a light that does not report state. The only state Home Assistant can report on after sending a command is the assumed state: what do we expect the state of the light to be if the command worked.
-
We want our users to get the best home automation experience out there and this starts with making sure they have devices that work well with Home Assistant. That’s why we will start applying the following classifiers to our integrations:
-
-
-
-
Classifier
-
Description
-
-
-
-
Assumed State
-
- We are unable to get the state of the device. Best we can do is to assume the state based on our last command.
-
-
-
-
-
Cloud Polling
-
- Integration of this device happens via the cloud and requires an active internet connection. Polling the state means that an update might be noticed later.
-
-
-
-
-
Cloud Push
-
- Integration of this device happens via the cloud and requires an active internet connection. Home Assistant will be notified as soon as a new state is available.
-
-
-
-
-
Local Polling
-
- Offers direct communication with device. Polling the state means that an update might be noticed later.
-
-
-
-
-
Local Push
-
- Offers direct communication with device. Home Assistant will be notified as soon as a new state is available.
-
-
-
-
The background to how we got to these classifiers can be read after the break.
There are a bunch of online services which can help you if you are developing for Home Assistant or maintaining components. Some of these are directly connected to Pull Requests and the repositories, while others publish details and updates in our Gitter.im chatroom.
+
There are a bunch of online services which can help you if you are developing for Home Assistant or maintaining components. Some of these are directly connected to Pull Requests and the repositories, while others publish details and updates on our Discord chat server.
You’ll notice that this example includes a secondary parameter section (under the steam section) as well as a better example of the way comments can be used to break down files into sections.
That about wraps it up.
-
If you have issues checkout home-assistant.log in the configuration directory as well as your indentations. If all else fails, head over to the Gitter Chatroom and ask away.
+
If you have issues checkout home-assistant.log in the configuration directory as well as your indentations. If all else fails, head over to our Discord chat server and ask away.
Debugging multiple configuration files
If you have many configuration files, the check_config script allows you to see how Home Assistant interprets them:
Now that you saw a glimpse of what is possible, take a look at the documentation, ask your questions in our forum, join us for a chat, or report your issues.
+
Now that you saw a glimpse of what is possible, take a look at the documentation, ask your questions in our forum, join us for a chat, or report your issues.
Around a week ago we started with the first survey. Now 30 people have participated. Thank you very much if you did. We think that’s enough time to have some “only partially representative” data. It’s hard to tell how many Home Assistant users are out there. Currently there are 215 members in our 
+ 
-
-
-
-
I (Paulus) have added a logbook component. The logbook component provides a different perspective on the history of your house by showing all the changes that happened to your house in chronological order. 
- A message triggered by the simple_alarm component is shown by PushBullet on the Moto360.
-
-
-One of the graphs created with this tutorial.
-
- Here are my keys - with a Estimote Nearable iBeacon stuck to them. Ugly but effective!
-