0.30 #3715
Merged
0.30 #3715
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sep 29 00:59:22 pi hass[21333]: if self.device.measurment_scale == 'F': Sep 29 00:59:22 pi hass[21333]: AttributeError: 'Device' object has no attribute 'measurment_scale'
Loopenergy library - bump to catch more exceptions in poll thread.
Signed-off-by: Hugo D. (jabesq) <jabesq@gmail.com>
* Add ability to change Nest mode to all available options * Make Nest state reflect current operation not current operation mode * Update Nest sensor to use operation mode * Fix linting * Revert "Make Nest state reflect current operation not current operation mode" This reverts commit 573ba02. Conflicts: homeassistant/components/climate/nest.py
…#3495) * Update Command classes and device types to Sigma SDK * Fix some pylint * Seperate constants to file * Flake8 * coverage and flake8 pylint * Add services.yaml * Service descriptions was missing * Spelling :) * grammar * Remove zwave service descriptions from main
* Add Digital Ocean implementation * Remove kernel
* Convert Entity.update_ha_state to be async * Make Service.call async * Update entity.py * Add Entity.async_update * Make automation zone trigger async * Fix linting * Reduce flakiness in hass.block_till_done * Make automation.numeric_state async * Make mqtt.subscribe async * Make automation.mqtt async * Make automation.time async * Make automation.sun async * Add async_track_point_in_utc_time * Make helpers.track_sunrise/set async * Add async_track_state_change * Make automation.state async * Clean up helpers/entity.py tests * Lint * Lint * Core.is_state and Core.is_state_attr are async friendly * Lint * Lint
* Added support for MySensors cover device * Fixed set_req not defined * Fixed V_PERCENTAGE is str * Removed set_cover_position The MySensors documentation doesn’t specify when sending a V_PERCENTAGE is allowed. * Fixed homeassistant/components/mysensors.py line too long * Fixed lint ATTR_POSITION imported but unused * Use V_PERCENTAGE for MySensors cover * Revert "Removed set_cover_position" This reverts commit d78cb3a. * Fix set_req, ATTR_POSITION not defined * Added support for non-exactly positionable covers * Fixed V_PERCENTAGE cast to bool * Ported MySensors cover back to v1.4 `V_PERCENTAGE` and `V_DIMMER` are aliases just like `V_STATUS` and `V_LIGHT`, so the code inside `MySensorsCover` doesn’t need to be updated. * Fixed v1.5 V_TYPES not in in v1.4 gateway SetReq
* Migrate to voluptuous * Adjust sensor.arest for new template system * Use items() to align the var section with the pins
* Monkey-patch a weakref set in Task to be a no-op. * Fix linting issues
* Skip RFXtrx tests unless RFXTRX=RUN * Remove my previous hacks to slightly speed up rfxtrx * Exclude RFXTRX tests from coverage * Remove unused import in rfxtrx tstt * Add close connection back to RFXtrx tests * Typo
|
@fabaff, thanks for your PR! By analyzing the history of the files in this pull request, we identified @balloob, @turb 10000 okongen and @pvizeli to be potential reviewers. |
balloobbot
reviewed
Oct 5, 2016
|
|
||
| @patch('homeassistant.components.device_tracker.owntracks.get_cipher', | ||
| mock_cipher) | ||
| def test_encrypted_payload(self): |
There was a problem hiding this comment.
- D102: Missing docstring in public method
balloobbot
reviewed
Oct 5, 2016
|
|
||
| @patch('homeassistant.components.device_tracker.owntracks.get_cipher', | ||
| mock_cipher) | ||
| def test_encrypted_payload_topic_key(self): |
There was a problem hiding this comment.
- D102: Missing docstring in public method
balloobbot
reviewed
Oct 5, 2016
|
|
||
| 6DB6 | @patch('homeassistant.components.device_tracker.owntracks.get_cipher', | |
| mock_cipher) | ||
| def test_encrypted_payload_no_key(self): |
There was a problem hiding this comment.
- D102: Missing docstring in public method
balloobbot
reviewed
Oct 5, 2016
|
|
||
| @patch('homeassistant.components.device_tracker.owntracks.get_cipher', | ||
| 9E12 | mock_cipher) | |
| def test_encrypted_payload_wrong_key(self): |
There was a problem hiding this comment.
- D102: Missing docstring in public method
balloobbot
reviewed
Oct 5, 2016
|
|
||
| @patch('homeassistant.components.device_tracker.owntracks.get_cipher', | ||
| mock_cipher) | ||
| def test_encrypted_payload_wrong_topic_key(self): |
There was a problem hiding this comment.
- D102: Missing docstring in public method
balloobbot
reviewed
Oct 5, 2016
|
|
||
| @patch('homeassistant.components.device_tracker.owntracks.get_cipher', | ||
| mock_cipher) | ||
| def test_encrypted_payload_no_topic_key(self): |
There was a problem hiding this comment.
- D102: Missing docstring in public method
* Rename Forecast.io platform to Dark Sky * Upgrade to python-forecastio to 1.3.5 * Update to reflect name change (Forecast.io -> Dark Sky) * Rename forecast to darksky
* remove unused exception * add logging * disable pylint broad-except * add exception handler * fix lint * update log output * change log message in async with exc_info * Add exc_info to asyncio exception handler
* Load yaml using validator, consider_home * timedelta, track_if_away * improve voluptuous * Add default back * Change time_period validation order
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 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, issue report, and suggestions 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.
To reduce the run-time of your tests, @balloob did a lot of tweaking. For now the RFXtrx tests are excluded which cut the needed time for running on your Pull Request in half.
Documentation
All configuration sample entries are now minimized. This should help to avoid problem for starters and newbies as they only get what's needed and not a full sample with all optional entries. If there is an issue with an entry in your
configuration.yamlfile the error message will provide you an URL that point to the documentation.As soon as the Hacktoberfest started there were a lot of incoming Pull Requests for the documentation. A huge "Thank you" to all participants. Especially, we would like to give a cookie to @hillaryfraley. She created around a dozen Pull Requests so far and didn't only fix typos but complete sections. The Hacktoberfest is still on-going and we are looking forward to get more Pull Requests.
Statistics
With the statistics sensor we would like to introduce a new sensor that is similar to the template sensor or the trend sensor. This sensor is consuming values from another sensor and is doing some statistical analysis of the data. Over a group of samples is the average/mean, the min/max, the total, the standard deviation, and the variance calculated which can be used in your automation rules. If the source is a binary sensor then the state changes are counted.
As the results are processed on-the-fly you still need to use the data from your database for a in-depth analysis of your stored information. Check the latest notebook for doing statistics with your Home Assistant database.
REST! We don't...
There was a lot of work done on our implementation which are working with RESTful APIs. @w1ll1am23 extended the aREST platforms to display if an aREST unit is available or not. The aREST is now covered by the configuration check as well. Please check the Breaking changes section for more details.
The REST sensor supports now HTTP authentication (basic and digest) and custom header. This will allow you to access resources which are protected. This sample sensor will access GitHub and retrieve the latest release number while by-passing the rate limit for non-authenticated requests.
Misc
All changes
known_device.yamlfile is now validated (@kellerza)Breaking changes
automationhave been removed (deprecated since May and have printed warnings to your console):use_trigger_valuesis gone. You have to copy your triggers to conditions and adjust for the correct config.condition_typeis gone. Usecondition: orinstead.condition:instead ofplatform:.- platform: forecastwith- platform: darksky.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.