How to setup Argon / Photon2 using Ethernet shield?

Connectivity
,
1

I'm coming back to Particle to hopefully build a successful product that needs internet access often though network cables (not WiFi).

I got a few Argon's and an original Particle "Ethernet Feather Wing v1.0" to test on.

I got the Argon over network cable working in the cloud (including uploading code) by setting it up using WiFi first. Then adding the following inside an exable "blick light" script :

SYSTEM_THREAD(ENABLED);

void setup() 
{
  System.enableFeature(FEATURE_ETHERNET_DETECTION);
}

As described in the documentation here :

After removing the WiFi connection it does work over network cable.

But... I read the setup process should be also allowed through Ethernet.
But I'm running in dead ends trying to find out how.

Removed // Mobile App "Ethernet" option :
You used to be able to tell the setup in the mobile app that there is an Ethernet shield that it should use instead of WiFi.
Mobile App no longer exists!

Removed // CLI setup :
I think you could also tell there is an Ethernet shield present through CLI.
CLI setup no longer exists!

Removed // Web setup Auto Check during setup :
I read somewhere that it used to check for presence of ethernet shield through the web setup (https://setup.particle.io/).
But I also read now that this is no longer done as it might do unwanted trigger on pins used in other projects.

So...

How does one now do the setup process using an ethernet shield, if all the past way's have been removed?

2

It depends on whether you are setting up a single developer device or a product.

For a product, you'd typically flash the device with an upgrade of Device OS, as well as your product firmware, which includes the line to enable the Ethernet configuration so the device will boot up being able to connect to Ethernet.

Since you have Ethernet and a product, as long as you pre-add the Device IDs to your product when the device is plugged into Ethernet and turned on, it will immediately connect to the Particle cloud running your firmware and be part of your product.

3

Hey, some food for thought. Since Argons are deprecated, you will need to look into viable options.

You have the Photon 2, which is kind of the replacement for the Argon, and you have the Muons, which is a dev board that comes with an Ethernet port.
Cheers,

image

image

4

Thank you,

So I guess it is possible then, but something you do when scaling up.

I have already setup my Argon's to be inside a product group in the Particle cloud.

Will have to do some reading up on how to do this proper and how to flash it yourself without having to go through the setup process.

So as I understand there is no other way anymore to do it. That answers my question :slight_smile:

@gusgonnet Thank you, I'm aware of the Argon's being deprecated. We will switch for Photon2 if the product starts to gain traction.
As I understood so far there should be little change between the Argon and Photon. But will need to do some testing at some point.

Also, I guess the Muons dev board would also not be able to setup over ethernet? I guess this would be a setup to test flashing devices yourself? And later also use it to flash smaller production runs?