Blog
Using Fedora Atomic with Home Assistant
The Hackerspace Eastermundigen
Updated release schedule
So this weekend we’re going to shake things a little up. Instead of releasing a new version today, we’ve released a beta version of the new version: 0.66.0.beta0. After a week of being in beta, the version will be promoted to be the new stable release. While the beta is live, we will accept contributions on the dev branch for the next version as usual.
Diagram of the new release schedule
The goal is to create a more stable first release without the need for a quick follow up hot fix. So if you want to be able to access the new features faster but don’t mind the risk of running into the occasional bug, get yourself on the beta channel today:
- Hass.io users will be able to enable the dev channel in the system settings.
- For Docker users, the beta’s will be published under the
rc
tag. - Beta’s are also published to PyPi. Because it is a beta release, it will not be installed by Pip unless explictely specified in the install command:
pip3 install --pre --upgrade homeassistant
.
The documentation for the beta version can be found at https://rc.home-assistant.io/.
If you find issues with either the code or the docs of the pre-release, please open an issue in the appropriate place or, even better, submit a pull request to fix it.
0.65: Rename entities, new filter sensor, UpCloud and Channels
Release 0.65 has arrived and oh boy, is it awesome. First off, in case you have missed the previous release notes and announcements: Starting with this release, Home Assistant has dropped support for Python 3.4. The minimum supported version is now Python 3.5.3. If you are on Hass.io or Docker, you’ll automatically be running the latest and greatest. If you’re on an older Hassbian installation or did your own Linux setup you’ll need to upgrade to at least Python 3.5.3.
Naming entities
With the introduction of the entity registry in 0.63, Home Assistant is making sure that the same devices always receive the same entity IDs. This release is taking it a step further by allowing users to change the name of a device from the frontend. Changing the name will be instantly applied and overrides whatever name the device is given by the integration. If you want to switch back to the name from the integration, set the name to blank.
This feature is, just like the entity registry, only available for integrations that provide unique IDs for their entities. Adding this to each integration is still a work in progress.
The new entity registry settings page in action.
Filter sensor
The filter sensor is a new 2nd order sensor by @dgomes
sensor:
- platform: filter
name: "filtered realistic humidity"
entity_id: sensor.realistic_humidity
filters:
- filter: outlier
window_size: 4
radius: 4.0
- filter: lowpass
time_constant: 10
precision: 2
Graph showing both the input sensor and the output of the filter sensor.
Light Group
We have had some discussion lately and realized that our current group component is very limiting. Extending it would probably lead to more confusion so we’ve decided to take a new approach: groups that are designed to be part of a specific component. The first one in this series comes at the hand of @OttoWinter
The group light creates a single light inside Home Assistant that is representing a group of lights. All commands will be forwarded and the state is a combination of all the lights.
light:
- platform: group
name: Cool Light Group
entities:
- light.amazing_light
- light.foobar
- light.sun
HomeKit
HomeKit got some more upgrades. We’ve added support for temperature sensors in Fahrenheit, alarm systems, switches and thermostats. Just a few releases more and we should be able to cover it all.
Optional words for the Conversation component
The conversation component has always been a great introduction to controlling your house by voice. There is no hotword detection or powerful language engine behind it, but it gives a great intro to what is possible. Starting with this release, it will get a little bit more powerful with the introduction of optional words. To mark a word optional, wrap it in square brackets: Change the light to [the color] {color}
.
# Example configuration.yaml entry
conversation:
intents:
LivingRoomTemperature:
- What is the temperature in the living room
- What is [the] living room temperature
intent_script:
LivingRoomTemperature:
speech:
text: It is currently degrees in the living room.
Have conversations with Home Assistant via the conversation component.
New Platforms
- Synology Chat as a notification platform (@cmsimike
- #12596 ) (notify.synology_chat docs) (new-platform) - KNX Component: Scene support and expose sensor values (@Julius2342
- #11978 ) (knx docs) (scene docs) (binary_sensor.knx docs) (new-platform) - Adds simulated sensor (@robmarkcole
- #12539 ) (sensor.simulated docs) (new-platform) - Add Songpal (“Sony Audio Control API”) platform (@rytilahti
- #12143 ) (media_player.songpal docs) (new-platform) - Add UpCloud platform (@scop
- #12011 ) (upcloud docs) (binary_sensor.upcloud docs) (switch.upcloud docs) (new-platform) - Added Sense energy monitor sensor (@kbickar
- #11580 ) (sensor.sense docs) (new-platform) - Filter Sensor (@dgomes
- #12650 ) (sensor.filter docs) (new-platform) - Add light.group platform (@OttoWinter
- #12229 ) (light.group docs) (new-platform) - Egardia redesign - generic component and sensor support (@jeroenterheerdt
- #11994 ) (egardia docs) (alarm_control_panel.egardia docs) (binary_sensor.egardia docs) (breaking change) (new-platform) - Add support for Zillow Zestimate sensor (@jcconnell
- #12597 ) (sensor.zestimate docs) (new-platform) - Add a Media Player Component for Channels (@maddox
- #12937 ) (media_player.channels docs) (new-platform) - Add support for alarm system, switch and thermostat to homekit (@maxclaey
- #12819 ) (homekit docs) (new-platform) - Add camera proxy (@PhracturedBlue
- #12006 ) (camera.proxy docs) (new-platform)
Release 0.65.1 - March 10
- allow ios device tracker see calls to go through (@balloob
- #13020 ) (device_tracker docs) - Fix config component loading YAML (@kellerza
- #13024 ) - Make Throttle async aware (@balloob
- #13027 ) - Add support for input boolean to Google Assistant (@balloob
- #13030 ) (google_assistant docs) - HomeKit Bugfix: names (@cdce8p
- #13031 ) (homekit docs)
Release 0.65.2 - March 10
- Fix translations sometimes not loading in the frontend (@armills
) - Fix sensibo’s min/max_temp properties (@jra3
- #12996 ) (climate.sensibo docs) - Use request.query (@ptarjan
- #13037 ) (wink docs) - Ensure we have valid config AFTER merging packages #13015 (@kellerza
- #13038 ) - Bump pysabnzbd version (@jeradM
- #13042 ) (sensor.sabnzbd docs) - Fix async lifx_set_state (@amelchio
- #13045 ) (light.lifx docs) - Yeelight version bumped. (@syssi
- #13056 ) (light.yeelight docs) - Don’t call async from sync (@balloob
- #13057 ) (xiaomi_aqara docs) - Convert decimals from SQL results (@balloob
- #13059 ) (sensor.sql docs)
Release 0.65.3 - March 11
- Implement Hue available property (@balloob
- #12939 ) (light.hue docs) - Catch async from sync context by running asyncio event loop in debug mode during tests (@balloob
- #13058 ) (camera.arlo docs) (climate.generic_thermostat docs) - Fixes KNX fire event problem, issue https://github.com/home-assistant/home-assistant/issues/13049
(@Julius2342 - #13062 ) (knx docs) - Bump iGlo Version (@jesserockz
- #13063 ) (light.iglo docs) - Fix Tado doing async wrong (@balloob
- #13078 ) (device_tracker.tado docs) - Synology Camera: auto-renew session when it’s expired (@snjoetw
- #13079 ) (camera.synology docs) - Revert “Cast automatically drop connection (#12635)” (@OttoWinter
- #13094 ) (media_player.cast docs) - Bump pyvera to 0.2.42. Improve event loop robustness. (@pavoni
- #13095 ) (vera docs) - Fix Kodi by updateding jsonrpc-websocket to 0.6 (@Tadly
- #13096 ) (media_player.kodi docs)
Release 0.65.4 - March 12
- Fix unavailable property for wemo switch (@balloob
- #13106 ) (switch.wemo docs) - Hue: Catch if bridge goes unavailable (@balloob
- #13109 ) (hue docs) (light.hue docs) - Adding check for empty discovery info in alarm control panel Egardia. (@jeroenterheerdt
- #13114 ) (alarm_control_panel.egardia docs) - Throttle Arlo api calls (@arsaboo
- #13143 ) (arlo docs)
Release 0.65.5 - March 14
- Bugfix HomeKit: Error string values for temperature (@cdce8p
- #13162 ) (homekit docs) - Revert throttle Arlo api calls (@arsaboo
- #13174 ) (arlo docs) - Ignore unsupported Sonos favorites (@amelchio
- #13195 ) (media_player.sonos docs) - Avoid Sonos error when joining with self (@amelchio
- #13196 ) (media_player.sonos docs) - Fix input_boolean Google Assistant serialize error (@balloob
- #13220 ) (google_assistant docs)
Release 0.65.6 - March 21
- More robust MJPEG parser. Fixes #13138. (@PhracturedBlue
- #13226 ) (camera.proxy docs) - Tado: don’t reference unset hass var (@balloob
- #13237 ) (device_tracker docs) - Fix Sonos join/unjoin in scripts (@amelchio
- #13248 ) (media_player.sonos docs) - Fix Sonos radio stations with ampersand (@amelchio
- #13293 ) (media_player.sonos docs) - Do not include unavailable entities in Google Assistant SYNC (@balloob
- #13358 ) (google_assistant docs) (light docs)
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Reporting Issues
Experiencing issues introduced by this release? Please report them in our issue tracker
0.64: Over 1000 integrations! New: HomeKit, BMW, August.
🎉 1000 integrations, 1000 integrations, 1000 integrations! 🎉
That’s right, Home Assistant 0.64 is here! In case you have missed our latest Cloud update, the Home Assistant Alexa skill is now live in all regions and we’re working with Google in getting the Smart Home skill for Google Assistant approved. Exciting times!
In the meanwhile, some great new integrations have landed, including yet another car 🚗 This time it’s BMW.
This is going to be the last release that supports Python 3.4. Starting with the next release, the minimum version required will be Python 3.5.3. Learn more here.
HomeKit
Native HomeKit support has arrived! Thanks to @cdce8p It is now possible to expose some devices over HomeKit to allow control via Siri and other things speaking the HomeKit protocol. Initial support has been added for temperature sensors and cover devices. Expect more devices to be added soon.
Hass.io UI update
Some of you already noticed that your Hass.io panel looks a bit different since this morning: @pvizeli pressed the red green button and the new UI got live. The Hass.io team (@frenck
That’s where @c727
We know that some features are still missing or broken, we are fixing this right now! Check this issue
Chart.js
The frontend is now rendering the graphs and charts using Chart.js thanks to the hard work by @fanthos
August integration
Major new integration by @snjoetw
Cast bug fixes
@OttoWinter
New Platforms
- Support for August doorbell (@snjoetw
- #11124 ) (august docs) (binary_sensor.august docs) (camera.august docs) (lock.august docs) (new-platform) - Add new component: BMW connected drive (@ChristianKuehnel
- #12277 ) (bmw_connected_drive docs) (device_tracker.bmw_connected_drive docs) (sensor.bmw_connected_drive docs) (new-platform) - Add New Sensor for ISP Start.ca (@mikeodr
- #12356 ) (sensor.startca docs) (new-platform) - Add the Xiaomi TV platform. (@simse
- #12359 ) (media_player.xiaomi_tv docs) (new-platform) - added smappee component (@hmn
- #11491 ) (smappee docs) (sensor.smappee docs) (switch.smappee docs) (new-platform) - Add support for HomeKit (@cdce8p
- #12488 ) (homekit docs) (new-platform) - Adds filesize component (@robmarkcole
- #12211 ) (sensor.filesize docs) (new-platform) - Adds folder sensor (@robmarkcole
- #12208 ) (sensor.folder docs) (new-platform) - Spotcrime (@jcconnell
- #12460 ) (sensor.spotcrime docs) (new-platform) - Add Tahoma scenes (@thijsdejong
- #12498 ) (scene docs) (tahoma docs) (new-platform)
Release 0.64.1 - February 27
- Frontend: Don’t put unit of sensor on new line (@NovapaX
) - Frontend: Fix display issues on iOS 9.3.5 (@NovapaX
) - Frontend: Fix chart legend not showing correctly when data has 1 serie (@fanthos
) - Frontend: Fix cards not getting updated (@balloob
) - Cast automatically drop connection (@OttoWinter
- #12635 ) (media_player.cast docs) - Roomba timeout (@kellerza
- #12645 ) (vacuum.roomba docs) - Fix a problem with calling
deconz.close
(@aronsky- #12657 ) (deconz docs) - Harmony: make activity optional (@balloob
- #12679 ) (remote.harmony docs) - Fix getting state from iglo (@jesserockz
- #12685 ) (light.iglo docs) - Fix mysensor defaults (@balloob
- #12687 ) (mysensors docs) - Component deconz: Fix dark attribute on presence sensors (@tumik
- #12691 ) (binary_sensor.deconz docs) - Bugfix: Update of sources for non AVR-X devices always fails (@scarface-4711
- #12711 ) (media_player.denonavr docs) - Don’t allow to use a old unsecure library (@pvizeli
- #12715 ) - Unbreak tahoma (@thijsdejong
- #12719 ) (tahoma docs) - fix for https://github.com/home-assistant/home-assistant/issues/12673
(@ChristianKuehnel - #12726 ) (sensor.alpha_vantage docs) - Fix harmony duplicate detection (@amelchio
- #12729 ) (remote.harmony docs) - Update ZHA deps (@balloob
- #12737 ) (zha docs) - MQTT: Fix doing async inside sync context (@OttoWinter
) - Fix DarSky humidity precision (@PhilRW
)
Release 0.64.2 - March 1
- updated to bimmer_connected 0.4.1 (@ChristianKuehnel
- #12759 ) (bmw_connected_drive docs) - Revert optimized logbook SQL (@amelchio
- #12762 ) (logbook docs) - bump fedex version (@happyleavesaoc
- #12764 ) - Silence harmless sonos data structure warnings (@amelchio
- #12767 ) (media_player.sonos docs) - Update samsungctl library to latest version (@uchagani
- #12769 ) (media_player.samsungtv docs) - Fixed missing optional keyerror data_bits (@basschipper
- #12789 ) (binary_sensor.rfxtrx docs) - Fixed Pollen.com bugs with ZIP codes and invalid API responses (@bachya
- #12790 ) (sensor.pollen docs) - Fix dead Sonos web interface with some music sources (@amelchio
- #12796 ) (media_player.sonos docs) - Unique IDs for Plex Clients (@ryanm101
- #12799 ) (media_player.plex docs)
Release 0.64.3 - March 2
- is_allowed_path: Also test folder #12788 #12807 (@kellerza
- #12810 ) - Fix sensibo default IDs to be according to schema (@andrey-git
- #12837 ) (climate.sensibo docs) - Cloud: handle unauth better (@balloob
- #12840 ) (cloud docs) - Handle Hue errors better (@balloob
- #12845 ) (hue docs)
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Reporting Issues
Experiencing issues introduced by this release? Please report them in our issue tracker
Cloud Update
We’re happy to announce that the Home Assistant skill is now available in Canada, UK, Germany, India and Australia! Check it out in the Amazon Alexa Skill store
In the meanwhile, we have also been working on the Google Assistant integration. We passed the first verification and are now working with Google to do the final verification. Stay tuned!
In less than 2 weeks the open beta is about to expire. We’re still working on setting up the company and payment system so we can start accepting payments. Until we do, Home Assistant Cloud will remain free.
0.63: Entity Registry, SQL Sensor, Mercedes cars
Date set for dropping Python 3.4 support
As announced in October, we’re going to drop Python 3.4 support in 2018. We’ve now decided that in two releases, 0.65, the minimum Python version that will be supported is bumped to 3.5.3. This won’t impact most users. You are already fine if you’re using Hass.io, the latest Debian stable (Stretch) or a derivative of that (Raspbian, Ubuntu).
Entity Registry
This release introduces the entity registry. The entity registry allows integrations to reserve entity IDs. This means that we’ll automatically grant an entity ID to a device. It’s reserved so that no other device will ever get that entity ID. It also means that as a user, you will be able to customize the entity IDs for these devices.
For an integration to leverage the entity registry, it needs to define a unique ID for each of their entities. A unique ID is something that we can uniquely identify the device and that is not configurable. So a serial number and mac address are ok, IP addresses or names are not.
Examples of integrations that have unique IDs defined in this release are Z-Wave, Hue, Nest, LIFX, Sonos, Apple TV.
To update the entity ID that will be assigned to your device, update <config>/entity_registry.yaml
and restart Home Assistant (reloading on the fly is planned for a future release).
The entity registry will assign an entity ID the first time that a device is seen. This should be the same entity ID as it always was before. If this is not the case, update the registration entity to change it back to the old entity ID.
We’re planning a lot of cool stuff around the entity registry. Stay tuned!
New Platforms
- Adds allergy/disease sensor platform from Pollen.com (@bachya
- #11573 ) (sensor.pollen docs) (new-platform) - Add Goalfeed platform (@craigjmidwinter
- #11098 ) (goalfeed docs) (new-platform) - Add Melissa (HVAC/climate) component (@kennedyshead
- #11503 ) (melissa docs) (sensor.melissa docs) (new-platform) - Mediaroom (@dgomes
- #11864 ) (media_player.mediaroom docs) (new-platform) - Add Xiaomi Universal IR Remote (Chuangmi IR) (@cnrd
- #11891 ) (remote.xiaomi_miio docs) (new-platform) - SQL sensor (@dgomes
- #12142 ) (sensor.sql docs) (new-platform) - Add Mercedes me component (@ReneNulschDE
- #11743 ) (new-platform)
Release 0.63.1 - February 12
- Fix Alexa Step Volume (@lucasweb78
- #12314 ) (alexa docs) - Remove unique ID from netatmo (@balloob
- #12317 ) (binary_sensor.netatmo docs) (camera.netatmo docs) (sensor.netatmo docs) - Allow overriding name via entity registry (@balloob
- #12292 ) - Respect entity namespace for entity registry (@balloob
- #12313 ) - Fix Report State for Alexa Brightness Controller (@lucasweb78
- #12318 ) (alexa docs) - Always return lockState == LOCKED when handling Alexa.LockController (@lucasweb78
- #12328 ) (alexa docs) - Fix platform dependencies (@balloob
- #12330 )
Release 0.63.2 - February 14
- Fix MercedesMe - add check for unsupported features (@ReneNulschDE
- #12342 ) (mercedesme docs) (binary_sensor.mercedesme docs) (device_tracker.mercedesme docs) (sensor.mercedesme docs) - Fix WUnderground names (@OttoWinter
- #12346 ) (sensor.wunderground docs) - Updated beacontools (@citruz
- #12368 ) (sensor.eddystone_temperature docs) - Introduce zone_id to identify player+zone (@sdague
- #12382 ) (media_player.yamaha docs) - Downgrade limitlessled to 1.0.8 (@amelchio
- #12403 ) (light.limitlessled docs)
Release 0.63.3 - February 17
- python-miio version bumped. (Closes: #12389, Closes: #12298) (@syssi
- #12392 ) (fan.xiaomi_miio docs) (light.xiaomi_miio docs) (remote.xiaomi_miio docs) (switch.xiaomi_miio docs) (vacuum.xiaomi_miio docs) - Fixed 3 small issues in isy994 component (@OverloadUT
- #12421 ) (isy994 docs) - Reduce the load on met.no servers, yr.no sensor (@danielhiversen
- #12435 ) - Fix for contentRating error (@ryanm101
- #12445 ) (media_player.plex docs) - Fix light template to return brightness as int (@andrey-git
- #12447 ) (light.template docs) - Optimize recorder purge (@amelchio
- #12448 ) - [SQL Sensor] always close session (@dgomes
- #12452 ) (sensor.sql docs)
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Reporting Issues
Experiencing issues introduced by this release? Please report them in our issue tracker
Disabling Disqus comments
Last week, starting with the release of Home Assistant 0.62, we switched to using our community forums for comments on our blog posts. By doing so, people are able to use their existing Home Assistant community accounts to comment on our blog posts and engage with one another. It has been easier for our users to stay in the loop with one less channel to keep track off.
Previously, we were using the free version of Disqus to power comments on our blog. After the switch, to preserve the old comments, we decided to keep Disqus active on the older blog post pages. However, today we decided to turn them off.
Today Disqus changed their advertisement strategy and turned on irrelevant graphical advertisement above and below the comment thread (screenshot
Today we have switched all blog posts to the new commenting system and are no longer serving Disqus comments. We are exploring ways to restore the old comments.
0.62: MyChevy, Iota and Venstar Thermostat
Second release of the year and it’s buzzing on GitHub. This release we had 70 people contribute code. We’ve also managed to finally get our PR count below a 100 open PRs again. A lot of cool stuff still waiting to make it to a future Home Assistant release.
I want to give a shout out to @martinhjelmare
MyChevy
With this new integration by @sdague
New Platforms
- Adding support for Lutron covers (@nickovs
- #11602 ) (lutron docs) (cover.lutron docs) (new-platform) - Add basic mychevy component (@sdague
- #11409 ) (mychevy docs) (new-platform) - Added support for TekSavvy bandwidth sensor (@jpjodoin
- #11186 ) (new-platform) - Ihc component and platforms (@dingusdk
- #10916 ) (ihc docs) (binary_sensor.ihc docs) (light.ihc docs) (sensor.ihc docs) (switch.ihc docs) (new-platform) - Iota wallet (@jinnerbichler
- #11398 ) (iota docs) (sensor.iota docs) (new-platform)
Release 0.62.1 - January 30
- Snips - (fix/change) remove response when intent not handled (@tschmidty69
- #11929 ) (snips docs) - Fix asuswrt AttributeError on neigh for unknown device (@scop
- #11960 ) (device_tracker.asuswrt docs) - Set default values for Daikin devices that don’t support fan direction and fan speed features (@rofrantz
- #12000 ) (climate.daikin docs) - Fix parameter escaping (@smoldaner
- #12008 ) (media_player.squeezebox docs) - Error handling, in case no connections are available (@ReneNulschDE
- #12010 ) (sensor.deutsche_bahn docs) - Fix 404 for Hass.io panel using frontend dev (@c727
- #12039 ) (frontend docs) - Upgrade pyharmony to 1.0.20 (@amelchio
- #12043 ) (remote.harmony docs)
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Reporting Issues
Experiencing issues introduced by this release? Please report them in our issue tracker
Clarification about Emulated Hue
There are some misconceptions floating around about the future of the Emulated Hue component and I would like to set the record straight. The Emulated Hue component is not going to be removed nor will we ever remove any functionality from Home Assistant to push you to support the Home Assistant project by subscribing to the Community Support Package.
The reason people are concerned about the future of the Emulated Hue component is because of a poor choice of words in a deprecation message. This message was introduced a year agotype: alexa
for the Emulated Hue component:
Alexa type is deprecated and will be removed in a future version
That config option should never have been called type: alexa
but instead have been called mode: legacy
. If you think about it, why would emulating something even have different modes it emulates based on the consumer? That means that one of the two emulation modes is incorrect.
The old implementation was not 100% correct. It was correct enough to work with Alexa (the original target) but not with Google Home. When fixing Emulated Hue we added type: alexa
to re-enable the old implementation so that people did not have to go through the trouble to re-add their Alexa devices. The option was deprecated to indicate that we would remove the incorrect emulation in the future. However, we forgot about actually following through with that.
The mistake we made was calling the correct mode google_home
although it had nothing to do with Google Home. It confused people and they kept adding type: alexa
to their configuration, triggering the deprecation warning.
The warning will be updated starting Home Assistant 0.62 and will also include a link to this blog post.
More info:
- To read about what was incorrect in the first version of Emulated Hue, take a look at the PR fixing it: Re-org emulated_hue and fix google home
. - Read the documentation on how to configure Emulated Hue
0.61: Coinbase, Discogs, iGlo, Sochain
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 backward-incompatible changes. Please make sure that you check the section below if you are running into trouble.
Assistant configs
We made a mistake in the foundation of both the Google Assistant and Alexa integrations: they were storing their config inside customize. This is not the right place and we moved them to be under the components itself. See the backward-incompatible changes section on how to migrate.
Hass.io updates
@pvizeli
Improved loading speed
@amelchio
todoist.new_task -> calendar.todoist_new_task
snapcast.snapcast_snapshot -> media_player.snapcast_snapshot
snapcast.snapcast_restore -> media_player.snapcast_restore
mopar.remote_command -> sensor.mopar_remote_command
broadlink.learn_command_192_168_0_107 -> switch.broadlink_learn_command_192_168_0_107
broadlink.send_packet_192_168_0_107 -> switch.broadlink_send_packet_192_168_0_107
New Platforms
- Add Discogs Sensor platform (@thibmaek
- #10957 ) (sensor.discogs docs) (new-platform) - Greenwave Reality (TCP Connected) Lighting Component (@dfiel
- #11282 ) (light.greenwave docs) (new-platform) - Added rainsensor (@jbarrancos
- #11023 ) (rainbird docs) (sensor.rainbird docs) (switch.rainbird docs) (new-platform) - Sochain cryptocurrency sensor (@Klathmon
- #11335 ) (sensor.sochain docs) (new-platform) - Support for EcoNet water heaters (@w1ll1am23
- #11260 ) (climate.econet docs) (new-platform) - Add deCONZ component (@Kane610
- #10321 ) (deconz docs) (binary_sensor.deconz docs) (light.deconz docs) (sensor.deconz docs) (new-platform) - Added new climate component from Daikin (@rofrantz
- #10983 ) (climate.daikin docs) (new-platform) - Add Touchline climate platform (@abondoe
- #10547 ) (climate.touchline docs) (new-platform) - Add new iGlo component (@jesserockz
- #11171 ) (light.iglo docs) (new-platform) - Add Dark Sky weather component (@DanNixon
- #11435 ) (weather.darksky docs) (new-platform) - Coinbase.com sensor platform (@nkgilley
- #11036 ) (coinbase docs) (sensor.coinbase docs) (new-platform)
Release 0.61.1 - January 16
- Fix zha color probe (@rcloran
- #11670 ) (zha docs) (light.zha docs) - Move several local services to their right domain (@amelchio
- #11677 ) (calendar.todoist docs) (media_player.snapcast docs) (media_player.soundtouch docs) (switch.broadlink docs) (switch.scsgate docs) (breaking change) - Rfxtrx fix (@danielhiversen
- #11678 ) (rfxtrx docs) (binary_sensor.rfxtrx docs) - History order bugfix and opt-in option (@rwa
- #11686 ) (history docs) - Fix purge with MariaDB / MySQL (@tinloaf
- #11713 )
If you need help…
…don’t hesitate to use our very active forums or join us for a little chat
Reporting Issues
Experiencing issues introduced by this release? Please report them in our issue tracker