Helper (combine two values) cannot be selected as temperature entity in integrations, why?

vghgvbh · October 13, 2024, 6:12pm

I’d like to use a helper, that combines 6 zigbee temperature sensors and shows the lowest temperature amongst them. So that I can use that helper later in an automation. The helper works great and I can show it’s value in Graphs etc.-

The problem I have is, that I cannot select said helper as a temperature entity within an automation. It’s just not selectable within any blueprint or integration, that asks for a temperature sensor.

How can I change that?

Edwin_D · October 13, 2024, 6:18pm

It is probably the blueprint that uses filters to limit choices. The blueprint creator should be the one to fix it. It is impossible to know why your entity is not included without knowing how the blueprint is filtering.

You go on to name integrations and automtions as well: which integrtion are we talking about? Automations can be made on any entity, so that is unlikely.

vghgvbh · October 13, 2024, 6:27pm

Thanks for your fast reply!

I just uploaded a picture in the main post.

The configuration of the helper is shown in the top,
and the most important integration for my endeavor (Better Thermostat) is shown below, where I cannot select it as choice.

EDIT:
I found an Issue on GitHub with Better Thermostat, that describes my Issue and a possible solution.

github.com/KartoffelToby/better_thermostat

device_class=temperature filtering prevents selecting helpers for external temperature/humidity sensors

opened 09:23AM - 30 Nov 23 UTC

PabloCamp0s

new bug

### Prerequisites * [ ] Model name of your Devices * [ ] Output from Home As…sistant Developer Tools state e.g. * [ ] Output from Home Assistant Device Diagnostic from BT ### Description [This commit](https://github.com/KartoffelToby/better_thermostat/commit/a901b8227bfe2eecc0a487882869505b66d61f38) added a filter for external sensors using device_class. Although makes perfect sense, filtering by device_class actually breaks selecting a helper sensor instead of a temperature/humidity one. In my specific case, I group several sensors in the same room and use a min/max sensor configured with mean calculation for the final room temperature. With this commit, I cannot create new thermostats. As a workaround, I've added to the helper the "device_class: temperature" and "device_class: humidity" with the developer tools just before provisioning the new thermostat, but this assignment doesn't last. Unfortunately, Home Assistant does not allow to define a device_class attribute for helpers. ### Steps to Reproduce 1. Create a helper with min/max integration grouping temperature or humidity sensors. 2. Add a new thermostat and use the external temperature sensor selector. **Expected behavior:** The helper should be as an option in the selector. **Actual behavior:** The helper does not appear. ### Versions HA: Core 2023.11.3, Frontend 20231030.2 BT: 1.4.0 ### Additional Information Until Home Assistant provides a definition for device_class attribute when creating a helper, the quick fix should be removing the device_class filter. As an alternative, perhaps adding a checkbox alongside the selector in order to enable/disable the filter by the user. I don't have the knowledge for creating the checkbox and manage it accordingly and creating a pull request removing the filter with no previous discussion doesn't sound good either. Therefore, the issue seemed to be the best approach. Thanks in advance.

But I don’t understand the solution yet, as I’m too new to this whole homeassistant.

Didgeridrew · October 13, 2024, 6:43pm

I think the “Combine…” Helper should apply the correct device class to the resulting sensor as long as all the source sensors share the same device class.

Using the States tool, check that your source sensors all have an entry for device_class in the attributes column and that they are all temperature. If any of them lack a device class or have the wrong value, you can fix it in your configuration.yaml file using Manual Customization. If that doesn’t work, or they all already have device class properly set, manually add a device class to the combined sensor.

vghgvbh · October 13, 2024, 6:52pm

It doesn’t seem to matter much.

I also created the helper anew to test, if it creates the device_class.

Didgeridrew · October 13, 2024, 6:54pm

Then manually add the device class to the combined sensor entity.

vghgvbh · October 13, 2024, 6:59pm

Am I doing the syntax right?

I go to configuration.yaml and add:

homeassistant:
  customize:
    sensor.kombisensor_minimale_aussentemperatur:
      device_class: temperature

Didgeridrew · October 13, 2024, 7:00pm

Yes, save the config and then restart Home Assistant.

vghgvbh · October 13, 2024, 7:20pm

It worked! Thanks!

I added the following code to the configuration.yaml


homeassistant:
  customize:
  
#Helper als Temperatursensoren  

    sensor.kombisensor_aussentemperaturen:
      device_class: temperature
    sensor.kombisensor_minimale_aussentemperatur:
      device_class: temperature
    sensor.kombisensor_innentemperatur:
      device_class: temperature

#Helper als Feuchtigkeitssensoren        
      
    sensor.kombisensor_innenluftfeuchtigkeit:
      device_class: humidity
    sensor.kombisensor_feuchtigkeit_fenstersensoren:
      device_class: humidity
    sensor.kombisensor_aussenluftfeuchtigkeit_in_prozent:
      device_class: humidity

I can now select the helpers in the integration: