[Updated 12/17] Particle Mesh Known Issues and Fixes


Outstanding issues

Setup Issues

These known issues affect the Particle iOS and Android apps and will be resolved with updates to the Particle mobile application.

  1. Argons unable to connect to wi-fi network in setup flow.
    Status: Reported

    Customers experiencing this issue are able to go through an Argon setup flow up to the point of connecting to a wi-fi network. After inputting the password, the device will attempt to connect until such a point it times out, giving an error on the mobile application. (At this time, this is only tested and identified on Android.)

  2. Using xenon as assisting device prompts wrong password
    Status: Reported
    Example: Mesh password problem with Xenon as assist device
    Workaround: Use your gateway as the assisting device.

Device issues

These known issues affect the Particle Device OS and will be resolved with updates to 3rd Gen hardware over Bluetooth or the Particle CLI.

  1. SYSTEM_MODE(MANUAL) and SEMI_AUTOMATIC not working properly
    Status: Under investigation (reported in 0.8.0-rc.25)
    Example: Xenon, combining threaded and manual modes can leave Xenon flashing green permanently

  2. Devices go into SOS 7 panic state
    Status: Under investigation
    Example: Xenon won't stay online long enough to flash RC26

Mobile Device issues

There have been a number of mobile devices experiencing connectivity or other issues in regards to pairing and setup with mesh devices. As we discover more devices, they will be listed here.

  1. Identified devices with known data matrix barcode scanning issues.
    • Samsung Galaxy S7 Edge

Known limitations

  1. Cellular.command() not implemented on the Boron
  2. Sleep modes have not been implemented for 3rd Gen devices
  3. Argons do not currently support connections to IPv6-only networks
  4. Ethernet Featherwings do not support connections to IPv6-only networks
  5. The current version of the CLI (1.35.2) has incomplete support for 3rd gen hardware:
  • Supported
    • compile and flash mesh devices
    • particle keys doctor
  • Not supported
    • particle doctor
    • particle keys server (unless you pass in the correct mesh-specific key)
    • particle update
    • particle serial mac (outputs 00:00:00:00:00:00 )
    • particle flash --usb tinker (also --serial, and with a device ID or name)

Refund for large pile of Mesh devices
Initial pairing and update fails - Argon
Argon, particle-cli & WPA2 Enterprise (PEAP/MSCHAPv2)
Argon DHCP IP address assignment fail if there is more than three DNS servers assigned
Mesh still not stable
What port does the Argon use to connect to the Particle Cloud?
Argon to Argon Mesh Setup
Boron LTE System Modes
Mesh: issue with certain? Xfinity routers
Gen 3 improvements update - 12/17
High School Robotics Course using the Particle.io Mesh Devices Blog

Solved Issues

Issues in the section above will be added to this solved issues list along with the version of firmware in which they have been fixed.

Setup Issues (resolved)

  1. Barcode scanning fails for some Xenon devices
    Status: Resolved Android app 2.3.7, iOS app 2.6
    Example: Unable to setup my Xenon

    Customers experiencing this issue are unable to successfully scan and pair with their Xenon and are presented with an error message that reads,
    This is not a Xenon. Please scan Xenon sticker or restart the set up and choose different device type.

  2. Bluetooth pairing does not work for some Android devices (confirmed for Nexus 6)
    Status: Resolved in Device OS 0.8.0-rc.26
    Example: Unable to set up Boron LTE

    Customers experiencing this issue are unable to successfully pair to 3rd Gen devices using Android devices. This issue has been confirmed on the Nexus 6. Note: Because bluetooth pairing fails, a manual upgrade of the device by USB will required if you are experiencing this problem.

  3. DeviceOS updates over Bluetooth fail for some Android users
    Status: Resolved in Device OS 0.8.0-rc.26
    Example: Mesh device setup failing with android app

    Customers experiencing this issue are able to pair over Bluetooth with their 3rd Gen devices but are unable to complete the DeviceOS update step using their Android mobile device.

    Note: Because updates fail over bluetooth, a manual upgrade of the device by USB will required if you are experiencing this problem. It’s most common on Android 7 devices.

