0.50 #8685
0.50 #8685
Conversation
* Use pip install --user if venv not active * Set PYTHONUSERBASE to deps directory, when installing with --user option. * Reset --prefix option to workaround incompatability when installing with --user option. This requires pip version 8.0.0 or greater. * Require pip version 8.0.3. * Do not delete deps directory on home assistant upgrade. * Fix local lib mount and check package exist. * Update and add tests * Fix upgrade from before version 0.46 * Extract function to get user site * Add function(s) to package util to get user site. * Use async subprocess for one of the functions to get user site. * Add function to package util to check if virtual environment is active. * Add and update tests. * Update version for last removal of deps dir * Address comments * Rewrite package util tests with pytest * Rewrite all existing unittest class based tests for package util as test functions, and capitalize pytest fixtures. * Add test for installing with target inside venv.
* Make aiolifx modules easily available * Use aiolifx features_map for deciding bulb features Also move the feature detection out of Light so it is available even during the initial detection. * Move each LIFX light type to a separate class * Simplify AwaitAioLIFX This has become possible with recent aiolifx that calls the callback even when a message is lost. Now the wrapper can be used also before a Light is added though the register callback then has to become a coroutine. * Refactor send_color * Add support for multizone This lets lifx_set_state work on individual zones. Also update to aiolifx_effects 0.1.1 that restores the state for individual zones.
* Make it available during state paused. * Don't adjust for media_position_updated_at. I.e. do as vlc, sonos etc so that returned position is the position at the time of media_position_updated_at, not now.
* Remove km from visibility, add visibility_distance * Fix line length * Fix trailing space and line break indentation * Indentation * More whitespace
* Import and use the function from pip instead of defining it ourselves. * Fix tests.
* Bump to KNXIP 0.5 * Updated requirements file
* Add components concept * Lint * Raise ImportError if component not found
* Add bind_hass to components * Add bind_hass to group
* Rewrite persistent notification creation * Update components.is_on to use auto loading * Fix two hass parameters
* Added additional attributes to OwnTracks device_tracker * Added missing space after :
* Update dlib_face_detect.py * fix lint * Update dlib_face_detect.py
…hts; double quotes in log msgs (#8524)
* Remove deprecated automation keywords * Remove retired test case * Remove retired keyword
* Return a 0 temperature value when none is found It's well documented that these TRVs will only return the current temperature for a short time after the actuator has moved. This means that, usually, they will not return the current temperature. Setting a non-value here causes errors in the logs and for the TRV to not show on the dashboard at all * Fix lint issue
* Update zwave.py to work with updated OpenZwave library Update zwave.py to work with updated OpenZwave library * Update zwave.py * Update zwave.py * Update to fix garage door openers Update to fix garage door support for latest version of openzwavelib * Update to cover.zwave list of states Update to cover.zwave to provide list of states based on dev version of openzwave lib * Some values not saved * Formatting fix * Formatting fix * Variable typo * Formatting fix * Formatting * Variable Update Variable Update and properties added * Formatting fixes * Formatting Fix * Update test case for door states * Formatting / Testing process fix * Formatting * Formatting / Test Fixes * Variable rename * Added members to CoverDevice * Removed un-needed else * Formatting * Formatting * Variable name changes and const updates * Changed variable names to cover_state * Added constains into const.py * Updated to change the main state on the cover device * Fixes * Formatting fixes * Formatting/Variables * Formatting * Variable fixes * Import update * Formatting / Variables * Update test for new states * Revert state changes * Test fix * Variable Fix * Formatting * Variable typo * Missing constant * Variable fix * Requested changes * Added is_opening * Added is_closing * Updated test based on changes * Formatting * Changed cover_state back to _state * Formatting and variable fixes * Test fixes * Formatting and variable touchup * Formatting * Optimizations * Add new cover features to demo * Add tests for demo cover closing/opening * Remove unused STATE_STOPPED * Add tests for new zwave cover values
|
@balloob, thanks for your PR! By analyzing the history of the files in this pull request, we identified @capellini, @fabaff and @postlund to be potential reviewers. |
|
Would it be possible to include home-assistant/frontend/pull/358 in 0.50? (Would require another frontend update) |
|
@balloob Not sure what the process is to get things added to the release info, but figured I would make some requests here. Can the information from #8208 be added basically the part about Also can #8607 get added to the release? With a note that users can enable local control but it is still experimental? Local control is disabled by default. I will try to get the documentation PR opened for local control today. |
|
i think #8632 is a huge improvement and should be mentioned explicitly. it makes the History Statistics Sensor usable — finaly! for the first time i can use serveral of these sensors, without blocking HA startup for minutes with SQL queries. |
|
@w1ll1am23 you can add PRs to a milestone. I've added your PR to the milestone and will make sure to cherry-pick it before the release. |
|
@diplix done! |
|
@w1ll1am23 make sure you add those labels when you create a PR and it will be categorized automatically. |
|
@balloob Thanks, I'll make sure to do that next time. Sorry for the trouble. |
|
No trouble, I'm glad you're paying attention to this PR so we caught it in time. Generating this list is all automated, so that's why labels matter: https://github.com/home-assistant/hass-release |
* Shopping List: edit name / complete status * Change ID to be UUID based
* Support for Wink local control
|
Z-Wave Barrier Command Class Breaking Change: |
Last Wednesday we released Hass.io, an operating system to take care of all the updating hassles that come with running home automation at home and so much more. This is a major milestone for Home Assistant as it is our first step to offering a fully integrated solution using a bring your own hardware approach.
The launch has been crazy successful. The 20 minute introduction video by BRUHAutomation already has 12.5k views in just 4 days with no less than 150 comments.
Hass.io will be a great foundation for bigger and better integrated features. Stay tuned.
Adding the power of voice to integrations
This release has completely revamped the way how we deal with voice integrations. We turned Home Assistant into a platform to write voice apps, no matter where the processing of the voice happens. This can be done by Alexa, Google Assistant or in the Home Assistant user interface.
We are super excited about the new functionality and hope that it will trigger a new type of applications and systems to be built on top of Home Assistant. To demo all this new functionality, we've included a new shopping list component. As a user you can add any item to the shopping list with your voice and also ask what is on your shopping list.
To make testing these applications easier, we've updated the conversation component. The component will now allow sentences to be configured that hook directly into the new voice functionality. Combined with the new interface it will allow for some great interactions!
https://www.youtube.com/watch?v=Ij0zDF3qwmE
History improvements
@OverloadUT has been recently spending a lot of time on optimizing the history database queries. This release includes PR #8632, the first in a list of improvements that he is working on. This PR greatly improves requests for single entities by using an optimized query for this use case.
The performance change in some of his tests shows this change to be about 300x faster (30 seconds to 0.1 seconds!) (There is no theoretical upper limit due to the issue with multi-entity queries getting worse the longer the current recorder run has been going.)
Xiaomi integration
Yes, it has happened! After being in beta for a while, the Xiaomi support is now available to all. @danielhiversen did an amazing job and we now support sensors, switches, lights and covers.
Velbus integration
Another awesome integration is that of the Velbus home automation system which has been contributed by @thomasdelaet. It integrates their sensors, covers, fans, lights and switches.
New Platforms
Breaking Changes
stateand the time trigger keywordafterwere deprecated in 0.46. They have now been removed. (@amelchio - #8510) (automation.state docs) (automation.time docs) (breaking change)access_tokenin the config. Use the new OAuth authentication or add your username and password to the config. (@w1ll1am23 - #8208) (wink docs) (breaking change)intent_script. Conversation now allows configuring sentences to map to intents. (@balloob - #8434) (alexa docs) (intent docs) (intent_script docs)(shopping_list docs) (snips docs) (breaking change) (new-platform)
All changes