[TS0601 / _TZE284_ye5jkfsb] antifrost status not exposed + incorrect Running state

[Eyeless77]

What happened?

1. The thermostat has antifrost function, this setting is not exposed via zigbee2mqtt, though it is configurable via service menu, here is the documentation screenshot. But there is Min temperature limit exposed to zigbee2mqtt.

2. When I set antifrost function to off via service menu and the temperature is below Min temperature limit, zigbee2mqtt shows that the current Running State is heat, though the thermostat is actually off. Also this thermostat doesn't expose anything including Local Temperature while it's turned off. So the current behavior, I guess, is the following: zigbee2mqtt remembers the last running state before turning off and exposes it. If it was heat before powering off, it remains heat, if it was off - it remains off.

What did you expect to happen?

1. Antifrost function is exposed via zigbee2mqtt with no need to configure it on the thermostat itself.
2. Zigbee2mqtt doesn't expose heat Running state when the thermostat System Mode is off.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.7.2-1

Adapter firmware version

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

Adapter

EmberZNet

Setup

os: #1 SMP PREEMPT_DYNAMIC Tue Nov 4 13:52:04 UTC 2025 - 6.12.51-haos - x64
node: v22.16.0
ha: true

Device database.db entry

No response

Debug log

No response

Notes

Device

software_build_id: undefined
date_code: ``
endpoints:

{"1":{"bindings":[],"clusters":{"input":["genBasic","genGroups","genScenes","manuSpecificTuya","zosungIRTransmit"],"output":["genOta","genTime"]},"configured_reportings":[],"scenes":[]}}

Health

time: Fri Jan 02 2026 21:10:44 GMT+0300 (Moscow Standard Time)
os.load_average: 1.34, 1.35, 1.35
os.memory_percent: 79.0233
process.memory_percent: 2.7296
process.uptime_sec: 34813

{"leave_count":1,"messages":1561,"messages_per_sec":0.0449,"network_address_changes":0}