Problems compiling Blynk.edgent for Particle

I am migrating a working device from an ESP32/Arduino platform to the Particle Boron platform. Many functions and libraries are compatible and I am successful in getting my non-edgent code to compile and run. But as I added in the Blynk.edgent() example code and required includes I ran into a problem: there is a dependency for a file called <BlynkSimpleEsp32_SSL.h>. So, I added this file and now the problems cascaded into compiler (C++, not Arduino) messages like “this code is for ESP32”. Before going down this (likely) long path, I am looking for advice on how to proceed. As Particle is supported by Blynk I assume there is a solution somewhere…

#define BLYNK_TEMPLATE_ID "TMPL2p5P7W8B5"
#define BLYNK_TEMPLATE_NAME "Asset Tracker 1"
// Adding the required libraries
#include "Particle.h"
#include <blynk.h>
#include "BlynkEdgent.h"
#include <SensirionI2CScd4x.h>
#include <SensirionI2cSen66.h>
#include <Adafruit_SSD1306.h> // .9 inch OLED
#include <Adafruit_GFX.h>

Blynk Edgent only supports a limited number of board types:

Pete.

Ok thanks Pete, should have looked more closely at the docs. So guess it’s Static Tokens for my cellular Particle device. But not sure how to manage, say, 100 unique tokens while avoiding 100 separate firmwares. Thinking about using, say, EEPROM to store token and insert into code before shipment to end user?

@Oleksii-QA could you please check with hardware team for a link to particle provisioning code. Thanks

Will do thanks much!

Hello @drewc228.

I asked in our hardware team. Blynk.Edgent for Particle is available at GitHub - Blynk-Technologies/Blynk-Edgent-Particle: Blynk.Edgent for Particle