Dan Klaffenbach

> If the discussion with the integration maintainer was done in public, maybe add link that for some more background information for others to read? The discussion is in the...

@balloob That sounds a little like the current approach in Sonos and Bluesound (and my proposed HEOS PR). What I did not really get from your point is whether you...

Is there a place like a wiki for Home Assistant development, where multiple people can add/comment pros and cons of various approches? Right now I feel like a lot have...

@JeffLIrion Regarding group volume a few things come to my mind: - I think the vast majority of systems actually have native support for group volume. We should use that....

Thanks @pvizeli for your feedback. > However, to use the group function we should just implement the approach of i.e. Sonos and let handle that with a nice UI card....

What is the workflow with this now? Any comments on my suggestion in https://github.com/home-assistant/architecture/issues/364#issuecomment-625405413? I'd like to finish my PR for grouping in the HEOS component. I have already put...

> I'm not sure I have any input on the primary issue here but unless I'm missing something the suggested spec for "grouping/ungrouping through Lovelace" might need a little more...

@Ramblurr The basic idea was that each player entity provides an attribute called `group_candidates` (see https://github.com/home-assistant/architecture/issues/364#issuecomment-625405413). Paulus suggested to leave this out in the beginning (see https://github.com/home-assistant/core/pull/41193#discussion_r556654149). So once proper...

@mimugmail The thing is that you might not always have control over the default route which is pushed to you. For example I am getting a default route from my...

@seebaerhh Did you purchase the Digibit R1 as a used device or has it ever been used with the custom satip-axe firmware before? My guess is that the network config...