Difference between revisions of "Device Firmware Updater"

From Hubitat Documentation
Jump to: navigation, search
(Created Device Firmware Updater doc)
m
Line 1: Line 1:
With the Device Firmware Update app, you may update your Z-Wave devices by downloading the appropriate firmware files from the manufacturer and store them directly on the hub for easy access. Support for securely joined devices and firmware file types HEX, OTZ, BIN, and GBL.  
+
With the Device Firmware Update app, you may update your Z-Wave devices by downloading the appropriate firmware files from the manufacturer and store them directly on the hub for easy access. Supports securely joined devices and firmware file types HEX, OTZ, BIN, and GBL.  
  
 
'''NOTE:''' Due to limitations of the former Z-Wave protocol version, this application is only compatible with '''Model C-7''' hubs.
 
'''NOTE:''' Due to limitations of the former Z-Wave protocol version, this application is only compatible with '''Model C-7''' hubs.
  
=== Perquisites ===
+
===Perquisites===
  
# Z-wave device that is Over the Air capable and supports ''Firmware Update MD Command Class V1-4''
+
#Z-wave device that is Over the Air capable and supports ''Firmware Update MD Command Class V1-4''
# Good connectivity between the device and your Hubitat hub.
+
#Good connectivity between the device and your Hubitat hub.
  
=== Warnings ===
+
===Warnings===
  
# Z-Wave devices are region specific. Make certain you have the firmware file that is correct for your region.
+
#Z-Wave devices are region specific. Make certain you have the firmware file that is correct for your region.
# Some devices will require Exclude and Include when the firmware update process is complete.
+
#Some devices will require Exclude and Include when the firmware update process is complete.
# '''DO NOT POWER CYCLE YOUR DEVICE UNTIL THE UPDATE COMPLETES'''
+
#'''DO NOT POWER CYCLE YOUR DEVICE UNTIL THE UPDATE COMPLETES'''
  
=== Installing the Device Firmware Updater app ===
+
===Installing the Device Firmware Updater app===
  
# From the Hubitat Web Interface select '''Apps'''[[File:Install Built-In App 2.0.png|none|thumb|600x600px]]
+
#From the Hubitat Web Interface select '''Apps'''[[File:Install Built-In App 2.0.png|none|thumb|600x600px]]
# Choose '''Device Firmware Updater''' from the list of Hubitat Elevation<sup>®</sup> built-In apps.[[File:Install Device Firmware Updater.png|none|thumb|600x600px]]
+
#Choose '''Device Firmware Updater''' from the list of Hubitat Elevation<sup>®</sup> built-In apps.[[File:Install Device Firmware Updater.png|none|thumb|600x600px]]
  
=== Uploading device firmware to the hub ===
+
===Uploading device firmware to the hub===
  
