2024.3: Drag 'n Drop it like it's hot! 🎉

[slimak]

Hi!

Question: Can “script user input” be used like “tap_action confirmation” but allow for more choices? E.g. currently I have a button to open the front gate, and a confirmation which triggers a popup. I can either press OK or Cancel. Instead, I’d like to have 3 choices in this popup: Open, Open&Close, Cancel.

[dshokouhi]

@nkb

It’s changed the b in the name of the notify service to an h, but only for the notify service, and not for any of the sensor entities.

that really shouldnt happen on its own but the names are slugified I believe and I do see a dependency update for that in ths release. Not sure if that caused this change but I woudl say thats unexpected. The service call should only update when the device name is updated.

[mekanics]

Well, well…

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:156
First occurred: 18:06:50 (1 occurrences)
Last logged: 18:06:50

Detected that custom integration 'browser_mod' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/browser_mod/mod_view.py, line 24: hass.components.frontend.async_register_built_in_panel(, please report it to the author of the 'browser_mod' custom integration

Many rely heavily on browser_mod in their UI, especially with popups

Browser_mod’s development has not been active lately, so the question at this point is, what are the options/alternatives for handling popups with user’s own contents?

[petro]

Just write up an issue. Thomasloven is a moderator here and still active with his repositories.

[mekanics]

There is an issue already: Detected that custom integration 'browser_mod' accesses hass.components.frontend · Issue #690 · thomasloven/hass-browser_mod · GitHub

[Dilligaf]

There be gremlins. All of a sudden my button (the script for which doesn’t seem to reproduce properly in the blockquote window):

cards:

• show_name: true
  show_icon: true
  type: button
  icon: mdi:heat-wave
  name: Boost Heating to 21C House
  entity: input_button.boost_heating
  tap_action:
  action: call-service
  service: tado.set_climate_timer
  data:
  time_period: ‘00:45:00’
  temperature: 21
  target:
  entity_id:
  - climate.ensuite
  - climate.house_core
  [etc]
  show_state: false

for boosting heating complains:

Failed to call service tado/set_climate_timer. TadoClimate.set_timer() missing 1 required positional argument: ‘requested_overlay’

You can’t specify both a timer and an overlay. But all of a sudden if you set a timer it seems to be demanding an overlay anyway. In the local parlance - what’s occurring?

[petitpiton]

The core update 2024.3 appears to have broken the Axis IP Camera integration as the integration now fails during startup.

Logger: homeassistant.config_entries
Source: config_entries.py:504
First occurred: 16:29:31 (1 occurrences)
Last logged: 16:29:31

Error setting up entry Garage for axis
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 504, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/axis/__init__.py", line 21, in async_setup_entry
    api = await get_axis_device(hass, config_entry.data)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/axis/device.py", line 261, in get_axis_device
    await device.vapix.initialize()
  File "/usr/local/lib/python3.12/site-packages/axis/vapix/vapix.py", line 144, in initialize
    await self.initialize_api_discovery()
  File "/usr/local/lib/python3.12/site-packages/axis/vapix/vapix.py", line 162, in initialize_api_discovery
    await asyncio.gather(*[api.update() for api in apis if api.supported])
  File "/usr/local/lib/python3.12/site-packages/axis/vapix/interfaces/api_handler.py", line 126, in update
    obj_ids = await self._update()
              ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/axis/vapix/interfaces/api_handler.py", line 115, in _update
    objects = await self._api_request()
              ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/axis/vapix/interfaces/port_management.py", line 31, in _api_request
    return await self.get_ports()
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/axis/vapix/interfaces/port_management.py", line 36, in get_ports
    return GetPortsResponse.decode(bytes_data).data
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/axis/vapix/models/port_management.py", line 221, in decode
    data=Port.decode_to_dict(data["data"]["items"]),
                             ~~~~~~~~~~~~^^^^^^^^^
KeyError: 'items'

[WedHumpDay (Jason)]

UniFi OS - Dream Machines 3.2.12 (Official)
UniFi Network Application 8.1.111 (EA)
UniFi Protect Application 3.0.10 (EA) So, yes.

I know there is a warning with running Protect EA but it was only a warning and we could acknowledge. Was working great on previous HA 2024.2.x release just fine. Only when upgrading to HA 2024.3 is when things went south.

How soon before an update release to come out?

[Smiley1244 (Ross)]

2024.3 is showing me a repair for System Monitor
" Process sensors processor_use, memory_use, memory_free, memory_use_percent, disk_use_percent, disk_free, disk_use have been created as binary sensors and the sensors will be removed in 2024.9.0.

Please update all automations, scripts, dashboards or other things depending on these sensors to use the newly created binary sensors instead and press Submit to fix this issue."

binary_sensor.system_monitor_process_disk_free
binary_sensor.system_monitor_process_disk_use
binary_sensor.system_monitor_process_disk_use_percent
etc

The binary sensors only seem to allow me to start stop monitoring but don’t give any numbers when running? Change Add Process binary sensor in System Monitor by gjohansson-ST · Pull Request #108585 · home-assistant/core · GitHub seems to detail the change but not how to use the sensors and the “System Monitor” documentation doesn’t list any changes.

Any help would be appreciated as to where I’m going wrong?

[petro]

There’s really nothing to it, they are just now configured via the UI.

Once you get through the configuration, they appear exactly the same as before, just now in the UI.

[wdehoogh]

Are there some sort of unstated/undocumented limits on the types or quantities of script fields that will show up in the more-info popup? Some of my scripts correctly show the script fields while others don’t show them.

My vacuum one for example, I see the fields when I open a script in the developer tools but not when I open a more-info popup on the dashboard. All I see is the Cancel & Run buttons…

How it looks in the developer tools:

[petro]

Clear your cache and refresh the page. There’s no limits as far as I know.

[Fred54]

Does HA support temperature correction for ZHA integrated climate devices like the Aqara hum/temp/pressure devices? I use those devices all around the house but they require a correction of -0,3 celcius. I understand zigbee2mqtt supports such a correction but ZHA?

[cdmlb]

Calendar broken now since this new update?

Unable to parse date/time value: [ValueError(“Expected value to match DATE pattern: ‘’”), ValueError('Expected value to match DATE-TIME pattern: ')]

When trying to delete or modify events

[Holdestmade]

Have a look at the GitHub issue I posted, the code owner replied

[Mariusthvdb (Marius)]

seems a bit weird as those sensors are still sensors and not binary_sensors, they should show the values of men /disk usage etc? see:

this is running 2024.4 dev, so definitely see to assume they still are there, and no repair at all.

there is a configuration button

that allows you to select several processes to track being active

to my understanding those were the former sensors, now turned into binaries

sorry for the dark images, changed to a lighter theme…

[Mats789]

I don’t see how your question is related to this release thread so you should probably ask elsewhere, but as far as I know the answer is No. You could use a template sensor to adjust your values.

[Smiley1244 (Ross)]

I’ve already set the sensors up through the UI, it is those sensors I’m getting the repair warning about and a binary sensor is useless for RAM free for example. I’ll try clearing it all out and running through the System Monitor setup again . . .I think I’ve found the issue, seems the percent usage sensors must have been leftover from the YAML setup even though they had been removed.

No idea why it created binary sensors?! Removing System monitor and setting it up again cleared everythign down and created the sensors as I’d expect them.

[Zweierpotenz]

@madelena The new section layout looks great! I think you said in the stream to post feedback/feature requests under the release post. I’d like to suggest to make the number of columns editable. I have a widescreen display and half of my viewport is empty because I cant tell the layout to use more than 4 columns.

[wdehoogh]

Actually, I think I’ve figured out where the bug is. It looks like the script fields don’t appear in the more-info popup when selector options are set up with label mapping, like below:

select:
  options:
    - label: Red
      value: r
    - label: Green
      value: g
    - label: Blue
      value: b

As soon as I remove the mapping, they start working again.

I’ll work on submitting a bug report

Edit: scratch that… its not that simple to reproduce. I need to keep digging but it appears to be related to the selector mapping