Add websocket list APIs for the registries #16597
Conversation
ghost
assigned 
| msg['id'], [{ | ||
| 'config_entries': list(entry.config_entries), | ||
| 'connections': list(entry.connections), | ||
| 'identifiers': list(entry.identifiers), |
There was a problem hiding this comment.
Are connections and identifiers really relevant to expose to the Gui? Config entries I can understand to tie be able to tie them together in some hierarchy but the others are mostly internal usage.
There was a problem hiding this comment.
Good point, little too eager!
There was a problem hiding this comment.
Actually connections could be beneficial? you can see mac address etc ?
There was a problem hiding this comment.
If we want to expose connections and identifiers we need to up our game and standardise what can be a part of them. Right now it is not concrete enough.
There was a problem hiding this comment.
Well if we do expose connections we can just as well keep identifiers as well.
There was a problem hiding this comment.
haha.
Look, connections is actually standardized to an extend:
Description:
This adds two APIs: one to list the device registry entries, one to list the entity registry entries.
Meant to power a frontend for devices 馃憤
CC @Kane610
Checklist:
tox. Your PR cannot be merged unless tests passIf the code does not interact with devices: