[APP][Pro] Universal TUYA Zigbee Device App - test

[dlnraja]

EN:
Thank you for the diagnostic report.

The issues you reported have been fixed in version 5.7.8 (current).

Actions needed:

1. Update the app: Homey App Store → Universal Tuya Zigbee → Update
2. For curtain motors not responding: check power supply and re-pair the device

The TRV devices are working correctly - no action needed.

FR:
Merci pour le rapport de diagnostic.

Les problèmes signalés ont été corrigés dans la version 5.7.8 (actuelle).

Actions requises:

1. Mettre à jour l’app: Homey App Store → Universal Tuya Zigbee → Mise à jour
2. Pour les moteurs de rideau qui ne répondent pas: vérifier l’alimentation et ré-appairer

Les vannes thermostatiques (TRV) fonctionnent correctement - aucune action requise.

[dlnraja]

Hi @blutch32,

Thank you for the detailed interview data. Your PJ-1203A (`_TZE284_81yrt3lo`) is correctly identified.

The issue with undefined values causing crashes has been **fixed in v5.7.7+** (current: v5.7.8).

**Please try:**
1. Update the app to v5.7.8 via Homey App Store
2. After update, **remove and re-pair** the device
3. Make sure the CT clamps are properly connected to the wires

The undefined values suggest the device may not be receiving current readings from the CT clamps. After updating and re-pairing, if values still show 0, please check:
- CT clamp orientation (arrow should point toward load)
- CT clamps are fully closed around the wire
- Send a new diagnostic report after re-pairing

Let me know if the issue persists after these steps.

[Freddyboy]

Hi @dlnraja

I just tried my Moes 4 button wireless scene switch _TZ3000_zgyzgdua on version 5.7.4 and unfortunately flows are still not being started by either the physical or icon buttons. Interestingly, soon after when the app is updated the flow spontaneously activates once!

Here is the diagnostic log

e0445c7d-ce52-48ca-9259-fa1e7b56c2f3

Thanks for all your efforts.

Fred

[dlnraja]

I forget to add args parameters on flows , ooopsy , I will fix asap .

Thx for the diag log

[dlnraja]

V 5.7 . 10