Device issues (resolved)

  1. 3rd Gen devices cannot reliably reconnect to certain routers with IPv6 enabled (confirmed for Xfinity Arris and X1 routers)
    Status: Fixed in 0.8.0-rc.26
    Example: Mesh: issue with certain? Xfinity routers

    Customers with Xfinity routers (confirmed with “Arris” and “Xfinity X1” brands) have reported connectivity issues with Xenons connected to mesh networks hosted by Argons or Ethernet FeatherWing devices.

  2. Unable to use a Wi-Fi password or connect to SSIDs with a comma, double-quote, or backslash
    Status: Fixed in 0.8.0-rc.26
    Example: Argon can't connect through app

  3. UDP byte ordering bug
    Status: Fixed in 0.8.0-rc.26
    Example: Argon 0.8.0-rc-25 Issues
    Note: You must target your user firmware to 0.8.0-rc.26 in order to get this fix; it’s in the wiring library compiled into your code, not in system firmware itself.

  4. Xenons cannot always reconnect to the Cloud after a gateway update / reset
    Status: Fixed in 0.8.0-rc.26.
    Example: Xenons not making Cloud Connection via mesh

Mobile device issues (resolved)

  1. Identified devices with known Bluetooth/BLE connectivity issues.

    • Google Pixel 1
    • Google Nexus 5
    • Google Nexus 6
    • OnePlus 5
    • Samsung Galaxy J7
    • Other devices running Android 7 (Nougat)

    Status: You will need to upgrade the device firmware to 0.8.0-rc.26 via USB to correct this issue. After that, pairing and firmware updates over BLE should work properly.

  2. Xenons with Ethernet FeatherWing and Argons go into a panic state when offered more than 2 DNS servers by the DHCP server
    Status: Fixed in 0.8.0-rc.26

Known limitations (resolved)

  1. 3rd Gen devices are not supported in Particle Workbench


Updating to the most recent release (v0.8.0-rc.26)

The most recent release for Particle Mesh is v0.8.0-rc.26. 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.8.0-rc.26 using the Using the Particle CLI instructions below. The BLE fix requires a Particle Device OS fix, which for obvious reasons can’t be delivered by BLE during the normal mobile app setup process if BLE is not working, so you’ll need to do the manual upgrade process once by USB to get the device to 0.8.0-rc.26 which contains the fix.

Using the Particle CLI

  • Install the Particle CLI on your computer if you have not already done so.
  • Go to the mesh firmware releases page.
  • Download the hybrid .bin file for your device. For example: hybrid-0.8.0-rc.26-argon.bin
  • Put your device into DFU mode (blinking yellow), instructions here.
  • Flash the code from a command prompt or terminal window:
particle flash --usb hybrid-0.8.0-rc.26-argon.bin

For the Argon, if you are upgrading a factory unit without using the mobile app, you must manually apply the NCP (network coprocessor) update as well. Upgrade your device OS to 0.8.0-rc.26 first, then go to the Argon NCP Release Page and download argon-ncp-firmware-0.0.5-ota.bin. With the Argon in blinking blue (listening mode):

particle flash --serial argon-ncp-firmware-0.0.5-ota.bin

You may get the error “Error writing firmware: TimeoutError: timed out after 10000ms” but this is normal if the Argon is still blinking magenta rapidly. Let it sit for a minute and then it should reboot and be updated.

Note that this must be done in --serial mode not --dfu. The mobile app does this automatically, so this step isn’t required in normal circumstances. Also, the NCP binary does not need to be updated for every system firmware version. At this time, only factory new devices need an update.

