SET_COMMAND_RESPONSE TIMER_ACK - E1.20 RDM (Remote Device Management) Protocol Forums

ericthegeek · November 2nd, 2018

Unsupported Command Class is the correct response in this case.

The automated test suites (such as the OLA Responder Test) are great tools for finding problems with your implementation. But they're not a formal compliance test, and your implementation may be just fine even if you get some "failures".

In this case, it's just telling you that you NACK'd the SET command. Yes, that's right, you NACK'd the SET and that's exactly what you meant to do. You should ignore the advisory message. That's why it's an advisory.

I generally recommend that you treat the automated test suites like warnings from a compiler. They can help you find mistakes and errors, and things you may not have thought of. But if the behavior was intentional, and you understand why you did it that way, than you can safely ignore it.

November 2nd, 2018	#18
ericthegeek Task Group Member Join Date: Aug 2008 Posts: 390	Unsupported Command Class is the correct response in this case. The automated test suites (such as the OLA Responder Test) are great tools for finding problems with your implementation. But they're not a formal compliance test, and your implementation may be just fine even if you get some "failures". In this case, it's just telling you that you NACK'd the SET command. Yes, that's right, you NACK'd the SET and that's exactly what you meant to do. You should ignore the advisory message. That's why it's an advisory. I generally recommend that you treat the automated test suites like warnings from a compiler. They can help you find mistakes and errors, and things you may not have thought of. But if the behavior was intentional, and you understand why you did it that way, than you can safely ignore it.