Home Assistant info:
- Core 2024.10.2
- Frontend 20241002.3

I get the following error:

Thanks!
Home Assistant info:

I get the following error:

Thanks!
Iām very interested too.
I use this solution as the primary event notification channel (flood detection, etc.). Since I have the Home Assistant server connected to the UPS, this solution is the most reliable.
Iām using Huawei E3372.
This is the approach I took. It does require you to use an install method where you have control at the OS level. I just use cellular when I notice that my cable is down. This was one of the main reasons I use a supervised install.
Your solution, although brilliant, has one flaw. It constantly relies on a stable internet connection. For example, when you are going on holidays to the mountains, such a connection is difficult to find.
āSMS notifications via GSM-modemā allows you to receive an alert in a place where there is practically no internet, but also to issue a ācommandā to Home Assistant (run an automation or so).
This was the main reason why I chose HA instead of other commercial solutions based solely on an Internet connection.
I guess I donāt understand. My method uses cellular as a backup to connect HA with the cloud. Once in the cloud Iāve used various methods to get the message delivered to me, SMS being one. I assumed that my SMS messages would be delivered by my cellular network in the same manner yours would be. Maybe this isnāt the case. For me, when Iām out of the area I dual route all my urgent notifications to a family member, so someone can physically respond if need be. So, my system also includes alternative end users as part of the solution.
Current solution did not require me to engage additional end users. I could do everything using SMS, bypassing any additional services (including Internet SMS gateways), which for various reasons may be temporarily unavailable. Even in places where is a problem with mobile internet, the mobile network works well enough that you can easily make a call, not to mention receiving/sending SMS.
This is what makes it the most universal and reliable solution.
Same problem for me, my Home Assistant is also dedicated to security with SMS notifications via GSM modem.
Here in Belgium, weāre not talking too much about the end of 2G yet, but itās actually quite practical because with a simple SIM800C USB for ā¬5-6 and a Base 0 subscription, you can get emergency SMS for ā¬0.10 without a fixed line.
The SIM800L for ā¬2.50 is ESPhome compatible.
But shouldnāt we invest in a 4G LTE module for the future?
Is SMS easily compatible with LTE? I have my doubts. Thereās the A7670 for ā¬15, but I donāt see any easy integration.
Since SMS notifications via GSM modem are based on Gammu, we could easily imagine a Gammu add-on with Home Assistant that communicates with it this way. But will they do it?
I am in the same situation. At the moment I have only found this project. Hopefully someone will implement a solution to this problem.
If I understand correctly, work is underway on integration on new terms.
Hey, I just ran into the same issue when the SMS notifications via GSM modem integration was removed.
As an alternative, Iāve built a Home Assistant add-on: SMS-Gammu-Gateway
Itās based on Gammu (Iāve tested it with SIM800L) and works as a proper add-on in HAOS.
You can send/receive SMS either through REST API or MQTT, so itās easy to integrate back into your automations.
Hi. @pavelve: Your add-on installs additional packages listed in files requirements.txt? Or it is just the list of required additional packages? I just donāt know how it works
Iām asking, because python-gammu will be removed from HAOS, and because of this the old SMS Notification will be removed. Your addon will install gammu back?
Hi. Great question! Yes, my add-on installs all packages from requirements.txt during the Docker build process.
How it works:
1. Docker Build Process:
2. Complete Independence:
3. Regarding python-gammu removal from HAOS:
Current requirements.txt includes:
So yes - the add-on will install gammu back (in its own container) and will be the perfect replacement for the deprecated SMS Notification integration!
This is exactly why I created this add-on - to provide a modern, maintained alternative when the built-in integration gets removed.
@pavelve: Thanks for the answer. Iāll test it. First I should uninstall deprecated SMS add-on? Or removing of its configuration is enough?
Are you planning to add the add-on to HACS?
You just need to make sure that the integration is not talking to the hardware at the same timeāotherwise the add-on wonāt be able to communicate with it.
And about HACS: add-ons are not distributed via HACS. HACS is meant for integrations, Lovelace cards, themes, etc. Add-ons are installed through the Home Assistant add-on store, not HACS.
How its possible to delete all sms?
Thank you for the great add-on!
Hi Michael,
please check the Documentation tab and the REST API section ā there youāll find an explanation on how to delete SMS.
any suggestion for a 4g modem thatās working with your integration? (3g is being shutdown in my country)
I have not tested any 4G modem.
The add-on relies on Gammu, and Gammu works with any modem that provides a standard AT command interface for SMS. So as long as the modem exposes that interface, it should work regardless of whether itās a 2G, 3G, or 4G device.
The only limitation is that some newer devices act only as āHiLink/router modeā without exposing AT commands, and those wouldnāt be supported.
Hi everybody,
When I try to add the repository of sms-gammu, I get an error message
Cmd(āgitā) failed due to: exit code(128) cmdline: git clone -v --recursive --depth=1 --shallow-submodules ā home-assistant-addons/sms-gammu-gateway at main Ā· PavelVe/home-assistant-addons Ā· GitHub /data/addons/git/60b93bdb stderr: 'Cloning into ā/data/addons/git/60b93bdbā⦠fatal: repository āhome-assistant-addons/sms-gammu-gateway at main Ā· PavelVe/home-assistant-addons Ā· GitHubā not found ā
Do you know why ?