Closed chicknlil closed 1 year ago
You are using a wrong definition for the “attribute” option.
Actually, I was using the wrong attribute, which I figured out by looking in developer tools -> states. Thus why I closed this. No additional comments needed. Problem has been solved.
The reason is not only in “using wrong attribute”. This definition is just wrong: “attribute: Pm 10”. This could be an attribute’s name displayed in more-info - but not a real attribute’s name.
Not sure why you're trying to be argumentative on a topic I closed because it was solved but the actual attribute was pm_10, as opposed to Pm 10, as referenced in the image. It didn't occur to me that it might be different. But again, not sure why you're being so aggressive. The problem is solved.
You completely misunderstood me, no aggression at all. I just pointed at your mistake in your 1st post - as a matter of assistance, nothing else And instead of saying “thank you” you are trying to raise your voice, not cool.
You didn't contribute to the discussion in any meaningful way, why would I thank you? The problem was solved long before you commented, and your comment wasn't even applicable. You continue to trying to make a mountain out of a molehill instead of just letting it go. For the love of all things good and holy, please STOP.
No, you are hopeless.
I've got the following sensor:
In trying to setup a card for this, it doesn't seem to know how to respond to the attribute provided (but perhaps I'm supplying it wrong?):
That makes this:![image](https://user-images.githubusercontent.com/100124187/223620880-a6611b0a-797e-4d8e-b708-e7504aead1d8.png)
Ideally, what I'm looking to do is have one (or several if necessary) cards that tells me what the "Dominentpol" is and displays it (at the moment, it's PM 25), as well as the Pm 10 and Pm 2 5, all of which are attributes.
Am I doing this wrong?