That is fantastic news! The “Repair” action successfully flushed the bad cache from Homey, which explains why your Lux and distance readings are finally accurate and why it stopped reverting to a Curtain device.
Your current settings (Sensitivity at 5, Departure at 20s) are a very solid baseline for a bathroom environment. If you ever experience “ghost presence” again once you turn the exhaust fan back on, try slightly reducing the sensitivity to 4 or 3.
I am currently finalizing the code for the “Ultimate Software Shield” update. Once it passes my local testing, I will push it to the Test channel and ping you here so you can try it out.
Enjoy your stable sensors in the meantime, and thank you for the detailed feedback!
I can see that the app has been updated to version 9.0.1053, and the sensors have become misconfigured again, remaining stuck with presence and motion detection active.
It also seems that the distance and lux readings are not correct, or they are reporting unusual values.
When I get back home, I will try repairing them and check how they behave with the new version.
I’ve been testing the sensor since Friday, and to be honest, I haven’t managed to get it to detect me all weekend, :S.
I kept updating the app as you released new versions to see if that would fix it, but no luck…
If I re-pair or reinstall the sensor, it detects it as “presence”, but no data changes (presence, motion, and lux stay frozen at 10 lux, and distance/meters stay fixed too).
After a while, it switches to curtain mode and stays stuck detecting presence and motion, just like before.
I tried the new advanced settings features, and I can restart it without having to press the physical button to get it detected as a presence sensor again. However, I was already able to do this manually by enabling the “Clear presence now” button and then disabling it again.
Attached is the diagnostics code:
af98752d-f02e-4e74-a06e-ab8c025534bf
Hello again @dlnraja
Additionally, I’ve noticed that the Homey app is running slower within Advanced Flows. When I move a card, there is a noticeable lag, and the presence sensor cards seem to continuously disappear and reload.
I tried uninstalling the most recent apps I installed, but the issue persists. Because of this, I suspect it might be related to the latest updates for ‘Universal Tuya’ and that continuous refreshing required for the sensor to detect properly.
I also tried disabling the app (without uninstalling it), but I haven’t been able to resolve the lagging issue.
Could you add support for the AOYAN AY-303Z Zigbee soil moisture sensor? It’s a white-label version of the HOBEIAN ZG-303Z, so hopefully it only needs its fingerprint added to the existing soil sensor driver.
Zigbee2MQTT handles it in the same definition as the ZG-303Z (zigbeeModel: ZG-303Z / AY-303Z / AY-302Z, COOLO CS-201Z). A ZHA quirk for the AY-303Z is also in progress (zigpy/zha-device-handlers PR #5352).
One thing to be aware of: the native humidity cluster (0x0405) reports the soil moisture value, while the real ambient humidity comes from DP 109.
Currently it pairs as a generic Zigbee device on my Homey SHS.
I couldn’t get a full Zigbee interview: it keeps timing out because it’s a sleepy battery device, even when I wake it with the button. The manufacturer name and model ID above are taken from the Developer Tools Zigbee overview. Happy to send diagnostic logs from the app or provide anything else you need.
Happy to test a build on the test channel. Thanks for all the work on this app!
Hi,
Could you please add support for this Tuya Zigbee Radiator Thermostat (TRV)?
It is sold by a local (Slovak) brand called ANTIK (model ATK-TRV02), but it pairs incorrectly as a Generic “socket” with a virtual driver on my Homey Pro 2026.
Here is the data from Developer Tools:
Property: Value
ID: c6d8ee46-b7b4-42cf-93e0-0e9294d59ce7
Name: Zigbee Device
Class: socket (paired incorrectly, it is a TRV thermostat)
Driver: homey:virtualdriverzigbee:driver
Ready: Yes
Available: Yes
Warning: No
Hi
I m new in this topic!
Please help me to find which device i need use for this 4in1 sensor, not clearly to find the right one, or maybe need to add support this device?!?!
Thank’s a lot
Best regards Istvan
Even though I select the dedicated “Add LCD Temperature & Humidity Sensor” option, Homey completely rejects the driver and throws the error: “Unknown Zigbee Device added - The device has been added as an Unknown Zigbee device, because there currently is no compatible Homey app available.”
I have the latest ver of Universal Tuya for Homey pro mini 9.0142.
However, in Homey Developer Tools, it does show up in the Zigbee table as a generic “Zigbee Device” with active TX/RX packets, but with no functional capabilities.
Hi, can you please add 6 Gang Scene Switch _TZ3000_nrfkrgf4 / TS0046. until now no availbale device is working with home por 2023 and latest tuya beta.
Device request: TZ-ZT01_GA4 (temp/humidity + external probe) — long manufacturer name
Manufacturer: _TZE2841000000_8se38w3c, Product ID: TS0601
Same device as Z2M TZ-ZT01_GA4 (_TZE284_8se38w3c), which is already in climate_sensor. The long-name variant is missing, so it pairs as “Unknown Zigbee Device”.
Datapoints (Z2M): dp1 temperature ÷10, dp2 humidity, dp3 battery_state enum (0/1/2), dp38 probe temperature ÷10.
Please add _TZE2841000000_8se38w3c to climate_sensor (the battery_state enum mapping used for hodyryli would fit here too).
Hi Umberto, thanks for the report. The Beca BAC-006AZB (_TZE204_dzuqwsyg / _TZE200_dzuqwsyg, TS0601) is now handled by the Wall Thermostat driver, with power, heat/cool/fan mode, setpoint, room temperature, fan speed, manual/auto and child lock (DP map from Zigbee2MQTT BAC-002-ALZB). It will be in the next published version. Please remove the device and pair it again once, so Homey picks the thermostat driver. A diagnostic report afterwards is welcome if anything is missing.
artisare (issue #560) :
Thanks a lot @artisare for the detailed log. From 9.0.1574 (Test): the humidity capability is no longer shown for _TZE200_rxq4iti9 (this TRV has no humidity sensor). Battery: Zigbee2MQTT lists no battery-percentage DP for this TRV06, only a low-battery flag (DP35), so the device now shows a battery alarm; a percentage appears automatically if the TRV ever reports one. The triggerDPReceived invalid_flow_card_id messages are fixed, and the DP values are still stored for flows. The “0/12 queries sent / No active query method” case now falls back to a single “report all” query instead of sending nothing; that part ships with the next Test build. Could you update and send a new diagnostic after a wake-up?
Hi @artisare, thanks again for the detailed report. About precision: this TRV06 firmware (_TZE200_rxq4iti9) only supports whole degrees for room temperature, setpoint and calibration (same in Zigbee2MQTT: step 1 °C). The next version sets the Homey setpoint step to 1 °C and always sends whole degrees, which avoids the odd setpoint jumps some users saw with decimals. About battery: the device does not report a battery percentage, only a “battery low” alarm, which the app now shows as the battery alarm. The next version also fixes an internal mapping that could mix up valve settings on some radiator valves. After updating, a diagnostic report would help confirm everything is OK.