While trying to diagnose some “unavailable” entities associated with my Rivian, I’ve noticed that there are also two entries (which it calls “hubs”) for the vehicle. One has 131 entities and the other has 12. Almost all of the 12 have to do with OTA updates for the vehicle, but the other “hub” has some OTA entities, too.
I’m wondering if this is all from a botched install and if I should maybe completely remove it and re-install, but I’d like to hear from others if this is just how it’s supposed to work.
Also, on a slightly broader topic: How are we supposed to handle when an integration stops providing data for an entity. It seems that those entities are merely labeled “unavailable”, so it’s unclear if that’s because there’s momentarily no data available or if the integration has deliberately stopped providing it. Is there a way to tell when an entity has be end-of-life’d?
Full disclosure: I had never heard of this Rivian integration before reading your post. Any advice is purely based on searching on google.
Are you sure the entities say unavailable & not unknown? If so, it’s probably related to this issue which seems to be still being worked on.
Ah, yes. That bug hit me, too. I’ve already manually applied the fix they’re talking about in that thread. I think that bug causes the whole integration to get flagged as having an issue, so I don’t think it’s that problem, again.
To answer your problem, directly, it’s a mix of Unavailable, Unknown, and valid values.
Just to follow up, I ended up deleting both “hubs” from the Rivian integration (which caused it to disappear from Integrations) and then re-downloaded the Rivian integration from HACS, and then created the Rivian instance, again, and now I have a single “hub” with all 141 entities.
1 Like
