Updat update doc

Author: npentrel

assets/how-tos/deploy-packages/add-package.png

@@ -10,7 +10,7 @@ languages: []
 viamresources: []
 platformarea: ["registry", "fleet"]
 level: "Intermediate"
-date: "2024-08-28"
+date: "2025-02-05"
 aliases:
   - /how-tos/deploy-packages/
   - /manage/software/deploy-packages/
@@ -37,7 +37,7 @@ If at least some of your machine control logic should run on your machine, place
 
 {{% alert title="OTA updates for microcontrollers" color="note" %}}
 The following steps do not cover how to create a module with machine control logic for microcontrollers.
-For microcontrollers, see [Micro-RDK modules](/operate/get-started/other-hardware/micro-module) and [Over-the-air firmware updates](/operate/get-started/other-hardware/micro-module/#over-the-air-updates) instead.
+For microcontrollers, see [Micro-RDK modules](/operate/get-started/other-hardware/micro-module/) and [Over-the-air firmware updates](/operate/get-started/other-hardware/micro-module/#over-the-air-updates) instead.
 {{% /alert %}}
 
 {{< table >}}
@@ -60,7 +60,7 @@ Follow the prompts, selecting the following options:
   In the example snippets below, the namespace is `naomi`.
 - Resource to be added to the module: `Generic Component`.[^generic]
 - Model name: Your choice, for example `control-logic`
-- Enable cloud build: Choose `Yes` if you are using GitHub or want to make use of cloud build.
+- Enable cloud build: Choose `Yes` if you are using GitHub or want to use cloud build.
 - Register module: `Yes`
 
 Press the Enter key and the generator will create a folder for your control logic component.
@@ -81,7 +81,7 @@ Be sure to also implement logic to handle subsequent calls to the reconfigure me
 
 For example, in Python, start your logic in <FILE>src/main.py</FILE>:
 
-```python {class="line-numbers linkable-line-numbers" data-line="15-23"}
+```python {class="line-numbers linkable-line-numbers" data-line="19-26"}
 # Add these imports
 import asyncio
 from threading import Event
@@ -90,6 +90,7 @@ from viam.logging import getLogger
 
 LOGGER = getLogger("control-logic")
 
+
 class ControlLogic(Generic, EasyResource):
     MODEL: ClassVar[Model] = Model(
         ModelFamily("naomi", "my-control-logic"), "control-logic"
@@ -101,7 +102,8 @@ class ControlLogic(Generic, EasyResource):
     # Other methods omitted for brevity
 
     def reconfigure(
-        self, config: ComponentConfig, dependencies: Mapping[ResourceName, ResourceBase]
+        self, config: ComponentConfig,
+        dependencies: Mapping[ResourceName, ResourceBase]
     ):
         # starts automatically
         if self.running is None:
@@ -174,7 +176,7 @@ For complete examples that implement control logic, see:
 
 Once you have implemented your control logic, commit and push your changes to a GitHub repository.
 
-If you are not using GitHub, see [Upload your module](/operate/get-started/other-hardware/#upload-your-module) and [Update an existing module](/other-hardware/manage-modules/#update-an-existing-module) for more information on alternatives.
+If you are not using GitHub, see [Upload your module](/operate/get-started/other-hardware/#upload-your-module) and [Update an existing module](/operate/get-started/other-hardware/manage-modules/#update-an-existing-module-using-a-github-action) for more information on alternatives.
 
 Follow the steps in [Upload your module](/operate/get-started/other-hardware/#upload-your-module) using cloud build.
 

assets/how-tos/deploy-packages/fragment.png

@@ -5,15 +5,20 @@ weight: 40
 layout: "docs"
 type: "docs"
 description: "As new versions of software modules or ML models become available, you can update the deployed version on all machines in one go."
+date: "2025-02-05"
 aliases:
   - /manage/software/update-packages/
 ---
 
 If you have already [deployed software](/manage/software/deploy-software/), you can inspect the fragment you have created.
-The JSON object for the deployed package has a `version` field.
+The JSON object for the deployed module or package has a `version` field.
+Unless the `version` field is set to a specific version, some or all updates for that module or package can happen automatically.
 
-As new versions of software modules or ML models become available, you can update the deployed version in one go using the fragment.
-TODO - might auto update?
+To perform other updates or changes to the configuration of all machines using the fragment:
+
+1. [Test your updates](#test-updates)
+2. [Update the software version and roll out the changes](#update-the-software-version)
+3. [Check the status of your machines](#check-machine-status)
 
 We strongly recommend that you test updates on a subset of machines before deploying it to all machines.
 
@@ -41,26 +46,32 @@ Paste the JSON object from your primary fragment.
 {{% tablestep %}}
 **2. Edit the fragment**
 
-Change the version of your package in the development fragment.
+Change the version of your module or package in the development fragment.
 For example:
 
-```json {class="line-numbers linkable-line-numbers" data-line="16"}
+```json {class="line-numbers linkable-line-numbers" data-line="22"}
 {
-  "services": [
+  "components": [
+    {
+      "api": "rdk:component:camera",
+      "attributes": {},
+      "model": "rdk:builtin:fake",
+      "name": "camera-1"
+    },
     {
-      "name": "speech-1",
-      "namespace": "viam-labs",
-      "type": "speech",
-      "model": "viam-labs:speech:speechio",
-      "attributes": {}
+      "api": "rdk:component:generic",
+      "attributes": {},
+      "model": "naomi:my-control-logic:control-logic",
+      "name": "generic-1"
     }
   ],
+  "debug": true,
   "modules": [
     {
+      "module_id": "naomi:my-control-logic",
+      "name": "naomi_my-control-logic",
       "type": "registry",
-      "name": "viam-labs_speech",
-      "module_id": "viam-labs:speech",
-      "version": "0.5.3"
+      "version": "0.0.7"
     }
   ]
 }
@@ -78,7 +89,7 @@ If you had configured them already with the primary fragment, remove that fragme
 **4. Test the new version**
 
 Test the new version of your package.
-When you are satisfied that your package works as expected, continue to [update your primary fragment](#update-a-package-version).
+When you are satisfied that your package works as expected, continue to update your primary fragment.
 
 {{% /tablestep %}}
 {{< /table >}}
@@ -103,37 +114,43 @@ Click **Save** in the upper right corner of the screen.
 **2. Test the new version**
 
 Test the new version of your package.
-When you are satisfied that your package works as expected, continue to [update your primary fragment](#update-a-package-version).
+When you are satisfied that your package works as expected, continue to [update your primary fragment](#update-the-software-version).
 
 {{% /tablestep %}}
 {{< /table >}}
 
 {{% /tab %}}
 {{< /tabs >}}
 
-## Update a package version
+## Update the software version
 
-Once you have confirmed that the new version of your package works, go to your primary fragment and edit it to use the new version of your package.
+Once you have confirmed that the new version of your module or package works, go to your primary fragment and edit it to use the new version.
 
 For example:
 
-```json {class="line-numbers linkable-line-numbers" data-line="16"}
+```json {class="line-numbers linkable-line-numbers" data-line="22"}
 {
-  "services": [
+  "components": [
+    {
+      "api": "rdk:component:camera",
+      "attributes": {},
+      "model": "rdk:builtin:fake",
+      "name": "camera-1"
+    },
     {
-      "name": "speech-1",
-      "namespace": "viam-labs",
-      "type": "speech",
-      "model": "viam-labs:speech:speechio",
-      "attributes": {}
+      "api": "rdk:component:generic",
+      "attributes": {},
+      "model": "naomi:my-control-logic:control-logic",
+      "name": "generic-1"
     }
   ],
+  "debug": true,
   "modules": [
     {
+      "module_id": "naomi:my-control-logic",
+      "name": "naomi_my-control-logic",
       "type": "registry",
-      "name": "viam-labs_speech",
-      "module_id": "viam-labs:speech",
-      "version": "0.5.3"
+      "version": "0.0.7"
     }
   ]
 }

assets/how-tos/deploy-packages/insert.png

@@ -285,7 +285,7 @@ There is no way to roll back to previous firmware after a bad upgrade without re
 {{% /alert %}}
 
 {{% alert title="Tip" color="tip" %}}
-To update the firmware version for a group of microcontrollers at the same time, you can [create a fragment](/manage/software/deploy-packages/) with the OTA service configuration and apply it to multiple machines.
+To update the firmware version for a group of microcontrollers at the same time, you can [create a fragment](/manage/software/deploy-software/) with the OTA service configuration and apply it to multiple machines.
 Then, whenever you update the `version` field in the fragment, the version will be updated for each machine that has that fragment in its config, triggering a firmware update the next time the devices fetch their configs.
 {{% /alert %}}