Macros branch updated. Here’s the doc info for this new feature:
Macros are a more powerful alternative to automation than the RULE system
provided by the Tile Customizer. With Macros you can string together any number of action calls that HousePanel supports and connect it to any field on any tile. The catch is there is no GUI for defining Macros (yet). Macros must be hand-written and saved in your hmoptions.cfg file, so this is a feature only for power users. Macros are defined in a section of the hmoptions.cfg file called “macros”. That section looks something like:
"macros":{ "custom|custom_4|test": [ ["-","adcd1-12345-4a33-c111-11223ea123","switch","switch","toggle"], ["-","dcba9-54321-4cda-a222-223344abcd","switch","switch","off"], ["-","dcba9-26371-5cda-b333-65432abcda","switchlevel","level","on","60"] ] }
The keys are a string composed of the type, the id, and the field, separated by the “|” symbol. The type|id pair is the “connected tile” that is used to trigger the macro. This should be one of the tiles listed in the “index” section of the hmoptions.cfg file. The field specified is the field that is clicked on to invoke the macro. An array of arrays follow. Each array entry has up to 6 fields. The first array element is the hub id. If “-” is entered, the hubid of the connected tile is used. The second element is the id of the thing to automate. The third element is the type of thing. The fourth element is the field to control. The fifth element is the command or value to pass to HP.
For example, it could be “on”, “off”, “open”, or “close”. A sixth element is attribute that is sent for some tiles to be controlled. For example, level can be sent this way.
Any number of macros can be defined and they can be tied to anything, including custom fields as is shown in the above example. The only restriction is they cannot be mixed with RULE custom fields.