[TS011F (JR-ZPM03) / _TZ3000_okaz9tjs] Missing image and OTA support for firmware 500+TZSKT31BS102

Open
  • Is something wrong?
#33,658 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
40/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
embedded-iot

Research direction

The payload names no source file. Start from the device definition for JR-ZPM03 / _TZ3000_okaz9tjs and compare it with the working 500+TZSKT31BS103 entry, checking how the software_build_id is matched and where the image and OTA fields are set. Confirm the 500+TZSKT31BS102 build resolves to the same image and OTA options. Done means the older firmware gets the same behaviour, verified against the device data in the issue.

Written by the indexing model from the issue text.

Description

problem
What happened?

I have two identical Girier JR-ZPM03 smart plugs (TS011F / _TZ3000_okaz9tjs), but they belong to different hardware revisions.

The unit with the newer firmware works perfectly with the correct product image and OTA options. However, the second unit with firmware "500+TZSKT31BS102" displays an incorrect/missing image in the Z2M frontend and does not provide any OTA update option.

Device Data Comparison

  1. Working Device (Correct image & OTA available):**
    Model Zigbee: TS011F _TZ3000_okaz9tjs
    Firmware ID: 500+TZSKT31BS103
    OUI: Silicon Laboratories

  2. Problematic Device (Missing image, no OTA option):**
    Model Zigbee: TS011F _TZ3000_okaz9tjs`
    Firmware ID: 500+TZSKT31BS102
    OUI: IEEE Registration Authority

It seems that this specific older firmware revision (500+TZSKT31BS102) lacks the correct frontend image mapping and OTA entry in the definition. Could this fingerprint/firmware be added so it behaves identically to the newer revision?

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.14.3 (unknown)

Adapter firmware version

{"build":397,"ezsp":14,"major":8,"minor":0,"patch":2,"revision":"8.0.2 [GA]","special":0,"type":170}

Adapter

EmberZNet

Setup

os: #1 SMP PREEMPT_DYNAMIC Tue Oct 27 13:21:12 UTC 2026 - 6.18.58-haos - x64
node: v24.22.1
ha: true

Device database.db entry

No response

Debug log

No response

Notes
Device

definition: JR-ZPM03 - Girier (v0.0.0)
software_build_id: 500+TZSKT31BS102
date_code: 20210625
endpoints:

{"1":{"bindings":[],"clusters":{"input":["genBasic","genOnOff","genIdentify","genGroups","genScenes","manuSpecificTuya3","haElectricalMeasurement","seMetering"],"output":[]},"configured_reportings":[],"scenes":[]}}
Health

time: Mon Nov 09 2026 15:52:21 GMT+0100 (czas środkowoeuropejski standardowy)
os.load_average: 0.22, 0.14, 0.1
os.memory_percent: 26.1993
process.memory_percent: 2.0234
process.uptime_sec: 604

{"leave_count":0,"messages":20,"messages_per_sec":0.037,"network_address_changes":0}
Dominant language
TypeScript
Stars
15.8k
Forks
2.1k
Avg merge
1d 6h
Merged PRs (30d)
38

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from Koenkk/zigbee2mqtt

All issues in Koenkk/zigbee2mqtt

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.