Koenkk / Koenkk/zigbee2mqtt

[3RMS16BZ / Third Reality, Inc] ???

Open
#32,698 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

problem
Dominant language
TypeScript
Stars
15.7k
Forks
2k
Avg merge
18h 55m
Merged PRs (30d)
35

Description

What happened?

Updated to latest firmware but new features/settings are not visible.

Image Image Image
What did you expect to happen?

I expected to see:

  • Support for customizing
  • Configurable "Cold-Down Period" (cooldown) setting
  • LED Brightness settings
Image
How to reproduce it (minimal and precise)
  • Successfully OTA updated the firmware from v1.00.24 to v1.00.79 but saw no change in Z2M exposed settings.
  • Interviewed the device - no change.
  • Reconfigured the device - no change.
  • Re-paired - no change.
Zigbee2MQTT version

2.12.1 (aa909a8a62f76e2dd98ace3a172bca88ee56f5fe
)

Adapter firmware version

{"build":0,"ezsp":13,"major":7,"minor":5,"patch":1,"revision":"7.5.1 [GA]","special":0,"type":170}

Adapter

EmberZNet

Setup

os: #1 SMP PREEMPT Thu Apr 30 15:24:52 CST 2026 - 7.0.2-vendor-sunxi64 - arm64
node: v24.17.0
ha: true

Device database.db entry

No response

Debug log

No response

Notes
Device

definition: 3RMS16BZ - Third Reality (v0.0.0)
software_build_id: v1.00.79
date_code: undefined
endpoints:

{"1":{"bindings":[],"clusters":{"input":["genBasic","3rMotionSpecialCluster","65280","genPowerCfg","ssIasZone"],"output":["genOta"]},"configured_reportings":[],"scenes":[]}}
Health

time: Thu Jul 30 2026 04:16:44 GMT-0700 (Pacific Daylight Time)
os.load_average: 0.17, 0.13, 0.09
os.memory_percent: 78.9773
process.memory_percent: 8.4928
process.uptime_sec: 382222

{"leave_count":1,"messages":2976,"messages_per_sec":0.6692,"network_address_changes":0}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the 3RMS16BZ device definition and compare the reported firmware, clusters, and expected settings with the issue details. Check how the device is interviewed, reconfigured, and exposed to Zigbee2MQTT, then verify that customization, cooldown, and LED brightness settings appear after the firmware update and re-pairing.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.