I have over a dozen 404X devices that went offline in the past few weeks at different times and haven't come back online. They are located in different geographical locations. Initially, I thought it was a power issue, but it increasingly seems like a deeper problem. Is there anyone from support who can look into this? I can provide the device IDs if needed. These devices are part of a product I’ve been trying to commercialize, and they are all running the 4.2.0 base code.
Hi, I believe your best shot is by DM'ing your device IDs to @Support so they can look at the issue.
Best,
Thanks, @gusgonnet. I'll give that a try. It's getting very frustrating, and I'm confident my code isn't the issue. I have devices running the same code that have been online for almost a year, while these devices only stayed online for a few weeks before dropping. They are physically built the same way and use the same components.
Does anyone know if there are any bug fixes between versions 4.2.0 and 6.1.1 that potentially address a known cellular issue?
What’s the typical signal strength and signal quality from devices prior to them going offline?
If you take a device that went offline, does it come back online with a power cycle (assuming you can find someone to access it)?
If you take a device that went offline to a physical different area does it go online?
Do you have a hardware watchdog or external watchdog power cycle the device due to not being able to connect?
Is this battery operated or mains power?
What’s the typical signal strength and signal quality from devices prior to them going offline? It varies, from 40Q/30S to 80Q/85S. I don't think it's a signal issue as they are all static locations with no movement
If you take a device that went offline, does it come back online with a power cycle (assuming you can find someone to access it) I'll be trying this soon once I get to the locations where they are installed.
If you take a device that went offline to a physical different area does it go online? Will give it a try soon.
Do you have a hardware watchdog or external watchdog power cycle the device due to not being able to connect? No, I have not implemented this in the code yet. The devices are always online and only run code once a function is called which isn't often. They sit idle 99% of the time.
Is this battery operated or mains power? Grid power and no battery.
Thanks for the DM - I've responded with some details.
Hey, I was thinking that there might be ways to improve the firmware, so it reacts better to the lack of connection.
There are best practices around the community explained by community members (Jeff and Chipmc come to mind to name a few) and Particle team (Rick comes to mind).
If your code is doing nothing to reconnect, maybe that is one thing that can be looked at. The idea is to help DeviceOS by providing clear directions of what we want the device to look for and consequently do when connections take time or do not happen at all.
One example that comes to mind is sending the device to hibernation for 30 seconds to effectively reset the modem. I learned that recently in this thread.
Best,
1 Like