QuickApps child's custom view management - example

[m.roszak 763]

Hello everyone

As in the recently launched beta, we introduced the way of managing the custom views for QuickApp's child - I am attaching a simple example how to use the view definition to update the view of the device

If something is unclear, let me know.

Please login or register to see this attachment.

[Ronald Taal 0]

Please login or register to see this code.

[Sankotronic 2,370]

Hi @m.roszak ,

 

not only that custom button is not visible in Yubii Home app, but even default buttons are arranged differently. I wonder who in Fibaro is responsible for testing? Is there a testing even done before releasing software?

 

It seems that Fibaro is in "auto destruct" mode

Why I wrote that. because what ever you did in last few firmware updates was just destroying what was already working and new stuff is not working by default.

I can make a list, but is getting longer and longer with each software version and my hope and patience is burning out.

[m.roszak 763]

Some devices types (for. ex. weather, thermostats) have native handling in the app, upcoming 2.2 version solves most of the issues we are aware.

[marbe 23]

Hello @m.roszak ,

Please specify what attributes can be used so that they work in both the Web GUI and the application.
In the example the following are used:

• for object "style":{"weight": "1.0"}
• for row "style":{"weight": "1.0"}

Please provide a list of possible attributes, a more detailed description and an explanation of the meaning.
Thank you very much

[Neo Andersson 230]

@m.roszak Michale, i dont know if you know about it, but changing setpoint on a child thermostat device ends up applying a value-1

 

So i set 17 on the slider, and the thermostat setpoint is set to 16 and so on..

I tried to record it

See the log in the video