Skip to content

GiEx QT06_1 (_TZE200_sh1btabb) unreliability problems #17784

Description

@Cossey

What happened?

I've had this smart valve for a couple of months now and have noticed some reliability issues.

Sometimes this valve doesn't respond to the controls or sends back any water consumed information like it should.

In the morning I have it turn on for 10 minutes. On rare occasions (maybe once every 10 days) it runs for hours because it didn't turn off automatically - which is not ideal. When this does occur, I noticed zigbee2mqtt says the state is OFF but the valve is still open. I have to toggle the state to ON, then back to OFF again (and sometimes I have to do this 2-3 times) for the valve to actually close. I should note that when it is in this incorrect state, sometimes the water_consumed will not change despite water flowing.

I experience this issue in two ways - one where I have a timer in openHAB, in which after 10 minutes it will send the OFF state to the valve, and the other is via the mode = duration and irrigation_target = 10 through zigbee2mqtt. In both of these cases I have had that same problem.

Further to this, I've noticed that there has been times where the valve didn't update the water_consumed at all. The valve is running, but this value is not being updated.

Re-pairing the device to coordinator seems to fix the water_consumed issue and I feel like the device becomes more reliable for a while, until its back to its unreliable self.

Batteries are still at 100% and the device is signal is 149lqi. According to network map, this device is routed through my Hue white ambiance E26 (LTW015) and then straight to the coordinator. Has anyone experienced an issue with this?

I have not yet had the chance to get the sniffer out to watch the packets when things are going wrong - but I hope to get some time to set this back up soon. I am mainly just posting to see if others in the community are having the same problem.

What did you expect to happen?

That the valve state in zigbee2mqtt would actually reflect the physical state. When in the OFF state, it should be off and the water flow stopped. Also, if the water is flowing, it should always be updating the water_consumed state.

How to reproduce it (minimal and precise)

I have not yet found a way to reproduce this - it occurs sporadically.

Zigbee2MQTT version

1.30.3

Adapter firmware version

20221226

Adapter

SONOFF ZBDongle-P

Debug log

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    problemSomething isn't workingstaleStale issues

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions