Particle Mesh Devices and OpenThread Connections in Anticipation of Google Breaking Changes
What is the plan when Google Nests OpenThread platform finds a security issue that needs to be corrected? They do what Google does best and make breaking changes to their platform, like what recently happened with the Google Product, Tensorflowjs .
How will Particle respond to that? The Particle Mesh Platform is based on the Nordic nrf52840 chip which is opensourced at OpenThread.
Anyone with that nrf52840 chip would then download a new Border Router with the corrected code and re-install corrected software to their chips and be up and running reasonably quickly.
But Particle has an Experimental Cloud Border Router instead of the on-site Border Router that OpenThread was designed to work with. Breaking changes will put Particle into a difficult situation: continue with their out-of-date product with the security hole, or upgrade to the new OpenThread that breaks the Particle System.
Easy solution: Particle releases a barebones version of the nrf52840 platform on OpenThread specifically designed for the Particle Mesh Devices, that would allow Particle Owners the choice to use a local Border Router and to install barebones software to their Mesh Devices while waiting for Particle to fix the breaking changes. Businesses need to be able to tell their customers they have backup plans ready and in place. People need to be able to design these backups now.
In a smaller way this is probably PART of the problem with the Particle HA Mesh Networks. OpenThread has probably changed from what worked 12 months ago when the Mesh Devices were being planned. Breaking changes are a matter of fact when working with Google Products. I have been simplifying Machine Learning Examples since 2015 and about every 3-6 months Google creates breaking changes while improving their products. The latest change to Tensorflowjs (see link above) has made obsolete my 78 Deep Learning examples. Over the last several weeks I have updated 33 of them ( https://www.rocksetta.com/tensorflowjs/ ). That is just how it works when using Google Products.
In many ways the Particle Photon is more stable than the Mesh Devices since Particle has made all the software that the Photon needs and does not rely on software from an outside source.
Let’s get our hardware working by beginning able to connect to OpenThread. Remember that connecting to OpenThread is not a big problem for Particle, it is the natural ability that the Nordic nrf52840 chip was designed for.
At the very least, let’s talk about the issues.
If you are interested in OpenThread abilities for your Particle Mesh Devices email me at firstname.lastname@example.org or follow me at twitter https://twitter.com/rocksetta or message me at github https://github.com/hpssjellis