Issue with "updateView" function in QuickApp on version 5.171.13 (beta)

[DJ6971 1]

Hi,

After updating my Fibaro system to version 5.171.13 (beta), I noticed that the updateView function in QuickApp no longer works correctly. Below are the details of the issue:

 

1. I create a new label in the QuickApp interface, assigning it an ID, e.g., label_ID_0.
2. In the QuickApp code, I use the updateView function to update the label's text, e.g.:

   Please login or register to see this code.

3. In the logs, I see that updateView is being called correctly:[DEBUG] Text updated: New text

   Please login or register to see this code.

4. However, the text in the QuickApp interface (user view) does not update. This issue occurs with both existing and newly created QuickApps.

 

What I Have Tested:

 

• I created a simple QuickApp with the following test code:

  Please login or register to see this code.

• Although the code runs without errors (as confirmed in the logs), the text in the QuickApp interface does not change.

• I also tried manually editing the label in the QuickApp interface and reassigning its ID, but this did not solve the issue.

• The problem affects all QuickApps in my system.

 

Assumption:

 

It seems that theupdateView function stopped working properly after updating the system to version 5.171.13 (beta). Before the update, the view was being updated correctly.

 

 

System Details:

• Hub Model: Home Center 3
• Software Version: 5.171.13 (beta)
• QuickApp Type: Roller Shade integrated with Zigbee2MQTT
• Additional Notes: The issue affects all QuickApps in my system and started occurring after the 5.171.13 beta update.

 

Request:

 

Please investigate this issue. If it is a system bug, could you provide an estimated fix date? If additional configuration or code changes are required on my side, I would appreciate detailed instructions.

Thank you in advance for your assistance!

 

 

Edited November 28, 2024 by DJ6971

[m.roszak 763]

We are on it, thanks for the report.

We will try to fix the issues ASAP.

[DJ6971 1]

Hello,

I wanted to inform you that after updating to the Beta version 5.171.15, the issue with refreshing data in QuickApps, which was present in version 5.171.13, has been resolved. The updateView function now works correctly – data in QuickApps refreshes in real-time as expected.

At this moment, I can confirm that this part of the system is functioning properly. I’m still testing other features in this Beta version, but I wanted to share this update since the QuickApp issue was quite significant.

Thank you to the Fibaro team, and especially to @m.roszak, for quickly addressing this issue and restoring the functionality.

Best regards,

[Sankotronic 2,370]

Hi @m.roszak ,

 

Issue with updating QA of Color controller type is not resolved since it was added to the system. it is so badly coded that is completely unreliable. Sometimes updating labels works, but then mostly doesn't work in the new view, but it works always in the old view.

 

Updating of the drop down selector is disaster! For example:

Please login or register to see this code.

Sometimes fills in list, but mostly it stays empty in the new view after QA is restarted. Didn't figure out if refreshing web page helps because that is also not persistent. Of course, same is in the latest version of the mobile app. Of course in the old html view this always works.

Please login or register to see this code.

This command does not work at all on the new view. I do not know how do you preform testing after changing code, but it seems that is not done to check all possibilities and options or at all. Of course that in the old view this works as expected.

 

Instead of making old HTML view better and faster, your team introduced this new view which is so badly and poorly coded that I'm surprised that person in charge even allowed this to see users.

 

BTW - I do not care if I can format label text or anything with HTML tags, but if that is taken away, then at least I expect that new view works 100% of the time and that it looks organized as VD's were on HC2. For example, without too large empty spaces between labels and sliders, so I don't know what is better to put label that explains slider above it, or below it.

 

Anyway, why sliders do not have name, like drop down menu has?????? If sliders on HC2 virtual devices has names, then why remove that on successor QA on HC3?

 

 

[m.roszak 763]

Thanks for the reports.

We are aware of the issues with Color Controller QuickApp and refresh issue there, we are actually fixing it right now.
The same with drop-downs in general.

 

[Sankotronic 2,370]

Hi @m.roszak ,

 

Thanks for the info. It came just in time when I start loosing hope and start thinking to... I better not even write it down