You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can manually create an entity for each of the data points and use them (i.e. click on the cockwheel at the end of the line and enable "loveace" there). Looking at your example, that probably is the best course of action. Another option is using the markup card and iobroker bindings. Depends a bit on what you want to do in your UI.
Generally: If a device does not fit into the iobroker device categories, feel free to suppose a new type in iobroker.type-detector. After a new device is added there, I can check if there is anything similar in HomeAssistant that the device can be mapped to and add support for that. Or I can use the device type-detector detecs and create single entites from it with the right settings. Otherwise and "automated" detection and creation of entities would not be very useful, because you could not configure them (currently).
You can also check the other way around: is anything that you request possible in HomeAssistant? If not, the lovelace UI does not have support for it and creating entities for it is also not very possible and you'll have to build your own UI anyway. So you can just do that from multiple entities and automated creation would not add a lot of benefit.
Is your feature request related to a problem? Please describe.
I created a device by assigning a function and a function to a folder. I would like to use this entity in Lovelace for a custom card.
Describe the solution you'd like
Info objects as entity in Lovelace.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: