Eakin

I don't think the the problem is with messages that respond to specific commands. Instead, they look like some sort of debug, or erroneous messages leaking out. If you look at the extended message with the command of 0x88 from the Brian's post, The D1, D2, D3 and D4 look like some sort of counter, or clock. Shown here: They seam to count from 0x73CA to 0x7B46. On my machine, I got the count up to 0x1A5AA5. Would it be easy to just ignore the Extend message with a command of 0x88?

I wrote a C# program to read to query configuration of an ISY99 via the services API, with the 2.8.8 firmware, and it worked great. Now that I've upgraded to 2.8.10, there are the following new controls, that are not defied in the /WEB/udiws20.ws spec: UOM. CPW, TPW, and Reset. Which causes the response parser to error out. Is the udiws20.ws document supposed to be updated when new services are added? Also, is there a workaround for Dev Studio, where I edit the file on my hard drive, and update the protocol? -- Yes, edit the file, and use file://C:/projects/udiws20.ws as the source.