DOP2 structure interpretation disagree with (some?) devices from MieleRESTServer #1
Description
Hi,
I'm the author of the original MieleRESTServer -- nice project you started, and glad to see that reversing of the DOP2 protocol is gaining traction.
I am surprised that your code departs from some of the DOP2 attribute IDs that I thought were constant across devices, however. Your code is looking for a program list at 14/1570. All devices I have seen during development have the SuperVisionList at that node, which is why MieleRESTServer does not even attempt to decode 14/1570 as a program list. I'm not sure if that's a bug, or if you have any examples of a device that uses 14/1570 for the program list -- if you do, could you send me a dump of their DOP2 tree?
I also have never seen a device that has any string list (or anything) at 14/2570. Could you send me a dump of one of the DOP2 tree for these so I can include decoding of this structure in MieleRESTServer as well?
Cheers.