What to do when Eyedro energy monitor device notifications not working
If your Eyedro alerts suddenly stop arriving, the problem is usually tied to notification settings, network connectivity, or a device sync issue rather than a complete system failure.
This guide walks through the most common causes and the exact checks that restore alerts on Eyedro energy monitoring systems.
Eyedro is widely used for real-time electricity monitoring in homes and small businesses, so missed notifications can hide abnormal energy use, outages, or equipment problems.
The good news is that most notification failures can be diagnosed quickly if you follow a structured sequence.
How Eyedro notifications are supposed to work
Eyedro monitoring devices typically collect electrical usage data and send it to the Eyedro cloud platform, where alert rules determine when a notification should be triggered.
Those notifications may be delivered through the mobile app, email, or web-based alert settings depending on the user’s configuration.
For alerts to work correctly, several pieces must align:
- The monitoring device must be powered and connected.
- Data must reach the Eyedro cloud without interruption.
- Alert thresholds must be enabled and configured correctly.
- Notification destinations such as email addresses or app push settings must be valid.
- The receiving device or mailbox must not block or suppress the alert.
Most common reasons Eyedro notifications stop working
Incorrect alert configuration
A common cause of Eyedro energy monitor device notifications not working is a simple configuration problem.
Alerts may be disabled, set to the wrong measurement source, or configured with thresholds that are too high to trigger during normal usage.
Review whether the alert is tied to the correct circuit, meter, or monitored load.
If the wrong device is selected, the system may be collecting data but never reaching the condition required to send a notification.
Network or internet interruptions
Eyedro devices depend on a stable network connection to transmit data.
If the router reboots, the internet drops, or the local Wi-Fi settings change, the device may continue measuring usage but fail to upload data reliably.
In these cases, notifications may be delayed or stopped entirely because the cloud platform never receives the trigger condition in time.
Power loss or device reboot
If the Eyedro unit loses power, gets unplugged, or resets after a power event, alerts may pause until the device fully reconnects and resumes reporting.
This is especially important after outages, electrical panel work, or maintenance near the monitoring hardware.
Email filtering or spam handling
When alerts are delivered by email, the messages may be filtered into spam, promotions, or quarantine folders.
Corporate email systems and custom domain filters can be especially aggressive with automated alerts from monitoring services.
If the notification system is email-based, add Eyedro’s sending address to a safe sender list and check whether your mail provider blocks automated or transactional messages.
Push notification permissions disabled
For app-based alerts, push notifications must be enabled at both the operating system level and within the Eyedro app.
If notification permissions are turned off, the app may still work for viewing data but fail to interrupt you with active alerts.
This issue is common after app updates, device migrations, or restoring a phone from backup.
Outdated app or firmware
Older app versions and outdated device firmware can create compatibility issues that affect alert delivery.
While Eyedro systems are generally reliable, software updates often include fixes for cloud syncing, user account behavior, and notification delivery.
Step-by-step troubleshooting checklist
1. Confirm the alert is enabled
Start in the Eyedro dashboard or app and verify that the alert is active.
Check the rule status, threshold value, and the monitored source.
- Make sure the alert is turned on.
- Confirm the threshold is realistic for the load being monitored.
- Verify that the correct device or circuit is selected.
- Look for multiple rules that may conflict with each other.
2. Test the notification destination
Confirm the destination itself is valid.
If you are using email, send a test message to that address from another account.
If you rely on push notifications, open the app and verify that the phone is still signed in to the correct account.
Also check whether you recently changed:
- Email addresses
- Phone numbers
- App permissions
- Apple ID or Google account settings
3. Check device connectivity
Inspect the Eyedro device status in the dashboard.
Look for gaps in reporting, delayed readings, or a last-seen timestamp that suggests the unit is offline.
If the device appears disconnected, restart the local router and confirm the monitoring hardware has power.
In some installations, moving the router or changing Wi-Fi credentials can silently break the connection.
4. Review spam, junk, and filtering rules
Search all folders and filters in your inbox for missed alerts.
If using a workplace email account, ask your administrator whether security software or message rules are quarantining Eyedro notifications before they reach your inbox.
For best results, create a mailbox rule that marks Eyedro alerts as important and bypasses aggressive filtering.
5. Recheck push notification permissions
On iPhone or Android, open the system settings and confirm the Eyedro app can send notifications.
Make sure notification previews, banner alerts, sound alerts, and background refresh are allowed if the app requires them.
If alerts still do not appear, log out and back in to the app, then reinstall it if needed to refresh stored permissions and cached settings.
6. Update the app and reboot the device
Updating the mobile app often resolves notification issues caused by older builds.
After updating, reboot the phone or tablet to clear background app states that may block alerts.
If you are using a web browser to manage the account, clear the browser cache or try a different browser to rule out session problems.
Advanced checks for persistent notification failures
Verify alert thresholds with real usage data
Sometimes notifications are functioning, but the chosen thresholds never trigger.
Compare the alert settings against actual energy patterns from the last several days.
If the threshold is too broad, too narrow, or tied to an inactive time window, alerts may appear broken when they are simply not being triggered.
Check for account and subscription issues
Some alert functions depend on an active account state and proper access permissions.
If you manage multiple users, confirm that the account receiving alerts still has permission to view the monitored device and receive notifications.
Billing issues, expired access, or account changes can disrupt alert delivery even when the hardware remains online.
Inspect for duplicate or conflicting alert rules
Multiple similar rules can cause confusion, especially if one alert is disabled, one is pointing to a different meter, and another uses a threshold that will never be met.
Consolidate overlapping rules so you can tell whether the problem is delivery, configuration, or trigger logic.
When the Eyedro device itself may be the issue
If the dashboard shows no recent readings, the issue may be deeper than notifications.
In that case, the monitoring hardware, power supply, current transformer installation, or network bridge may need attention.
Signs that point to a device-side problem include:
- No new data points in the dashboard
- The device appears offline for extended periods
- Alerts fail only after power outages
- Readings resume briefly and then stop again
If the hardware appears physically damaged, improperly mounted, or disconnected from the monitored circuits, contact a qualified electrician or Eyedro support before assuming the notification system is at fault.
Best practices to prevent missed alerts
- Use a dedicated email address for monitoring alerts.
- Keep the Eyedro app updated on all devices.
- Review alert rules monthly to make sure they still match your energy use.
- Store notification contacts in more than one place if the workflow allows it.
- After router changes, confirm the device reconnected successfully.
- Test alerts after any app, phone, or account update.
Where to focus first if you need fast results
If you need a quick path to resolution, start with the notification destination, then the device connection, then the alert rule itself.
That order solves most cases of Eyedro energy monitor device notifications not working because it separates delivery problems from trigger problems.
Once alerts are confirmed, you can fine-tune thresholds, recipient lists, and app settings to make sure future notifications arrive when they should.