# Download the device manufacturer firmware update file and store it on your computer. Supported firmware file types are '''HEX, OTZ, BIN,''' and '''GBL'''.
+
#Download the device manufacturer firmware update file and store it on your computer. Supported firmware file types are '''HEX, OTZ, BIN,''' and '''GBL'''.
#* '''NOTE:''' Hubitat does not supply device firmware update files. You must obtain these directly from the device manufacturer.
+
#*'''NOTE:''' Hubitat does not supply device firmware update files. You must obtain these directly from the device manufacturer.
# Press the '''Update''' button to reveal the '''Choose File''' button, then navigate to the correct firmware update file for your device.[[File:Firmware update file selected.png|none|thumb|600x600px]]
+
#Press the '''Update''' button to reveal the '''Choose File''' button, then navigate to the correct firmware update file for your device.[[File:Firmware update file selected.png|none|thumb|600x600px]]
# Press the '''Upload''' button and confirm the file upload was successful before proceeding.[[File:Firmware upload confirmation.png|none|thumb|600x600px]]
+
#Press the '''Upload''' button and confirm the file upload was successful before proceeding.[[File:Firmware upload confirmation.png|none|thumb|600x600px]]
# Press the '''Back''' button, or the '''Done''' button to return to the main menu.[[File:Navigate back after firmware upload.png|none|thumb|600x600px]]
+
#Press the '''Back''' button, or the '''Done''' button to return to the main menu.[[File:Navigate back after firmware upload.png|none|thumb|600x600px]]
# Press the '''Update Z-Wave Firmware''' button.[[File:Update Z-Wave Firmware button.png|none|thumb|600x600px]]
+
#Press the '''Update Z-Wave Firmware''' button.[[File:Update Z-Wave Firmware button.png|none|thumb|600x600px]]
# Select the device for firmware update and choose the target firmware version to update.[[File:Select target device for firmware update.png|none|thumb|600x600px]]
+
#Select the device for firmware update and choose the target firmware version to update.[[File:Select target device for firmware update.png|none|thumb|600x600px]]
# Select the device firmware update file you uploaded to the hub, then press the '''Start Firmware Update''' button.[[File:Select device firmware file and start update.png|none|thumb|600x600px]]
+
#Select the device firmware update file you uploaded to the hub, then press the '''Start Firmware Update''' button.[[File:Select device firmware file and start update.png|none|thumb|600x600px]]
#* '''<span style="color: red;;">IMPORTANT</span>''': Battery powered devices frequently "Sleep" to preserve battery power, and you may need to "Wake" them a few times before the process can complete. Refer to the  manufacturer instruction manual to determine the wake mechanism for your particular device. You must also [[Devices#Disable Device Drivers|disable the device driver]] for "sleepy" devices to prevent ''wakeupNoMoreInformation'' from being sent during the update process. Mains powered devices are not "sleepy" and do not require their driver be disabled.[[File:Requesting firmware transfer start.png|none|thumb|600x600px]][[File:Starting transfer of firmware image.png|none|thumb|600x600px]][[File:Starting update on Node.png|none|thumb|600x600px]]
+
#*'''<span style="color: red;;">IMPORTANT</span>''': Battery powered devices frequently "Sleep" to preserve battery power, and you may need to "Wake" them a few times before the process can complete. Refer to the  manufacturer instruction manual to determine the wake mechanism for your particular device. You must also [[Devices#Disable Device Drivers|disable the device driver]] for "sleepy" devices to prevent ''wakeupNoMoreInformation'' from being sent during the update process. Mains powered devices are not "sleepy" and do not require their driver be disabled.[[File:Requesting firmware transfer start.png|none|thumb|600x600px]][[File:Starting transfer of firmware image.png|none|thumb|600x600px]][[File:Starting update on Node.png|none|thumb|600x600px]]
#* '''NOTE''': Some devices will update very slowly when device security is enabled. Additionally the firmware update protocol is designed to ease-off if there is an increase in network activity, and factors such as network conditions, the number of hops from the hub to the device, and distance will influence the amount of time required to complete the firmware update. The maximum size of a frame is 64 bytes. The protocol header and checksum takes 10 bytes in a single cast, leaving 54 bytes for the payload. A S0 security enabled single cast takes 20 bytes as overhead. The maximum dataLength field depends on the transmit options and whether a nonsecure/secure frame is used. Therefore if there is no security enabled, the firmware can be sent to the device in larger chunks and the overall update process will be faster.[[File:Update 2 percent complete.png|none|thumb|600x600px]]
+
#*'''NOTE''': Some devices will update very slowly when device security is enabled. Additionally the firmware update protocol is designed to ease-off if there is an increase in network activity, and factors such as network conditions, the number of hops from the hub to the device, and distance will influence the amount of time required to complete the firmware update. The maximum size of a frame is 64 bytes. The protocol header and checksum takes 10 bytes in a single cast, leaving 54 bytes for the payload. A S0 security enabled single cast takes 20 bytes as overhead. The maximum dataLength field depends on the transmit options and whether a nonsecure/secure frame is used. Therefore if there is no security enabled, the firmware can be sent to the device in larger chunks and the overall update process will be faster.[[File:Update 2 percent complete.png|none|thumb|600x600px]]
#* '''<span style="color: red;;">WARNING:</span> DO NOT POWER CYCLE YOUR DEVICE UNTIL THE UPDATE COMPLETES'''[[File:Firmware update 26 percent complete.png|none|thumb|600x600px]][[File:Firmware update 100 percent complete.png|none|thumb|600x600px]][[File:Sent last fragment waiting for device.png|none|thumb|600x600px]][[File:Transfer 100 percent confirmation.png|none|thumb|600x600px]][[File:Firmware update complete.png|none|thumb|600x600px]]
+
#*'''<span style="color: red;;">WARNING:</span> DO NOT POWER CYCLE YOUR DEVICE UNTIL THE UPDATE COMPLETES'''[[File:Firmware update 26 percent complete.png|none|thumb|600x600px]][[File:Firmware update 100 percent complete.png|none|thumb|600x600px]][[File:Sent last fragment waiting for device.png|none|thumb|600x600px]][[File:Transfer 100 percent confirmation.png|none|thumb|600x600px]][[File:Firmware update complete.png|none|thumb|600x600px]]
# Press '''Done''' to exit the Device Firmware Updater. For best results, you should power cycle your device '''AFTER''' the firmware update is complete.[[File:Press Done to exit Firmware updater.png|none|thumb|600x600px]]
+
#Press '''Done''' to exit the Device Firmware Updater. For best results, you should power cycle your device '''AFTER''' the firmware update is complete.[[File:Press Done to exit Firmware updater.png|none|thumb|600x600px]]

