Attributes vs sensors

[Stutchbury]

First, thank you for this integration - exactly what I need.

In HA (2024.10) I was trying to create a Dashboard Badge that only appeared 2 days before the recycling was due but it appears that 'attribute:' is not used in dashboard conditions, so having read the (wrong) conditions docs, I raised an issue.

It would appear UI conditions have a different set of docs and one of the replies suggests HA developers are moving away from attributes towards sensors. It kinda makes sense to me if attributes remain as config values and runtime values become sensors.

Eg 'next_collection' and 'days' become sensors but not sure about 'colour'?

colour: red
next_collection: "2024-10-09"
days: 6
device_class: bin_collection_schedule
icon: mdi:trash-can
friendly_name: Recycling

Thoughts?

[robbrad]

I like what your saying

Can you provide a versus example ?

I'm not quite understanding or finding it hard to picture what this looks like

Thank you

[Stutchbury]

I'm not quite sure what you mean by a 'versus example' but it is possible to emulate a 'sensor' by creating a template based on an attribute (in configuration.yaml):

template:
  - sensor:
      - name: "Recycling Days"
        unit_of_measurement: "Days"
        device_class: "duration"
        state: "{{ state_attr('sensor.ukbins_recycling', 'days') }}"

This 'Recycling Days' sensor will now appear as an entity in the drop down list in the 'VISIBILITY' tab on Dashboard badges and cards:

Without the template you would only be offered 'ukbins_recycling' in the drop down but of course the state of ukbins_recycling is not a numeric value so will always fail.

This is the yaml for that card:

type: entity
show_name: true
show_state: true
show_icon: true
entity: sensor.ukbins_recycling
color: ""
visibility:
  - condition: numeric_state
    entity: sensor.recycling_days
    below: 2

In the conditions section, you'd expect to be able to add an 'attribute: days' line (as you can in conditions elsewhere in HA) but this is not the case.

I can understand the 'sensors are runtime values vs attributes are config values' but have no idea how it would be implemented in code!

Hope this helps - happy to keep 'helping' :-)

[robbrad]

This does help thank you.

What I meant by versus example is - do you know of another custom comp that does it like this

Something to compare to in the code.

I'll also do some research

[Stutchbury]

Ah, yes - but no, sorry. This is the first custom integration where I've tried to use the Dashboard visibility. I really need to find out more about coding HA - my scratch to itch is a programmable thermostat but life keeps getting in the way.

[robbrad]

Hey @Stutchbury - I have been working on this for you and I think I have what you want, but im well aware this is going to break a few peoples automations.

If you could let me know if this is what you wanted - note there are now no attributes

@dp247 - FYI

[Stutchbury]

Oh wow! Wasn't expecting that! Presumably entities that have been migrated from attribute are now classed as 'sensors' by HA? Which means they now show up in the 'Visibility' tab on the Dashboard? Apologies for the questions - I would test but unfortunately bricked my test system (a lovely fanless NUC) trying to update the BIOS!

I think this is probably the way to go as my ticket was classed as a Feature Request, not an Issue. I'm not sure if the original ticket will be acted upon as there's not yet an answer.

Other than the 'backwards incompatibility' with existing automations, it will allow less experienced users to use easily the 'Visibility' conditions - always a win.

Would be good to find some clarification (rather than hearsay) from the core developers on the attribute vs sensor question.

Thank you Robert.

[robbrad]

Your welcome

FYI mentioned PR isn't merged yet.

I have also fixed a few other things in the PR

Added Welsh/Gaeilge and Gaelic to the translations

And best of all I added the ability for users to set the icon and colour of the bin sensor based on a mapping json they provide on setup of the component. This maps to the bin type allowing configuration

[robbrad]

#907

[Stutchbury]

That is a fair bit of work, thank you! I like the idea of the colour coding as it will hopefully mean the 'badge' can just be appropriately coloured bin icon(s)! A reminder at a glance until HA provides an automated way to take the bins to the kerb :-)