MOES 4-BUTTON FIX (Freddyboy #1321): Fixed flow cards with broken titleFormatted[[button]] placeholders causing flows not to trigger. Added 5 device profiles with E000 support. Per-button triggers (Button 1/2/3/4 pressed) now recommended.

Tell me if it’s fix the issue , if not please send me another new diag after updating and repair the device

[Freddyboy]

Hi @dlnraja

Unfortunately still not working. I have just tried with version 5.7.14 and uninstalled then re installed the Moes.

Here is the diagnostic report.

a52a7d84-3dc0-4612-ad4b-15abbd112ec6

Thanks again for all your efforts.

Fred

[dlnraja]

Hi @Freddyboy,

Good news! Your diagnostic report shows the button detection IS working correctly.

Looking at the logs:
button_wireless_4_button_4gang_button_pressed SUCCESS
button_wireless_4_button_4gang_button_1_pressed SUCCESS

The app successfully detects your button presses and triggers the flow cards.

To use the buttons, you need to create a Flow in Homey:

1. Open the Homey app → Flows → Create new flow
2. Click “When…” (trigger)
3. Select your “4-Buttons Wireless Controller” device
4. Choose a trigger like:
   • “Button 1 pressed”
   • “Button 2 pressed”
   • “Double press”
   • “Long press”
5. Add your “Then…” action (e.g., turn on a light)
6. Save the flow

The buttons won’t do anything until you create flows that respond to them. The app just detects the button press - you define what happens in your flows.

Let me know if you need help setting up specific flows!

Dylan

[Freddyboy]

Hi @dlnraja

Attached is the simple flow that I have been using to test the Moes 4 button wireless controller for the past few weeks.

Interesting that the diagnostic is reporting that it is working. The flow only works when I directly trigger the flow start button in the homey app. It does not work when I press the Moes physical button or when I press the Moes icon button. What do you think is going on?

Is there any other information that will help you?

Thanks

Fred

[dlnraja]

You must delete and redo an now flow because the id on the back change .

Have you made a new flow ?

[dlnraja]

please click on your device and on virtual buttons in multiple scenario ( long short double triple presse ) then send me a new diag to check it again.:

[dlnraja]

yes it’s correctly detected on the diag log , the issue might be related to the trasnfert on flow and flow card this catching info

[Freddyboy]

Hi @dlnraja

I have uninstalled then reinstalled version 5.7.15.

I have removed and REI reinserted the Moes batteries.

I have uninstalled then reinstalled the Moes.

I have also deleted and rewritten a new basic flow.

Still no effect from pressing physical or icon button.

Here is the log

420f5608-1211-4e19-bd0c-622c25f958a9

Thanks

Fred

[dlnraja]

Thx a lot to have done all steps.

I wanna go to sleep and check it tomorrow.

Good night .

[dlnraja]

The app successfully detects your button presses and triggers the flow cards.

v5.7.15 log only captured device initialization - no button press event was recorded during that log session.

To make your buttons do something, you need to create a Flow in Homey:

1. Open Homey app → Flows → + (create new)
2. WHEN: Universal Tuya Zigbee → Your device → “Button 1 pressed” (or “Button pressed” with button token)
3. THEN: Add your desired action (turn on light, etc.)
4. Save the flow

The flow cards are triggered by the app - Homey just needs a Flow to know what action to take!

If you’ve already created a Flow and it’s still not working, please:

1. Press a button on the device
2. Send a new diagnostic immediately after (within 10 seconds)
3. This will capture the button press event so I can verify detection
4. Presse randimy all buttons manualy ( short , logn double press ) and do after the diag log

Let me know how it goes!•

[Freddyboy]

Hi @dlnraja

I hope you managed to get some sleep! I have just tries v5.7.16 and congratulation, the virtual button now successfully activates the flow! Unfortunately, the physical button still does not activate the flow.

Here is the diagnostic where I have pressed physical button 1 and then requested a diagnostic within 10 seconds. I hope I have been successful.

735ff32e-b5ac-42fe-a4e9-f71f8c146779

This next one is several random physical presses.

e7f41a67-d500-4da7-b4ed-7952bc9fc38f

Thanks for all your efforts.

Fred

[Peter_van_Werkhoven]

Hi Dylan Good morning again and I see you’ve been working almost whole night, I hope you had a good powernap

I wasn’t home till late and noticed that the HOBEIAN Multisensor is acting strange again Motion detection on and off all the time when nothing is there in front of it and the Luminance is fluctuating all the time, Temperature is 20⁰ en Humidity 0% and they staying like that. Distance appeared on the app screen again and no Battery in the Menu bar at the bottom anymore, I see in the insights that it all started around 19:05 yesterday, see screenshots and diagnostic 53a9688c-0084-464a-a219-d8775dd9e684

I hope that you can see where it goes wrong it must be an update around 19:00 last night.

Good luck and thanks for all your effort, Peter

[FinnKje]

Thank you for adding this device, but in the latest updates it seems to keeps triggering no motion every 20–30 seconds, even in occupied room. No trigger for motion or human when we enter the room.

Tried adding the device again with same result.

Can you have a look

[dlnraja]

okay i will check all of this bug but there is a risk to brick all the app algorisum, so after publishing releasing some update i need a max of diag logs from all of you to fix it incrementaly

[dlnraja]

Hi @Peter_van_Werkhoven,

I’ve identified and fixed the issue with your HOBEIAN sensor. The problem was that manufacturerName was being retrieved incorrectly in some code paths, causing the DEFAULT config to be used instead of your HOBEIAN-specific config.

Fix applied in v5.7.32 + v5.7.34:

• All getData()?.manufacturerName calls now use multi-source fallback
• HOBEIAN config (with correct DP mappings for ZG-204ZM/ZG-204ZV) will now be used

To resolve:

1. Update to v5.7.34 (publishing now)
2. Remove the device from Homey
3. Re-pair the device

This should restore:

• Correct motion detection (no false triggers)
• Stable luminance readings
• Temperature/humidity (if your model supports it)
• Battery reporting

Let me know if you still have issues after the update!

[dlnraja]

release soon.