Using the Particle app

  • If you have not configured your Particle device
    Complete the setup process using your iOS or Android mobile device. Your devices should automatically be upgraded to the most recent release.

  • If you have already configured your Particle device
    Your devices should already be running Device OS v080-rc.26. You can confirm this by:

    • Putting your device into listening mode and typing particle serial identify into the CLI
    • Inspecting your device in the Particle Console (http://console.particle.io) under the Devices tab.

Using the Particle Web IDE (for devices already connected to the Cloud)

If your device is online and breathing cyan, you can upgrade the Device OS by flashing firmware targeting the newer version. Click on the Devices icon (circle with 4 lines on the left side), make sure the device has a gold star before its name, click on the >, then select the version you want to upgrade to, and compile and flash firmware to your device.


This will only upgrade, it will not downgrade to an earlier device OS version.

The first time you flash code from the Web IDE to a device running 0.8.0-rc.25 that targets 0.8.0-rc.26 or later, the first flash operation will fail but it will start a mandatory Device OS upgrade. You can then flash your user code again. This will only happen on the first flash from 0.8.0-rc.25 to 0.8.0-rc.26 or later from the Web IDE.

New Xenon Wouldn't Connect, Now Flashing Yellow, I'm Lost
Refund for large pile of Mesh devices
Off to a bumpy start - disheartening for a ME
Argon can't connect through app
Mesh range / external antenna?
Xenon blinking green after breathing cyan
Unable to set up Boron LTE
Argon 0.8.0-rc-25 Issues
LG5 not pairing with Argon or Xenon
Mesh device setup failing with android app [Solved]
Argon Flashing Cyan (running on 0.8.0-rc.26)
Argon instability issues
Mesh: issue with certain? Xfinity routers

Update - Android app v2.3.7 released

This release should be available in the play store in the next 1-3 hours. It includes a fix for the following issue:

We expect a fix for iOS devices to be available early next week. Stay tuned for updates.


Update - iOS mobile app 2.7 released

This version allows data matrix codes that are missing digits to be automatically compensated for, eliminating the “This is not a Xenon” error when scanning some Xenon data matrix codes. (November 3, 2018)


Update - 3rd Gen devices are SUPPORTED in Particle Workbench Dec 4 release


Update - rc.26 released as new default firmware for Mesh devices

v080-rc.26 is now live in all Particle development tools as the default compile target for 3rd Gen devices. The high level fixes include:

  • Improved reliability of OpenThread mesh networking
  • Improved wireless transmission range between 3rd Gen devices over mesh
  • Improved Bluetooth compatibility with Android devices (requires firmware update to device)
  • Improved compatibility with networks with IPv6 enabled

Detailed release notes for rc.26 is available at Github, below:


IMPORTANT: Argon NCP firmware needs to be updated to v0.0.5 after updating to 0.8.0-rc.26 from any release under 0.8.0-rc.25. The release binaries can be found here


  • [Argon] Escape special characters in SSIDs and passwords (#1604)
  • [Gen 3] Network system events are correctly generated (#1585)
  • [Gen 3] Correct C++ contructor array alignment in system-part1 (#1594)
  • [Gen 3] Fixed a conflict between DHCPv4-assigned and ND6-assigned DNS servers (#1596)
  • [Argon / Boron] Fixed a race condition when restarting the GSM07.10 multiplexer causing a memory leak/corruption (#1608)
  • [Gen 3] IPv4 IPAddress endianness issue fixed (#1610)
  • [Boron] Fixed a crash when using STARTUP() macro to manage Cellular credentials (#1613)
  • [Gen 3] Embedded user part update procedure fixed in for hybrid builds (#1617)
  • [communication] Sticky SKIP_SESSION_RESUME_HELLO no longer set immediately after session resume (#1623)
  • [Gen 3] OpenThread locking fixes (#1625)
  • [Gen 3] NetworkManager initiail state initialized in network_setup()
  • [Gen 3] IPv4 IPAddress endianness issue fixed (#1610)
  • [Gen 3] Fixes an assertion failure in LwIP DHCP code when receiving an offer with > 2 DNS servers (#1618)
  • [Argon / Xenon] Wire1 enabled (#1633)


  • [Boron] 3G Borons no longer incur 10 second power-on delay when cold booting (#1584)
  • [Gen 3] Build time significantly improved (#1587)
  • [Gen 3] Hardware-accelerated SHA-1 (#1593)
  • [Gen 3] Newlib 3.0 compatibility (#1599)
  • [Argon / Boron] AT parser immediately interrupted when GSM07.10 multiplexer exits asynchronously (e.g. terminated by the peer or due to keepalive timeout) (#1608)
  • [Gen 3] NAT64 initial base source port randomized on boot (#1609)
  • [Gen 3] LwIP optimizations (#1610)
  • [Gen 3] DHCP hostname option enabled (defaults to DeviceID) (#1595)
  • [Argon] WiFi passwords are not included in the logging output (#1619)
  • [Gen 3] Power failure comparator always configured with 2.8V threshold (#1621)
  • [Gen 3] Default mesh transmit power setting changed from 0dBm to 8dBm (#1629)
  • [Gen 3] BLE MTU and data length changed to default minimum values, while still allowing upgrade by the peer up to the maximums available on nRF52840 (#1634)


  • [Gen 3] SPI slave mode (#1588)
  • [Gen 3] I2C slave mode (#1591)
  • [Gen 3] Servo HAL (#1589)
  • [Gen 3] Implement a control request to retrieve the module info in the protobuf format (#1614)


  • [Gen 3] Run unit tests as part of a CI build (#1604).

Putting back in box (update: took back out of box...)
Can't flash Blink to Boron
Gen 3 improvements update - 12/17
Argon Setup Failure

Update - Android app v2.3.8 released

This release should be available in the Play store in the next 1-3 hours. It includes the ability to create debug logs to help with troubleshooting, and also fixes the top app crashes.

(The iOS app has had debug log support for a week or so and it has turned out to be very useful.)


Gen 3 improvements update - 12/17

We’ve put together a status update on past and future engineering efforts to improve the stability and reliability of Gen 3 hardware. To read the latest updates and provide feedback, please visit the update post.

Thank you for your feedback!