MOES ZHT-002 – valve_state entity disappeared after updating to 2.14.3

Open
#33,648 0 comments 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
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
backend

Research direction

Start by comparing the MOES ZHT-002 device definition and exposed properties in versions 2.14.2 and 2.14.3, then inspect the relevant device tests or debug logs if available. Confirm whether valve_state was removed or stopped being exposed; done means the intended behavior is established and, if this is a regression, the property and Home Assistant entity are restored.

Written by the indexing model from the issue text.

Description

problem
What happened?

After updating the Zigbee2MQTT Home Assistant add-on from 2.14.2-1 to 2.14.3-1, the valve_state entity for my MOES ZHT-002 thermostat disappeared.

Previously, Home Assistant exposed the entity:
sensor.thermostat_valve_state

It correctly reported open and close.

After the update:
The entity is no longer available in Home Assistant.

The valve_state property is missing from the device's exposed properties in Zigbee2MQTT.
The thermostat itself continues to work.
The hvac_action attribute still correctly reports idle and heating.

Expected behavior
The valve_state property should remain available, as it was before the update.

Actual behavior
The valve_state property and its corresponding Home Assistant entity are missing.

Environment
Device: MOES ZHT-002
Zigbee2MQTT add-on: 2.14.3-1
Previous working version: 2.14.2-1

Could you please check whether this is an unintended regression or an intentional change?

Thank you!

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.14.3-1

Adapter firmware version

?

Adapter

SONOFF_SONOFF_Dongle_Plus_MG24

Setup

Add-on on HomeAssistant.

Device database.db entry

No response

Debug log

No response

Notes

No response

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.