-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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.61 #11589
Merged
Merged
0.61 #11589
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
* Cleanup logic & New gen of HomeMatic * fix lint * cleanup * fix coverage * cleanup * name consistenc * fix lint * Rename ip * cleanup wrong property * fix bug * handle callback better * fix lint * Running now
* Final touch for cloud component * Fix test
An error was being log that seems more like debug info
* Fix X10 commands for mochad light turn on This commit attempts to address issues that a lot of people are having with the x10 light component. Originally this was written to use the xdim (extended dim) X10 command. However, not every X10 dimmer device supports the xdim command. Additionally, it turns out the number of dim/brighness levels the X10 device supports is device specific and there is no way to detect this (given the mostly 1 way nature of X10) To address these issues, this commit removes the usage of xdim and instead relies on using the 'on' command and the 'dim' command. This should work on all x10 light devices. In an attempt to address the different dim/brightness levels supported by different devices this commit also adds a new optional config value, 'brightness_levels', to specify if it's either 32, 64, or 256. By default 32 levels are used as this is the normal case and what is documented by mochad. Fixes #8943 * make code more readable * fix style * fix lint * fix tests
* convert alarmdecoder interface from async to sync * Convert he rest of alarmdecoder rom async to sync * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py * Update alarmdecoder.py
#10699) * Add unittest for yahoo weather component. * Add requitements for tests. * Update requirements. * Revert "Update requirements." This reverts commit 024b5cf. * Update requirements. * Randomize sample data. * Remove unnecessary methods. * Remove dependency and replace with MockDependency. * Add temporary fix for yahoo weather API issue.
With #11538 I forgot to add another type of Roller shutters that should be supported.
* Added support for enable/disable motion detection * Changed name of variable for exception, lint error * Moved motion_detection_enabled property to the other properties
can you also add the pushsafer pullrequest! Thanks Kevin |
This relates to issue #11556
* 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
* Simplified push calls * Cleaned up and added unittests * Fixed email parameter * Fixed email parameter
* 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
* fix arming away cmd for concord232 client * bump required version of concord232 to 0.15
* rfxtrx clean up * rfxtrx clean up * rfxtrx clean up
* upgrade xiaomi lib * xiaomi lib
* Use kelvin/mireds correctly for setting iglo white * Update requirements_all.txt * Fix line lengths
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.
Almost a 100 contributors to this release 🎉 That's what you get when you skip a release. It's a little late but "Happy New Year" and welcome to 0.61 the first release 2018.
This release contain some breaking changes. Please make sure that you check the section below if you are running into trouble.
There is not much more to tell and I don't want to make something up.
New Platforms
If you need help...
...don't hesitate to use our very active forums or join us for a little chat. The release notes have comments enabled but it's preferred if you use the former communication channels. Thanks.
Reporting Issues
Experiencing issues introduced by this release? Please report them in our issue tracker. Make sure to fill in all fields of the issue template.
Breaking Changes
Extend Threshold binary sensor to support ranges. This means that you can now set
up
andlower
. (@DanNixon - #11110) (binary_sensor.threshold docs) (breaking change)The Steam game platform contains changes:
game
attribute no longer set indevice_state_attributes
if no game is currently being played as the string "None" is no longer passed if no current game is being played, instead thegame
attribute is not present.(@frwickst - #11182) (sensor.steam_online docs) (breaking change)
The
tile
platform now shows only active Tiles by default; to show all Tiles, including expired/inactive ones,show_inactive
must beTrue
. The following state attributes have been removed:last_seen
andlast_updated
. (@bachya - #11172) (device_tracker.tile docs) (breaking change)The
hidden_string
feature has been removed from the isy994 component. Previously, this allowed entities to be "hidden" in Home Assistant if a configured string was present in an ISY device's name or folder path. This was removed because hiding devices is now done via the customization feature.Note however, that this feature was replaced by a new ignore_string config option, which will now cause Home Assistant to completely ignore devices with the matching string so that they will not be imported as a Home Assistant device at all. This can be helpful if you have nodes in the ISY that aren't useful at all in Hass (IR transmitter nodes are a good example.) (@OverloadUT - #11243) (isy994 docs) (binary_sensor.isy994 docs) (cover.isy994 docs) (fan.isy994 docs) (light.isy994 docs) (lock.isy994 docs) (sensor.isy994 docs) (switch.isy994 docs) (breaking change)
The
egardia
alarm panel platform no longer a need the users to run a separate Egardiaserver component. It can now also run on HASS.io. (@jeroenterheerdt - #11344) (alarm_control_panel.egardia docs) (breaking change)The binary sensor platform of the DoorBird integration has been deleted, so remove DoorBird from your
binary_sensor
configuration. Instead, set thedoorbell_events
option of thedoorbird
component toTrue
. Thelast_visitor
option has been removed from the camera component, as it is now always added as an entity. (@Klikini - #11193) (camera.doorbird docs) (breaking change)The following attributes of the TP-Link switch and light platform have been renamed:
current_consumption
->current_power_w
,daily_consumption
->daily_energy_kwh
andmonthly_consumption
->monthly_energy_kwh
current
->current_a
,current_consumption
->current_power_w
,total_consumption
->total_energy_kwh
anddaily_consumption
->today_energy_kwh
(@DanNixon - #10979) (light.tplink docs) (switch.tplink docs) (breaking change)Move IMAP Email Content body to an attribute (@notoriousbdg - #11096) (sensor.imap_email_content docs) (breaking change)
Automations which were using
state
that was returningtarget_temperature
of thenetatmo
climate platform needs an update. (@ciotlosm - #11345) (climate.netatmo docs) (breaking change)The default availability payloads for the
MQTT
switch platform have changed from "ON" and "OFF" to "online" and "offline" (in order to match the majority of MQTT platforms that already supported availability reporting). (@DanNixon - #11336) (breaking change)Customizations for how entities are exposed to Alexa are no longer set via
customize
. Instead they are set via the configuration of the cloud component:(@balloob - #11461) (cloud docs) (alexa.smart_home docs) (breaking change)
The extension of the
alpha_vantage
requires an update of the configuration as now are exchange data available as well. (@ChristianKuehnel - #11427) (sensor.alpha_vantage docs) (breaking change)The
prometheus
component now supports pushing all sensors and fixes wrong metrics. If may require that you update your configuration. (@michaelkuty - #11159) (prometheus docs) (breaking change)Insteon local devices will now use their address as the
entity_id
andname
. The friendly name can be customized using the standard customization configuration. (@camrun91 - #11088) (insteon_local docs) (fan.insteon_local docs) (light.insteon_local docs) (switch.insteon_local docs) (breaking change)Google Assistant is no longer configured via
customize
but instead has its configuration under thegoogle_assistant
entry in yourconfiguration.yaml
. The attributes will no longer have to be prefixed withgoogle_assistant_
either.Before:
After:
(@balloob - #11499) (cloud docs) (google_assistant docs) (breaking change)
climate.set_aux_heat
service is no longer available for the Sensibo cliamte platform. Now callclimate.turn_on
orclimate.turn_off
. (@andrey-git - #11579) (climate.sensibo docs) (breaking change)All changes