Namron Zigbee Edge Termostat (4512783/4512784)

papatistos · September 19, 2025, 4:24pm

I find the documentation for this device rather lacking and wonder if anyone has figured out the answers to the following questions:

Is there a newer firmware than v1.12 (20241017)?
The only way to update the firmware is via “the mobile app” via bluetooth, right? (The mobile app seems to be called “Namron Simplify”, but it doesn’t seem to b available on the German App Store.)
Is there any way of showing the current temperature of the floor sensor or the external sensor? (I have tried setting the Control function to “floor sensor” as well as to “external sensor” but the temperature shown in the display is always the temperature of the internal sensor. Edit: I might have to take that back. The temperatures of all sensors might be too similar right now, so I’ll have to check again once one of them is clearly different)
What does the “Intelligence” setting do?

Please feel free to share any information about the device, even if it doesn’t respond to any of these questions.

papatistos · September 23, 2025, 1:37pm

I can confirm that the displayed temperature (as well as the temperature transmitted via Zigbee) is the temperature of whatever sensor is set to control the heating (Shown as Sensor mode in Zigbee2mqtt). Unfortunately, the display won’t tell you which of the sensors is currently active.

Likewise, in HA, the temperatures are logged to the same variable, regardless of what sensor is active. So I’m planning to create dummy sensors in HA that log the transmitted temperature based on which sensor is active, so that all readings from the external sensor are logged separately from the other sensors. Any suggestions of how to accomplish that in HA?

papatistos · October 13, 2025, 8:21am

I found the app. It is called “OTA upgrade” and is not published by Namron but by a Chinese company, presumably the one that is also manufacturing the hardware.

It offers two upgrades: MCU (Microcontroller unit) and Zigbee:

The MCU update worked (it upgraded from 1.0.9 to 1.0.14) but the Zigbee upgrade keeps failing with a simple “Oops!” error:

Turns out that that firmware version refers to the firmware of the Zigbee module, and since the update fails, I still don’t know whether there is a newer version.

I do, however, know now, that there is a higher version than 1.0.9 for the main MCU firmware. As of October 2025 it is 1.0.14. It was apparently published on 3 March 2025.

I don’t know what has changed. I did not notice any changes.

