Namron – Zigbee thermostats 4512737 measure_power stops updating

Apps
1

Hi everyone,

I am experiencing an intermittent issue with the official Namron app (Namron AS) on Homey, specifically with power measurement reporting from NAMRON Zigbee Touch Thermostats (model 4512737).

I have been investigating this for some time and would like to share my findings, as I suspect other users might be experiencing something similar.

My setup

  • Homey: Homey Self-Hosted Server 13.5.0

  • Zigbee coordinator: Homey Bridge

  • App: Namron (official app by Namron AS, net.filllip-namron)

  • Devices: Three NAMRON 4512737 Zigbee Touch Thermostats

  • Network: All three thermostats are connected directly to Homey’s Zigbee network.

For simplicity, I will refer to the devices as Thermostat 1, Thermostat 2 and Thermostat 3.

The problem

All three thermostats intermittently stop updating the measure_power capability in Homey.

The value either remains stuck at 0 W or stops changing, even when the connected heating equipment is actively consuming power.

Interestingly, the thermostats do not appear to be completely disconnected. Other device capabilities can continue working, and I have been able to communicate with the thermostats through Zigbee Developer Tools.

The problem appears to affect the updating of the power measurement rather than the entire device.

Important finding: Raw Zigbee reading works

During one of these incidents, I tested Thermostat 1 directly using Homey Developer Tools.

I read the activePower attribute from the Electrical Measurement cluster (0x0B04 / 2820).

The results were:

Measurement Value
Homey measure_power capability 0 W
Raw Zigbee activePower reading Approximately 680 W

This was particularly interesting because it demonstrated that the thermostat could return the actual power consumption when queried directly, while the Homey capability still displayed 0 W.

I understand that a successful raw attribute read does not necessarily mean automatic Zigbee attribute reporting is functioning correctly.

However, it suggests that the issue could be related to attribute reporting, processing of incoming reports, or capability updates within the app.

Restarting the Namron app

On October 6, I performed a controlled restart of the Namron app without removing or re-pairing any Zigbee devices.

After restarting the app, all three thermostats resumed updating measure_power.

This is one of my most interesting observations.

However, the problem has occurred intermittently before, and restarting the app has not always resolved it on previous occasions.

Therefore, I cannot conclude that this is purely an app issue.

Previous observations

On October 1, I recorded the approximate times when the three thermostats last changed their measure_power values:

  • Thermostat 1: 19:01 CEST

  • Thermostat 2: 21:13 CEST

  • Thermostat 3: 20:56 CEST

Unfortunately, my preserved Homey SHS log from that day only starts at approximately 21:20, so I cannot reliably correlate these times with Zigbee controller events.

Also, Homey’s capability lastUpdated timestamp may indicate the last value change rather than the last successful communication.

Possible connection to Zigbee stability

Separately, I have been investigating recurring Homey Bridge/Zigbee controller stability issues with Athom support.

These include controller reconnections, communication timeouts and occasional Zigbee stack errors.

It has been suggested that controller interruptions could potentially affect application-level reporting, but I currently have no evidence that the two problems share the same root cause.

I would therefore prefer to investigate the Namron power-reporting behavior independently rather than assume the Bridge is responsible.

Questions for the Namron app developer

I would really appreciate some clarification regarding how the app handles power measurements on these thermostats.

  1. Does the app rely on automatic Zigbee attribute reporting for activePower, or does it periodically poll the Electrical Measurement cluster?

  2. Is reporting configured again when the Zigbee controller reconnects or when the device becomes available?

  3. Could a temporary controller interruption leave measure_power stuck even though raw attribute reads still work?

  4. Is there any known issue with power reporting on model 4512737?

  5. Is there a recommended way to diagnose or reinitialize power reporting without restarting the entire app or re-pairing the devices?

Additional diagnostics

I have access to detailed SHS logs and Zigbee Developer Tools, and I can perform further non-destructive tests if needed.

I would be happy to provide anonymized logs or compare raw attribute readings with the Homey capability during the next occurrence.

Since these thermostats are used for heating control, I would prefer to avoid removing or re-pairing them unless absolutely necessary.

I hope this information is useful, and I would be interested to hear whether anyone else has experienced similar behavior.

Thanks in advance!

-Tim

2

Please remove the [APP] prefix from your topic title, this prefix is meant for official app support topics from the app developer

3

Thanks for pointing that out! I’ve removed the [APP] prefix from the topic title.