Add Sonoff MINI-ZBDIMMER v1.0.5

[1775939187]

OTA file

mini-zbdim_v1.0.5.zip

Release notes

Update:

• Added manual calibration.
• Modified default values ​​for external switch dimming rate and transition time.
• Long-press dimming function for single-rebound external buttons; simultaneously updated to long-press brightness adjustment function for double-rebound and triple-rebound buttons.
• Removed minimum brightness setting item.

How to handle existing images of the same type

Keep all (standard)

Optional metadata

manufacturer_names: [SONOFF]
model_names: [MINI-ZBDIM]

Checklist

• The OTA image provided is in a supported format (e.g., .zigbee, .ota, or a ZIP containing one of these)
• I have filled out the release notes to the best of my ability
• The OTA image is tested and verified to work on a physical device

Additional information

No response

[zigpy-bot]

✅ Successfully processed your OTA submission! A pull request has been created with your changes:

• Add Sonoff MINI-ZBDIMMER v1.0.5 #177

Last reprocessed: 2026-06-15 03:39 UTC

[TheJulianJES]

@1775939187 Thanks! The other Sonoff PRs are all good – I'll merge them next. I just did a bit of testing with the S60 plug.

This PR

I do have one quick question on the release notes for this MINI-ZBDIM v1.0.5:
Now, this PR adds the same OTA image that was already submitted with:

• Add Sonoff MINI-ZBDIM v1.0.5 #27 (submitted issue)
• Add Sonoff MINI-ZBDIM v1.0.5 #28 (auto-generated PR)

Merging this new submission/PR would only update the release notes a bit. That could also be done directly by editing the corresponding YAML metadata:

• So, in the future, if you ever want to update the metadata (e.g. release notes) for already merged updates directly, you can just go to images/sonoff/ in this repo, and select the corresponding YAML file with all the metadata.
• Then click the "Edit" button in the top of the GitHub web editor to edit it. It then submits a PR with that edit.
  For editing this device's metadata, it would be this file: https://github.com/zigpy/zigpy-ota/blob/dev/images/sonoff/1286-0045-00001005_ea654a.ota.yaml
• Note: There's also an overview of all the available firmware (with file names) in the README:
  "Browse available firmware" -> Dev channel (here).

I'll make sure this is all handled correctly now, but please confirm one thing:
Which release notes are correct for the MINI-ZBDIM v1.0.5 update:

A: Current ones:

Bugfixes

• Calibration method set fail

New features

• NTC threshold value update to 115°C
• Firmware supports manual calibration mode to allow direct configuration of minimum and maximum level
• Light dimming is supported when the key type is single touch key

B: New ones (from this submission):

• Added manual calibration.
• Modified default values ​​for external switch dimming rate and transition time.
• Long-press dimming function for single-rebound external buttons; simultaneously updated to long-press brightness adjustment function for double-rebound and triple-rebound buttons.
• Removed minimum brightness setting item.

Are A or B the correct release notes? Or a combination or both maybe? This is the only question I have for you.
No need to do anything else here. I'll handle the rest.

---

General note on the manufacturer_names and model_names

This is just some information below (and unrelated to my question above). No need to do anything, but it might simplify future submissions if you can just leave out the model_names and manufacturer_names:

• We do not strictly need manufacturer_names and model_names in the submission if the manufacturer ID and image type ID of the OTA files is correctly set.
• It's only needed if multiple OTA images (incorrectly) share the same image type ID. For example: a firmware update for a temperature sensor and another update for a smart plug both use the same image type ID.
  • That should not be the case anyway, but we can make it work with ZHA by adding model_names as extra matching metadata to both submissions/image metadata.

How ZHA OTA matching works

So to clarify what happens with zigpy/ZHA:

• ZHA always checks the manufacturer ID and image type ID that devices request.
  • They always need to match the OTA image header data. Otherwise, the update won't be shown for that device.
  • So without manufacturer_names and without model_names, ZHA already checks that the following match:
    OTA manufacturer ID and OTA image type ID (in OTA header need to match what the device requests)
• However, some manufacturers incorrectly use the same image type ID for multiple OTA files
  • To allow for that (incorrect) usage, the OTA submission can have the further manufacturer_names and/or model_names matching metadata added to really only apply to one correct device.
  • In that case, ZHA checks that the following match:
    OTA manufacturer ID and OTA image type ID and Zigbee manufacturer name and Zigbee model name

