Viewing and/or changing the source sensor for a threshold sensor created in the UI is not possible

[frankfrommelt]

The problem

When I create a Helper / Threshold Sensor in the UI and later need to check which source sensor I had been using or change the source sensor is not possible in the UI.

When viewing/editing such a sensor one can only view/modify

Hysteresis, Lower limit and Upper limit.

What version of Home Assistant Core has the issue?

core-2023.9.2

What was the last working version of Home Assistant Core?

?

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Threshold

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

threshold documentation threshold source

[lesissou]

I have same problem. Is it possible to change by another way ? exemple in configuration.yaml ?

[habratd]

Still the same issue even in 11.0

[bas89]

I don't see a way to upvote this so I'm just commenting that I can confirm the issue. Have to delete and re-assign the helpers.

[AndrewTruett]

+1

[FlexxFR]

I ran into the same issue. Was looking for a while but could not find the source sensor. So, still not visible in 2024.2.

[ironboy1]

+1 please add a dialog to maintain input sources of helpers, especially in regards to threshold sensors

[frankfrommelt]

I have same problem. Is it possible to change by another way ? exemple in configuration.yaml ?

You can configure the whole sensors in the configuration.yaml instead of the UI. But then you will have to restart core or at least re-read the configuration for all configuration changes and cannot edit anything about the sensors in the UI later on.

[ironboy1]

I have same problem. Is it possible to change by another way ? exemple in configuration.yaml ?

You can configure the whole sensors in the configuration.yaml instead of the UI. But then you will have to restart core or at least re-read the configuration for all configuration changes and cannot edit anything about the sensors in the UI later on.

Sure, and thanks for pointing this out! Some of my legacy threshold sensors are still configured in the configuration.yaml. However, this is actually not what I want. I think it is a way better, easier and more manageable option to manage them via th UI, but if the UI is missing one really important property, the whole value of the UI implementation is questionable. Advanced users will find their ways around it, but starters or people not interested in writing yaml for example will become frustrated quite quickly and will look for a different solution.

That's why I think, it's important to build an UI experience which supports all needed tools to fulfill a certain task, which is in regards to management of helpers not fully implemented yet.

[frankfrommelt]

That's why I think, it's important to build an UI experience which supports all needed tools to fulfill a certain task, which is in regards to management of helpers not fully implemented yet.

Exactly my option.

[pmueller2024]

I ran into the same issue. So, still not visible in 2024.4.2

[vartom]

Still the same issue. HA 2024.4.4

[qvdm]

I filed an issue about this under Frontend, but it was closed and I was redirected here. Below is my description of the issue there:

"Since the input sensor is THE core entity that is driving the helper, it does not make sense that it is not displayed when editing the helper. I would expect to be able to at least see the input sensor name, but preferably be able to edit it because one might want to change the input sensor for a helper that is used in many automations. Currently, the only way to change the input sensor is to create a new helper and change all the related automations."

I make extensive use of helpers, and this issue is really becoming a pain to deal with. It is an obvious defect, and I hope that it receives the attention it deserves.

[fxstein]

Changing the source sensor is a key capability missing here. Helpers are meant to create flexibility, but it's missing out when they need to be deleted and recreated every time something underlying changes - as is often the case with many integrations. One minor change then triggers painful deletions and manual recreations of helpers, and everything attached to them.

[dougiteixeira]

Implemented in #119157, this issue can be closed.

[frankfrommelt]

Perfect, thank you!