Queued Message for SubDevices - E1.20 RDM (Remote Device Management) Protocol Forums

sandor · May 13th, 2018

Hello,

I want to add the queued message handle for my dimmer system but as I see in the standard the queued_message_get is addressed only for the root device. If one of my sub-device have message to collect do I simple reply with the corresponding PID and modify the sub-device field in the reply message?

Sandor
www.pls.hu

sblair · May 13th, 2018

Yes, that is correct. The intent of this is to reduce the amount of polling needed so QUEUED_MESSAGEs are sent only to the root device and the response can be either from the root or the sub-device by setting the Sub-Device field accordingly in the response.

sandor · May 14th, 2018

Thank You Scott!

zano_villa · January 20th, 2026

Hello,
just about QUEUED and STATUS MESSAGES.
Explicitly in ANSI1.20-2025, it is written that the Message Count field in QUEUED MESSAGES defines the number of messages, excluding STATUS MESSAGES, that are queued in the responder.
Does it mean that STATUS MESSAGES can not queued like any other message, but they can be delivered to controller only as the last message of the queue, or otherwise by the specific STATUS_MESSAGE PID?

sblair · January 20th, 2026

I believe that the correct intent is to collect all the queued messages first and then after that you'll receive any status messages. If you determine it is more important to return a status message first, I don't see anything that prevents you from doing that. They key thing is that you wouldn't change the Message Count since that is only counting queued messages not including status messages.

zano_villa · January 21st, 2026

Hello,
about STATUS MESSAGE IDs definitions.
In RDM standard I see that DataValue1 & 2 shall be integers, but I would need to show voltage and current with decimal digits.
Is it possible in any way?

Thank you

ericthegeek · January 23rd, 2026

You can use the "Prefix" field of SENSOR_DEFINITION.

For example, if you need to display 6.3 volts, then you can use PREFIX_DECI in SENSOR_DEFINITION and return the integer 63 in SENSOR_VALUE.

Depending on how much precision you need, you could also use PREFIX_MILLI and return the integer 6300.

When using prefixes, it's up to the controller's User Interface to determine how to display the data. For my second example, the controller might display "6300 mV", or it might display "6.300 V". Or it might let the user configure how the data is displayed.

ericthegeek · January 23rd, 2026

Should have read more carefully - you're asking about Status Messages, not sensors.

Status messages use printf()-style string substitution. You can include the prefix in the string returned by STATUS_ID_DESCRIPTION.

Example: "Output range is %d mV"

May 13th, 2018	#1
sandor Junior Member Join Date: May 2018 Posts: 4	Queued Message for SubDevices Hello, I want to add the queued message handle for my dimmer system but as I see in the standard the queued_message_get is addressed only for the root device. If one of my sub-device have message to collect do I simple reply with the corresponding PID and modify the sub-device field in the reply message? Sandor www.pls.hu

May 13th, 2018	#2
sblair Administrator Join Date: Feb 2006 Posts: 441	Yes, that is correct. The intent of this is to reduce the amount of polling needed so QUEUED_MESSAGEs are sent only to the root device and the response can be either from the root or the sub-device by setting the Sub-Device field accordingly in the response. __________________ Scott M. Blair RDM Protocol Forums Admin

January 20th, 2026	#5
sblair Administrator Join Date: Feb 2006 Posts: 441	I believe that the correct intent is to collect all the queued messages first and then after that you'll receive any status messages. If you determine it is more important to return a status message first, I don't see anything that prevents you from doing that. They key thing is that you wouldn't change the Message Count since that is only counting queued messages not including status messages. __________________ Scott M. Blair RDM Protocol Forums Admin

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Response to GET:QUEUED MESSAGE when NACKing query	prwatE120	RDM Interpretation Questions	3	February 24th, 2016 05:33 PM
What NACK to use for messages sent to Subdevices ?	prwatE120	RDM Interpretation Questions	0	February 24th, 2016 05:08 PM
Status Message Markers	hamish	RDM General Implementation Discussion	4	December 9th, 2010 11:12 PM
Personality & Subdevices	kocurr	RDM General Implementation Discussion	1	July 8th, 2008 09:30 PM
ENTTEC RDM controller (subdevices)	nic123	RDM Marketplace Discussion	3	October 24th, 2007 12:03 AM

May 14th, 2018	#3
sandor Junior Member Join Date: May 2018 Posts: 4	Thank You Scott!

January 20th, 2026	#4
zano_villa Junior Member Join Date: Jan 2014 Location: Treviso, Italy Posts: 21	Hello, just about QUEUED and STATUS MESSAGES. Explicitly in ANSI1.20-2025, it is written that the Message Count field in QUEUED MESSAGES defines the number of messages, excluding STATUS MESSAGES, that are queued in the responder. Does it mean that STATUS MESSAGES can not queued like any other message, but they can be delivered to controller only as the last message of the queue, or otherwise by the specific STATUS_MESSAGE PID?

January 21st, 2026	#6
zano_villa Junior Member Join Date: Jan 2014 Location: Treviso, Italy Posts: 21	Hello, about STATUS MESSAGE IDs definitions. In RDM standard I see that DataValue1 & 2 shall be integers, but I would need to show voltage and current with decimal digits. Is it possible in any way? Thank you

January 23rd, 2026	#7
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	You can use the "Prefix" field of SENSOR_DEFINITION. For example, if you need to display 6.3 volts, then you can use PREFIX_DECI in SENSOR_DEFINITION and return the integer 63 in SENSOR_VALUE. Depending on how much precision you need, you could also use PREFIX_MILLI and return the integer 6300. When using prefixes, it's up to the controller's User Interface to determine how to display the data. For my second example, the controller might display "6300 mV", or it might display "6.300 V". Or it might let the user configure how the data is displayed.