onLongPressDown/onLongPressReleased

[jgab 2,642]

Anyone managed to get it work?

Tried Yubii Home app on iOS and Web UI on Safari without much success...

I'm I missing something obvious?

[Neo Andersson 230]

59 minutes ago, jgab said:

Anyone managed to get it work?

Tried Yubii Home app on iOS and Web UI on Safari without much success...

I'm I missing something obvious?

Have you tried with the new Yubii app?

[jgab 2,642]

Yep. Some setting I'm missing?

[Neo Andersson 230]

6 minutes ago, jgab said:

Yep. Some setting I'm missing?

I don't know, i did not try the longButton press. The only thing i got confirmed from developers, that some QAs are not supported at all. Those that are not actors, are not supported.

What type have you choosen for the QA? Try it with different types, maybe with sigle switch type.

Maybe @m.roszak can comment on this matter too.

[jgab 2,642]

Tried binarySwitch and binarySensor 

[m.roszak 763]

I will check this and get back to you

[m.roszak 763]

Ok, we have a problem there - it was missed, some small regression.
It will be fixed pretty soon, we are aiming for a quick release to fix everything related with new features added

[Neo Andersson 230]

7 minutes ago, m.roszak said:

Ok, we have a problem there - it was missed, some small regression.
It will be fixed pretty soon, we are aiming for a quick release to fix everything related with new features added

@m.roszak Michal, can we await other UI control related issues to be fixed?

Dropdown control does not fit into window, when it contains more data, so it closes the device randomly. /284734

Switch button state does not show up correctly / 282753

The most most annoying thing.. browser does not keep the focus on selcted QA device when getting out of LUA editor. We Always nee to serch again for the device. For first attempt it does nothing, for second it jumps back where it was, so we can continue on work. Like this driving us crazy.  / 283549

 

 

[m.roszak 763]

We cant fix everything now if we want to make a quick release, but I will verify status of those tasks - if something is almost ready we will add it.

[Christb 33]

Found 3 issues with new versions:

1) After installing HC3  version 5.153, I just lost the last QA I have developped with its 3 children, using the old or the new YUBII applications (Android) but they are still visible and working on the PC Devices web page.

Parent and children Category are Remotes, Other

Parent type is :

Please login or register to see this code.

2) On the new YUBII v2.0 Android application all the QA for Sonos (Krikroff) are totally unusable: all labels are unreadable, buttons seems not to work and showing "..." instead o the label.

They are still ok on the old YUBII application (with blue colord buttons now).

Also the height of the horizontal blank lines between buttons or labels in QAs have increased which forces now user to scroll down for accessing bottom buttons

 

[Neo Andersson 230]

1 hour ago, Christb said:

Found 3 issues with new versions:

1) After installing HC3  version 5.153, I just lost the last QA I have developped with its 3 children, using the old or the new YUBII applications (Android) but they are still visible and working on the PC Devices web page.

Parent and children Category are Remotes, Other

Parent type is :

Please login or register to see this code.

2) On the new YUBII v2.0 Android application all the QA for Sonos (Krikroff) are totally unusable: all labels are unreadable, buttons seems not to work and showing "..." instead o the label.

They are still ok on the old YUBII application (with blue colord buttons now).

Also the height of the horizontal blank lines between buttons or labels in QAs have increased which forces now user to scroll down for accessing bottom buttons

 

1. This is all discussed in other topic. At this moment other then actor type QAs won't work. Developers are working on a hot fix.

2. Html and css elements are not supported in the new app. I think this is not going to be fixed. You need to uncheck the use of new view chckbox in advanced tab.

[Christb 33]

1) Could you give me the link for the topic about this issue?

2) Sonos controler with "use the new view in mobile application" unticked make the QA to works as before.

 

When you say : I think this is not going to be fixed, do you means "NEVER" or "Not for the time being"?

[Neo Andersson 230]

10 minutes ago, Christb said:

1) Could you give me the link for the topic about this issue?

2) Sonos controler with "use the new view in mobile application" unticked make the QA to works as before.

 

When you say : I think this is not going to be fixed, do you means "NEVER" or "Not for the time being"?

1. 

Please login or register to see this link.

2. I am not a delevoper of Fibaro, but i think it will never be fixed, as the new app is constructed in different way.The view is a native part of the app, not a webview. Maybe @m.roszak can fix my statement if i am wrong.

