* ✅ Various markdown, spelling, and grammar fixes * ✅ Various markdown, spelling, and grammar fixes * ✅ Various markdown, spelling, and grammar fixes
This commit is contained in:
Franck Nijhof
Fabian Affolter
parent
42f9a8e5cd
commit
6224c71c08
98 changed files with 131 additions and 131 deletions
|
|
@ -15,7 +15,7 @@ Ever since the launch of Home Assistant you have been able to track the state of
|
|||
* Recorder component that will record every event to a SQLite database
|
||||
* History component that will query and aggregate the recorded events
|
||||
|
||||
By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of todays release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.
|
||||
By adding this view into the past, we are adding an extra dimension into the state of your house. This brings great new possibilities for future features. The focus of today's release is on getting the recording component to you to start recording and getting some data. To show what is being recorded a view has been added that shows the last 24 hours of your house. Expect more extensive tools to explore your history in the future.
|
||||
|
||||
Adding history to the UI was a challenge on itself because the old UI did not support easy navigation. So to add to the awesomeness of this release, Home Assistant also got a face lift.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ date_formatted: March 8, 2015
|
|||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Organisation
|
||||
categories: Organization
|
||||
---
|
||||
|
||||
It is well known that you are either a good programmer or a good designer. It's rare you'll meet someone that is both. That's why it wasn't surprising to anyone that the logo that I made was mediocre — at best. Luckily, [Jeremy Geltman](http://jeremygeltman.com/) has come to the rescue and contributed a brand new logo for Home Assistant.
|
||||
|
|
|
|||
|
|
@ -132,7 +132,7 @@ char* deviceId = "sensor01"; // Name of the sensor
|
|||
char* stateTopic = "home-assistant/sensor01/brightness"; // MQTT topic where values are published
|
||||
int sensorPin = A0; // Pin to which the sensor is connected to
|
||||
char buf[4]; // Buffer to store the sensor value
|
||||
int updateInterval = 1000; // Interval in miliseconds
|
||||
int updateInterval = 1000; // Interval in milliseconds
|
||||
|
||||
// MQTT server settings
|
||||
IPAddress mqttServer(192, 168, 0, 12);
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ og_image: /images/supported_brands/glances.png
|
|||
---
|
||||
|
||||
<img src='/images/supported_brands/glances.png' style='border:none; box-shadow: none; float: right;' height='80' />
|
||||
Inspried by a [feature requests](https://github.com/home-assistant/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
|
||||
Inspired by a [feature requests](https://github.com/home-assistant/home-assistant/issues/310) I started looking into the available options to do monitoring of remote hosts. The feature request is about displaying system information in a similar way than the [systemmonitor](/components/sensor.systemmonitor/) sensor does it for the local system. After a while I started to think that it would be a nice addition for a small home network where no full-blown system monitoring setup is present.
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: post
|
||||
title: "Updated documentation"
|
||||
description: "We have reorganised our documentation which should make it easier to get started and develop for Home Assistant."
|
||||
description: "We have reorganized our documentation which should make it easier to get started and develop for Home Assistant."
|
||||
date: 2016-04-17 23:09:00 UTC
|
||||
date_formatted: "April 17, 2016"
|
||||
author: Paulus Schoutsen
|
||||
|
|
@ -14,7 +14,7 @@ One of the main complaints that we receive is something along the lines "I read
|
|||
|
||||
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](https://github.com/home-assistant/home-assistant.io/blob/86bb2df430ce267ab2123d51592d3f068ae509b5/source/components/index.markdown).
|
||||
|
||||
As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) 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](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organisation.
|
||||
As Home Assistant grew, so did our documentation. [Fabian Affolter](https://github.com/fabaff) 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](https://home-assistant.io/blog/categories/release-notes/)! But despite all the efforts, the documentation outgrew our existing documentation organization.
|
||||
|
||||
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.
|
||||
|
||||
|
|
|
|||
|
|
@ -7,10 +7,10 @@ date_formatted: "April 19, 2016"
|
|||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Organisation
|
||||
categories: Organization
|
||||
---
|
||||
|
||||
After 2.5 years I think we can proudly say: Home Assistant is a success. I write _we_ because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own [organisation on GitHub][gh-ha].
|
||||
After 2.5 years I think we can proudly say: Home Assistant is a success. I write _we_ because Home Assistant is no longer a one-person side project. It has become the side project of many people who spend countless hours on making Home Assistant the best home automation software out there. To acknowledge this we migrated the repositories from being under my name to be under our own [organization on GitHub][gh-ha].
|
||||
|
||||
On our journey we've reached many noteworthy milestones:
|
||||
|
||||
|
|
|
|||
|
|
@ -11,9 +11,9 @@ categories: Release-Notes
|
|||
og_image: /images/blog/2016-04-release-18/social.png
|
||||
---
|
||||
|
||||
It's time for 0.18. This release cycle is 2 days shorter than usual as I'll be travelling to Europe. This also means that it can take some more time before you get feedback on PRs.
|
||||
It's time for 0.18. This release cycle is 2 days shorter than usual as I'll be traveling to Europe. This also means that it can take some more time before you get feedback on PRs.
|
||||
|
||||
Since the last release we have moved all Home Assistant source code etc into it's own [organisation on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
|
||||
Since the last release we have moved all Home Assistant source code etc into it's own [organization on GitHub](https://github.com/home-assistant). We're growing up! This sadly did cause us to have to move all Docker images. Check the breaking changes section for more info.
|
||||
|
||||
<a href='/demo/'><img src='/images/blog/2016-04-release-18/media_player.png' style='box-shadow: none; border: 0;' /></a>
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ The reason I started using iBeacons was to improve presence detection (and I thi
|
|||
|
||||
When you use OwnTracks in standard _major move_ mode (which is kind to your phone battery) it sometimes fails to update when you’d like it to. In my case I found that it would often send a location update as I was on my way home, but then not update when I got home. The result would be that Home Assistant would think I was 500M away from home, and take quite a while to notice I was home. It would also mean that the automation that should turn on my lights when I got home didn’t work very well! There were a few times when my phone location updated at 2am and turned the lights on for me. Fortunately my wife is very patient!
|
||||
|
||||
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognises, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
|
||||
Luckily, OwnTracks supports iBeacons so I could use them to make presence detection more reliable. When OwnTracks sees a beacon it recognizes, it will send an update. This means that if you put a beacon at your front door - OwnTracks will see it within a few seconds of you arriving home - and send an update saying it has seen this iBeacon.
|
||||
|
||||
<!--more-->
|
||||
|
||||
|
|
@ -31,7 +31,7 @@ To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - a
|
|||
[MQTT]: /components/mqtt/#picking-a-broker
|
||||
[OwnTracks]: /components/device_tracker.owntracks/
|
||||
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognise the beacon.
|
||||
You then have to (A) tell Home Assistant where the beacon is located and (B) tell OwnTracks to recognize the beacon.
|
||||
|
||||
#### {% linkable_title A. Tell Home Assistant where your beacon is located %}
|
||||
|
||||
|
|
|
|||
|
|
@ -35,7 +35,7 @@ crw-rw----+ 1 root video 81, 0 Jun 23 08:05 /dev/video0
|
|||
crw-rw----+ 1 root video 81, 1 Jun 23 08:36 /dev/video1
|
||||
```
|
||||
|
||||
We need an additional software part to handle the cameras. [motion](http://lavrsen.dk/foswiki/bin/view/Motion/WebHome) is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the [RPM Fusion respository](http://rpmfusion.org/) enabled.
|
||||
We need an additional software part to handle the cameras. [motion](http://lavrsen.dk/foswiki/bin/view/Motion/WebHome) is capable of monitoring the video signal from USB and network cameras, do motion detection, and other nifty stuff like saving images, add text, or basic image manipulations. Make sure that you have the [RPM Fusion repository](http://rpmfusion.org/) enabled.
|
||||
|
||||
```bash
|
||||
$ sudo dnf -y install motion
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@ plt.xlabel('Time line')
|
|||
plt.savefig('sensor.png')
|
||||
```
|
||||
|
||||
Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are splitted into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.
|
||||
Creating a connection to the database and executing a query is similar to the ways already seen. The return values from the query are split into two lists. The time stamps must be converted in an value which is accepted by matplotlib and then the graph is generated and saved as image.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2016-07-reporting/mpl-sensor.png' />
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ categories: Release-Notes
|
|||
|
||||
When Home Assistant started the focus has always been on making a great developer experience. Allowing anyone to add support for their favorite devices to Home Assistant easily. This focus has been a great success since we now have 339 components and platforms!
|
||||
|
||||
Starting with this release, we are extending our extensability to the frontend. Starting this release, any component can [add it's own page to the frontend][custom-panels]. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you'll come up with!
|
||||
Starting with this release, we are extending our extensibility to the frontend. Starting this release, any component can [add it's own page to the frontend][custom-panels]. Examples of this today are the map, logbook and history. We are looking forward to all the crazy panels you'll come up with!
|
||||
|
||||
We have also seen an exciting trend of people starting to visualize their Internet of Things data using [Jupyter] Notebooks, which are a great way to create and share documents that contain code, visualizations, and explanatory text. In case you missed it, the [blog] post by [@kireyeu] shows an advanced usecase while our [Notebooks][jupyter-notebooks] in the [Home Assistant Notebooks repository][jupyter-repo] cover the basics.
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ And thus started my journey to take a critical look at how the Home Assistant ap
|
|||
|
||||
I hope this list can be useful to other people, as a guide for optimizing their own apps or for avoiding pitfalls when building a new one.
|
||||
|
||||
The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. **On my Mac the app starts in 1400 miliseconds and on my Nexus 5x in ~6500 miliseconds (~4.5 times slower!).**
|
||||
The first thing to do is to measure. The Home Assistant front end is a mobile web app, so we shouldn’t measure this on a machine with 8 cores and gigabytes of ram but instead measure on devices you expect a mobile web app to run: phones. Below are two timelines recorded with Home Assistant 0.18.2 (pre-optimizations) and Google Chrome 53. **On my Mac the app starts in 1400 milliseconds and on my Nexus 5x in ~6500 milliseconds (~4.5 times slower!).**
|
||||
|
||||
<p class='img'>
|
||||
<img
|
||||
|
|
@ -30,7 +30,7 @@ The first thing to do is to measure. The Home Assistant front end is a mobile we
|
|||
alt='Timeline of loading the front end in Home Assistant 0.18.2' />
|
||||
</p>
|
||||
|
||||
Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 miliseconds (-35%) on my Mac and 2400 miliseconds (-63%) on my Nexus 5x. [Check out the demo here.][demo]
|
||||
Although the app takes 6500 milliseconds to load on my phone, it would perform well afterwards. Still, that initial load is unacceptable. You expect to open an app on your phone and be able to use it, quickly. After I applied all the changes described below, I managed to reduce startup time to 900 milliseconds (-35%) on my Mac and 2400 milliseconds (-63%) on my Nexus 5x. [Check out the demo here.][demo]
|
||||
|
||||
<p class='img'>
|
||||
<img
|
||||
|
|
|
|||
|
|
@ -27,10 +27,10 @@ Singleboard computers are very popular to run Home Assistant. To support this fa
|
|||
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...
|
||||
|
||||
### {% linkable_title API documentation %}
|
||||
The [Home Assistant API Documentation](https://dev-docs.home-assistant.io/en/dev/) is a great addition to the already exisiting user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.
|
||||
The [Home Assistant API Documentation](https://dev-docs.home-assistant.io/en/dev/) is a great addition to the already existing user documentation. The focus is not end-users but developers who want to get details about the code without actually browsing the code on Github.
|
||||
|
||||
### {% linkable_title 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!
|
||||
The validation of the configuration is still on-going. Approximately 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!
|
||||
|
||||
### {% linkable_title All changes %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: post
|
||||
title: "We have a Raspberry Pi image now"
|
||||
description: "Release of the Rapsberry Pi Image for Home Assistant"
|
||||
description: "Release of the Raspberry Pi Image for Home Assistant"
|
||||
date: 2016-10-01 01:00:00 -0400
|
||||
date_formatted: "October 1, 2016"
|
||||
author: Fredrik Lindqvist
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ categories: Community
|
|||
og_image: /images/blog/2016-10-hacktoberfest/social.png
|
||||
---
|
||||
|
||||
Home Assistant will join this year for [Hacktoberfest], an event organised by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!
|
||||
Home Assistant will join this year for [Hacktoberfest], an event organized by DigitalOcean and GitHub to support and celebrate open source. The idea is that open source projects like Home Assistant will gather a bunch of entry-level bugs, features and documentation enhancements and that you, a current or future contributor, will fix them. If you submit four pull-requests during the month of October you will have earned yourself a limited edition Hacktoberfest T-shirt!
|
||||
|
||||
Why contribute to Home Assistant:
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ date_formatted: "October 25, 2016"
|
|||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Organisation
|
||||
categories: Organization
|
||||
---
|
||||
|
||||
On Saturday, we released [Home Assistant 0.31][0.31] which includes an improved updater component that checks for new versions using the Home Assistant servers. We wanted to update the community on its rollout and answer some questions that have come up. As part of the update check anonymous information about your operating system and Python version is submitted to Home Assistant servers unless you have opted out.
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ date_formatted: "January 21, 2017"
|
|||
author: Paulus Schoutsen
|
||||
author_twitter: balloob
|
||||
comments: true
|
||||
categories: Organisation
|
||||
categories: Organization
|
||||
---
|
||||
|
||||
### {% linkable_title UPDATE JAN 28, 2017 %}
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@ Thanks to [@konikvranik] the [HDMI CEC][cec] integration got a huge update with
|
|||
- Switch - Pilight: Implement echo config option ([@janLo])
|
||||
- Core: Support customize in packages ([@kellerza])
|
||||
- Switch - Flux: Allow disabling setting the brightness ([@rytilahti])
|
||||
- Media player - Sonos: Add `is_coordinator`, set coordinator after join/unjoin, and no emtpy image ([@pvizeli], [@andrey-git], [@robbiet480])
|
||||
- Media player - Sonos: Add `is_coordinator`, set coordinator after join/unjoin, and no empty image ([@pvizeli], [@andrey-git], [@robbiet480])
|
||||
- Climate: Hold mode ([@Duoxilian])
|
||||
- Switch - TPlink: No longer doing I/O in event bus ([@balloob])
|
||||
- Light - Insteon local: Improve Insteon configuration ([@wardcraigj])
|
||||
|
|
|
|||
|
|
@ -190,7 +190,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
|
|||
- Add multi contracts support for Hydroquebec ([@titilambert])
|
||||
- Add Zwave refresh services ([@andrey-git])
|
||||
- Add keep-alive feature to the generic thermostat ([@aronsky])
|
||||
- Fix wake_on_lan for german version of Windows 10 (#6397) ([@siebert])
|
||||
- Fix wake_on_lan for German version of Windows 10 (#6397) ([@siebert])
|
||||
- flux led lib ([@danielhiversen])
|
||||
- Cleanup async handling ([@pvizeli])
|
||||
- Restore for automation entities ([@kellerza])
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ Create an entry in our [Forum][forum]. Be creative and use your imagination.
|
|||
- Dead line: April, 23 2017 - 23.59 UTC
|
||||
- Voting period: April, 24th till April, 30 2017 - 23.59 UTC
|
||||
|
||||
The decision of the jury will be final. If there will be a dispute then the Top-5 commiter of the Home Assistant organisation on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the [Forum][forum] and on [Twitter][twitter].
|
||||
The decision of the jury will be final. If there will be a dispute then the Top-5 committer of the Home Assistant organization on Github will decide. Also, we reserve us the right to ban applications if we suspect cheating or unfair methods. Updates will be available in the [Forum][forum] and on [Twitter][twitter].
|
||||
|
||||
Keep in mind that you may have to pay the fee for customs handling and the import duty by yourself. The plan is to ship the hardware from Germany. If you are located in a country with import/export regulations, we may not be able to ship the hardware to you.
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ Also want to take a moment to thank Austin Andrews aka [Templarian] for his [Mat
|
|||
## Breaking changes
|
||||
|
||||
- We were incorrectly treating groups named `default_view` as default views. Make sure you set `view: true` in the config for these groups. [#251 (frontend)](https://github.com/home-assistant/home-assistant-polymer/pull/251)
|
||||
- The last release introduced a revamped LIFX platform. We only realised after deploy that this version does not work on Windows. We have added the old LIFX implementation back as `lifx_legacy`.
|
||||
- The last release introduced a revamped LIFX platform. We only realized after deploy that this version does not work on Windows. We have added the old LIFX implementation back as `lifx_legacy`.
|
||||
- We added indexes to the database to speed up the history view. Initial boot can take a couple of minutes. Do not shut down while migration is occurring. [#6688]
|
||||
- Z-Wave cover workaround has been removed. Use device config instead. [#6832]
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ I received emails and forum posts almost every day, even when the app would go w
|
|||
|
||||
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.
|
||||
It may not look the way that I wanted it to initially, with beautiful native UI components, but that's 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.
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ With the release of 1.21 a small problem with the OpenZWave build script wasn't
|
|||
|
||||
To allow you to customize your installation further, we have included a tool called `hassbian-config`. This tool comes with a set of packages that can easily be installed for easier customization of your Home Assistant installation. This replaces the `hassbian-scripts` functionality from 1.1.
|
||||
|
||||
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component thats used with Amazon Echo, Google Home and Mycroft.ai.
|
||||
- Install Hue. Configures the Python executable to allow usage of low numbered ports for use with Emulated Hue component that's used with Amazon Echo, Google Home and Mycroft.ai.
|
||||
- Install Mosquitto MQTT server. Installs the latest Mosquitto package and client tools from the Mosquitto projects official repository. Now includes websocket support.
|
||||
- Install Libcec. Adds local [HDMI CEC support][cec].
|
||||
- Install Open Z-Wave-pip. Installs Python Open Z-Wave from a pip package. This is the quickest and recommended way of installing Z-Wave support but does not OZWCP pre-installed.
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ og_image: /images/blog/2017-05-hassbian-pi-zero/home_assistant_plus_rpi_600x315.
|
|||
|
||||
Saw the [announcement](/blog/2017/04/30/hassbian-1.21-its-about-time/) yesterday for HASSbian 1.21 and got super excited?
|
||||
|
||||
Today we'll flash the latest HASSbian to a [Raspbery Pi Zero W](https://www.raspberrypi.org/products/pi-zero/).
|
||||
Today we'll flash the latest HASSbian to a [Raspberry Pi Zero W](https://www.raspberrypi.org/products/pi-zero/).
|
||||
**With an added bonus** that besides for an USB cable for power, there's no need for any cables!
|
||||
|
||||
What you'll need:
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ This release introduces a new input component: `input_text` contributed by @BioS
|
|||
|
||||
## {% linkable_title KNX %}
|
||||
|
||||
This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunnelling devices. In the background it uses asyncio communication. Check the climate integration in action [here](https://www.youtube.com/watch?v=JI0VJzlGpx4) and see the lights in action below:
|
||||
This release ships a new KNX implementation thanks to @Julius2342. It will instantly show all changed states of KNX devices within Home Assistant. Additionally it brings support for HVAC devices and notification services. It also adds a service for direct communication with the KNX bus. You can connect to KNX/IP routing and tunneling devices. In the background it uses asyncio communication. Check the climate integration in action [here](https://www.youtube.com/watch?v=JI0VJzlGpx4) and see the lights in action below:
|
||||
|
||||
<div class='videoWrapper'>
|
||||
<iframe src="https://www.youtube.com/embed/Fe3yaflU2XM" frameborder="0" allowfullscreen></iframe>
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ The most amazing part? It is super easy to set up!
|
|||
|
||||
## {% linkable_title Setting up Tor %}
|
||||
|
||||
Our [documentation](/docs/ecosystem/tor/) provides an detailled guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward:
|
||||
Our [documentation](/docs/ecosystem/tor/) provides an detailed guide about seting up a [Tor's Hidden Service](https://www.torproject.org/docs/hidden-services.html.en). The setup is straight-forward:
|
||||
|
||||
1. Install Tor. On a Debian-based system: `$ sudo apt-get install tor`. On Fedora: `$ sudo dnf install tor`
|
||||
2. Modify Tor's main configuration file `/etc/tor/torrc` to include the following lines:
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ The Hass.io release of 0.58 will be delayed by a couple of days because Pascal i
|
|||
|
||||
## {% linkable_title Translation update %}
|
||||
|
||||
Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. [@armills] and [@c727] are doing an amazing job managing this project. We've doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translaters are on top of their game and 79% is already translated.
|
||||
Translations are up and running in full speed. Shortly after the last release we got our translation pipeline figured out. [@armills] and [@c727] are doing an amazing job managing this project. We've doubled the number of supported languages to 42 and the amount of keys to translate went from 8 to 130. Our translators are on top of their game and 79% is already translated.
|
||||
|
||||
Talking about our translators, we now have 445 people with an account to help with translations. Not bad for 3 weeks!
|
||||
|
||||
|
|
|
|||
|
|
@ -27,14 +27,14 @@ With the Dominos Pizza integration made by [@wardcraigj] your home is now taking
|
|||
</p>
|
||||
|
||||
## {% linkable_title Shopping list tweaks %}
|
||||
[@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editting has been made easier.
|
||||
[@balloob] has refreshed the shopping list UI to make it more usable. It's now possible to add items by typing, instead of just voice. Also editing has been made easier.
|
||||
|
||||
## {% linkable_title Entity picker %}
|
||||
[@balloob] improved the way if you want to pick an entity. In the automation editor, the script editor and the service section of the Developer Tools it's much easier to identify the right one! The automation editor will only suggest relevant entities.
|
||||
|
||||
<p class='img'>
|
||||
<img src='/images/blog/2017-12-0.59/picker.png' alt='Screenshot of the Entity Picker.'>
|
||||
Screenshot of the of the Enitity Picker.
|
||||
Screenshot of the of the Entity Picker.
|
||||
</p>
|
||||
|
||||
## {% linkable_title Hass.io Add-ons %}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue