Hello. I have a few questions about my intended strategy for setting up Google Cloud Integrations in Particle Console.
First main question, is there a limit to how many integrations I can have?
Further explanation of intended application - I welcome feedback or advice on what I intend to do.
I will have many possible locations, each with a single Particle device. Each location will stream operational data, and will also receive control instructions triggered by Cloud Functions. There may eventually be 1000 or more locations.
To conserve cellular data, I want to make sure all control events are not sent to all devices, and similarly, if a given location sends sensor data, I want to make sure any acknowledgement packets are only sent back to the original device, and not all devices thus wasting cell data.
Also, I feel each location should have its own topic and associated integration, so we don’t have all 1000 locations publishing to the same topic (though I’m willing to do this if it is the ‘correct’ approach and doesn’t incur negatives).
My idea is as follows:
Create two Google Cloud pub/sub topics for each device/location, one for incoming data (called ‘pub_data’ or something similar) and one for outgoing control data (called ‘control_data’ or similar).
I would then create two new matching integrations for each device/location. This of course will eventually result in up to 2000+ integrations inside the Particle Console. This sounds like it may cause problems later, unless this is totally okay to do. (I notice the Integrations window in Particle Console shows each Integration as a large icon, so this page may become very full with over 1000 of them).
Each device/location may have slightly different firmware as each location may be slightly custom. For this reason, I prefer to avoid adding them all as a “product” and rather, track them as individual devices that will be named by location number. This would allow us to remotely update a given location/device if a customer needs a change.
Any thoughts or advice on this approach very much appreciated.