So, adding manufacturer_names and model_names is not bad, but we don't really need it. Leaving it out can simplify things if you correctly use the OTA image type ID (and OTA manufacturer ID).

(I guess you can keep it for extra safety, but I think your device firmware and OTAs correctly use OTA image type IDs, so you likely don’t need the extra metadata matching.)

No need to change anything here now. Just a friendly note that you probably don't need to bother adding model_names and manufacturer_names in all submissions.

[1775939187]

@1775939187 Thanks! The other Sonoff PRs are all good – I'll merge them next. I just did a bit of testing with the S60 plug.

This PR

I do have one quick question on the release notes for this MINI-ZBDIM v1.0.5: Now, this PR adds the same OTA image that was already submitted with:

• Add Sonoff MINI-ZBDIM v1.0.5 #27 (submitted issue)
• Add Sonoff MINI-ZBDIM v1.0.5 #28 (auto-generated PR)

Merging this new submission/PR would only update the release notes a bit. That could also be done directly by editing the corresponding YAML metadata:

• So, in the future, if you ever want to update the metadata (e.g. release notes) for already merged updates directly, you can just go to images/sonoff/ in this repo, and select the corresponding YAML file with all the metadata.
• Then click the "Edit" button in the top of the GitHub web editor to edit it. It then submits a PR with that edit.
  For editing this device's metadata, it would be this file: https://github.com/zigpy/zigpy-ota/blob/dev/images/sonoff/1286-0045-00001005_ea654a.ota.yaml
• Note: There's also an overview of all the available firmware (with file names) in the README:
  "Browse available firmware" -> Dev channel (here).

I'll make sure this is all handled correctly now, but please confirm one thing: Which release notes are correct for the MINI-ZBDIM v1.0.5 update:

A: Current ones:

Bugfixes

• Calibration method set fail

New features

• NTC threshold value update to 115°C
• Firmware supports manual calibration mode to allow direct configuration of minimum and maximum level
• Light dimming is supported when the key type is single touch key

B: New ones (from this submission):

• Added manual calibration.
• Modified default values ​​for external switch dimming rate and transition time.
• Long-press dimming function for single-rebound external buttons; simultaneously updated to long-press brightness adjustment function for double-rebound and triple-rebound buttons.
• Removed minimum brightness setting item.

Are A or B the correct release notes? Or a combination or both maybe? This is the only question I have for you. No need to do anything else here. I'll handle the rest.

General note on the manufacturer_names and model_names

This is just some information below (and unrelated to my question above). No need to do anything, but it might simplify future submissions if you can just leave out the model_names and manufacturer_names:

• We do not strictly need manufacturer_names and model_names in the submission if the manufacturer ID and image type ID of the OTA files is correctly set.

• It's only needed if multiple OTA images (incorrectly) share the same image type ID. For example: a firmware update for a temperature sensor and another update for a smart plug both use the same image type ID.

  • That should not be the case anyway, but we can make it work with ZHA by adding model_names as extra matching metadata to both submissions/image metadata.

How ZHA OTA matching works

So to clarify what happens with zigpy/ZHA:

• ZHA always checks the manufacturer ID and image type ID that devices request.

  • They always need to match the OTA image header data. Otherwise, the update won't be shown for that device.
  • So without manufacturer_names and without model_names, ZHA already checks that the following match:
    OTA manufacturer ID and OTA image type ID (in OTA header need to match what the device requests)

• However, some manufacturers incorrectly use the same image type ID for multiple OTA files

  • To allow for that (incorrect) usage, the OTA submission can have the further manufacturer_names and/or model_names matching metadata added to really only apply to one correct device.
  • In that case, ZHA checks that the following match:
    OTA manufacturer ID and OTA image type ID and Zigbee manufacturer name and Zigbee model name

So, adding manufacturer_names and model_names is not bad, but we don't really need it. Leaving it out can simplify things if you correctly use the OTA image type ID (and OTA manufacturer ID).

(I guess you can keep it for extra safety, but I think your device firmware and OTAs correctly use OTA image type IDs, so you likely don’t need the extra metadata matching.)

No need to change anything here now. Just a friendly note that you probably don't need to bother adding model_names and manufacturer_names in all submissions.

Hi,thanks for the detailed explanation and the guidance on editing the YAML metadata directly — that's very helpful!
Regarding the release notes for MINI-ZBDIM v1.0.5:
Both A and B are correct.
Thanks again for handling this!