Once a command is created and executed successfully against a device, you can then save it in the app for use later. Unfortunately the command I created in the above screen didn’t execute on any of my devices.
Here is a command I was able to save, this is for a Figaro RGBW controller. When executed this command sets the controller to a built in color cycle that @twack exposed in the custom device type.
No that’s not what I was after. This app is for harvesting and testing device commands on devices without having to write a dedicated app to do so. In all likelihood it will be in a future release of @bravenel s rule machine.
The available commands are now parsed and available to select for testing and saving if desired.
There’s also a base device type to select from (just in case your device doesn’t have capability actuator)
–select base device type
–select the test device
–new custom command
–available device commands shows all commands the device is capable of
–configure the parameters (if any)
unless the command failed, you can optionally save the command, if saved, the command will available on the main page for future use with other devices.
@pstuart and I had a pretty good time messing with this and his HTML hacks on LCF tonight.
And an additional bit of disclaimer here.
This app will expose methods for devices that do not have published device types, meaning device types that ST has elected not to publish as examples in the IDE.
Experimenting with exposed methods that you don’t have the code for is at your own risk.
So, should you find a method somewhere called selfDistruct(), you might want to pause (or at least run like hell) when executing it.
Make the request to Bruce, I’m currently running a modified version with the custom command code in it for rule and trigger. I think with more interest (other than just me bugging him) he may make it a higher priority.