# Argon instability issues **URL:** \ **Category:** BLE // NFC\ **Created:** [November 25, 2018, 10:07am UTC](https://community.particle.io/t/argon-instability-issues/45557 "2018-11-25T10:07:36Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![guussie](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@guussie](https://community.particle.io/u/guussie)\ **Post date:** [November 25, 2018, 10:07am UTC](https://community.particle.io/t/argon-instability-issues/45557/1 "2018-11-25T10:07:36Z")
I just received my 8 Argons. Argon 1: initial setup seemed to go well, but then the rainbow didn’t work. Visible as online in Tinker app. Setting D7 to digitalwrite crashed the Argon. Reboot restored Argon as online, but setting D7 to digitalwrite keeps crashing Argon. When Argon is not powered on, it shows up as online in WebIDE and Console. After several minutes Argon starts flashing green rapidly. I flashed a simple led on/off sketch, this works initially but after a few minutes Argon flashing green rapidly and going offline, even though as showing online in Console and IDE. Argon 2: exactly the same story. Basically another dead Argon. Argon always showing as online in the cloud, but it isn’t. Run Diagnostics gives an error. Argon 3: initial setup went fine and rainbow working. led firmware flashed and operational. However, leaving it overnight, Argon goes offline, even though led breathing blue. Reboot will restore functionality. BLE: I was expecting normal BLE functionality out of the box as advertised (WiFi + Mesh + Bluetooth), but it looks like we have to wait for this. My photons are working well and are stable, but this only started happening in firmware 8. So far not impressed with Argon and afraid to test the other Argons in the box. I have not yet tried the Xenon, wanting a stable Argon first. No one else seems to have these problems, judging from the Forum. ---
**Author:** ![kennethlimcp](https://avatars.discourse-cdn.com/v4/letter/k/c0e974/32.png) [@kennethlimcp](https://community.particle.io/u/kennethlimcp)\ **Post date:** [November 25, 2018, 10:14am UTC](https://community.particle.io/t/argon-instability-issues/45557/2 "2018-11-25T10:14:11Z")
Well, There’s an ongoing issue with a particular router --\> [Mesh: issue with certain? Xfinity routers](https://community.particle.io/t/mesh-issue-with-certain-xfinity-routers/45185/7) ---
**Author:** ![guussie](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@guussie](https://community.particle.io/u/guussie)\ **Post date:** [November 25, 2018, 3:40pm UTC](https://community.particle.io/t/argon-instability-issues/45557/3 "2018-11-25T15:40:35Z")
Thanks for flagging that. I saw that in the Forum before I posted. I am using an Airport Express network (Apple). And the issue does not seem to affect all Argons. I will try some more and report back. ---
**Author:** ![okeefe](https://avatars.discourse-cdn.com/v4/letter/o/ce7236/32.png) [@okeefe](https://community.particle.io/u/okeefe)\ **Post date:** [November 25, 2018, 3:56pm UTC](https://community.particle.io/t/argon-instability-issues/45557/4 "2018-11-25T15:56:07Z")
Argons also seem to be having issues obtaining DHCP leases from Microsoft DHCP servers. ---
**Author:** ![Mjones](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/mjones/32/21658_2.png) [@Mjones](https://community.particle.io/u/Mjones)\ **Post date:** [November 25, 2018, 8:15pm UTC](https://community.particle.io/t/argon-instability-issues/45557/5 "2018-11-25T20:15:17Z")
Quite a few people have reported similar issues, myself included, just have to search a little. I’m not familiar with apple equipment, other than to say most everything is locked tight. If possible, turn off all IPV6 routing. ---
**Author:** ![guussie](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@guussie](https://community.particle.io/u/guussie)\ **Post date:** [December 2, 2018, 7:22pm UTC](https://community.particle.io/t/argon-instability-issues/45557/6 "2018-12-02T19:22:56Z")
Here is an update. I created a new wireless network, not using any Apple components. I set up three more Argons using that network. Initially it looked OK, as Tinker worked without a flaw. However, after a couple of hours, all three Argons were offline, just like with the Apple network. Any suggestions on how to troubleshoot this will be highly appreciated. I have several projects that need these Argons urgently! ---
**Author:** ![Jig](https://avatars.discourse-cdn.com/v4/letter/j/a87d85/32.png) [@Jig](https://community.particle.io/u/Jig)\ **Post date:** [December 2, 2018, 10:27pm UTC](https://community.particle.io/t/argon-instability-issues/45557/7 "2018-12-02T22:27:34Z")
I similarly had a Xenon mysteriously disconnect from the Mesh spontaneously in the middle of the night. Had to hard power cycle to get it to connect again. Unstable is right. ---
**Author:** ![Fragma](https://avatars.discourse-cdn.com/v4/letter/f/5fc32e/32.png) [@Fragma](https://community.particle.io/u/Fragma)\ **Post date:** [December 9, 2018, 11:46pm UTC](https://community.particle.io/t/argon-instability-issues/45557/8 "2018-12-09T23:46:59Z")
I’m having a similar problem. Just setup my first Argon via Android, it went through the setup process and seem to get stuck downloading updates but restarting the process allowed it to finish successfully. I then set up a network for it and finally I setup a new Xenon, no issues with either. I let it sit there for awhile and I noticed he Argon crashes, does an SOS and reboots every 2 to 3 min. The Xenon is doing a fast green blinking almost all the time. I thought maybe the Xenon was causing the issue before when I unplugged it the Argon continues to crash repeatedly. Oddly the ‘Device Vitals’ show the Xenon has tons of disconnection events while the Argon has none. Firmware for both is 0.8.0-rc.25. I also tried flashing the ‘Blink’ example and it runs and blinks the led a bit before an SOS and a reboot, just like before. It flashes red seven times after the SOS which is listed as ‘Exit’ in the Photon docs. No issues with my 6 photons so I figure this is a firmware or device issue and will await for updates. Just wanted to make it known you aren’t the only one with issues, though for me, the diagnostics function works and shows no issues. ---
**Author:** ![will](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/will/32/23374_2.png) [@will](https://community.particle.io/u/will)\ **Post date:** [December 13, 2018, 5:51pm UTC](https://community.particle.io/t/argon-instability-issues/45557/9 "2018-12-13T17:51:16Z")
Hey folks – just wanted to jump into this thread to let you know that we've released `v080-rc.26` which contains a bunch of fixes that improve the setup process, Mesh stability, and range between devices. Among them is a fix which should improve compatibility issues with IPv4/IPv6 routers that result in Xenons and Argons getting stuck in "blinking green" mode. Instructions for updating to `rc.26` are available here – would love to hear your feedback! > [@\[Updated 3/21/19\] Gen 3 known issues](https://community.particle.io/t/updated-12-12-particle-mesh-known-issues-and-fixes/45722/3): > > Updating to the most recent release (v0.9.0) The most recent release for Particle Mesh is v0.9.0. To update your device to this version of firmware, use the following instructions: If you previously tried to set up your device using the Android mobile app and got a Bluetooth (BLE) pairing error (Nexus 6) or an error during device firmware upgrade, you should first manually update the device firmware to 0.9.0 using the Using the Particle CLI instructions below. The BLE fix requires a Particle De…