2023.11 To-do: Add release title

[jerrm]

Don’t use device triggers. Use State triggers.

[TimoJ]

Failed automations used time trigger, but had ‘if conditions’ and those had the ID problem devices.

[jerrm]

@TimoJ

had ‘if conditions’

Still basically the same answer.

Don’t use device conditions, use state conditions.

[TimoJ]

OK, I’ll try to remember that when adding new automations.

[rafkra]

Worth mentioning: ShellyForHASS closes. It was the first Shelly integration in Home Assistant. Many thanks to Håkan Åkerberg as author and main developer. His recommendation is to use Home Assistant’s own Shelly integration.

[123 (Taras)]

Here’s a helpful Community Guide explaining the pros and cons of Device Triggers/Conditions/Actions versus other kinds of Triggers/Conditions/Actions.

Why and how to avoid device_ids in automations and scripts

Don’t forget that the first post in a community guide is a wiki - feel free to add to it or correct it. This guide was written with reference to: Home Assistant 2023.8.3 Supervisor 2023.08.1 Operating System 10.5 Frontend 20230802.1 - latest Background When you start writing automations, a device trigger seems the obvious choice. Everybody knows what a device is and it comes at the top of the UI dropdown list. [image] It works… but it is certainly not a “great way to start” because it …

[rcblackwell (Robert Blackwell)]

I’m running Home Assistant;

• Core 2023.11.1
• Supervisor 2023.10.1
• Operating System 11.1
• Frontend 20231030.1

Since upgrading to Core 2023.11.0, the “Refresh” button on the “Developers Tools/State” tab hasn’t functioned correctly. If I select an “entity” from the list of those shown, then click on the “Refresh” button, the area showing the entities attributes (Set State) clears rather than updating entity details.

I’ve only noticed this behaviour since upgrading to Core 2023.11.0. Prior to the upgrade, pressing the refresh button would update the entities attributes. I’ve restarted HA and rebooted the server in hopes of correcting the issue but it remains. Is anyone else experiencing this behaviour?

Regards

[Caswell1000]

Good day,

I have a slight problem, after I upgrade the core to 11.1 there are errors to do with no platform sensor.average, also homeassintant.util.temperature, how can I overcome this because it prevents restarting, when I restore the previous version I do not have issues. It does not point to a line in the config or to any automation.

Regards
Caswell

[joelp]

I didn’t see this upgrading from 2023.11.0 to .11.1 thankfully.

[Caswell1000]

I have added a photo of the error, how can I resolve this, I am afraid to reboot.

Regards,
Caswell

[makai]

You are using a custom integration that needs to be updated

[makai]

There’s already a PR to fix that. It may be available in the next fix release

[tom_l]

Since updating to 2023.11 I no longer seem to be able to theme the colours of sliders. e.g. in my theme:

  paper-slider-knob-color: '#e45e65' # red
  paper-slider-active-color: var(--paper-slider-knob-color)

However the inspector shows:

This is the same in firefox and chrome.

Is anyone else seeing this?

[averater (Gustav Svensson)]

Then I would have to do that on all devices for all users. Not what I asked for. I want to clean up the system and make it easier to use for all users so there isn’t a lot of unused stuff in the menus.

[TimoJ]

I think Energy Dashboard date selector change made it worse to use. Before there were direct shortcuts for week, month, year etc. But now I have to do extra click to open the calendar to see those. Bring them back to the main page or allow to customize the view via yaml edit.

[Mariusthvdb (Marius)]

been stoked on replacing my custom:state-switch cards with the new condition options, and indeed found a few. which is great, in trying to be as core as possible.

However I now realize again what power tool that state-switch card is, as it offers the ‘all’ option if the condition isnt met.

  - type: custom:state-switch
    entity: mediaquery
    states:
      '(min-width: 800px)':
        !include /config/dashboard/includes/include_sankey_energie.yaml
      all:
        type: custom:swipe-card

Or, just more than 1 condition in the same card config, which behave as an if/else:

type: custom:state-switch
entity: binary_sensor.saver_offline
states:
  'on':
    type: custom:button-card

  'off':
    type: custom:button-card

also, the group function in admin/users is so cool, I had forgotten all about that…

  - type: custom:state-switch
    entity: group
    states:
      admin:
        type:
      user:
        type:

instead of the now possible:

  - type: conditional
    conditions:
      - condition: user
        users:
          - !secret admin_m
          - !secret admin_w
    card:

So, nice improvement already, several useful conditions. Please keep developing on these options though, and do have a look at state-switch

Won’t mention the template option, as that would probably never make it into core…

[mhoogenbosch (Martijn Hoogenbosch)]

@makai is right, and it is the “Home assistant plant” should be updated to 2023.10.0. Had the same issue during beta.

[Mariusthvdb (Marius)]

on the new Improv BLE:

I have a few of the m5 stacks, in both voice or bt proxy version. for some time now.

Should I be seeing the new Improv integration in the Integration list now? Because I dint, and when trying to add it, it states

How can I tell my M5 stacks are Improv ready/functioning?

[petro]

No, the device_id’s werent’ changed. The automations had errors and HA didn’t know it. Now HA knows the errors and wants you to fix them. It creates a repair and disables the automation. I.e. working as intended. There’s no “fix” other than users needing to fix their automations. That’s what I gathered from reading the issue.

[Caswell1000]

All is sorted now, it was not due to the upgrade.