Transform push notifications into phone calls (Crucial for alarm/security systems)

Hi Everyone,

I am writing to propose a feature that I believe is essential for anyone using the eWeLink ecosystem to manage home security or alarm systems.

The Request: Add an option (or a native integration/VIP service) to convert specific emergency push notifications into an automated phone call (Voice Call) to the user’s phone number.

Why it is needed:

  • High Priority Awareness: Standard push notifications are easily missed, buried under other app alerts, or silenced by “Do Not Disturb” and silent modes.

  • Immediate Reaction Time: In the event of a break-in, gas leak, or water flood, a phone call triggers the main ringtone, ensuring immediate attention or waking the user up at night.

  • DIY Alarm Systems: Many users rely on eWeLink motion sensors, door/window contacts, and sirens as a primary security system. Without automated call alerts, the reliability of the system is severely limited.

It would be fantastic to set a rule in Scenes such as:

  • IF: Door sensor opens (System Armed)

  • THEN: Place an automated voice call to the registered phone number

I hope the development team considers implementing this feature, even as a premium option within the eWeLink Advanced plan.

Who else feels this feature is indispensable? Please upvote or comment to help bring visibility to this request!

Thanks!

Fabrizio

I understand the idea, but I don’t think a cloud-based phone call service is a good solution for a security system. If an alarm is important enough to require a phone call, it is probably better handled locally by a proper alarm system or by Home Assistant, where you can use multiple notification channels and define your own escalation logic.

A phone call through eWeLink would also introduce another cloud dependency and another potential point of failure. And there is another small detail: who is actually going to make those calls, and who is going to pay for them?

Dear jam3,

You don’t necessarily need an actual phone call—the key requirement is a high-priority sound, because a silent popup notification is easy to miss during an alarm event.

While phone OS settings allow turning notifications into sounds, it would be extremely useful if the eWeLink app natively allowed users to assign custom alert sounds to specific events. That way, a critical alert like an intrusion detection can trigger a distinct, loud siren sound, differentiating it from everyday device notifications.

Best regards

Fabrizio

A custom high-priority sound for critical notifications makes much more sense than automated phone calls.

Just keep in mind that this is still a notification mechanism, not a reliable alarm system. For security-critical events, I wouldn’t rely on a single smartphone notification channel.

Exactly. And for anyone who does need that absolute level of reliability, they can always hardware-trigger a standalone GSM phone dialer using a Sonoff relay output. That way, you get a direct PSTN/cellular phone call guaranteed by hardware, without relying solely on smartphone push notification channels.

F.

“Guaranteed” is doing a lot of work there. :grinning_face_with_smiling_eyes:

It still assumes the power is on, the network is available, and the operator actually completes the call. Nothing is guaranteed - except death and taxes. :wink:

True! :rofl:

We achieve this in a different way in systems equipped with Sonoff iHost which has an integral security alarm system. We use a Sonoff Basic WiFi switch that has been modified to provide clean voltage free relay contacts which are wired into the trigger input of an Alarm Dialler. In the non- alarm condition the Sonoff Switch is ON meaning the relay contacts are closed and the alarm dialler is not triggered. On an alarm condition the Sonoff Switch toggles to OFF for a brief period which causes the alarm dialler to call the pre-programmed telephone number. Also in the event of a Mains Electricty power failure the relay inside the Sonoff Switch will de-energise and trigger the dialler (which has battery backup) to call the pre-programmed telephone number. Although we have chosen to modify a basic Sonoff Switch there is no reason why the same cannot be achieved with a standard wi-fi or zigbee switch by just connecting the output of the switch to the mains rated coil of a relay and use the relay’s Normally Open volt free clean contacts. We mainly use Cooper- Menvia Alarm diallers but there are plenty of low cost models about. We have also used the low cost BrandingPlus system for a dialler and just disabled the top mounted motion sensor.

Theoretically, this can be achieved to some extent using the MacroDroid app.

However, it remains inefficient and unstable, as it relies on internet access and cloud services.

If, on the other hand, we were to migrate the ecosystem from eWeLink to a 100% local solution within our LAN, it would be possible to handle this locally, without the cloud or the internet.

An Android smartphone with a SIM card and the MacroDroid app could serve as the communication component for voice calls and SMS. You would just need to define the trigger that activates the macro.

A Sonoff door sensor is a good example, but its status information needs to reach MacroDroid this requires an automation ecosystem capable of handling such a setup. While this can still be done via the cloud (internet), it comes with all the associated downsides.

Sonoff sends data to the eWeLink cloud. The cloud runs a scene “IF open, THEN webhook” targeting a MacroDroid web server that handles webhooks, this acts as the trigger to activate the macro, which then initiates the call or sends the SMS/call from the phone.

If you have an ecosystem capable of local sensor data processing, you could bypass the cloud entirely. However, that would require a very in depth analysis of your specific local setup.

You could also try a MacGyver style approach.

Run both MacroDroid and the eWeLink app on an Android phone. Set up a macro triggered by a change in the text displayed at a specific location on the screen specifically, the area in the eWeLink app showing the sensor’s status(the sensor must operate in LAN mode). This way, you could handle it locally, without relying on the cloud or a dedicated ecosystem.

Of course, the phone must be dedicated 100% to these tasks, and nothing can interfere with what is happening on the screen.

Ring without payment no one does it.

When they ring the doorbell I can choose whether to receive a notification or a phone call.

I activate it when I don’t want to miss a notification and I assure you that it’s a good option, the cell phone doesn’t stop ringing until I hang up the call.

With the notification and more in silent mode, I pass by the notifications many times.

But you can’t pass the calls, since they are even annoying :sweat_smile: it’s a very good option and you can always activate or deactivate it.

HTTP request in node-red , ntfy , tailscale, tailscale app on phone, ntfy app on phone, and Macrodroid app on phone is another solution for alert