There is a lot to unpack when using Allonis Nested replacement server variables. There is a double substitution going on here. You can learn alot by going to the Allonis Dashboard, selecting "Management", then "Server Variables". The server variable names that actually exist will be listed, along with their values.
For the beginner, I would recommend substituting the actual and complete variable name, without using any Allonis nested "replacement" variables. After you get the hang of it, you can go back and put back in the "replacement" variables (I have chosen not to, because I do not need the complexity. Allonis uses those variables for larger environments that have multiple remote controls, and mutiple rooms with equipment.
This is the macro (I call "hs_run_event") I use to run a Homeseer event:
GetUrl|http://192.168.0.80/JSON?request=runevent&groupname=
&name=
<p1> and <p2> are macro parameters. I then run this statement, in a button for example, to invoke the FamilyRoomLeft event in group Lights:
Macro|hs-run-event|Lights~FamilyRoomLeft!
Homeseer has a lot more JSON input command options you can also use.
To send a command to Allonis, the URL you would use would be
http://192.168.0.65/api/docommand?command=
This assumes of course that both Homeseer and Allonis are on the same LAN.