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
0.47 #8055
Merged
Merged
0.47 #8055
Conversation
This file contains 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
Do not fail in case no players are connected, in which case squeezeserver will return a result without player_loop.
* Fix #7758 subscription expiration/removal Removes a subscription after receiving an HTTP 410 response when trying to send a new message. * Fix tests failing due to additional call * Fix code style * Lint
* Added effects to Yeelight bulbs * Fix Typo and Use randint instead of randrange * Added Effects * updated requirements_all.txt * fix empty line * minor fixes * fix passing effects as parameter
* Support for renaming ZWave values * Improve test
This makes LIFX Gen3 lights work with the current firmware.
* Change to pypi * add requirements
* Added a Taps Aff binary sensor * PR Review updates * Added a Taps Aff binary sensor * PR Review updates * Improved error handling * Cosmetic changes (ordering, docstings, etc.)
* Manage Sesame devices through CANDY HOUSE's cloud API * Add dependency on new pysesame library
* Revert "Update to dsmr_parser supporting v5 arguments." This reverts commit 3567de4. * Revert "Using dev branch until released upstream." This reverts commit 53e8de1. * Revert "Give good example." This reverts commit 4f90fc4. * Revert "Allow configuring DSMR5 protocol." This reverts commit 9fa0e14.
Enabled by default in Chrome 60. Only accepts the param, doesn't act on the actual expiration date. Chrome will always pass NULL for now. w3c/push-api#248 https://www.chromestatus.com/feature/4929396687241216 https://bugs.chromium.org/p/chromium/issues/detail?id=718837
* etherscan sensor * Update etherscan.py
* blockchain sensor * Update blockchain.py * Update blockchain.py * add validation of btc addresses
* adding set position ability removing command_topic being required * flaking * flaking test * updating docs * requested updates * Revert "updating docs" This reverts commit 9cfc5ed. * forgot to update constructor calls in tests
* Add radarr.py * Update radarr.py * Update radarr.py * Add test_radarr.py * Update test_radarr.py * Update test_radarr.py * Update radarr.py * Update .coveragerc * Fix hound.
* Add service to set nest away/home modes * New service `nest.set_mode` * Update the NestDevice object to export the local structures * Validation and structure cleanup
* Added buienradar sensor and weather * used external library for parsing * used external library for parsing * updated buienradar lib to 0.4 * Make sure you import 3rd party libraries inside methods. * Make sure you import 3rd party libraries inside methods. * clean up code; optimized * imports, sensor name and attributes * updated requirements to match imports * use asyncio for http get
* Add support for Vanderbilt SPC alarm panels. * Arm/disarm + read state * Autodiscover and add motion sensors * Fix code formatting. * Use asyncio.async for Python < 3.4.4. * Fix for moved aiohttp exceptions. * Add docstrings. * Fix tests and add docstrings.
* Adding ssocr to docker to support Seven Segments Display * Adding cleanup
* Added host variable to Splunk.py and updated tox tests * Update splunk.py * Update splunk.py
) * Fixed the Wind sensor following new release of netatmo-api-python The NetAtmo PR was at: jabesq/netatmo-api-python#5 Essentially, this commit adds a protection when adding an incorrect monitored conditions to avoid to fail the entire NetAtmo component, plus for consistency reasons all conditions are now in lower case. * Fixes following the CI tests
* Adding support for https. This change allows to access a firetv-server instance that runs over https (via a reverse proxy for exemple). Default stays http, but if `ssl: true` is set in the configuration the connection goes over https. Successfully tested. * respecting the 79 characters line limit
* Added ONVIF camera component * added requirements * corrected long lines * fixed indenting * fixed indenting * removed bad whitespace * updated coveragerc * Added ONVIF camera component * added requirements * corrected long lines * fixed indenting * fixed indenting * removed bad whitespace * updated requirements * updated requirements * Added ONVIF camera component * added requirements * corrected long lines * fixed indenting * fixed pylink error indenting * Added ONVIF camera component * added requirements * corrected long lines * fixed indenting * fixed indenting * removed bad whitespace * updated requirements * fixed indenting * removed bad whitespace * updated requirements * fixed pylink error indenting * rebased and fixed requirements * Removed Debug logging * Added info logging to show URL being used. * corrected spacing * Tidied up and renamed input to host * fixed typo * corrected line lengths * added default to ffmpeg_arguments * removed unecessary ffmpeg arguements * changed to use .format instead of + * fixed indenting * cleanup & make it more readable
* Setup to send component data is option is enabled * testcases, as well as moved to a single boolean, passed to the function * fixed pep8 failures * Clarify config option.
* Use standard entity_ids for zwave entities * Include temporary opt-in for new entity ids * Update link to blog post * Update tests * Add old entity_id as state attribute * Expose ZWave value details * Update tests * Also show new_entity_id * Just can't win with this one
@balloob maybe include language that aggregate component data will be public? |
* Bugfix entity attribute setter * Fix tests * Fix tests part 2 * Change filter only None * Fix tests part 3 * Update entity.py * Fix tests
* Added 'all_plants' group and support for plant groups state. * Reversed the group states.
* Fix EntityComponent handle entities without a name * Implement solution by Anders
…tter accommodate login failures with wrapper in pyunifi 2.13. (#7899) * Pyunifi update * Update pyunifi_test * Import API Error * Adjust test_unifi.py to import APIError * Remove urllib import * Remove urllib import from test * Try fix mock * Remove automations.yaml * Lint
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.
In this release a ton of new stuff! And who doesn't like new stuff? This release we're passing the 700 integrations for Home Assistant. As of today [we're 1369 days old][first-commit], which means that roughly every two days a new integration gets added!
Python Scripts
The biggest change is a new type of script component: Python scripts. This new component will allow you to write scripts to manipulate Home Assistant: call services, set states and fire events. Each Python script is made available as a service. Head over to the docs to see how to get started.
Updater
The updater has received a new opt-in option to let us know which components you use. This will allow us to focus development efforts on the components that are popular.
And as a reminder. We will never share gathered data in a manner that can be used to identify anyone. We do plan on making aggregate data public soon. This will include total number of users and which hardware/software platform people use to run Home Assistant.
Z-Wave
Z-Wave is also getting a big update in this release. The confusing entity_ids will be on their way out. There is a zwave blog post that gives more detail, but the upgrade steps will be as follows:
new_entity_ids: true
to your zwave config.New platforms
Breaking changes
lifx_effect_breathe
call has been deprecated. Uselifx_effect_pulse
with the newmode: breathe
attribute instead. (@amelchio - #8016) (light.lifx docs) (breaking change)EVENT_SCENE_ACTIVATED
andEVENT_NODE_EVENT
will no longer supply anobject_id
. They will now be tied to the node entity_id. (@armills - #7786) (zwave docs) (light.zwave docs) (breaking change)All changes
last_name
field optional (@azogue - #7988) (telegram_bot.init docs)