Hi all, I am finalising an application that will be deployed using Electrons powered via solar, so power and data minimisation are important. The implementation will have multiple Electrons sending a small payload every 10 minutes to a common web-service via particle publish. I can use the coreid within the json to uniquely identify the source of the payload, but would prefer to use the device name as this is fewer bytes and more meaningful in the dashboard reporting supporting the implementation. I could include Particle.subscribe("spark/", handler); Particle.publish("spark/device/name"); within the Electron code and and then send the device-name back as part of the data, however this incurs 2 additional cloud calls and a slightly larger payload. Does anyone know of a means to derive this from within the webhook json or can inclusion of {{spark_core_name}} as a webhook variable be a future consideration. Thanks, Dean

Hey Dean, did you ever get a solution to this? I am looking to do the same thing.

Me too! EDIT: Found answer here: [image] How to include Device Name (Not just Device ID) in SMS when using Messaging Cloud API (Twilio) Cloud The device name will not be added by the webhook services, so you’d need to actively embed it in your event payload. Although this would be a nice feature to propose, which can be done via a GitHub “issue” report here

Device name as variable for webhook

Cloud

jaza_tom November 21, 2017, 11:45pm 3

Me too!

EDIT:

Found answer here:

Topic		Replies	Views
Device name as a webhook variable options Cloud	1	1271	November 21, 2017
JSON WebHook Clarification Cloud	8	2300	August 1, 2016
How to include Device Name (Not just Device ID) in SMS when using Messaging Cloud API (Twilio) Cloud	23	5188	April 13, 2020
Device Name in Webhook Cloud	2	2467	June 27, 2017
Device Name Webhook pre-defined variable Cloud	2	482	October 20, 2021

Device name as variable for webhook

Related topics