Version 9.2.0 introduces 2 new commands to the Local Control interface.
The updated documentation is here.
The first new command is just a simplified syntax for activity execution that is easier to run from a browser or some other device that doesn’t handle the body json syntax.
The second new command takes advantage of our new support for audio media files and plays a sound on all active controllers. This can for example be used to create a doorbell or various other intercom scenarios.
Enjoy!
Excellent! Thanks, Will.
Any hope for being able to get/poll a room’s current activity? That would be quite powerful!
What is the use case for that one?
Thanks, Will. Like that the API is getting some attention. Might want to give the docs a review as I note a few issues. Looks like a copy / paste error for the introduction to the Run Activity section. Also, the simplified syntax for running the activities documents the syntax as a POST but the example shows a GET. I assume the correct approach is what the example shows.
The main thing that comes to mind:
Pushing current activity state for each room to a 3rd party automation controller (Indigo in my case) so Indigo events / triggers are aware of activity state and could conditionally trigger based on source (or if we’re really getting fancy… content, muted/not muted, etc.) Likely useful for other platforms too. Thx.
Fixed.