Bot releases are hidden (Show)
Published by make-all 7 months ago
Published by make-all 8 months ago
Fixes an issue with migration of "tank" binary sensors to either tank_full or tank_empty as appropriate in 2024.3.0
Published by make-all 8 months ago
translation_only_key
added to handle cases where we want the unique_id to ignore translation_key (mainly to keep backward compatibility) #1579Published by make-all 8 months ago
I acknowledge that some users may be upset by this decision, but the
decision is final so it will not help to argue against it. In
particular abusive comments in discussions will not be tolerated.
Published by make-all 8 months ago
Published by make-all 9 months ago
Lint was enabled for YAML files, leading to a lot of whitespace cleanup, and a few more significant changes that may have fixed some issues for some devices. Support for a couple more models of vacuum cleaner was also added, so you too can clean up ready for the new Lunar Year.
Published by make-all 9 months ago
This version requires Home Assistant 2023.9.0 or later. This is required for underlying support for lawn_mower (introduced in HA 2023.9) and event (introduced in HA 2023.8) entities.
Published by make-all 10 months ago
Published by make-all 11 months ago
In a last minute change to HA 2023.12, the backward compatible fallback
for a previously unnoticed change to fan API was broken. HA may fix
this in a point release, but in case not, it is being fixed here. #1380
Details: some time previously (at least 2 years ago), the turn_on
service for fans was changed from a simple on/off to also allow
passing percentage (speed) and preset_mode parameters as part of the
turn_on command. This integration did not implement that, and instead
relied on the backward compatibility provided for that change. As
part of improved error handling, a wrapper function was added just
before the HA 2023.12 release to check the preset_mode parameter
before calling the real turn_on service. This new function is missing
the backward compatibility that used to exist, so requires fan
integrations to implement the new API.
This release adds the preset_mode and percentage parameters to the
turn_on method to avoid the errors in HA 2023.12 and get fans working,
however the parameters are ignored, so passing these parameters to the
turn_on service will not work in this release, it is still necessary
to use separate set_percentage and set_preset_mode service calls.
The next release will finish off the implementation.
Published by make-all 11 months ago
HA 2023.12 changes the YAML parser in a way that breaks previous
releases of this integration. Please upgrade to this version before
upgrading Home Assistant if possible. If you already upgraded HA to
2023.12, then updating to this release will likely fix any issues you
are seeing as a result of that upgrade.
Published by make-all 11 months ago
Published by make-all about 1 year ago
Climate entities that do not have any hvac_mode dp now return a mode of None instead of "auto". This affects Inkbird ITC-308 devices, and maybe others, and should prevent an empty mode selection control from being displayed on the new climate UI in HA 2023.10. #1144
Lock entities now clear unlock dps immediately after reporting them. This may result in the unlock source disappearing from the UI too quickly, but helps with detection of multiple unlocks happening in quick succession. #796
Published by make-all about 1 year ago
Published by make-all about 1 year ago
No breaking changes in this release
Published by make-all about 1 year ago
unixtime
type for timestamp sensors. #687Published by make-all about 1 year ago
Due to the short time between 2023.8.0 and 2023.8.1, and the likelihood the previous release has been skipped, the breaking changes section for 2023.8.0 is repeated below. For more details on the other changes, see the release notes for 2023.8.0.
Many sensors are now defaulting to the HA standard name for their class, to make use of standard name translations. This has resulted in some entities being renamed. A migration attempts to handle the renaming in Home Assistant's registry but it may still be necessary to update automations or some other references to entities. There may also be some cases that were missed by the migration, in which case you will have new entities created, and the old ones will become "unavailable" and will need to be deleted manually.
If you are using a version of Home Assistant older than 2023.7, some entities will be displaying only the device name the UI. #871
These are the main changes:
- carbon_dioxide: some were previously named CO2
- carbon_monoxide: some were previously named CO
- humidity: some were previously named Current humidity, but no change was made for deprecated sensors (see below)
- pm1: some were previously named PM 1.0 (translates to pm_1_0 in entity naming)
- pm10: some were previously named PM 10 (translates to pm_10 in entity naming)
- pm25: were previously named PM 2.5 (translates to pm_2_5 in entity naming)
- temperature: some were previously named Current temperature
- volatile_organic_compounds some were previously named TVOC
Current humidity sensors for humidifiers and dehumidifiers have been deprecated, as the humidifier entity supports reporting of current humidity as of HA 2023.7 #869
As of HA 2023.8, the battery_level attribute of vacuums is deprecated, to be replaced by battery sensors. To avoid the deprecation warning, this change has been made already. After this change, battery status has full history recording available, however if you have any automations reading the battery_level from the vacuum, you will need to update these to read from the battery sensor instead.
Some custom cards may not yet be updated for this change, so the battery level may disappear from the card until it is updated. #954
After gathering more info on the preset modes available for this device, the main entity has been changed from water_heater to climate to make the cooling funtions available too. The water_heater entity is deprecated. #966
Previously a mapping could be marked hidden to hide it from the list of possible values. Now these mappings have also been made one-way, to only map device values to the UI. The main use case for these is to map unexpected values like null (missing any value) to something else for the UI. Mapping back to these unexpected values when a value is changed from the UI is not desirable behaviour for the use cases imagined for this feature, and if you need that the mapping should probably not be hidden. #914
Published by make-all about 1 year ago
Many sensors are now defaulting to the HA standard name for their class, to make use of standard name translations. This has resulted in some entities being renamed. A migration attempts to handle the renaming in Home Assistant's registry but it may still be necessary to update automations or some other references to entities. There may also be some cases that were missed by the migration, in which case you will have new entities created, and the old ones will become "unavailable" and will need to be deleted manually.
If you are using a version of Home Assistant older than 2023.7, some entities will be displaying only the device name the UI. #871
These are the main changes:
- carbon_dioxide: some were previously named CO2
- carbon_monoxide: some were previously named CO
- humidity: some were previously named Current humidity, but no change was made for deprecated sensors (see below)
- pm1: some were previously named PM 1.0 (translates to pm_1_0 in entity naming)
- pm10: some were previously named PM 10 (translates to pm_10 in entity naming)
- pm25: were previously named PM 2.5 (translates to pm_2_5 in entity naming)
- temperature: some were previously named Current temperature
- volatile_organic_compounds some were previously named TVOC
Current humidity sensors for humidifiers and dehumidifiers have been deprecated, as the humidifier entity supports reporting of current humidity as of HA 2023.7 #869
As of HA 2023.8, the battery_level attribute of vacuums is deprecated, to be replaced by battery sensors. To avoid the deprecation warning, this change has been made already. After this change, battery status has full history recording available, however if you have any automations reading the battery_level from the vacuum, you will need to update these to read from the battery sensor instead.
Some custom cards may not yet be updated for this change, so the battery level may disappear from the card until it is updated. #954
After gathering more info on the preset modes available for this device, the main entity has been changed from water_heater to climate to make the cooling funtions available too. The water_heater entity is deprecated. #966
Previously a mapping could be marked hidden to hide it from the list of possible values. Now these mappings have also been made one-way, to only map device values to the UI. The main use case for these is to map unexpected values like null (missing any value) to something else for the UI. Mapping back to these unexpected values when a value is changed from the UI is not desirable behaviour for the use cases imagined for this feature, and if you need that the mapping should probably not be hidden. #914
Published by make-all about 1 year ago
Published by make-all over 1 year ago
This build contains further translation improvements, and some changes to humidifier modes and fan preset_modes to support this.
The main changes are: