I understand that state is what is tracked if you don’t select an option, but it would be less confusing if it was default, or at least listed as an option to choose here.
State isn’t an attribute though. They are separate aspects of an entity.
Well that’s also confusing. Maybe the wording could be changed to “State or Attribute of entity that this sensor tracks”
That’s not how the field works though. The field is “use an attribute”, changing the UI to be state or attribute would force a config change for yaml users as well. That’s unlikely to happen.
I see. It’s optional. But I think a lot of users will see that field and think they must choose something. I did. Maybe just some informational text here could be helpful.
Yes, I agree. Many of the optional parameters in automations are not really shown as optional. It’s always been a gripe of mine.