@russ thanks for that suggestion though I may wait to see what you come up with.
The TRIGGERcmd Command does work, even if a bit clunky but maybe I'm just not using it correctly.
In any case I don't plan to use this temperature call often as I do have the read out in HomeGenie.
Yesterday I did a clean up of my HomeGenie disabling things I thought I no longer needed. After this I tested my Panic Alarm and discovered there were a few things required that I had left out. These may have been set by default with the initial install of HomeGenie.
Besides the Demo-Toggle Door having to be enabled the Virtual Modules Demo program must also be enabled.
As well the Automation.Demo 2 "DoorSensor" need to have the options to "Use as security sensor" and "Also trigger when armed Home" checked.
The Automation.Demo 2 "DoorSensor" has to be in the closed condition prior to arming the security widget or you will need to send 2 panic calls
@thibou-justin, yea the first time you ssh into a remote box, it will ask prompt you to accept the server's fingerprint. If you hadn't done that first, that might be why the command wasn't working.
You definately do need root's local public key (id_rsa.pub) in the remote pi's authorized_keys file though. You could put it in root's or pi's authorized_keys file depending on which user you want to be able to login as on the remote pi.