Revision as of 02:03, 19 December 2020

With the Device Firmware Update app, you may update your Z-Wave devices by downloading the appropriate firmware files from the manufacturer and store them directly on the hub for easy access. Supports securely joined devices and firmware file types HEX, OTZ, BIN, and GBL.

NOTE: Due to limitations of the former Z-Wave protocol version, this application is only compatible with Model C-7 hubs.

Perquisites

  1. Z-wave device that is Over the Air capable and supports Firmware Update MD Command Class V1-4
  2. Good connectivity between the device and your Hubitat hub.

Warnings

  1. Z-Wave devices are region specific. Make certain you have the firmware file that is correct for your region.
  2. Some devices will require Exclude and Include when the firmware update process is complete.
  3. DO NOT POWER CYCLE YOUR DEVICE UNTIL THE UPDATE COMPLETES

Installing the Device Firmware Updater app

  1. From the Hubitat Web Interface select Apps
    Install Built-In App 2.0.png
  2. Choose Device Firmware Updater from the list of Hubitat Elevation® built-In apps.
    Install Device Firmware Updater.png

Uploading device firmware to the hub

  1. Download the device manufacturer firmware update file and store it on your computer. Supported firmware file types are HEX, OTZ, BIN, and GBL.
    • NOTE: Hubitat does not supply device firmware update files. You must obtain these directly from the device manufacturer.
  2. Press the Update button to reveal the Choose File button, then navigate to the correct firmware update file for your device.
    Firmware update file selected.png
  3. Press the Upload button and confirm the file upload was successful before proceeding.
    Firmware upload confirmation.png
  4. Press the Back button, or the Done button to return to the main menu.
    Navigate back after firmware upload.png
  5. Press the Update Z-Wave Firmware button.
    Update Z-Wave Firmware button.png
  6. Select the device for firmware update and choose the target firmware version to update.
    Select target device for firmware update.png
  7. Select the device firmware update file you uploaded to the hub, then press the Start Firmware Update button.
    Select device firmware file and start update.png
    • IMPORTANT: Battery powered devices frequently "Sleep" to preserve battery power, and you may need to "Wake" them a few times before the process can complete. Refer to the manufacturer instruction manual to determine the wake mechanism for your particular device. You must also disable the device driver for "sleepy" devices to prevent wakeupNoMoreInformation from being sent during the update process. Mains powered devices are not "sleepy" and do not require their driver be disabled.
      Requesting firmware transfer start.png
      Starting transfer of firmware image.png
      Starting update on Node.png
    • NOTE: Some devices will update very slowly when device security is enabled. Additionally the firmware update protocol is designed to ease-off if there is an increase in network activity, and factors such as network conditions, the number of hops from the hub to the device, and distance will influence the amount of time required to complete the firmware update. The maximum size of a frame is 64 bytes. The protocol header and checksum takes 10 bytes in a single cast, leaving 54 bytes for the payload. A S0 security enabled single cast takes 20 bytes as overhead. The maximum dataLength field depends on the transmit options and whether a nonsecure/secure frame is used. Therefore if there is no security enabled, the firmware can be sent to the device in larger chunks and the overall update process will be faster.
      Update 2 percent complete.png
    • WARNING: DO NOT POWER CYCLE YOUR DEVICE UNTIL THE UPDATE COMPLETES
      Firmware update 26 percent complete.png
      Firmware update 100 percent complete.png
      Sent last fragment waiting for device.png
      Transfer 100 percent confirmation.png
      Firmware update complete.png
  8. Press Done to exit the Device Firmware Updater. For best results, you should power cycle your device AFTER the firmware update is complete.
    Press Done to exit Firmware updater.png