Add ThirdReality Smart Plug Gen3 v1.00.56

[3reality-support]

OTA image URL

https://s3.amazonaws.com/tr-ota-us-prod/3RSP02064Z_ZHA_056_20260803_013340.ota

Release notes

This updates the ThirdReality Smart Plug Gen3 (3RSP02064Z, hardware revision 0xD3BD) to v1.00.56.

Changes

• Restore the configured LED brightness after a power cycle

How to handle existing images of the same type

Keep all (standard)

Optional metadata

model_names: ["3RSP02064Z"]

Checklist

• The OTA image provided is in a supported format (e.g., .zigbee, .ota)
• The OTA image URL provided is from an official source (e.g., manufacturer's website, official repository)
• 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 ThirdReality Smart Plug Gen3 v1.00.56 #229

Last reprocessed: 2026-08-05 01:17 UTC

[zigpy-review-bot]

Could you confirm whether uploading this file still wrapped is intentional?

The file linked in this issue is 282,538 bytes: the 282,386-byte OTA image inside a 152-byte ThirdReality container (a length table plus two SHA-512 digests). Your previous submissions here have all been bare .ota files without the container, so this one is the first to arrive wrapped — which is why I wanted to check rather than just merge it.

It works either way. zigpy detects that container, strips it, and transmits only the inner image, so a plug updating via ZHA receives byte-for-byte the same firmware as one updating from your own build or from Zigbee2MQTT:

File	Size	SHA-256
This issue, as uploaded	282,538 bytes	7e634ed9…
This issue, container stripped	282,386 bytes	5af7d276…
Homey app index	282,386 bytes	5af7d276…
Zigbee2MQTT	282,386 bytes	5af7d276…

The container's inner SHA-512 digest also matches the sha512 that Zigbee2MQTT publishes for the same image.

So there is nothing blocking here — two things would just help us before we merge:

1. Is the wrapped upload intended going forward, or did the container survive by accident during export? Either is fine for us; it simply differs from your previous submissions, and knowing which to expect helps us review future ones.
2. The file here is named 3RSP02064Z_056_20260728_085838.ota, while the index above lists 3RSP02064Z_ZHA_056_20260803_013340.ota (newer date, and the _ZHA_ segment your other files use). The payloads are identical, so this is only a naming difference — but if the _ZHA_ build is the one you consider canonical, we are happy to point this issue at that URL instead. Just let us know.

[TheJulianJES]

Per the above, I've swapped the OTA URL:

• Old: https://s3.amazonaws.com/tr-ota-us-prod/3RSP02064Z_056_20260728_085838.ota (this is what you submitted originally)
• New: https://s3.amazonaws.com/tr-ota-us-prod/3RSP02064Z_ZHA_056_20260803_013340.ota (note the ZHA and newer date)

ZHA/zigpy works with both. It sends identical data to the device, since it just strips the container (of the initially submitted file), and the underlying firmware is exactly the same. It's just more consistent with the Homey submission, Z2M submission, and older zigpy-ota submissions.

This looks good to me now.

[3reality-support]

@TheJulianJES

Hello,

Just verified, you are correct. The OTA image URL we submitted this time is indeed https://s3.amazonaws.com/tr-ota-us-prod/3RSP02064Z_ZHA_056_20260803_013340.ota

It might be that when copying the link, we mistook the name of the list object.

By the way, there's another issue. Due to the last submission (URL: #148), you deleted the min_current_file_version and max_current_file_version that I set, and replied "We were able to remove this because ZHA always matches by at least image_type (and manufacturer_id)." Therefore, I won't set these two parameters this time.

Also, I think the "(PID 0xD3BD)" in the title doesn't need to be added anymore. This was used for version distinction in the previous submission, and it won't be needed for distinction in the future.

[TheJulianJES]

Also, I think the "(PID 0xD3BD)" in the title doesn't need to be added anymore. This was used for version distinction in the previous submission, and it won't be needed for distinction in the future.

Yep, agreed. We have a semi-automated tool that runs over all of the submissions and it added that back for consistency (similar to previous submissions), but I agree it is no longer needed now.

By the way, there's another issue. Due to the last submission (URL: #148), you deleted the min_current_file_version and max_current_file_version that I set, and replied "We were able to remove this because ZHA always matches by at least image_type (and manufacturer_id)." Therefore, I won't set these two parameters this time.

Yes, it's not needed for ZHA/zigpy here. Z2M OTA matching works a bit differently, so it may be needed for its index (for these plugs), but we do not need it.

Old Gen3 US plug versions will first get the update that switches their PID to the correct one (0xD3B4 -> 0xD3BD) and then they will get the newest update for the 0xD3BD immediately after that (so currently this update).

The 0xD3B4 -> 0xD3BD step for old Gen3 US plugs is unchanged in this PR and seems to work as expected.

And all UZ1/UK plug versions will never get the Gen3 US plug firmware, as both 0xD3B4 submissions (for UZ1/UK + Gen3/US) have model_names filters, which is correct.

---

Because PID 0xD3BD was only ever requested by (newer versions of) the Gen3 US plug, no special filtering needs to be done here. Technically, the model_names: ["3RSP02064Z"] from this submission doesn't even matter. It's only important for all UZ1/UK plug submissions and the older Gen3 US submissions (as both request the same 0xD3B4 but require different images).

Basically, everything should be good now. I've double checked everything and I'll merge this next. I always make sure to check everything for these plugs, so a wrong update doesn't apply to some plug. Everything is fine here.

---

In the PR for this submission, you can see it only replaces the one older image, not the others, so everything is good:

• Add ThirdReality Smart Plug Gen3 v1.00.56 #229 ("Note: Existing Images Found")