Now I want to instantiate a second ESP32 module with the same functions, and try to control module 1 or module 2 (that will control two different machines) from the same dashboard.
I do not find how to implement this functionality.
Thanks, Jackson, for your time, and pointing me to the Dashboard video.
I will try to clarify my question.
I got info from the subscription plan where Arduino Team states
Q Is in your definition each thing attached to a particular machine?"
"Or is like a class that we can instantiate many times ?"
No, Each "thing" can be on many machines, for example, you no longer want to use a device so you unlink it and you can associate another of your choice.
So I start from the concept that One Thing can be on many machines. My "Machines" are electronic devices for agricultural projects. They are mobile, open air devices, and GSM connected, because proximity is not doable.
I need to subscribe a paid plan, and I feel that my case will need a "Maker" plan, to get 90 day persistence, and Dash sharing.
NOW:
I need to implement this:
Define my "Thing" and create one instance in each machine.
Thing is defined and running properly, for the first instance.
Next step is to have a second instance of the same Thing.
Each user may have one or many machines.
The user needs one dashboard to controls their machine(s)
We, as machine and IoT provider, we need to access all machines data.
That is the case.
So we want to start creating a second instance of the same Thing, and simulate the dashboards scenarios.
Last: we get the concept of "Thing" from the technical point of view, but not from the plan licensing point of view.
I'm not using the Arduino cloud but what you want to achieve seems advanced for what I understand from the current capabilities.
It requires custom configuration each time based on the devices you have
things can share variables so that's one way to drive some synchronisation across devices
I'm not aware of a "super user" mode where you would see all the machines from all the customers
my view is that you need your own back end service. You could have a MQTT server as the central hub where device would register themselves as being part of a configuration and use MQTT messaging as the management layer (both ways).