Sponsored Content
Full Discussion: Send SMS to mobile
Top Forums UNIX for Advanced & Expert Users Send SMS to mobile Post 303044476 by Neo on Monday 24th of February 2020 01:48:28 AM
Old 02-24-2020
Update:

I have been doing a lot of Device / Server <--> MQTT <--> Node-RED <--> Device / Server / Mobile Phone recently.

In that work, I trying using a number of SMS gateway services; and all worked "slow" and delivered alerts between 1 and 2 minutes after the server sends the alert. Furthermore, their customer agreements (for example nexmo) say "up to 24 hours" to deliver an SMS message.

So, I switch gears and switched to sending messages using Telegram, and it works almost instantly.

Code:
Device / Server  <--> MQTT <--> Node-RED <--> Telegram <--> Device / Server / Mobile Phone

The Telegram module for Node-RED works well, although it can be a bit tricky to set up the first time (getting the chatid can be confusing); but after a short learning curve, this is a great combo:
  • Linux server Sends MQTT messages to MQTT broker.
  • Node-RED listens for MQTT topic.
  • Node-RED processes MQTT topic when received; and then,
  • Node-RED sends alert or message via Telegram to mobile phone.

This works well, and is FREE (except for your standard Internet fees, so it is no additional costs for most people).
This User Gave Thanks to Neo For This Post:
 

6 More Discussions You Might Find Interesting

1. Programming

can anyone send sms application

actually i need this sms application ,to gain some knowledge in linux platform. (1 Reply)
Discussion started by: parvathy
1 Replies

2. IP Networking

Send SMS from PC to mobile phones

Hi All, Can any expert provide me a guide on how i can send SMS from pc to mobile phone using VBA or some other language ? I am a newbie in networking. (1 Reply)
Discussion started by: Raynon
1 Replies

3. UNIX for Advanced & Expert Users

Script which will run every 10minutes and Send SMS to mobile

Hello Genuis guys, I am running Aix5 and Oracle 9 on it. I have sql query which only count a particular rows. I need to prepare a script which will run that sql query every 10 minutes and if the ouput count is greate than 20. It will send SMS to mobile numbers. Need your kind help to... (8 Replies)
Discussion started by: thepurple
8 Replies

4. Shell Programming and Scripting

Bash script to send SMS

Hey guys I was wondering how to go about creating a bash script to send SMS..any ideas are appreciated.. (2 Replies)
Discussion started by: blackzeus
2 Replies

5. UNIX for Dummies Questions & Answers

Need to set up UNIX script to send sms on mobile

Hi All, Can anyone please help in setting up Unix script for sending text messages on mobile?? Actually scenario is we want notification when there is any failures in our processes or if any service goes down we must be notified by a text message on our mobile, we already have email... (3 Replies)
Discussion started by: NikhilM
3 Replies

6. AIX

send SMS via curl

I need from aix to send an SMS, you know if the command curl serves me (3 Replies)
Discussion started by: tricampeon81
3 Replies
mosquitto_sub(1)														  mosquitto_sub(1)

NAME
mosquitto_sub - an mqtt version 3.1 client for subscribing to topics SYNOPSIS
mosquitto_sub [-c] [-d] [-h hostname] [-i client_id] [-I client id prefix] [-k keepalive time] [-p port number] [-q message QoS] [--quiet] [-v] [ -u username [-P password] ] [ --will-topic topic [--will-payload payload] [--will-qos qos] [--will-retain] ] -t message topic ... DESCRIPTION
mosquitto_sub is a simple mqtt version 3.1 client that will subscribe to a topic and print the messages that it receives. OPTIONS
-c, --disable-clean-session Disable the 'clean session' flag. This means that all of the subscriptions for the client will be maintained after it disconnects, along with subsequent QoS 1 and QoS 2 messages that arrive. When the client reconnects, it will receive all of the queued messages. If using this option, it is recommended that the client id is set manually with --id -d, --debug Enable debug messages. -h, --host Specify the host to connect to. Defaults to localhost. -i, --id The id to use for this client. If not given, defaults to mosquitto_sub_ appended with the process id of the client. Cannot be used at the same time as the --id-prefix argument. -I, --id-prefix Provide a prefix that the client id will be built from by appending the process id of the client. This is useful where the broker is using the clientid_prefixes option. Cannot be used at the same time as the --id argument. -k, --keepalive The number of seconds between sending PING commands to the broker for the purposes of informing it we are still connected and func- tioning. Defaults to 60 seconds. -p, --port Connect to the port specified instead of the default 1883. -P, --pw Provide a password to be used for authenticating with the broker. Using this argument without also specifying a username is invalid. This requires a broker that supports MQTT v3.1. See also the --username option. -q, --qos Specify the quality of service desired for the incoming messages, from 0, 1 and 2. Defaults to 0. See mqtt(7) for more information on QoS. The QoS is identical for all topics subscribed to in a single instance of mosquitto_sub. --quiet If this argument is given, no runtime errors will be printed. This excludes any error messages given in case of invalid user input (e.g. using --port without a port). -t, --topic The mqtt topic to subscribe to. See mqtt(7) for more information on mqtt topics. This option may be repeated to subscribe to multiple topics. -u, --username Provide a username to be used for authenticating with the broker. This requires a broker that supports MQTT v3.1. See also the --pw argument. -v, --verbose Print received messages verbosely. With this argument, messages will be printed as "topic payload". When this argument is not given, the messages are printed as "payload". --will-payload Specify a message that will be stored by the broker and sent out if this client disconnects unexpectedly. This must be used in con- junction with --will-topic. --will-qos The QoS to use for the Will. Defaults to 0. This must be used in conjunction with --will-topic. --will-retain If given, if the client disconnects unexpectedly the message sent out will be treated as a retained message. This must be used in conjunction with --will-topic. --will-topic The topic on which to send a Will, in the event that the client disconnects unexpectedly. WILLS
mosquitto_sub can register a message with the broker that will be sent out if it disconnects unexpectedly. See mqtt(7) for more informa- tion. The minimum requirement for this is to use --will-topic to specify which topic the will should be sent out on. This will result in a non- retained, zero length message with QoS 0. Use the --will-retain, --will-payload and --will-qos arguments to modify the other will parameters. EXAMPLES
Note that these really are examples - the subscriptions will work if you run them as shown, but there must be something publishing messages on those topics for you to receive anything. Subscribe to temperature information on localhost with QoS 1: o mosquitto_sub -t sensors/temperature -q 1 Subscribe to hard drive temperature updates on multiple machines/hard drives. This expects each machine to be publishing its hard drive temperature to sensors/machines/HOSTNAME/temperature/HD_NAME. o mosquitto_sub -t sensors/machines/+/temperature/+ Subscribe to all broker status messages: o mosquitto_sub -v -t $SYS/# BUGS
mosquitto_sub bug information can be found at http://launchpad.net/mosquitto SEE ALSO
mqtt(7) mosquitto_pub(1) mosquitto(8) libmosquitto(3) AUTHOR
Roger Light <roger@atchoo.org> 5 February 2012 mosquitto_sub(1)
All times are GMT -4. The time now is 03:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy