I am new here and created a forum account because I can’t find a nice solution for this problem after days of research.
I have a product using Electrons which has a Product ID and push version updates via this.
The product is sold previously to just one customer.
We are using Ubidots for visualisation and alerts, and push events to Ubidots using Webhooks.
We also in parallel are creating our own web app on our own server, and push the same events to it using webhooks. (to eventually replace Ubidots)
This first customer runs his own Azure IoT hub and we push events to him for Azure using Azure integration webhook from our product devices.
Now we have a second customer who is purchasing the same product and in the future there will be (hopefully) many new different customers.
If I add a device to the same product, then the Azure webhook will publish the event of the 2nd customer also to the first customer.
I want to have the device firmware identical in the same product so I can’t use different event names for the same events just to control the web hooks.
The only way I can think off is to create a new Product / ID, but the device is really the same “product” and future firmware upgrades would mean multiple deployments. We also have to setup new webhooks, and this would occur for every new customer. - New Product ID plus new Webhooks for each customer who has his own IoT platform.
It seems the solution would require that the Webhooks in web console have a Device selection option, instead of just “all”. So for example in the Azure integration you can choose the devices to webhook for instead of “all” in the Product.
This would also be useful I guess for standard webhooks as well.
Alternatively the particle server needs some sort of “Customer” or “Organisation” grouping structure as well as Product grouping?
Looking for feedback if I am actually using Products > Webhooks correctly, or if I am missing something?
Surely this would have come up before?
Thank you in advance.