User Manual

82
expressions will be replaced by the relevant content before the Agent/Client sends a notification to the SMS
provider.
e.g.
URL: http://send-sms-company.com/sms
POST Body: user=xxxxxx&password=xxxxxx &to=EVENT_ACTION_PHONE_NUMBER
&text=EVENT_ACTION_MESSAGE
 Service provider accepts HTTP GET to sends messages:
This specification from the SMS provider is required before using the HTTP GET method. Select the Using HTTP
GET option at the Service Provider field. Insert the EVENT_ACTION_PHONE_NUMBER as recipient's mobile
phone number and the EVENT_ACTION_MESSAGE as event message's content described in the specification,
and fill in the URL field. The expressions will be replaced by relevant content before the Agent/Client sends a
notification to SMS provider.
e.g.
URL: http://send-sms-company.com/sms?user=xxxxxx&password=xxxxxx
&to=EVENT_ACTION_PHONE_NUMBER&text=EVENT_ACTION_MESSAGE
 Service provider accepts E-mail to send messages:
This specification from an SMS provider is required before using the E-mail to deliver the messages to SMS
providers. Select the Using E-mail option at the Service Provider field. Insert
EVENT_ACTION_PHONE_NUMBER as recipient's mobile phone number and the EVENT_ACTION_MESSAGE
as event message content described in the specification. Fill in the Address, Subject and Content fields. The
expressions will be replaced with relevant content before the Agent/Client sends a notification to the SMS provider.
e.g.
Address: [e-mail]
Subject: xxxxxx
Content: user:xxxxxx
password:xxxxxx
to:EVENT_ACTION_PHONE_NUMBER
text:EVENT_ACTION_MESSAGE
Note: Each message sent by the SMS system through the SMS provider will be subject to the SMS provider fee.
Logs
Event Logs
Logs/Event Logs page lets you view logs that record power event details in the Agent or the Client. The logs can be
analyzed to determine whether the system and the power device are operating correctly.