-
-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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.86.0 #20354
Conversation
* added support for homekit security systems * fixed linting issues * fixed indentation issues * simplifired logic on homekit_controller alarm controller panel * cleaned up battery level const on homekit controller alarm control panel
* Fix some ESPHome race conditions * Remove debug * Update requirements_all.txt * 🚑 Fix IDE line length settings
* Bugfixes for connection issues
Thank you 👍 * added zwave lock state from alarm type workaround * fixed test indents * more linting fixes * one more linting fix * simplified logic * fixed lint new lines * fixed merge conflict issue * fixed definition of _alarm_type_workaround in zwave lock
* ESPHome discovery * Add note about netdisco * 🔡 * Address comments * Bump netdisco to 2.3.0 * Update requirements_all.txt
* mv component folder * moved in airquality * changed names in files * renamed test init * renamed test air quality * renamed in tests * renamed coverage * fixed naming * corrected attr names * changed attr names
* Update version to 0.10.1 * Update of requirements files
…gistry (#19462) * Refactor mqtt-vacuum in preparation for discovery and device registry
* add discoverability to mqtt-vacuum
* add device registry to mqtt-vacuum
…gs (#19792) * This makes the vasttrafik platform stop spamming the logs with warrnings * Forcing build
* Bump pybotvac to support No Go lines * Update requirements
* Cleanup if discovered mqtt switch can't be added
…0263) * Should require the 'GATTOOL' setup extras which includes pexpect. * Also fix skybeacon's requirement and requirements_all.
* Update google_maps.py There are known bug in locationsharinglib version 3.0.9, the developer has fixed this in 3.0.11. (costastf/locationsharinglib#42) * Update requirements_all.txt
Breaking change for sensor.sma: The SMA sensor can monitor several new sensors. Unfortunately some of the existing sensors were renamed: |
Emulated Roku should be called out as a new component as well. |
If still possible to make the change. The breaking change
Should be updated to
|
@balloob I would suggest that #19664 together with Frontend PR home-assistant/frontend#2389 & home-assistant/frontend#2421 are a large enough that the #19664 feature should relly be mentioned under "New Platforms" for this release. Great if could blog about #19664 together with Frontend PR home-assistant/frontend#2389 & home-assistant/frontend#2421 for home-assistant-polymer. Those changes really make Zigbee become a first-class native citizen in Home Assistant, (similar to Z-Wave now). Zigpy also supports new radio hardware which makes Zigbee even more accessible. PS: Please also see related request for a dedicated "Zigbee" sub-forum for the community https://community.home-assistant.io/t/suggestion-zigbee-sub-forum-equivalent-to-the-z-wave-subforum-here/74844 |
New Platforms
Breaking Changes
current_power
is nowgrid_power
andgrid_voltage
is nowvoltage_l1
(the voltage from all three phases are available). The sensors also support the entity registry, making editing their names a breeze from the frontend. (@kellerza - #19753) (sensor.sma docs)Beta Fixes
All changes