Edited February 21, 2024 by Neo Andersson

[Christb 33]

If it is never, I hope that the old YUBII application will have a very long life... 🥶

[m.roszak 763]

There will be by default (for advanced QuickApps - com.fibaro.genericDevice/com.fibaro.deviceController) old view enabled - to allow using webview by default with all the html and css elements.
For actors/sensors default view will be a native one with possiblity to manually change it to webview from the hub.

Webview itself will be improved. 

[Christb 33]

Another issue: in a scene, hub.debug("string") does not work any more but print("string") yes

in fact if the tag is not present, it will not work but hub.debug("Scene203","string") is OK. I think this is a change from last version of firmware

I just install the "Presence Simulation" scene from Joep an I had to change all "hub.debug" to "print".

Edited February 21, 2024 by Christb

[Neo Andersson 230]

4 hours ago, m.roszak said:

There will be by default (for advanced QuickApps - com.fibaro.genericDevice/com.fibaro.deviceController) old view enabled - to allow using webview by default with all the html and css elements.
For actors/sensors default view will be a native one with possiblity to manually change it to webview from the hub.

Webview itself will be improved. 

@m.roszak Michal, if it will be handled this way, please ensure, that allowing webview make the QA show up the exact way as it was in old App, i mean fullscreen, html etc. Don't you think, that we will ever have native support for customizing buttons,labels etc outlook? There is so much to do with them, to somehow make a more complex QA user firendly and transparent. I think if Fibaro would somehow give us more freedom in customizing a QA view, it would be an immense help not only for us, who create complex codes, but for other regular users, as they can download and use more developed plugins for several smart house regions. This way Fibaro would help himself, so Fibaro would not need develop more and more plugins. Experienced users can make it. There is really so little that we can do about the look and a funcionality of QAs. Like positioning controls, color of controls, font size etc..these thing have really high impact on competitivness of Fibaro system. Do you think, will this ever happen, or this is not the way Fibaro is planning the future?

[m.roszak 763]

It will be shown in the same way (with some small styling changes to be more consistent with app visuals), with leaving html etc. alone.
For now, not full screen but it will scale the size of the bottom dialog according to the content (so it will take almost whole screen if necessary) and we will get rid of redundant frame which consumes some space - this one:

Please login or register to see this image.

/monthly_2024_02/image.png.de35dd8fbf7ec732f74b8368cceb45d9.png" />

We are planning some changes there, including full styling alignment with the rest of the system (buttons shape, colors, styles of sliders and other components), about more customization - not sure for now, can guarantee anything about that. 
In webview you will be free to use everything you used until now.
 

[Christb 33]

On 2/20/2024 at 11:40 AM, Neo Andersson said:

Have you tried with the new Yubii app?

I have tested Short/Long press in my Test Binary Switch QA and it seems to work perfectly: you have the possibility to add a method for each case:

- short press (seems to be less than 200ms)

- Long Press Maintained (for 500ms or more)

- log press released (always launched after the above)

 

It is working on the old and new YUBII application but only with the new view unticked:

Please login or register to see this attachment.

Edited February 23, 2024 by Christb

[Christb 33]

New discrepency between PC View and Yubii applications:

1) The command

 self:updateView("buttonSwitch1","value","true") or "false"

does not change the color of the switch button in the 2 Yubiis aps (always Blue) but does on the PC view ("true"= blue, "false"=light grey)

2) QA with "use the new views in mobile application" ticked,  is also changing the views in the PC application 

3) With the old Yubii app the Switch button is not working and displayed correctly: see below:

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

New View, Old application                                                                                       Old View, Old Application and New Application                                  New View, New application

 

4) In the "New View" activated, for "New application", "Old application" and "PC view", it is not possible to have the functions defined for "onLongPressDown" and "onLongPressReleased" to work.
    All 3 functions OK with "PC view", "Old application" and "New application" if not using new view.

 

Please login or register to see this image.

/monthly_2024_02/image.png.68f221a73a9cb746226a39aa94c33204.png" />

New view                                                                                       Old view

5) Will be good if Old view  silder value being upgraded to New view display

 

That's all for now...

Edited February 25, 2024 by Christb
adding new items