-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
0.26 #2760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
Try to deflake discovery tests
* Allow multiple proximities * Distance conversion * Add unit of measurement and conversion to proximity * Shorten attribute name * Fix get unit of measurement * Fix the km <-> m conversion * Add type check and errors * first path unit test around distance utility * Fix numeric type check * Fix conversion type-os * Actually set the exception thrown flag * Test for exact conversion * More descriptive variable names * Update method invocation to match change in method name * Missed a couple variables * Line continuation * Fix linting too many return issue * Break out proximity setup for list of proximity and for single proximity device * Pass hass to setup function * Check if setup succeeded for each proximity component * Change variable name * Break out branches in convert to avoid too many branches linting error * Remove disable lint line * Variables for default properties * Combine logic * Test loading multiple proximities for 100% code coverage on proximity component * Unit test to reach 100% Fail to configure proximities missing devices * Fail first before processing * Combine return statements * lstrip = bad Teagan * Utilize string formating instead of concatenation * Fix variable reference * Typeo * Clean up conversion to reduce complexity * Update unit tests to match code changes on distance util * Test non numeric value * Private methods, value type has already been checked.
...because I was bored
...because I was still bored
...because I was somehow still bored
Was so bored I forgot some things :(
...because I was almost done being bored
* Add docker test runner * Move test Dockerfile into virtualization folder * Don't build zwave in test environment
* Recorder typing & wait on DB ready
* Added mired and kelvin mode to flux * changed as requested * Renamed varible * attempt to add test for new method in flux.py * removed line to fix lint error
Instead of always assuming we want to change the heat, instead use the setback attribute which sets heat / cool setback based on current HVAC mode. This means that the proliphix thermostat will do sensible things during cooling season.
* Add support for new mqtt_json light platform. * Fix W503 errors. * Bring in feedback from @balloob. * Add test coverage for invalid color and brightness data. * Add coverage for transition in turn_off.
* fast.com speedtest sensor * update for fastdotcom
* Update remote unit tests * Sleep again
* Update link to docs * Use fast.com * Update docstring * Add link to docs * Add link to docs * Update docstrings * Update docstrings * Fix typo
update rfxtrx lib
update rfxtrx lib
Fix minor bug in flux led
improve logging from rfxtrx component
improve logging from rfxtrx component
Conflicts: homeassistant/components/recorder/__init__.py homeassistant/const.py requirements_all.txt setup.py
* Fix for braviatv get mac regex none case * E128 fix
* Add support for GPSD * Add gpsd.py * Check if socket is open * Fix pylint issue * Rename file to be a sensor * Update for being a sensor * Rework for being a sensor
* Add CORS fixes to support OPTIONS preflight requests. * Add CORS tests * Fix formatting
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.
It's time for 0.26 and it's again full of new features and fixes. First I want to highlight that we are now having 500 000 monthly pageviews on the website. A big milestone for us! It's been an amazing journey. Big thanks to the Home Assistant community for being such a delightful bunch.
This release includes code contributed by 31 different people. The biggest change in this release is a new unit system. Instead of picking Celsius or Fahrenheit you'll have to pick imperial or metric now. This influences the units for your temperature, distance, weight. This will simplify any platform or component that needs to know this information. Big thanks to @Teagan42 for her hard work on this!
Breaking changes