Closed generalk25 closed 3 years ago
Try referencing sensor.vacuum? I have already put these into attributes for easy reference in the LL card and automations.
I can't reference it anymore. Since the integration of rest980 the others just show unavailable all the time.
It's kind of irrelevant anyway since yours gives much more info.
I'd prefer to use yours. You stated you already put them up for easy reference. I see them visually on the lovelace card but i'm not sure how i'd poll their state for an automation.
Let me clarify, my integration also has a sensor.vacuum!
It's in the vacuum.yaml file
Oh, neat let me give that a try, thanks jeremy.
It worked great, thanks.
On Wed, Jun 23, 2021 at 7:54 AM Jeremy Willans @.***> wrote:
Let me clarify, my integration also has a sensor.vacuum!
It's in the vacuum.yaml file
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jeremywillans/ha-rest980-roomba/issues/28#issuecomment-866809593, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUELHUDVWNBWIOXRV6PQ76DTUHKPLANCNFSM47FVZ6JA .
referenced sensor.vacuum
pilotak/homeassistant-attributes
I'm using the above from HACs to display attributes of entities as their own entities.
It's worked fine till i tried to extract attribute states from your rest980 app. The sensor shows things as a subset of attributes and i have no idea how to reference them.
Normally we'd do the following....
However, now that we're doing rest980 instead of the standard roomba integration.. i have no idea how to reference a nested attribute.
And that sure as heck doesn't work.
Nor this.
Nor this.