Meanwhile, I bumped into a limitation of the thermostat: it only reads (and displays) the temperature at the sensor that is currently controlling the thermostat (except when it is in “regulator” mode; in that case, it continues to read (but not display) the last used sensor.

When using the thermostat with zigbee2mqtt, this means that the local_temperature topic that it publishes can mean three different things, depending on the value of sensor_mode : it can indicate the temperature of the floor, the external sensor or the internal sensor. This means, that the current value cannot be interpreted without also consulting the the sensor_mode value. Also, it leads to inconsistent time series, if you’re logging the values over time.

I have tried to fix this with the script (a zigbee2mqtt extension) I published here:

github.com/Koenkk/zigbee2mqtt

[Feature request]: add mutiple temperature topics for Namron Thermostat (4512783/4512784)

opened 03:44PM - 11 Oct 25 UTC

tophee

### Is your feature request related to a problem? Please describe Currently the… `local_temperarure`topic can mean three different things, depending on the value of `sensor_mode`: it can indicate the temperature of the floor, the external sensor or the internal sensor. This means, that the current value cannot be iterpretet without also consulting the the `sensor_mode` value. Also, it leads to inconsistent time series, if you're logging the values over time. ### Describe the solution you'd like It would be great if zigbee2mqtt could publish (additional) separate topics that might be called something like `local_temperature_floor`, `local_temperature_external`, and `local_temperature_air` to which the correspodning values are published depending on the value of `sensor_mode`. It would also make sense to publish the datetime for when each of these values was last updated. ### Describe alternatives you've considered I have troed to accomplish this through an extension, but succeeded only partially (see code below). One problem was that I was not able to read the Friendly Name of the device so that I had to hard code it. The main problem, however, is that I can't seem to access the values that I managed to publish in Home Assistant.I don't understand how it picks up the existing values and I see that it is not picking up the topics published by the extension. ``` class LocalTemperatureExternalExtension { constructor(zigbee, mqtt, state, publishEntityState, eventBus, enableDisableExtension, restartCallback, addExtension, settings, logger) { this.mqtt = mqtt; this.eventBus = eventBus; this.logger = logger; this.state = state; this.deviceId = '0x70c59cfffe61076b'; this.fallbackname = 'Greenhouse Floorheating'; // remember last non-regulator mode per device this.lastNonRegMode = new Map(); logger.info('Loaded LocalTemperatureExternalExtension'); } start() { this.eventBus.onStateChange(this, this.onStateChange.bind(this)); } stop() { this.eventBus.removeListeners(this); } _pick(v) { return (v === null || v === undefined) ? undefined : v; } _name(data) { const e = data?.entity; return e?.friendlyName ?? e?.settings?.friendlyName ?? data?.friendlyName ?? this.fallbackname; } _ieee(data) { const e = data?.entity; return e?.ieeeAddr || e?.device?.ieeeAddr || data?.device?.ieeeAddr; } _readModeFromStateStore(entity) { const keys = [entity, entity?.friendlyName, entity?.id ?? entity?.ID, entity?.ieeeAddr, this.deviceId].filter(Boolean); for (const k of keys) { try { const s = this.state?.get?.(k); const m = s?.sensor_mode ?? s?.state?.sensor_mode; if (m !== undefined && m !== null) return m; } catch {} } return undefined; } _topics(name, mode) { if (mode === 'external') return { val: `${name}/local_temperature_external`, ts: `${name}/local_temperature_external_last_updated` }; if (mode === 'floor') return { val: `${name}/local_temperature_floor`, ts: `${name}/local_temperature_floor_last_updated` }; if (mode === 'air') return { val: `${name}/local_temperature_air`, ts: `${name}/local_temperature_air_last_updated` }; return { val: null, ts: null }; } async onStateChange(data) { const entity = data?.entity; if (!entity) return; const ieee = this._ieee(data); if (this.deviceId && ieee && ieee.toLowerCase() !== this.deviceId.toLowerCase()) return; const id = ieee || this.deviceId; const name = this._name(data); // Observe current mode (to update cache if it's non-regulator) const observedMode = this._pick(data?.update?.sensor_mode) ?? this._pick(entity?.state?.sensor_mode) ?? this._readModeFromStateStore(entity); if (observedMode === 'external' || observedMode === 'floor' || observedMode === 'air') { this.lastNonRegMode.set(id, observedMode); } // Only act on explicit temperature updates if (!Object.prototype.hasOwnProperty.call(data?.update ?? {}, 'local_temperature')) return; const temp = this._pick(data.update.local_temperature); if (temp === undefined) return; // Decide effective mode for routing (and for last_updated) let effectiveMode = observedMode; if (effectiveMode === 'regulator') { effectiveMode = this.lastNonRegMode.get(id); if (!effectiveMode) { this.logger.debug?.(`Regulator active but no previous non-reg mode cached; skipping for "${name}".`); return; } } const { val: topic, ts: lastUpdatedTopic } = this._topics(name, effectiveMode); if (!topic || !lastUpdatedTopic) { this.logger.debug?.(`Unknown effective mode "${effectiveMode}" — not publishing for "${name}".`); return; } // Always publish BOTH value and last_updated for the effective mode await this.mqtt.publish(topic, String(temp)); const iso = new Date().toISOString(); await this.mqtt.publish(lastUpdatedTopic, iso); this.logger.info(`Published ${temp} to ${topic}`); this.logger.info(`Published timestamp ${iso} to ${lastUpdatedTopic}`); } } module.exports = LocalTemperatureExternalExtension; ``` ### Additional context None

It does indeed publish separate topics for each sensor but the problem is that those don’t show up in home assistant. I guess I will have to read up on how to itengrate mqtt topics into home assistant, but if anyone can give me a hint, that would be great.