Hello,
Should Recipe updates be automatically carried over to all devices? Or is there a step missing to push updated recipes to all devices?
Picture below…shows that we made some changes to attribute tags but the parameters were not carried over.
Hey @Micheal_Davis!
Device recipe changes are not automatically applied to devices created from that recipe. You’ll have to use the Bulk Update functionality to make the same change to your existing devices.
Devices created from a recipe are automatically tagged with the name of that recipe (DeviceRecipe=Name). You can use that to filter devices when performing the bulk update.
Thanks Brandon. We updated an attribute tag. What property/action is the correct one? Is it the Attribute Tag Set? 
Correct, it is the Attribute Tag: Set action.
Thank you. Wish me luck!
When doing bulk updates, I do recommend doing a test run on a single device to ensure you get the correct result. You can then expand the query to include multiple devices.
1 Like
Would be nice to have the ability to Push a Recipe Update from the Devie Recipe location. More intuitive too but that’s from my POV.
Totally agree. We have discussed internally how we could accomplish something like that.
1 Like
Oh wait. So we went into the recipe and added the new attributes there but now we have to redo it on the Attribute Tag set too on the Bulk Update? What’s the purpose of the Device Recipe section? Seems like something is missing connecting the two.
Recipes are used when creating devices only. Once the device is created, it is disconnected and changes can be made to either independently. If you’re creating devices from recipes, you’ll still need to update the recipe so that future devices have the modified attribute tag.
Ok Thank you for the explanation. If you ever have a poweruser conference on change request….let me know. We have tons of ideas.
We’d love to get the feedback! We do periodic customer success calls with nearly every customer and that’s a great way to discuss. We’ll reach out and get one on the calendar.
1 Like
Morning Brandon, I came to post something similar. Thanks Micheal_Davis for getting here before me. Our fleets are intended to get OTA updates that often add new functionality worthy of monitoring. We have historically done Patches but it would be a great feature to simply apply a new Recipe.
+1 to request for some kind of functionality like this.
We’re noodling over how best to handle this request, because there are a lot of “gotcha” cases about updates to recipes that you actually wouldn’t want to propagate to devices created from the recipe. For example, device tag values that are unique per device or parent system IDs.
So, would you mind sharing the actual use you think this feature would help with? For example, are you adding a new attribute to each device created from the recipe? Are you bulk-changing a tag value to a single, static value? Adding a new tag to each device but with a different value per device?
If you can tell us more about the real-world use case, that would be helpful.
I’ll give you the scenario as it has played out over the past 12 months or so. A set of devices, fielded over the course of months have capability in the platform that we were not leveraging on day 1. As the firmware catches up to the capability of the hardware, more information becomes available from the edge (both tags and attributes).
When this occurs, we create a new recipe that correlates to the new attribute/tag set. That recipe is used for newly created devices henceforth.
Fielded devices that are already reporting get a bulk update that adds the new tags and attributes. MUCH care must be taken when doing the bulk updates to ensure they basically match the newly created recipe.
I do see the challenge you face with innumerable ‘gocha’ cases. The only way I would know to address that would be to have some devices created with an immutable tag of the recipe id used to create them, and they themselves become immutable. (no new attributes or tags could be added)
Or have a pretty complicated melding process that groups up devices into ‘like kind’ collections that have the same tag/attribute set where the updating agent could handle the deltas.
All that being said, this is a nice to have, but its a sizable ask with not substantial reward for us. As days go by, and the platform becoming more stable, we find that we are having to do this less and less.
1 Like