Pfau LISA alerts reach the person on duty as an SMS. SMSEagle sends them over its own cellular connection, so they don’t depend on internet access or a cloud service.
If LISA sent SMS through a GSM modem, SMSEagle takes over its role. You set it up as an SMS server in LISA IO.
SMS from LISA workflows
You add a Send SMS command to LISA workflows, so the right people get a message at the right step.
Works without internet
SMSEagle sends alerts through its own SIM card straight to the mobile network, so they don’t depend on internet access or a cloud SMS provider.
How it works
1
Create an SMSEagle API user
In the SMSEagle web interface, create the user the key will act as in System > Users, then create an API key for it on the API v1 page in Settings > Global settings > API, granting Send SMS, Send to contact, Send to group permissions.
2
Add an SMS-Server process in LISA IO
In LISA IO, add a new process of type SMS-Server with SMSEagle’s address, the API access token, and the provider this device uses.
3
Send SMS from your workflows
SMSEagle delivers the alert over its own cellular connection, not through a third-party service, as an SMS to the recipient’s phone.
Set up in about 10 minutes
Setting up SMSEagle with LISA takes just a few minutes – create an API user in SMSEagle, add it as an SMS-Server process in LISA IO, and start sending SMS from your existing workflows immediately.
SMSEagle sends LISA alerts to the right person by SMS, day and night.
No per-message fees
SMSEagle sends SMS through a regular SIM card, so you only pay for your mobile plan.
Alerts keep going if one carrier fails
On devices with two SIM cards from different operators, SMSEagle switches to the second one when the first operator’s network is down.
Alerts keep working even if one device fails
Two SMSEagle devices can work as an HA cluster: if one fails, the other takes over sending.
SMSEagle configuration
Create a new user in SMSEagle (menu System > Users, user access level: “User”).
Grant API access to the created user:
go to Settings > Global settings > API and open the API v1 page
click Create API key, fill in Key name and select the user created above as Owner
Add access permissions in section Permissions for: Send SMS, Send to contact, Send to group
click Create key. The access token is shown only once, right after saving
LISA configuration
LISA: Prerequisite for new integrations (can be skipped if replacing existing GSM Modem):
In the LISA configuration program Konfiguration.exe und “System 1”->”Provider Regeln” add a new Provider with Pooltyp “SMS”. Name them after your provider.
SMSEagle Confguration in LISA:
In LISA IO add a new Process from Type SMS-Server.
“Serveraddresse” is the IP or Hostname of SMSEagle
“AccessToken” the AccessToken of the user LISA uses to access the API.
“Provider” select the provider this device uses.
“Default Absender” and “Default Empfänger” are optional for protocolling purposes.
Sending SMS:
To send SMS you can add a “Send SMS” command to your workflows.
Explore SMSEagle Demo device
SMSEagle is a hardware & software solution that guarantees a swift delivery of your messages to designated recipients, whether it’s for notifications, alerts, or important updates.
After registering to a demo you get a remote access to our physical device NXS-9750.