-
-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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.87.0 #20794
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
Calling clear all is enough to turn off the light. Calling the color command makes the light no longer function until clear all is called again. The component calls clear all beforing turning it on which is why it works through home assistant. However if you try to control the light via the hyperion app or through kodi after it has been turned off via home assistant it will not function until you call clear all again.
* Embed zoneminder platforms into component * Add a binary sensor for ZoneMinder availability * Lint * Add missing docstrings
* Add JSON attribute topic to MQTT cover * Lint
* Log exceptions thrown by signal callbacks * Fix unsub * Simplify traceback print * Typing * Add test * lint * Review comments * Rework MQTT test case * Fix bad merge * Fix bad merge
Put myself (ehendrix23) as code owner for remote.harmony platform
* Add platform image_processing.qrcode * Update qrcode.py
* Bump aioesphomeapi to 1.4.2 * Update requirements_all.txt
* Use local_ip from config to discover IGD device In case of multi-homed server UPNP discovery finds IGD device on some "default" interface. WIth this modification discovery will be performed from 'local_ip'. * Update device.py * Changed version of async_upnp_client in requirements * Used aysnc_upnp_client==0.14.0 * Changed requirement to async_upnp_client==0.14.0.dev0 * Changed requirement to async_upnp_client==0.14.0.dev0 * Changed requirement to async_upnp_client==0.14.0.dev0 * Fixed code style * Fixed code style * Changed version of async_upnp_client in requerements * Changed version of async_upnp_client in requirements * Regenerated requirements (new async_upnp_client) * Regenerated requirements (new async_upnp_client) * Changed requirement to async_upnp_client=0.14.1 * Changed requirement to async_upnp_client=0.14.1 * Updated requirements * Updated requirements.txt * Corrected requirements * Corrected import of DeviceState * Constants changed according new async_upnp_client * Upgraded for async_upnp_client==0.14.2
* Added Search Configuration to IMAP Sensor The IMAP sensor currently only counts unread emails in a folder. By exposing the IMAP search parameter, the sensor can be used to count other results: - All emails in an inbox - Emails sent from an address - Emails matching a subject - Other advanced searches, especially with vendor-specific extensions. Gmail in particular supports X-GM-RAW, which lets you use any Gmail search directly ("emails with X label older than 14 days with", etc) For my use case, I just wanted total emails in a folder, to show an "X/Y" counter for total/unread. I started work on a one-off script to throw the data in, but figured I'd try to extend Home Assistant more directly, especially since this IMAP sensor correctly handles servers that push data. This is my first Home Assistant contribution, so apologies in advance if something is out of place! It's a pretty minimal modification. * Added Server Response Checking Looks like no library exception is thrown, so check for response text before parsing out results (previous code just counts spaces, so an error actually returns a state value of 4). * IMAP Warning -> Error, Count Initializes to None IMAP search response parsing throws an error instead of a warning. Email count initializes as None instead 0. Email count is untouched in case of failure to parse response (i.e. if server is temporarily down or throwing errors, or maybe due to user updating their authentication/login/etc). Fixed line length on error so it fits under 80 characters. * Fixed Indent on Logger Error Sorry about the churn! Python is pretty far from my daily-use language. (I did run this one through pep8, at least)
* Added relay ports to LCN lights platform * Exchanged validation for ports with uppercase validator. Makes interfacing with pypck enums much more simple. * Removed supported_features property as it is correctly inherited from parent * Removed type annotations.
* Add LCN switch platform * Added guard clause for discovery_info check and removed unnecessary parathesis
* Add binary sensor for Lutron RadioRA2 keypad buttons Allow automations to be triggered from RadioRA2 keypads by exposing each button as a binary sensor. * Remove binary sensor component; fire events directly instead. * Address comments from code review
* Added discovery_info check to LCN light platform * Removed whitespaces
* Bugfix cloud webhooks text response * address comments * Fix lint
* Fix the line reference in config error message * Fix platform config validation * Fix test * Handle error in error handling routine
* Keep auth token always valid * Remove unused refresh_auth message * Capture EndpointConnectionError * Lint
* use async_call_later for update * no need to timeout * fixes * move init tasks to hass.loop * version bump of tellduslive * fixes for @MartinHjelmare * fixes task cancel * don't return from new client
Update version of pymyq to 1.1.0; this version brings improved functionality, reducing errors for retrieving current state for the MyQ covers.
amelchio
approved these changes
Feb 6, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ship it!
fabaff
approved these changes
Feb 6, 2019
system_health: must be before frontend: in configuration.yaml: system_health: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
New Platforms
New Features
Breaking Changes
Beta Fixes
All changes