why sms texting isn't supported?
 
Notifications
Clear all

why sms texting isn't supported?  

  RSS
DanV
 DanV
(@danv)
New Member
why sms texting isn't supported?

I've spent a full day trying to get the notifications in Prusa connect on an xl setup using telegram, with no luck, very frustrating. I wonder why sms texting isn't supported in Prusa Connect notifications. It would seem to be a much more universal method to get error and status notifications to a user. Any hope that sms texting will be added soon, or is there a good reason why it isn't supported now? 

 

I tried to get help from Prusa Support chat, and they were no help at all... said they had never worked with Prusa Connect notifications. After buying 9 xl's I was pretty disappointed with that answer.

This topic was modified před 1 year by DanV
Napsal : 09/08/2023 5:24 pm
_KaszpiR_
(@_kaszpir_)
Prominent Member
RE:

I guess number of people requesting SMS notifications was probably so low they just did not bother to implement it.

Of course I believe there are more reasons because I worked in company that needed SMS notifications and we did some research and implementation for it for our own need, below some notes we took:

- if you want to send SMS from one device you usually need a directly attached GSM modem and SIM card and paid service for it - the cost of this is usually high enough to be used for special cases, thankfully nowadays this is not a really high cost but over 10y ago it was noticeable (especially if you want SMS from the really detached location where only satellite phones were working...), which gets a bit problematic if you say have 10 devices and each would require dedicated modem + sim card (which naturally leads to next option below)

- if you want to send message form multiple devices you need some host to gather those data, queue messages and send them via GSM modem - this makes things a bit more complex and I remember we ended in writing our own custom code for it (mainly for queuing) - sill you would have to make some kind protocol calls to API to send those messages, and that increases firmware complexity further (which is extended to next option below)

- nowadays you could use SMS gateways but days when they were wide open are gone and you need subscription to use them - some companies created more business around it (like servicenow/twillo) so maybe it is just easier to integrate with that nowadays, yet there is so many of them and usually they are a bit different between that writing and supporting such code was just too much work compared to the returns you get from it.

BTW, sending SMS is really more complex than sending a notification to a web endpoint like Telegram.

See my GitHub and printables.com for some 3d stuff that you may like.

Napsal : 10/08/2023 6:44 am
Tojik se líbí
Tojik
(@tojik)
Member Moderator
RE: why sms texting isn't supported?

Hi, thank you for that write up, that was very interesting. I never liked SMS as a notification system. When I was a kid, an SMS was

From what I've seen Discord notifications are the easiest to setup and telegram is the hardest. Sorry for the missing guides. I cannot do anything more about them than just ask for a status, once in a while. And that does not do anything :/

The support situation should be improving in the future. We might have been missing a support person whose job it was to be informed on things connect. That should be changing.

Yea, never thought that SMS should be used for notifications, none of my other apps do that.
As for setting up a telegram notification link, i can refer you to the guide , but you have most likely seen that. I have set up a bot using it so it definitely can work. I can help you troubleshoot if you share details of how it went and where you got stuck

Napsal : 10/08/2023 8:24 pm
_KaszpiR_
(@_kaszpir_)
Prominent Member
RE: why sms texting isn't supported?

I were going to write it now with resources I fully own, and if prusa software supports sending errors to any webhook, then I would something like below:

- set up a Rpi/vm/container (depends on what you have and are able to do) with a GSM modem which could send SMS messages. In general it would be visible as USB device. Double check that this is a modem and not a GSM router.

- a shell script to use existing software that knows how to send SMS messages  (or integrate AT commands directly, which is the hard way I once did) by giving certain parameters, lik hardcoding target number and just pass message

- install https://github.com/adnanh/webhook on the host which will be a target for a webhook. The script would expose web endpoint that would allow to run shell written in earlier stage, would have to see what prusa supports (I guess faking discord endpoint could be just be the easiest?)

- configure prusa software to use that webhook as target for notifications for errors.

This way you could have a single host that be good enough to handle receiving incoming webhooks form printer farm and sending sms messages as well.

For queuing there could be some kind simple lock mechanism to avoid race conditions when multiple webhooks are received (you know, sending SMS takes few moments via talking with the modem) - in that case quite well works something like task spooler to queue executing the script https://manpages.ubuntu.com/manpages/xenial/man1/tsp.1.html

See my GitHub and printables.com for some 3d stuff that you may like.

Napsal : 11/08/2023 5:22 pm
Share: