The Zigbee TRV TV06 is now fully compatible with Z2M and will be compatible with ZHA after the ZHA update in September.
Is there any way to adjust the reported time on these devices? I have the GX02s with TZE204_7ytb3h8u firmware and the time is off by many hours.
I have the same issues
Hi! Do you happen to have a source for ordering one of your GX06 Humidity sensors? I could not find them on Ebay, AliExpress, Amazon etc.
I bought a GX-06ZG 3-in-1 Smart Soil Detector, which is advertised on Amazon as working with ZHA. Home Assistant can see the device but there are no entities, except for Firmware, which it says is unavailable.
How can I see the actual entities for humidity, temperature and light?
Sorry about that. There was indeed a timezone issue with ZHA for this device, but it has now been fixed.
Please try updating/reloading it again and check whether the reported time is now correct.
Sorry for the inconvenience. The ZHA project has already picked up my fork, but it still has not been updated/merged on their side, and Iâm not sure why yet.
For now, I can provide you with the quirk file so you can use it locally first. I will also email the ZHA maintainers to ask about the current status, and I will create a new fork/PR if needed.
from zigpy.quirks.v2 import EntityPlatform, EntityType
from zigpy.types import t
from zhaquirks.tuya.builder import TuyaQuirkBuilder
class GiexBrightnessLevel(t.enum8):
"""GIEX GX06 brightness level enum."""
Lower = 0x00
Low = 0x01
Normal = 0x02
High = 0x03
Higher = 0x04
# GIEX GX06
# manufacturer: _TZE284_3urschql
# model: TS0601
#
# Datapoints:
# DP 2 -> Brightness level: lower, low, normal, high, higher
# DP 3 -> Soil moisture (%)
# DP 5 -> Temperature (scale 10)
# DP 15 -> Battery (%)
(
TuyaQuirkBuilder("_TZE284_3urschql", "TS0601")
.tuya_enum(
dp_id=2,
attribute_name="brightness_level",
enum_class=GiexBrightnessLevel,
entity_type=EntityType.STANDARD,
entity_platform=EntityPlatform.SENSOR,
translation_key="brightness_level",
fallback_name="Brightness level",
)
.tuya_temperature(dp_id=5, scale=10)
.tuya_soil_moisture(dp_id=3)
.tuya_battery(dp_id=15)
.skip_configuration()
.add_to_registry()
)
This should be the same ZHA quirk issue. Please try the custom quirk I posted above first.
I will also follow up with the ZHA maintainers and try to get this included officially as soon as possible.
Hi! Could you let me know which country you are in?
The GX06 is currently available on Amazon in Europe and Australia. It is also available on AliExpress, which supports shipping to many countries worldwide.
Once I know your country/region, I can point you to the most suitable sales channel.
Hi, sorry, this device is not currently supported by deCONZ from our side.
At the moment, we only have support/quirks for ZHA, and the device is also supported in Zigbee2MQTT. I do not currently have a deCONZ DDF file, and Iâm not very familiar with deCONZ yet.
If the device can pair but no entities are exposed, it likely means deCONZ does not have a proper device definition for this model. I can try to look into creating a deCONZ DDF file, but for now the recommended options are ZHA or Zigbee2MQTT.
@Giex: I just received this SGW08 and it was added to ZHA without any problems.
However switching the valves from HA does not work. If I turn the valves on/off manually using the buttons on the device it works just fine and their status gets reflected on HA with the status sensor showing "Manual" when "ON" then eventually "idle" when "OFF". But turning the valves on/off via HA does not actually turn the valves on/off. There is no error reported that the device did not respond and the valve "switch" stays "ON" until I turn it off.
I'm on 2026.7.0
On an unrelated note: getting the connectors not to leak was a PITA! I just re-read the listing and it is G thead, not NPT!
Hi there! Thanks for sharing the picture and the details of your issue.
Looking at the device fingerprint you mentioned, it seems it doesnât quite match our productâs signature. Itâs possible that the pairing process wasnât fully completed, which can result in an incorrect fingerprint being recognized by ZHA. Could you try moving the device much closer to your gateway and pairing it again just to rule out any signal range issues?
Regarding the thread type, you mentioned needing an NPT thread, but the device you received has a G thread. Based on this, Iâm assuming you might be located in the US, Canada, Mexico, or Colombia. For these regions, our default shipments use GHT (Garden Hose Thread), which is the standard for outdoor faucets there.
If you did receive a G thread device by mistake, please shoot us an email at [email protected] so our after-sales team can help you get a replacement with the correct thread.
Just a quick note to clarify: NPT and GHT threads are actually different. In the US, NPT is typically used for indoor plumbing, while GHT is used for outdoor setups (like garden faucets, hoses, washing machines, RVs, etc.). They arenât compatible, so connecting to an NPT faucet will indeed cause leaks, but this wouldnât be because the wrong item was sent. Please double-check if your faucet actually requires a GHT (or NH) thread instead. We donât manufacture this timer with NPT threads since they arenât commonly used for outdoor watering.
Let me know if moving it closer to the gateway helps, or if you have any other questions!
Thank you for your reply. Will try pairing closer to the radio and update (itâll be in a couple of weeks).
The G vs GHT thread is my mistake: the AliExpress listing clearly states it is G thread.
Hello,
Because AliExpress serves customers from all over the world, the product page usually shows only one thread standard. However, we normally select and ship the appropriate thread type according to the destination country.
If you are in a country that uses the US GHT thread standard but have received a product with a G/BSP thread, we will take responsibility and help resolve the issue.
If you have any questions, please contact us at [email protected] for support. It is a pleasure to meet such an understanding customer. If you encounter any other issues while using the product, please feel free to contact us at any time.
Best regards,
GIEXSMART-Raul
Pairing closer to the radio fixed the issue! Thank you!