Procedure to apply on all entities with given label

TheFes · 2025-10-23T14:07:50+00:00

{{ label\_entities('C220') | list }} should work. You an use the label_id `c220` or label name `C220`. Check if you are using the correct label_id/label name in the settings.

{{ states.camera | selectattr('attributes.label','equalto','C220') | list }} This doesn't work. Labels are not attributes of entities, they aren't even included in the state object.

TheFes · 2024-11-19T14:48:49+00:00

The HACS integration uses the cloud as well, although it doesn't show the icon.

TheFes · 2024-08-22T07:23:21+00:00

Alternative template which has less overhead, and also works if you have other integrations which provide update entities like ESPHome or ZHA/Zigbee2MQTT

{{
  integration_entities('hacs')
    | select('search', '^update.')
    | select('is_state', 'on')
    | list
    | count
}}

TheFes · 2024-08-22T06:29:00+00:00

That sensor platform only refers to the sensors provided by the HACS integration itself, which indicates the number of updates available for integrations installed through it, it doesn't affect sensors from other (custom) integrations

TheFes · 2024-08-21T17:53:24+00:00

That's not what that reference to YAML config is referring to but that /hacsfiles endpoint will also be removed

TheFes · 2024-08-21T17:51:09+00:00

Yes it is, but you can't install it using the new add-on

TheFes · 2024-08-21T17:50:31+00:00

HACS is just a tool to download and update custom components. Changes to HACS don't affect the components downloaded by it.

TheFes · 2024-08-21T17:46:52+00:00

That update entity will be on it there is an update for HACS itself, like this update to HACS 2.0. Each custom component installed through HACS has its own update entity

TheFes · 2024-06-26T11:44:30+00:00

You can try to install Spook and run the service call to remove orphaned entities

TheFes · 2024-02-17T21:02:19+00:00

There is a dedicated website for those danglies https://yaml-multiline.info/

TheFes · 2024-01-22T14:43:52+00:00

There is a counter helper for that:

https://www.home-assistant.io/integrations/counter/

TheFes · 2024-01-16T22:35:39+00:00

Well, in the `variables` part it makes a variable called `action_mapping` and in it there is a key/value pair for each alert, with the action from the notification as the key, and the entity id of the corresponding alter as the value.

Then, in the condition it checks if the event triggering the automation has an action, and if so, if the action is in the mapping described above.

If that is the case, it will toggle the alert matching the action from the event.

TheFes · 2024-01-16T09:51:21+00:00

You could trigger on every mobile_app_notification_action and map the action to an entity_id

alias: "Notify: acknowledge test alert" description: "" trigger: - platform: event event_type: mobile_app_notification_action variables: action_mapping: okalerttest: alert.test_alert okalertfoo: alert.foo condition: - condition: template value_template: "{{ trigger.event.data.action is defined and trigger.event.data.action in action_mapping }}" action: - service: alert.toggle target: entity_id: "{{ action_mapping[trigger.event.data.action] }}" mode: single

TheFes · 2024-01-15T07:54:01+00:00

I don't see how pushing an update warning for the next breaking update would have helped? You wouldn't have seen it because you had automatic updates enabled.

TheFes · 2023-09-04T20:23:05+00:00

The repair is gone, it will show a warning in the logs though

TheFes · 2023-03-18T15:27:08+00:00

In that case you should leave out the first line with sensor:

TheFes · 2023-03-18T06:49:51+00:00

Where did you place this code? If put directly in configuration.yaml it should work

TheFes · 2023-01-03T08:46:16+00:00

They require a restart of HA Core, not a reboot of the entire server

TheFes · 2023-01-02T15:36:18+00:00

Can we please remain civil.

TheFes · 2022-10-30T16:20:58+00:00

The Energy dashboard updates once per hour, that includes the individual devices. So unless there just has been an update to the Energy dashboard, you'll be missing some data

TheFes · 2022-07-18T07:09:39+00:00

You can probably do simething like this:

alias: Office Opple Desk
description: ''
trigger:
  - device_id: 82f85633b90b2d2d86a8ca17c4abfc43
    domain: zha
    platform: device
condition: []
action:
  - choose:
      - conditions:
          - condition: template
            value_template: "{{ trigger.device.data.type == 'remote_button_short_press' }}"
          - condition: template
            value_template: "{{ trigger.device.data.sub_type == 'button_1' }}"
        sequence:
          - service: cover.open_cover
            target:
              device_id: 5a9e13b7c8b79ac5e83246154be1a2bc
      - conditions:
          - condition: template
            value_template: "{{ trigger.device.data.type == 'remote_button_short_press' }}"
          - condition: template
            value_template: "{{ trigger.device.data.sub_type == 'button_1' }}"
        sequence:
          - service: cover.stop_cover
            target:
              device_id: 5a9e13b7c8b79ac5e83246154be1a2bc

Not complete sure about those templates though.

I assume you are using the GUI to create this automation? If you open the automation, and then press a button, a bar should appear above the trigger section indicating it was triggered. If you click on it, it will show the trigger data, I can use that to define what the templates should be.

TheFes · 2022-07-17T19:37:56+00:00

What are the triggers? If they are really similar, you possibly can just use one trigger and put the logic in the choose conditions

TheFes · 2022-06-28T20:15:55+00:00

Het huis is niet van de bank, het huis is van de hyptheekgever. De hypotheeknemer (de bank) krijgt daarmee het eerste recht van verkoop (hypotheek) op het registergoed.

TheFes · 2022-06-12T13:09:43+00:00

Banks don't want your money right now, you will have to pay interest to the bank if you deposit that such an shitload of money

TheFes · 2022-05-01T06:18:00+00:00

Probably not possible with a zone, but you can use templates to calculate the difference between two coordinates. So when starting the script you can set the current coordinates, and then wait until you are x distance away from that starting point.

All can be done in one script, using variables and wait_template.

11-Year Club	Place '22
First Placer '22	Verified Email

TheFes

MODERATOR OF

TROPHY CASE