Ongoing Incident Report: When Smart Home Devices Go Silent

Search for a command to run...

No comments yet. Be the first to comment.
Here are some tips to reduce Claude token usage and keep things efficient, based on my experience and some things I've been experimenting with. Some of these sound obvious until you realize you've bee

എന്താണ് ഡീപ്ഫെയ്ക്? ഈ സാങ്കേതിക വിദ്യയുടെ ചരിത്രവും സാധ്യതകളും അപകടങ്ങളും പരിചയപ്പെടുത്തുന്ന കുറിപ്പ്. നിര്മിത ബുദ്ധിയുടെ (Artificial Intelligence - AI) വരവോടു കൂടി സാങ്കേതിക മേഖലയില് വലിയ മാറ്റങ്ങളാണ് നിത്യേനയെന്നോണം വന്നുകൊണ്ടിരിക്കുന്നത്. പല ജോ...

തൊഴിലിടങ്ങളില് എ ഐ നിര്മിത ബുദ്ധി ഉപയോഗിച്ചുള്ള ക്ഷമത പരീക്ഷിച്ചുകൊണ്ടിരിക്കുകയാണ്. അത്തരം സാധ്യതകളെ കൂടി മുന്നില് കണ്ട് നിര്മിത ബുദ്ധി അടിസ്ഥാനമാക്കിയുള്ള കുറേയധികം ടൂളുകള് നിലവിലുണ്ട്. അവ പരിചയപ്പെടാം. എ ഐ മേഖലയില് വലിയ മാറ്റങ്ങളാണ് വന്നുകൊണ...

In the process of implementing skin tones and fixing emoji issues in Desh Keyboards, I have learned a lot about emojis! Hopefully, someone out there will find this information useful, or at least interesting. The Emoji world is expanding day by day ...

Thoughts of Yemzikk
5 posts
Incident Title: Smart Home Devices Not Responding to Pings
Start Date: July 17, 2025, 18:49 UTC
Status: Ongoing (will update as progress continues)
Incident Level: Major
My house is powered by an Omada network that connects a handful of smart devices. These help automate routine chores, keep tabs on which power source is active (KSEB, inverter, or UPS), and keep the place secure with wireless cameras.
Despite every device showing as “online” in the Omada dashboard, several went completely silent and refused to respond to even simple pings. This caused:
Automations started to fail
Difficulty in controlling and monitoring the device
Receiving a device down notification in Telegram from Uptime Kuma (If it is a main device, it sends several messages)
Dashboard status indicators provide misleading comfort
Device Restarts: Tried the classic solution, turning them off and on again. Fixes the issue temporarily.
Firmware Updates: Updated all devices to the latest firmware
Firewall & Rules: No Need to check this, the issue seems to start after some time, not always
VLANs and Subnets: Rechecked device segregation to ensure nothing was isolated by mistake.
Other Protocols: Verified that, while pings failed, devices also did not respond in their apps.
This incident is still in progress. Here’s what I plan to do as ongoing steps:
I’m currently at my workplace, and I need to get home and try to fix it from there. When trying to fix remotely, there are so many limitations, especially if something breaks, I had to travel back home to fix that, mostly.
Monitor the Fixes: Watch for device responsiveness as network policy changes take effect.
Document All Changes: Maintain a log of tweaks for easier rollback or review.
Collect Device Logs: Gather diagnostics from each device for follow-up analysis.
Regular Status Updates: I’ll continue amending this report as the situation evolves, detailing new symptoms or victories along the way.
Stay tuned for updates as I continue my quest to turn the “silent” devices back into smart home collaborators. If you’re navigating a similar saga, remember: sometimes the journey is half the fun (or at least good for a laugh later).