But where is it written that modes should be replaced with preset_modes? Documentation list them both and example values are different so looks like for different purpose:
modes list (optional)
A list of supported modes. Needs to be a subset of the default values.
Default:
[“auto”, “off”, “cool”, “heat”, “dry”, “fan_only”]
and
preset_modes list (optional, default: [])
List of preset modes this climate is supporting. Common examples include `eco`, `away`, `boost`, `comfort`, `home`, `sleep` and `activity`.
Those are two different things and they also are later on exposed in Lovelace in different ways:
Here an example for another type of climate integration:
Preset and mode are for different purposes and should both be available. My device needs only mode (operation in lovelace) and I don’t need the preset. But other devices/integrations need both of them.
Below is my case:
It uses off and fan_only modes and a fan_mode with values low, medium or high. All in line with the integration documentation.
The new “Play Media” service was working great in my automations yesterday. Now today I can no longer see the new “Play Media” service available in automations. Is anyone else having this issue?
Upgrade was successful but I encountered a little quirk with MQTT Discovery.
In previous versions, you could publish an updated discovery payload, for an existing entity, and the entity’s state value and attributes would update immediately (if the values were stored on the broker as retained messages).
While trying to enhance my MQTT HVAC climate entity, publishing an updated discovery payload caused the existing climate entity to lose its state and attribute values (became unknown).
That’s odd because the (retained) values are on the MQTT broker so they’re not unknown; Home Assistant is already subscribed to the entity’s topics so it should be able to receive the values immediately.
Restarting Home Assistant fixes it (i.e. the climate entity gets the values stored on the broker) but that’s to be expected because the restart forces Home Assistant to re-subscribe to all topics on the broker.
I’ll probably do a few more tests before reporting this as an Issue.
And additionally here more explanation from KNX integration which clearly explains that HA is having two parameters: hvac_mode and preset_mode - both used for different things:
I noticed that the Rainbird integration doesn’t work: it doesn’t show any switch of the zones. I checked that someone said it in the realese 2021.12, but I didn’t check in that moment. Anybody knows something about it? Thanks!
Maybe this has already been noted by others.
But this update, and previous ones, I am getting a lower user experience feeling.
After I press UPDATE, my Z-Wave devices are not working anymore.
I am using a external docker with a zwave2mqtt service.
Home assistant is not aware of this, just updates and after the update notices the zwave devices are not available.
What I ideally would like to see, is that when I press UPDATE, Home Assistant pops a message,
Warning: your current zwave server needs to be updated.
Do you still want to continue the update [Y/N]?
Dont get me wrong. For me, fixing it is not much fuzz, I am running Docker+Portainer+ouroboros. Just enable ouroboros and wait 2 minutes untill everything is updated.
But I would like to get a notice.
Home Assistant will already update the Z-Wave JS integration when it is installed as an add-on during the integration set up. You manage your own zwave2mqtt service so … you are the one that needs to manage it. We can’t do it for you.
I know i do. I can and will. But i find out by chance something is off.
It would be nice if HA is aware and pops a notice.
Like: current version detected: xxx.
Required version : yyy or higher
You can make an automation that looks for the error and creates a notification. Many people won’t want a pop up (myself included) and you have to option to create one for yourself through an automation.
You are right, I messed up. I just tested your config and it seems you always will get the send_if_off deprecated warning. I think is a bug. There is a default value set during validation, and that needs to change.
Deprecation warnings for send_if_off or hold_modes are logged regardless of there presence in the config. This is cause by default values in the schema, causing the values to be configured.
Could be as simple as browser cache. I had to clear site data for my HA domain, re-login and hard refresh (ctrl+F5) the Automations Dashboard in order to see the new option.
I think the answer may lie in this extract from the release notes
Your Cameras! Your Lovelace Dashboards! You can just pick one of your cameras or Lovelace dashboards and “Play” them on a **supported device ** (like a Google Nest Hub or television).
lovelace sharing works on my chromecast, not on my other devices.
