Add frient A/S US Smoke & CO Alarm (SCAZB-141) v1.8.4

[GAFfrient]

OTA image URL

https://github.com/Develco-Products/frient_upgrade_images/blob/main/SmokeUsAlarm_1.8.4.zigbee

Release notes

This updates the frient A/S US Smoke & CO Alarm (SCAZB-141) to v1.8.4.

Changes

• Change the factory reset to use the tamper switch as input (5 quick presses)

How to handle existing images of the same type

Keep all (standard)

Optional metadata

No response

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

Applicable for SCAZB-141

[zigpy-bot]

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

• Add frient A/S US Smoke & CO Alarm (SCAZB-141) v1.8.4 #231

Last reprocessed: 2026-08-31 18:57 UTC

[TheJulianJES]

Thanks! Everything seems to work fine, including the new reset-procedure.

Small release notes change

I've removed the following from the release notes:

When pressing the test mode button, both smoke and CO must be shown as⏎is testmode

HA shows a dedicated "Test" binary sensor (which looks at the IasZone test bit on endpoint 35 / IAS fire endpoint, but not the CO one currently). The HA "Smoke" and "Carbon monoxide" binary sensors are not affected by the test button, so I don't think including that release note makes much sense for HA users? HA doesn't use the BinaryInput clusters currently, only IasZone.

So I'm not sure what exactly changed compared to the previous firmware version that is referenced by that release note, but I don't think it affects HA users at the moment? We can always include it in the release notes later again if it makes sense to include.

Optional metadata matching change

Also, I've removed the optional metadata matching:

manufacturer_names: [frient A/S]
model_names: [SCAZB-141]

The manufacturer ID 0x1015 (4117) and image type 0x0258 (600) seem to be unique and are always used when matching, so we shouldn't need the additional metadata to match against.
Unless the image type is requested by another Onics/Frient product that requires a different image, we can just remove it.

With it, zigpy matches "manufacturer code AND image type AND manufacturer name AND model name".
Without it, it matches "manufacturer code AND image type", which is similar to all other images we have at the moment and seems to be fine here as well, as I'm not finding any colliding image types for other products.

So far, we've only needed it for manufacturers where different devices accidentally use the same image type, even though they require completely different images.