Using a Particle Xenon without Particle Mesh

In January of 2020, Particle announced that Mesh networking support in Gen3 devices would be deprecated. While this change does not affect the ability of customers to use the Argon and Boron as standalone devices, because the Particle Xenon is a Mesh-only device, it is not possible to use this device with the Particle Device Cloud in a production-supported context.

It is possible to continue to use your Particle Xenon, either as a standalone device, or in unsupported Particle Mesh networks. This document provides information regarding the various contexts in which the Xenon can be used, as well as instructions for provisioning your Xenon for another use, if needed.

Option 1: Continue to use your Xenon as a Particle Device

If you wish, you can continue to use your Xenon as a part of a pre-existing Particle Mesh network, provided that your network was provisioned before the end of 2020 and is running as version of Device OS that supports Mesh (i.e. 1.6.x). Later versions do not support Particle Mesh and do not support the Xenon as a build target.

Please note that this option, while available, is not supported by Particle for production use.

You can also use your Xenon in standalone mode, with no network connectivity.

Option 2: Provision your Xenon as a non-Particle dev kit

Alternatively, you can provision your Xenon for use as a dev kit disconnected from the Particle platform. Available options are:

These options will remove the Particle Device OS and bootloader, so the device will no longer be able to connect to the Particle Device Cloud.

Option 3: Use your Xenon with the Ethernet FeatherWing

Using Device OS 1.6.x you can continue to use a Xenon in the Ethernet FeatherWing. You can continue to do so after January 1, 2021, however you will only be able to claim a Xenon to your account using the Particle CLI as there will be no mobile app support at that time.