Page History

...

Since this information is configured as fugitivetransient, it is not necessary to reset the piloting it to 0. This implies that the Status Point plugin must be placed before the transient plugin in the sequence of south plugins.

...

 {
	"label" :"GAMBS_0_TS-SYST_ACCESPRT.INFA",
	"pivot_id" :"xxx",
	"pivot_type" :"SpsTyp",
	"pivot_subtypes" : ["prt.inf"],
	"protocols" :[
	   {
		  "name" :"hnzip",
		  "typeid":"yyy",
		  "address":"zzz"
	   }
	]
 }

...

Currently the plugin types available in Fledge (Filter, Notification Rule et and Notification Delivery) do not offer these functionalities in a single plugin:

...

Notification Rule plugins allow to send Notification messages (not Readings) when as an asset was modified and a predefined set of rules is matched by this asset (so no free Reading creation).

...

• A Notification Rule plugin (fledgepower-rule-systemsp) responsible of scanning the Readings flowing through Fledge and generate a Notification when a relevant event occured.
• A Notification Delivery plugin (fledgepower-notify-systemsp) responsible of:
  • Receiving the Notifications from the other plugin, create new Readings based on the data they contain in if necessary, and send those through Fledge.
  • Run cyclic task that will send a Reading through Fledge at regular intervals.

Here the Notification Rule plugin is used to detect changes in readings of type "south_event" and send a notification when a Connection Loss Status Point should be created containing the type of event it represents ("connected / not connected" / "connection lost").

The Notification Delivery plugin is used to send Access Status Point Readings periodically based on the exchanged_data configuration and to send Connection Loss Status Point Readings when receiving a notification from the Notification Rule plugin.

Notification structure:

 {
	"asset": "prt.inf",
	"reason": "connected" // or "connection lost"
 }