0.62#11921
Merged
Merged
Conversation
This relates to issue #11556
* fix arming away cmd for concord232 client * bump required version of concord232 to 0.15
* Initial overwrites * Add check_config function. * Update hassio.py * Address comments * add hassio support * add more tests * revert core changes * Address check_config * Address comment with api_bool * Bugfix check_config * Update core.py * Update test_core.py * Update config.py * Update hassio.py * Update config.py * Update test_config.py
* add working stop command This fixes the stop command for 2 types of roller shutters * fix line too long * fix indentation * fix indentation
* Added snips.say and snips.say_action services * Added snips.say and snips.say_action services * Merged services.yaml changes I missed * added tests for new service configs * Woof * Woof Woof * Changed attribute names to follow hass standards. * updated test_snips with new attribute names
* Simplified push calls * Cleaned up and added unittests * Fixed email parameter * Fixed email parameter
* rfxtrx clean up * rfxtrx clean up * rfxtrx clean up
* upgrade xiaomi lib * xiaomi lib
* Adding support for Lutron Radio RA2 shades as cover components. * Adding initial version of the Lutron shades component. * Fixed line-length violation detected by Hound.
* Use kelvin/mireds correctly for setting iglo white * Update requirements_all.txt * Fix line lengths
* Hyperion: Add brightness, HDMI and effect support - added brightness support to dim the hyperion light - changed the "OFF" command to set the color to [0,0,0] after clearing all priorities. This is neccesary to keep the light turned off when an HDMI grabber is used for ambilight with hyperion. - added HDMI ambilight mode recognition and control. by setting the "hdmi_priority" in your "configuration.yaml" file (defaults to 880), home assistant will now be able to recognize when the hyperion light is in HDMI ambilight mode and will change its icon to an HDMI symbol and set the status to ON. Switching the hyperion light to HDMI ambilight mode can be done through the effect option (clears all priorities such that the HDMI grabber remains). - added effect support for the default effects of hyperion, a custom list can be defined in the "configuration.yaml" file by using the "effect_list" option. * Hyperion: Add brightness, HDMI and effect support - added brightness support to dim the hyperion light - changed the "OFF" command to set the color to [0,0,0] after clearing all priorities. This is neccesary to keep the light turned off when an HDMI grabber is used for ambilight with hyperion. - added HDMI ambilight mode recognition and control. by setting the "hdmi_priority" in your "configuration.yaml" file (defaults to 880), home assistant will now be able to recognize when the hyperion light is in HDMI ambilight mode and will change its icon to an HDMI symbol and set the status to ON. Switching the hyperion light to HDMI ambilight mode can be done through the effect option (clears all priorities such that the HDMI grabber remains). - added effect support for the default effects of hyperion, a custom list can be defined in the "configuration.yaml" file by using the "effect_list" option. - fixed some style issues with too long lines * Hyperion: Add brightness, HDMI and effect support - fixed some more indentation style issues * Hyperion: Add brightness, HDMI and effect support - yet more fixed visuel indent issues * Hyperion: Add brightness, HDMI and effect support - more visuel indents * Hyperion: Add brightness, HDMI and effect support - fixed invalid variable "A" * Hyperion: Add brightness, HDMI and effect support - remove unnececary brackets - specify specific exceptions * correct changing state holding attributes during a service method Proccesed the comments of @MartinHjelmare: #11543 (review) * indent correction corrected tab instead of 4 spaces * Hyperion: Add brightness, HDMI and effect support - changed 'none' to None - renamed "self._skip_check" to "self._skip_update" * Add brightness, HDMI and effect support changed checking if a list is empty from "list == []" to "not list"
* Strip off the RTS/IO ID from the entity ID * Ignore exception thrown when the device does not provide an active state * Send actions with a label for easier identification in the Tahoma log * Linting * Strip off the RTS/IO ID from the entity ID, take 2 As per suggestions, let HA do the standard initialization and assign an appropriate entity_id, instead of overriding it with the lengthy unique_id coming from the TaHoma devices.
* Add templates * Make pylint happy
* Add support for Zigbee green power devices such as the Hue Tap * Clarify that imported SWITCH is a DECONZ_REMOTE
* Add ability to specify a sender in the clicksend notification * Style fixes * Fix remaining issue * Add sender validation
Temperature detection range: -20 - 60 Deg.C ( + / - 0.3 Deg.C ) Humidity detection range: 0 - 100pct RH ( + / - 0.3pct ) Atmospheric pressure detection range: 30 - 110KPa ( + / - 120Pa )
* New venstar climate component * Corrected items raised during the PR process. * Corrected flak8 issues. * Add support for venstar models without humidity control. * Changed the idle operation mode to off. Few other adjustments. * Minor changes (log messages, sorting, etc.)
* worked on first version of IOTA wallet * added sensor for IRI node * added requirements * ignored new component in test coverage * changed length of line * fixed linter issues * changed requested changes * moved attributes of IRI node * change coverage definitions * changed loading of platforms * changed loading of platforms * changed initial state of wallet sensor * changed handling of config * changed attribute handling for IOTA node sensor * Follow the component style * Fix ordering and docstring * Fix pylint issue
* Improve foscam library exception support Catches foscam exceptions that otherwise pollute the log. Many of these exception can safely be ignored * Fixed line length Fixed line length * Changed exception and log handling changed logging and catched only the TypeError effecting the library * Removed unused var Removed var * Fix remaining issue
* Added Xeoma camera platform * Switch to dict.get() for optional config values with no default * Minor changes
* Multi-Room Support for Greenwave Reality * PEP8 Line Too Long * Update requirements_all.txt * Shared State Object Shared State Object added, and implemented new function of greenwavereality to abstract complex runtimes. * Update requirements_all.txt * Lint issues * Rewrite method to not trigger "Method could be a function" * Remove unnecessary arguments for update call
* Send Alexa Smart Home responses to debug log
* Report scripts and groups as scenes to Alexa
The Alexa API docs have a couple display categories that sound relevant
to scenes or scripts:
ACTIVITY_TRIGGER: Describes a combination of devices set to a
specific state, when the state change must occur in a specific
order. For example, a “watch Neflix” scene might require the: 1. TV
to be powered on & 2. Input set to HDMI1.
SCENE_TRIGGER: Describes a combination of devices set to a specific
state, when the order of the state change is not important. For
example a bedtime scene might include turning off lights and
lowering the thermostat, but the order is unimportant.
Additionally, Alexa has a notion of scenes that support deactivation.
This is a natural fit for groups, and scripts with delays which can be
cancelled.
https://developer.amazon.com/docs/device-apis/alexa-discovery.html#display-categories
The mechanism to map entities to the Alexa Discovery response is
refactored since extending the data structures in MAPPING_COMPONENT to
implement supportsDeactivation would have added complication to what I
already found to be a confusing construct.
* upgrade python-etherscan-api * add support for erc20 tokens
…1075) * Allow separate command and state OIDs and payloads in SNMP switch Follow PEP8 style properly More PEP8 style fixes Fully PEP8 compliant * Fix pylint errors * Remove comment to satisfy pylint * Style changes/refactoring
balloob
requested review from
a team,
Danielhiversen,
andrey-git,
emlove and
rytilahti
as code owners
Contributor
|
I think #11802 should probably also be included? That one was probably missed because it still has the 0.61.2 milestone set… Edit: Cleared the milestone. I didn't dare to set the 0.62 milestone because I wasn't sure if this makes your release script go boom. ;) |
Member
Author
|
It's already included because it was part of the dev branch when I cut the release. It wasn't included in the milestone because it had a different milestone tagged. Should be included next time we generate the changelog. |
* Add API to write error log * Move write_error api to system_log.write service call * Restore empty line
* Allow setting climate devices to AUTO mode via Google Assistant * Remove cast to lower * Clarify const name
…11925) * Fixed rfxtrx binary_sensor KeyError on missing optional device_class * Fixed rfxtrx binary_sensor KeyError on missing optional device_class
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
20 participants
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
Breaking Changes
EntityComponent.add_entity(entity)andEntityComponent.async_add_entity(entity)have been removed. UseEntityComponent.add_entities([entity])andEntityComponent.async_add_entities([entity])instead. (@balloob - #11691) (breaking change)All changes