Unique ID not recognised?

Configuration
1

Can anyone let me know why the Unique ID isnt being picked up?

  stove_home_trv_compensation_value:
    source: sensor.outdoor_air_temperature
    unique_id: 'Stove TRV Compensated Setpoint'
    unit_of_measurement: °C
    data_points:
      - [-5, 13]
      - [15, 19]
    lower_limit: 14
    upper_limit: 45
2

That’s not the whole entry… What platform /type is that. Not all integrations support unique_id

3

Thanks for helping Nathan

Compensation… says to use unique_id

4

Ok, define ‘picked up’

Unique ID is an internal structure so that the UI knows what a device/entity is. If you’re not seeing an error i the log for that entity it’s working.

We’re you trying to define the entity_id?

That is built by slugifying (trim, lowercase, replace spaces with _) the name at creation time. Now that you have a unique ID you should be able to change the entity_id in the UI now.

5

So at the moment this is showing up as
‘sensor.compensation_sensor_outdoor_air_temperature_6’

its going to get very confusing having potentially 10 of them. I’d like to name each entity rather than having a number?

1 Like
6

Understandable, you can rename each of them in the UI once they’re pulled in. But unique_id isn’t what makes it happen it’s what allows it to be edited in the UI. Sorry. You’ll have to rename each by hand.

In fact I always use GUIDs for unique id’s because they’re not intended to be for the user.

7

OK understood thanks Nathan

1 Like