Closed sjabby closed 4 years ago
Same error here, do you need more info ?
well that's really a tricky one, would need to find out how to avoid "marking" entities as used. because it looks like the "unused entity" thingy within HA is applying some magic to find out if a certain entity was "used". flex-table "uses" all for filtering....
despite that the fact that the unused entity is not working without any non-used entities seems like a HA bug to me
Got the same issue I think
Using this to display train times and towards the end of the day, when there are no more trains and so no data for the table, everything goes blank as the data set is empty! I wonder if a way to end something to my list potentially that forces a “no more today” value so at least something for this table to use?
Your issue is likely not related to this discussion, you are looking for an empty data behavior, right? Not yet available, added an issue #12 to remind me the next time I am looking into it.
sorry, i just confirmed, my issue is the same as this one. when i use the following on a page, i lose the "unsued entitles" option.
- type: 'custom:flex-table-card' title: xxx to xxx Trains max_rows: 10 entities: exclude: null include: sensor.next_train_to_xxx columns: - align: center attr_as_list: next_trains modify: x.status name: status - align: center attr_as_list: next_trains modify: x.scheduled name: scheduled - align: center attr_as_list: next_trains modify: x.estimated name: estimated - align: center attr_as_list: next_trains modify: x.platform name: platform - align: center attr_as_list: next_trains modify: x.destination_name name: destination
was digging into that due to #25 + #27 and found out that lovelace does the unused entities computation (amongs other options) by simply iterating over .entities
of each card, thus assuming it is an Array. The very same reason this issue was opened. So this PR solves the issue. Means I would expect this issue here to be fixed with the next home-assistant/lovelace release.
On the other side the entities used by flex-table-card
will then not be accounted as "used", this is by-design also not possible as far as I understand: lovelace is parsing the configuration as of my understanding. Will have to do more tests, but at least overall the unused entities view will work again soon!
further discussions confirmed the statements above and I've found a similar issue here . So looks like this is not possible by-design, which is understandable as this would lead to the evaluation of all lovelace cards in order to determine the unused entities, which is quite inefficient if not waste of compute time. means: wont'fix ...
With this config added:
The Unused Entities view in lovelace does not work. (page is just blank) Gives this error in console: