ear Hubitat Technical Support Team,
Hello!
We are the manufacturer of the device with model number 3RSP02064Z , which has been submitted to you for official adaptation.
We are currently planning the firmware upgrade path for this device. Due to a PID change during product iteration, we intend to implement a "staged OTA" solution to ensure all existing devices in the field can upgrade correctly and securely to a unified new version. We are writing to inquire about the technical feasibility of this approach on your platform.
Requirement Details:
We aim to implement the following logic: when a device queries the OTA server for updates, the server should automatically deliver the corresponding firmware file based on the device's reported current firmware version (current_version ).
- For devices with a current version ≤ 40 , deliver Firmware A (which contains the old PID in its header).
- For devices with a current version > 40 , deliver Firmware B (which contains the new PID in its header).
(Both firmware files share the same target version number.)
Specific Questions:
- Platform-Level Support: Does Hubitat's official OTA management system natively support configuring and automatically routing different firmware files based on
current_version(or similar metadata fields likemin_current_file_version/max_current_file_version)? - Alternative Approach: If this is not a native feature of the platform, does Hubitat have a recommended implementation method or best practice to achieve the above requirement? (For example, implementing logic within a custom device driver).
Understanding this information is crucial for our development planning. We have the relevant technical details prepared and look forward to your professional advice.
Thank you for your support.