Is your feature request related to a problem? Please describe.
When we have multiple plates configured in the same home automation system, there are many things which are displayed the same on all the plates. Currently you have to configure these things one by one for all the plates.
Besides increasing the network traffic, it also makes it harder to maintain whenever something has to be changed - one has to manually change the same thing in all places.
One good use case is the weather example but also basic stuff like clock and temperature in the headers.
Describe the solution you'd like
Very simply add an extra dedicated config file like group.yaml to the CC configuration directory, with the group topic of the plates set as slug. An exception here that there's no discovery, this has to be added without discovery.
One may have multiple group topics configured (say 1st floor rooms, 2nd floor rooms) so it would be probably useful to handle multiple such configs (multiple slugs) within that file.
Also would be nice to have a stripped down entity for the pseudo-platee (no switches/pages etc, only reset and antiburn) so that services could be run against this - run commands on all the plates on the same group topic.
Describe alternatives you've considered
Achieving the same is only possible with automations outside CC, which make things a bit more complicated as they need triggers.
Is your feature request related to a problem? Please describe. When we have multiple plates configured in the same home automation system, there are many things which are displayed the same on all the plates. Currently you have to configure these things one by one for all the plates. Besides increasing the network traffic, it also makes it harder to maintain whenever something has to be changed - one has to manually change the same thing in all places. One good use case is the weather example but also basic stuff like clock and temperature in the headers.
Describe the solution you'd like Very simply add an extra dedicated config file like
group.yamlto the CC configuration directory, with the group topic of the plates set as slug. An exception here that there's no discovery, this has to be added without discovery. One may have multiple group topics configured (say 1st floor rooms, 2nd floor rooms) so it would be probably useful to handle multiple such configs (multiple slugs) within that file. Also would be nice to have a stripped down entity for the pseudo-platee (no switches/pages etc, only reset and antiburn) so that services could be run against this - run commands on all the plates on the same group topic.Describe alternatives you've considered Achieving the same is only possible with automations outside CC, which make things a bit more complicated as they need triggers.
Additional context N/A