The origin of the Last Gasp is normally a modem or concentrator. Currently we support the MOL last gasp modem (via MQTT) and the Riecktron last gasp modem, but we envision that many more devices can in future be used.

When adding the Last Gasp entity, you can specify to which server/s (optional) to escalate the events. This server to server messaging generally go through the central server (SlowQ), but a direct link can be created that would speed this up, by specifying:

FQ1=pnpscada.server.FasQ1
FQ11=2032:10.0.65.134
FQ12=2034:10.0.65.42

in live/Server.prp

Where FQ1 must be exactly like that, and the property names of the values underneath that should all start with FQ1 and then be followed by consecutive numbers, e.g. 1, 2, 3 etc.
The value of FQ11 etc is first the server id, and then the IP of that server from the local server.
This can be specified on both servers linking to the other.

When a meter is found, the origin server is updated with the result. You can get the gasp log with the getGaspLog.jsp API call on the origin server.

When the meter is found, a power failure meter event is inserted or ended (in the case of a power restoration). It has the value of 'gasp', thereby enabling you to identify that it is a Last Gasp power failure event.