HTTP Activity & Device Command Interface

With v9 is there an updated API doc? with HTTP device commands I’m getting {“da”:“BadParams”,“st”:“fail”,“me”:“Missing command array”,“co”:400} vs the previous success and code 200. Thanks

Same here

The error message I receive is “Missing au parameter”

An updated API guide (HTTP Activity & Device Command Interface) would be much appreciated please.

Same here!
I’m glad I’m not the only one.

This document has now been updated. The names of properties were all shortened:

You will need to make trivial updates to any of your call sites from things like “activity_uuid” to “au” as per the updated interface document.

2 Likes

Thank you Will especially for the quick turnaround. In retrospect “au” being short for activity_uuid seems obvious now :smile:

FYI It looks like “device” is still needed for the device uuid vs “du”

DEBUG-->strSimpleControlString: { "cs" : [ { "ty" : "command", "pa" : { "cm" : "MUTE TOGGLE", "du" : "54D05999-97C4-467B-85C5-721955087475" } }] }
DEBUG-->strURL: http://192.168.1.120:47147/api/v1/sendcommands
DEBUG-->strReturn: {"da":"BadParams","st":"fail","me":"Missing device uuid","co":400}

DEBUG-->strSimpleControlString: { "cs" : [ { "ty" : "command", "pa" : { "cm" : "MUTE TOGGLE", "device" : "54D05999-97C4-467B-85C5-721955087475" } } ] }
DEBUG-->strURL: http://192.168.1.120:47147/api/v1/sendcommands
DEBUG-->strReturn: {"st":"success","da":{"se":"38855C76-90E1-43A9-BDD3-8F2F31C9249C"},"co":200}

Fixed.