I'm trying to implement an application using the Events & Actions interface. I have some "virtual" appliances running, based on software which supports the Events & Actions interface:
- my own test application
Currently I'm also using the android example Event_Action_Browser, but I intend to reimplement its functionality in my own application. I am looking for a way to quickly discover all objects which support Events & Actions. The sample app simply discovers all devices on the network, and then recursively introspects all available objects. Clearly this is not an optimal solution.
I've thought about discovering only objects which are advertised as supporting org.allseen.Introspectable, but I've noticed that ACServerSample advertises this interface, while lighting_controller_service does not. Is this advertisement is redundant in ACServerSample, or missing in lighting_controller_service?
The Events & Actions Guide mentions this issue and comments about calling GetDescriptionLanguages to check for this feature. Unfortunately this is of little use, since I still need to query every object on every device.