frontend icon indicating copy to clipboard operation
frontend copied to clipboard

Number Entity Cannot be accessed using Labels as a Reference

Open jvmahon opened this issue 1 year ago • 1 comments

Checklist

  • [X] I have updated to the latest available Home Assistant version.
  • [X] I have cleared the cache of my browser.
  • [X] I have tried a different browser to see if it is related to my browser.
  • [X] I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

Background:

This relates to the "Number" entity and use of the "Labels" field to reference those entities in scripts and automations.

Problem:

Attempts to reference "Number" entities fails when trying to identify them by a Label.

Recreating the Issue:

  1. I have a large number of "Number" entities that are crated by the Matter integration which I have labeled using the "Labels" feature, as shown in this image:
image
  1. I then use these Labels in a script to select the number entities as shown below:
image

And in YAML, shown as:

action: number.set_value
metadata: {}
data:
  value: "1.0"
target:
  label_id:
    - on_transition_time

However, the script does not appear to be able to identify the entities using the labels. Expected behavior and problem are further described below.

Describe the behavior you expected

The Problem:

Use of labels as shown above appears to be ineffective. This is demonstrate in two ways:

  • If I click on the label expansion symbol (the "<>" marking on the label), I expect that the label will be replaced by the actual identified entities. However, what happens is that the label disappears and no entities appear
  • If I run the script with the label itself (i.e., without trying to expand the label), I expect the script to act on all of the entities with that label. However, nothing happens.

Steps to reproduce the issue

(already described above).

What version of Home Assistant Core has the issue?

2024.08.02

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

windows 10 and windows 11

State of relevant entities

"Number" entity (https://developers.home-assistant.io/docs/core/entity/number) as used in Matter implementation. I am not sure this Label issue has anything to do with "Matter" integration, but that is the integration I observed the behavior on.

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

jvmahon avatar Aug 20 '24 14:08 jvmahon

Hmm I can't reproduce, it works perfectly for me 😕

karwosts avatar Aug 20 '24 17:08 karwosts

Hmm I can't reproduce, it works perfectly for me 😕

@karwosts Definitely not working for me. I've tried both with entities created by the Matter Integration as well as by Z-Wave integration.

Is this the right issues list for this, or maybe there is something more narrowly focused on the "labels" function?

Here's an example of the issue repeated on Z-wave. Here, I've labeled several "ping" buttons with the label "ping label test"

image

I then set up a script where I try to access these by label and shown below, but if I click the symbol "<>", I expect the label to disappear and get the list of entities. Instead, the label disappear and I get no selected entities.

image

Currently running the following: image

jvmahon avatar Sep 30 '24 13:09 jvmahon

Hmmm, I now see in the "core" repository, there are some label functions there. I'll give a few more days here to see if there is a response, else I'll close this and repost the issue over to there in case its the appropriate place.

jvmahon avatar Sep 30 '24 13:09 jvmahon

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] avatar Dec 29 '24 14:12 github-actions[bot]