Fixed common spelling mistakes (#3544)
* fix spelling errors * Update binary_sensor.xiaomi_aqara.markdown Reverts to previous revision before spell check. * Update tellstick.markdown Reverts to previous revision before spell check. * Update owntracks_two_mqtt_broker.markdown Reverts to previous revision before spell check. * Update cla_sign.html Reverts to previous revision before spell check. * Update credits.markdown Reverts to previous revision before spell check. * Update api.markdown Fixed spell checker changing noone to no one.
This commit is contained in:
Ashton Campbell
Fabian Affolter
parent
ae24b5142f
commit
9e6b9cb658
68 changed files with 90 additions and 90 deletions
|
|
@ -13,7 +13,7 @@ categories: Internet-of-Things
|
|||
The internet has been buzzing over the last year about home automation. A lot of different terms fly around like the internet of things, home automation and the smart home.
|
||||
This article will try to explain how they all relate.
|
||||
|
||||
The first thing to introduce is the **Internet of Things** (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its resevoir.
|
||||
The first thing to introduce is the **Internet of Things** (IoT). This refers to a new generation of devices that cannot only be controlled by humans via buttons or remotes but also provide an interface to communicate with other devices and applications. For example, an IoT-capable coffee machine could receive commands to create different types of coffee and be able to broadcast the amount of water left in its reservoir.
|
||||
|
||||
There is no widely adopted open standard for smart device communication. This prevents a lot of devices to communicate with one another. And even if they could, most devices are not designed to manage other devices. To solve this we need a device to be able to communicate with and manage all these connected devices. This device is called a **hub**.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ categories: Release-Notes
|
|||
|
||||
Most people do not like configuring things. Things just have to work, out of the box. Reaching this scenario is the goal of what we are about to introduce: our new discovery component.
|
||||
|
||||
The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The intial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.
|
||||
The discovery component will scan the WiFi network from time to time for connected zeroconf/mDNS and uPnP devices. The initial introduction is mainly focussed on getting the right architecture in place and discovers Belkin WeMo switches and Google Chromecasts connected to your network. When found, it will load and notify the appropritate component and it will be ready to use within seconds.
|
||||
|
||||
Most devices still require some sort of interaction from the user after being discovered - be it a button being pressed or some sort of authentication. This is a challenge that will be solved in the future.
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ The history component will be enabled for new users by default. For current user
|
|||
</p>
|
||||
|
||||
<p class='note'>
|
||||
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transfered to anyone at any time.
|
||||
Events are saved in a local database. Google Graphs is used to draw the graph. Drawing is happening 100% in your browser - no data is transferred to anyone at any time.
|
||||
</p>
|
||||
|
||||
<!--more-->
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ categories: Release-Notes
|
|||
|
||||
Home Assistant has learned a new trick to get the latest information from the server: streaming updates. No longer will the frontend poll every 30 seconds for updates but instead it will keep a connection open and get the latest changes pushed as soon as they happen.
|
||||
|
||||
A new toggle has been added ot the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
|
||||
A new toggle has been added to the sidebar to turn streaming updates on and off. This preference will be saved on a per-browser basis using local storage. The toggle will also indicate when there is an error setting up a stream after which it will fall back to use polling.
|
||||
|
||||
<p class='img'><img src='/images/screenshots/streaming-updates.png' /></p>
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ comments: true
|
|||
categories: Release-Notes
|
||||
---
|
||||
|
||||
We discovered two issues annoying enough to warrent the release of 0.7.5:
|
||||
We discovered two issues annoying enough to warrant the release of 0.7.5:
|
||||
|
||||
- Home Assistant package did not include the CloudMQTT certificate.
|
||||
- A bug in the core caused issues when some platforms are loaded twice.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ og_image: /images/blog/2015-12-influxdb/grafana-graph.png
|
|||
---
|
||||
|
||||
<img src='/images/supported_brands/influxdb.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;' width='200' /><img src='/images/supported_brands/grafana.png' style='clear: right; border:none; box-shadow: none; float: right; margin-bottom: 12px;' width='200' />
|
||||
The [InfluxDB](https://influxdb.com/) database is a so-called time series database primarly designed to store sensor data and real-time analytics.
|
||||
The [InfluxDB](https://influxdb.com/) database is a so-called time series database primarily designed to store sensor data and real-time analytics.
|
||||
|
||||
The `influxdb` component makes it possible to transfer all state changes from Home Assistant to an external [InfluxDB](https://influxdb.com/) database.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ og_image: /images/blog/2016-01-release-12/social.png
|
|||
|
||||
Another sprint has come to an end and it seems that we have not slowed down a single bit 🚀. 0.12 is full of new components, platforms and organizational additions.
|
||||
|
||||
I would like to give a shout out to [Greg Dowling (@pavoni)][@pavoni] as every release includes new work from him. He is constantly adding support for new platforms or improving the reliablity of existing components and platforms. Keep up the good work!
|
||||
I would like to give a shout out to [Greg Dowling (@pavoni)][@pavoni] as every release includes new work from him. He is constantly adding support for new platforms or improving the reliability of existing components and platforms. Keep up the good work!
|
||||
|
||||
This release includes a very frequent requested feature: the ability to organize entities in different tabs in the frontend. See [the demo] to see this in action and read more in the [group documentation][group] how to get started.
|
||||
|
||||
|
|
|
|||
|
|
@ -111,7 +111,7 @@ mqtt:
|
|||
broker: localhost
|
||||
```
|
||||
|
||||
Replace `localhost` with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path `smartthings/<Device Name>/<Atribute>`
|
||||
Replace `localhost` with the location of the running MQTT Broker. Devices from the MQTT Bridge are published to the path `smartthings/<Device Name>/<Attribute>`
|
||||
|
||||
For example, my Dimmer Z-Wave Lamp is called "Fireplace Lights" in SmartThings. The following topics are published:
|
||||
|
||||
|
|
|
|||
|
|
@ -143,7 +143,7 @@ Controlling a device can, just like state, be done through cloud and/or local co
|
|||
These devices are not able to be controlled. They will only offer state.
|
||||
|
||||
### {% linkable_title Poll State after sending command %}
|
||||
These devices will require the state to be polled after sending a command to see if a command was successfull.
|
||||
These devices will require the state to be polled after sending a command to see if a command was successful.
|
||||
|
||||
Advantages:
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
---
|
||||
layout: post
|
||||
title: "0.23: Envisalink, Homematic, HDMI-CEC and Sony Bravia TV"
|
||||
description: "This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionaly was the Wink support improved and CherryPy is the new WSGI server."
|
||||
description: "This new release of Home Assistant contains support for Envisalink, Homematic, Sony Bravia TV and HDMI-CEC. Additionally was the Wink support improved and CherryPy is the new WSGI server."
|
||||
date: 2016-07-01 00:31:00 +0000
|
||||
date_formatted: "July 1, 2016"
|
||||
author: Paulus Schoutsen
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ Leaving...
|
|||
|
||||
Now reset the device. You should then be able to use the [REPL (Read Evaluate Print Loop)](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#getting-a-micropython-repl-prompt). On Linux there is `minicom` or `picocom`, on a Mac you can use `screen` (eg. `screen /dev/tty.SLAB_USBtoUART 115200`), and on Windows there is Putty to open a serial connection and get the REPL prompt.
|
||||
|
||||
The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is neccessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post.
|
||||
The [WebREPL](http://docs.micropython.org/en/latest/esp8266/esp8266/tutorial/repl.html#webrepl-a-prompt-over-wifi) work over a wireless connection and allows easy access to a prompt in your browser. An instance of the WebREPL client is hosted at [http://micropython.org/webrepl](http://micropython.org/webrepl). Alternatively, you can create a local clone of their [GitHub repository](https://github.com/micropython/webrepl). This is necessary if your want to use the command-line tool `webrepl_cli.py` which is mentionend later in this post.
|
||||
|
||||
```bash
|
||||
$ sudo minicom -D /dev/ttyUSB0
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ So why `AppDaemon`? `AppDaemon` is not meant to replace Home Assistant Automatio
|
|||
- Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened
|
||||
- All the power of Python - use any of Python's libraries, create your own modules, share variables, refactor and re-use code, create a single app to do everything, or multiple apps for individual tasks - nothing is off limits!
|
||||
|
||||
It is in fact a testament to Home Assistant's open nature that a component like `AppDaemon` can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant's underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for `AppDaemon` - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additonal functions to make things that were already possible easier.
|
||||
It is in fact a testament to Home Assistant's open nature that a component like `AppDaemon` can be integrated so neatly and closely that it acts in all ways like an extension of the system, not a second class citizen. Part of the strength of Home Assistant's underlying design is that it makes no assumptions whatever about what it is controlling or reacting to, or reporting state on. This is made achievable in part by the great flexibility of Python as a programming environment for Home Assistant, and carrying that forward has enabled me to use the same philosophy for `AppDaemon` - it took surprisingly little code to be able to respond to basic events and call services in a completely open ended manner - the bulk of the work after that was adding additional functions to make things that were already possible easier.
|
||||
|
||||
## {% linkable_title How it Works %}
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ 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 whant 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 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.
|
||||
|
||||
### {% 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!
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ categories: Release-Notes
|
|||
|
||||
Yes, after only nine days comes 0.30. Don't worry, we will try to keep our usual release cycle and not start to release every day.
|
||||
|
||||
We guess that you already know: The [Raspberry Pi image][pi-image] is available now. For Hassbian, [@Landrash] has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to recieve [feedback][hassbian-forum], [issue report][hassbian-forum], and [suggestions][hassbian-forum] to improve it.
|
||||
We guess that you already know: The [Raspberry Pi image][pi-image] is available now. For Hassbian, [@Landrash] has combined the most essential parts for a Home Assistant setup in an easy-to-use image for the Raspberry Pi device family. Hassbian is quite young, thus we are looking forward to receive [feedback][hassbian-forum], [issue report][hassbian-forum], and [suggestions][hassbian-forum] to improve it.
|
||||
|
||||
A large amount of resources of the development are still focusing on the effort to move Home Assistant further to asynchronous programming. It's a labor-intensive task, comes with segmentation faults, and unstable instances when certain combinations of sensors are used. The benefit will be more speed in the near future.
|
||||
|
||||
|
|
|
|||
|
|
@ -173,7 +173,7 @@ This is super annoying, I know, especially since we had said in [0.12][zero-one-
|
|||
- Weather: Allow tracking severe weather alerts with [WUnderground] ([@tchellomello])
|
||||
- Sensor: New support added to track [min/max/mean][min] ([@fabaff])
|
||||
- Convert EntityComponent to be async ([@pvizeli], [@balloob])
|
||||
- Z-Wave: Add assocation service ([@turbokongen])
|
||||
- Z-Wave: Add association service ([@turbokongen])
|
||||
- Frontend - Services dev tool: persist state and tweak UI ([@justweb1])
|
||||
- Sensor: Support added for [scraping][scrape] websites ([@fabaff])
|
||||
- Clean up of tests ([@capellini])
|
||||
|
|
|
|||
|
|
@ -117,7 +117,7 @@ We are working on a better solution for 0.35.
|
|||
- Fix InfluxDB without authentication ([@balloob])
|
||||
- Fix Kodi without authentication ([@balloob])
|
||||
- Fix incorrect caching of /api/error_log ([@armills])
|
||||
- Fix incorrect ordering of service calls which could cause delays inbetween turning on multiple entities ([@balloob])
|
||||
- Fix incorrect ordering of service calls which could cause delays between turning on multiple entities ([@balloob])
|
||||
- Fix Nest Climate temperature issues ([@technicalpickles])
|
||||
|
||||
### {% linkable_title Release 0.34.5 - December 12 %}
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ og_image:
|
|||
|
||||
A year ago [Home Assistant 0.10][0.10] landed. Last weekend we released 0.35. Doing 25 releases in a year is a big accomplishment by the community and each release has moved us forwards leaps and bounds. In this year alone we have seen 2800 pull requests on the main repo alone, that's more than 7 a day!
|
||||
|
||||
One of the things that Jon Walker, the founder of the company I work for ([AppFolio]), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Everytime you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.
|
||||
One of the things that Jon Walker, the founder of the company I work for ([AppFolio]), has taught me is that the biggest advantage that you can create for yourself compared to your competitors is to release more often. Every time you release you are able to get the new features into the hands of the users and developers. The faster people start using it, the faster you get feedback on the good and bad parts and thus the faster can you evolve.
|
||||
|
||||
That's why I structured Home Assistant around a two week release cycle. It makes sure that features get out fast and it also forces us to not accumulate a backlog of things to document or test properly. Every two weeks we can start fresh. This makes it easy for new people to start contributing because it's clear when things go out and people are not afraid to miss a release.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Hello and Happy New Year!
|
|||
|
||||
I am not Paulus. My name is Ben. I'm the creator of the [BRUH Automation YouTube channel][bruh]. If you've ever seen any of my videos then you'll know I love home automation and Home Assistant.
|
||||
|
||||
I wanted to share some exciting stats from one of my latest projects - [Control My Christmas tree!](https://github.com/bruhautomation/BRUH-Christmas-Tree-2016) For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publically accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.
|
||||
I wanted to share some exciting stats from one of my latest projects - [Control My Christmas tree!](https://github.com/bruhautomation/BRUH-Christmas-Tree-2016) For this project, I created a Home Assistant instance on a Raspberry Pi 2 that was publicly accessible via DuckDNS. Paulus was great in helping me disable several of the developer services that could have been exploited to disable the Home Assistant instance.
|
||||
|
||||
I added three devices to the Home Assistant instance - a Wemo Insight, Sonoff Switch (running MQTT firmware), and a DIY MQTT Digital LED strip. After adding a few 3D printed Star War decorations, the tree was ready to go!
|
||||
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@ Thanks to [@konikvranik] the [HDMI CEC][cec] integration got a huge update with
|
|||
- Light - tellstick.py: Tellstick light fix ([@stefan-jonasson])
|
||||
- Switch - insteon_local.py: only check for devices when not defined in config ([@wardcraigj])
|
||||
- Notify - Twitter: Allow direct messaging to user ([@fabaff])
|
||||
- Fan - MQTT: Dont set a speed when fan turns on ([@robbiet480])
|
||||
- Fan - MQTT: Don't set a speed when fan turns on ([@robbiet480])
|
||||
- Config: Allow easier customization of whole domain, entity lists, globs ([@andrey-git])
|
||||
- Sensor - Homematic: Update device support ([@danielperna84])
|
||||
- Binary sensor - ISS: Add location to attributes and option to show position on the map ([@fabaff])
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ categories: How-To
|
|||
og_image: /images/blog/2017-02-babyphone/social.png
|
||||
---
|
||||
|
||||
One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assitant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.
|
||||
One of the hardest part of being a parent is keeping a constant eye on the baby to make sure that the baby is doing well. Thus, it is not surprising that baby monitors are one of the fastest growing baby product category. However, many of the baby monitors available on the market are rather dumb and expect the parents to keep looking at the video stream or listen to the audio. This how-to will help you create a smart baby monitor on a budget and integrate it with Home Assistant. Instead of relying on the poor quality baby monitor speakers, we use our existing speakers (eg. Sonos). We can also send notifications (with pictures) to avoid constant monitoring of the feed.
|
||||
|
||||
Obviously, you can use the setup as a general purpose surveillance system to monitor noise in the whole house.
|
||||
|
||||
|
|
|
|||
|
|
@ -180,7 +180,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
|
|||
- twilio component ([@happyleavesaoc])
|
||||
- Add Z-Wave battery level as a sensor. ([@andrey-git])
|
||||
- OwnTrack Async ([@pvizeli])
|
||||
- Fix possibility that have multible topic subscribe mqtt ([@pvizeli])
|
||||
- Fix possibility that have multiple topic subscribe mqtt ([@pvizeli])
|
||||
- Migrate mqtt tracker and arwn sensor to async / cleanup owntrack ([@pvizeli])
|
||||
- Z-Wave prevent I/O event loop ([@balloob])
|
||||
- Update pwaqi to 3.0 to use public API ([@valentinalexeev])
|
||||
|
|
@ -230,7 +230,7 @@ Hot fix release to fix dependency issues. More detailed information about the is
|
|||
- Allow configurable conditions for Pi-Hole sensor ([@colinodell])
|
||||
- Improved iCloud 2FA support. ([@reedriley])
|
||||
- Update pymyq requirement ([@arraylabs])
|
||||
- Not always asume manufacturername is present ([@balloob])
|
||||
- Not always assume manufacturername is present ([@balloob])
|
||||
- Add first pass at Z-Wave light tests ([@balloob])
|
||||
- Bugfix mqtt socket memory error ([@pvizeli])
|
||||
- Increase upper limit on light transitions ([@amelchio])
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ categories: How-To
|
|||
og_image: /images/blog/2017-03-bridge/social.png
|
||||
---
|
||||
|
||||
The idea of creating [HTTP to MQTT bridge](https://github.com/petkov/http_to_mqtt) appeared when I was trying to integrate Google Assistant with my Home Assistant after watching [BRUH Automation](https://youtu.be/087tQ7Ly7f4?t=265) video. Right now there is no MQTT service available in [IFTTT](https://ifttt.com/about). Existing integration solution uses [Maker Webhooks](https://ifttt.com/maker_webhooks) which requires that your Home Assistant instance is publically accessible, which I think brings some security concerns or simply not always possible to set up.
|
||||
The idea of creating [HTTP to MQTT bridge](https://github.com/petkov/http_to_mqtt) appeared when I was trying to integrate Google Assistant with my Home Assistant after watching [BRUH Automation](https://youtu.be/087tQ7Ly7f4?t=265) video. Right now there is no MQTT service available in [IFTTT](https://ifttt.com/about). Existing integration solution uses [Maker Webhooks](https://ifttt.com/maker_webhooks) which requires that your Home Assistant instance is publicly accessible, which I think brings some security concerns or simply not always possible to set up.
|
||||
|
||||
The HTTP to MQTT bridge should fill that gap. The idea is to receive messages using HTTP requests and transfer them to your MQTT broker, which can be contacted by Home Assistant. The HTTP to MQTT bridge is written using Node.js with [Express](https://expressjs.com/) for the server part and [MQTT.js](https://www.npmjs.com/package/mqtt) for the client.
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ categories: Community
|
|||
og_image: /images/blog/2017-04-award/social.png
|
||||
---
|
||||
|
||||
You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the [Thomas-Krenn-Award][award] put us on the 2nd place. This is an awesome achievment for an independent community project.
|
||||
You may already know from our social media channels and the release blog post for 0.41: We are now an award-winning Open source project. The jury of the [Thomas-Krenn-Award][award] put us on the 2nd place. This is an awesome achievement for an independent community project.
|
||||
|
||||
I would like to thanks all contributors. Your endless effort made this possible.
|
||||
|
||||
|
|
|
|||
|
|
@ -149,7 +149,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
|||
- Upgrade sendgrid to 4.0.0 ([@fabaff] - [#7038]) ([notify.sendgrid docs])
|
||||
- Missing line name restriction added (fixes #7039) ([@DavidMStraub] - [#7040]) ([sensor.mvglive docs])
|
||||
- Plug file leak on LIFX unregister ([@amelchio] - [#7031]) ([light.lifx docs])
|
||||
- Make core to look avilable state of device on servicecall ([@pvizeli] - [#7045])
|
||||
- Make core to look available state of device on servicecall ([@pvizeli] - [#7045])
|
||||
- Remove configuration sample ([@fabaff] - [#7048])
|
||||
- Bugfix wait on start event ([@pvizeli] - [#7013])
|
||||
- Bugfix slider ([@pvizeli] - [#7047]) ([input_slider docs])
|
||||
|
|
@ -212,7 +212,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
|||
- Value of 0 should not be considered `unknown`. ([@aequitas] - [#7139])
|
||||
- Upgrade netdisco ([@balloob] - [#7171])
|
||||
- Added new services to platform kodi ([@alexmogavero] - [#6426]) ([media_player docs]) ([media_player.kodi docs])
|
||||
- Supress trackback and upgrade PyMata to 2.14 ([@fabaff] - [#7176]) ([arduino docs])
|
||||
- Suppress trackback and upgrade PyMata to 2.14 ([@fabaff] - [#7176]) ([arduino docs])
|
||||
- Disable invalid-sequence-index ([@fabaff] - [#7177])
|
||||
- Upgrade mypy to 0.501 (was renamed from mypy-lang) ([@fabaff] - [#7117])
|
||||
- Add condition for API failure ([@sytone] - [#7181])
|
||||
|
|
|
|||
|
|
@ -147,7 +147,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
|
|||
- Use expected behvaior for above/below ([@armills] - [#7857]) (breaking change)
|
||||
- log time delay of domain setup in info level ([@azogue] - [#7808])
|
||||
- Optimize history_stats efficiency and database usage ([@bokub] - [#7858]) ([sensor.history_stats docs])
|
||||
- dont use default for switch name, so that the object id is used ([@abmantis] - [#7845]) ([switch.broadlink docs]) (breaking change)
|
||||
- don't use default for switch name, so that the object id is used ([@abmantis] - [#7845]) ([switch.broadlink docs]) (breaking change)
|
||||
- Disallow ambiguous color descriptors in the light.turn_on schema ([@amelchio] - [#7765]) (breaking change)
|
||||
- Make monkey patch work in Python 3.6 ([@balloob] - [#7848])
|
||||
- fix permissions issue for Insteon Local #6558 ([@wardcraigj] - [#7860]) ([insteon_local docs])
|
||||
|
|
|
|||
|
|
@ -73,7 +73,7 @@ Straight to 0.50.2. We released 0.50 as 0.50.1 due to an upload error to PyPi.
|
|||
- Fix TP-Link light brightness issue #8744. ([@gollo] - [#8755])
|
||||
- Fix typo in script error ([@n8henrie] - [#8754])
|
||||
- Fix tradfri error spam ([@MartinHjelmare] - [#8738]) ([light.tradfri docs])
|
||||
- Media Player - Pioneer: Supress exception if host is not available (fixes #8684) ([@fabaff] - [#8732]) ([media_player.pioneer docs])
|
||||
- Media Player - Pioneer: Suppress exception if host is not available (fixes #8684) ([@fabaff] - [#8732]) ([media_player.pioneer docs])
|
||||
- Telegram Bot: Retry set_webhook up to three times, reduce timeout to 5s again ([@azogue] - [#8716]) ([telegram_bot.webhooks docs])
|
||||
- Fixed sensor issue with Google Wifi routers in bridge mode ([@fronzbot] - [#8710]) ([sensor.google_wifi docs])
|
||||
- Fix alexa cards ([@balloob] - [#8708]) ([alexa docs])
|
||||
|
|
|
|||
|
|
@ -154,7 +154,7 @@ frontend:
|
|||
- Skip automatic events older than latest data ([@armills] - [#9230]) ([device_tracker.automatic docs])
|
||||
- title and message was swapped in pushbullet ([@danielhiversen] - [#9241]) ([notify.pushbullet docs])
|
||||
- Fix possible KeyError ([@MartinHjelmare] - [#9242]) ([mysensors docs])
|
||||
- WIP: Homematic improvments with new hass interfaces ([@pvizeli] - [#9058]) ([homematic docs]) ([binary_sensor.homematic docs]) ([climate.homematic docs]) ([cover.homematic docs]) ([light.homematic docs]) ([sensor.homematic docs]) ([switch.homematic docs]) (breaking change)
|
||||
- WIP: Homematic improvements with new hass interfaces ([@pvizeli] - [#9058]) ([homematic docs]) ([binary_sensor.homematic docs]) ([climate.homematic docs]) ([cover.homematic docs]) ([light.homematic docs]) ([sensor.homematic docs]) ([switch.homematic docs]) (breaking change)
|
||||
- Add available to sonos ([@pvizeli] - [#9243]) ([media_player.sonos docs])
|
||||
- Make sure Ring binary_sensor state will update only if device_id matches ([@tchellomello] - [#9247]) ([binary_sensor.ring docs])
|
||||
- Added configurable timeout for receiver HTTP requests | Additional AV… ([@scarface-4711] - [#9244]) ([media_player.denonavr docs])
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue