Justification:

The existing standard doesn’t specify how Groups are set within the DC_DIMMER_COMMAND_2. A simple way of implementing this and staying within how the standard normally functions is specifying both the Instance and Group in one message.

Submitted by Troy Roersma

Monday, July 27, 2026 | 15:17pm
Attachment Size
6.24.6 DC dimmer Command 2 .docx 21.09 KB
You must be logged in to comment. Log in
2 comments

Martin Perlot Member for 11 months

OBJECTION

More explanation is needed here.   I suggest writing a full description of the desired scheme and inserting it after the DGN table (but before table 6.24.6c) - that would give you much more room.  The description should include a full explanation of how this idea could be used to add (and also subtract) instances from a group.  It should also describe how errors should be handled (e.g. either the instance or the group is invalid).

Beyond the readability issue, I have another concern.  There should be some sort of discovery process - a way for a device or tool determine whether a specific instance belongs in a particular group.  This could be as simple as creating a new command code (byte 3) and defining the appropriate ACK/NAK response.

Lucas Salviano Member for 3 months 1 week

Considering Martin's concerns (some of which I also share), as suggestion you can add: 

  • Send Instance with a valid value (1 to 250) and Group as 00000000b removes the device from all groups and node groups.

Also, to verify the current Group configuration of a device you can use the Information Request DGN (0xEA00) asking for the desired status DGN (adding a note about this might also be a good idea).