New Yubii Home App - update

[Neo Andersson 230]

@m.roszak Okay Michael, i can confirm, that generic device type is not shown anymore in the new Yubii app. I have tried it with several devices. Generic is not supported.

Neither Device controller.

Edited February 19, 2024 by Neo Andersson

[m.roszak 765]

Yep, we know that - it will come back shortly

[Neo Andersson 230]

@m.roszak Michal, the controls from my QA does not show up with unchecked "magic" checkbox, even if i choose other types. I have tried to use different device types for my Irrigation QA, but the controls doesn't show up. This is the old view

 

Please login or register to see this image.

/monthly_2024_02/image.png.1dbd96ae752c34004050e46116aa316b.png" />

 

and this is the new one, i tried with power meter.

 

Please login or register to see this attachment.

 

 

At this point it seems to me, that the App is not really suitable for users with quickapps.

 

 

Edited February 19, 2024 by Neo Andersson

[m.roszak 765]

MultilevelSensors (including meters) also do not support it, those were treated as a simple device and maybe it was a bad call - I already created a task for it.

As a workaround - any actor should work ok with the old view.

2 hours ago, SmartHomeEddy said:

@m.roszak Is there a way I can sort the sections or why doesn’t it show the section in the order it was ordered in the dashboard? 
 

 

 

I will need to check that out

[Neo Andersson 230]

30 minutes ago, m.roszak said:

As a workaround - any actor should work ok with the old view.

Well not really, as it doesn't show the entire QA. No full screen. It should automatically open in full screen, so user doesn't need to scroll.

Now it is very cumbersome, as there are many buttons, so when user needs to scroll many accidental button presses happen, and in general, it is not usable in half screen.

Maybe you can find out some quick solution for this. This affects quite a lot of users i think.

Edited February 19, 2024 by Neo Andersson

[tinman 1,070]

On 2/19/2024 at 7:32 PM, m.roszak said:

As a workaround - any actor should work ok with the old view.

 

hehe i played bit with my Sonos QuickApp which is using com.fibaro.sonosSpeaker as type, however as ui v2 is not working (yet) for QuicApp, i took the uiview jason layout from Sonos plugin and embedded into my QuickApp.

Good news, i have new look and actions are working. Bad news, i can't edit quickapp anymore (can't save changes), but at leat step in right direction.

 

Please login or register to see this spoiler.

 

Edited February 20, 2024 by tinman

[Fireman 7]

Why should i use Yubii Home (new) app instead of Yubii (old)?

 

Faster? More posibilities? No more updates old app?

 

Thanks

[SmartHomeEddy 1,006]

For the time being, you can use both and see what you like and if you are bothered by the current limitations of the new app. 

 

_{(The Yubii app supports the HC2. I haven't seen that yet in the new Yubii Home app. And there is also still the Fibaro app for the HC2.)} 

 

 

[Neo Andersson 230]

@m.roszak Dear Michal,

the push and simplePush function does not work anymore in a way it used to.

There are hunderds of lines of codes, frameworks, quickapps, where we are using some syntax. Dozens of custmoers daily system behaviour is completely stuck.

Michal, this is not a fair apporach to your users. We, installers almost all the time are using some frameworks, or LUA codes in QAs. Push and simplePush have thousands of appereances in our installations.

This is not the way we can coopeprate. Nothing mentioned in changeLogs, nowhere any warning about this.

If the system will show such base function syntax changes, you ruin everyone's existing work.

What can we do now?

Revert all the systems to previous versions? I think this is not the way we should go.

Please, fix the push and simplePush functions syntax, back as it was before. This shouild have a top priority as it affects every single customer.

See below a snippet from our discussion from another toipc regarding this issue from @jgab

You can see what is the situation now.

 

So at the moment

fibaro.alert('simplePush', {[1] = 923, }, 'hello')

works from scenes for me but not from QAs.

'push' does not work in either scenes or QAs for me.

The extra false arguments are strange/inconsistent as the device structure's action definition says it should only have one argument...

Please login or register to see this link.

For some reasons they have different fibaro.*/hub.* api implementations for scenes and QAs and now they don't seem to do the same thing...

 

 

Edited February 22, 2024 by Neo Andersson

[Neo Andersson 230]

@m.roszakMichal, another question. Is the new App working locally too? As the old app used to. It seems to me that the when using the new app, the communication is quite slow, seems to me that it never run locally.

[tinman 1,070]

2 minutes ago, Neo Andersson said:

@m.roszakMichal, another question. Is the new App working locally too? As the old app used to. It seems to me that the when using the new app, the communication is quite slow, seems to me that it never run locally.

 

sure it does, under the hcx-yyyyyy icon on the left top, it shows connected locally 

Edited February 22, 2024 by tinman

[tinman 1,070]

1 hour ago, Neo Andersson said:

the push and simplePush function does not work anymore in a way it used to.

There are hunderds of lines of codes, frameworks, quickapps, where we are using some syntax. Dozens of custmoers daily system behaviour is completely stuck.

 

must be a bug, i don't see any changes in QA engine API, except additions for empty UUID handling

 

1 hour ago, Neo Andersson said:

This is not the way we can coopeprate.

 

it's beta, use backup / restore if you don't like it, report bugs

 

1 hour ago, Neo Andersson said:

Nothing mentioned in changeLogs, nowhere any warning about this.

 

actually changelog could be better for sure, statement like "Possibility to use Quick App's old style view for backward compatibility." is cool, but what behind? i would like to see faq article ind link to it within changelog.

 

 

1 hour ago, Neo Andersson said:

What can we do now?

Revert all the systems to previous versions? I think this is not the way we should go.

 

again it's beta, use backup / restore if you don't like it, report bugs

 

1 hour ago, Neo Andersson said:

For some reasons they have different fibaro.*/hub.* api implementations for scenes and QAs and now they don't seem to do the same thing...

 

scene engine is different thing than QA engine, unfortunately / luckily some function have different syntax, from what one told me "introduced with HC2->HC3 migration to prevent HC2 be executed in QAs".

 

[jgab 2,645]

13 hours ago, tinman said:

scene engine is different thing than QA engine, unfortunately / luckily some function have different syntax, from what one told me "introduced with HC2->HC3 migration to prevent HC2 be executed in QAs".

But the fibaro.* sdk (hub.*) could be shared between the Scene and QA frameworks? To minimise the risk of diverging syntax/functionality?

The only thing not common is the (mysterious) get/set scene variable...

[Neo Andersson 230]

@tinman Dear Tinman, I am more than aware of what it means to go for a Beta version. However, it is not my desire to go for it before stable version is released. It is more forced, as in beta there were some bug fixes from earlier stable version, that i had many many problems with. So that is why i updated to beta on several customer's systems. It solved some bugs but broght up som unforeseen new syntaxes, or bugs, that were not mentioned in change logs. Like the one with the push, simplePush calls. If i new about these different function calls, i would never have gone for the beta, as push function is used in hundreds of lines of code. So that is the reason i was asking Fibaro to solve this with high priority, and to be more consistant with base function calls, or at least infrom us about changes, to let us decide, wheather we should(can) go for it or not. But thanks for your answers anyway. I hope Fibaro will solve this issue with push calls in next release, so i can keep the new beta and convince customers to be patient and wait for the fix. I hope, @m.roszak will help us with this, as he always did. Thanks again

Edited February 23, 2024 by Neo Andersson

[Oddi_78 16]

@m.roszak In the new Mobil View, is CSS3, Bootstrap supported?. Is it posible to link in any way to use links (html), so that we can link to our web app, heatit renergy. I see the old one works. See video

Please login or register to see this link.

[m.roszak 765]

On 2/22/2024 at 3:13 PM, Neo Andersson said:

@m.roszak Dear Michal,

the push and simplePush function does not work anymore in a way it used to.

There are hunderds of lines of codes, frameworks, quickapps, where we are using some syntax. Dozens of custmoers daily system behaviour is completely stuck.

Michal, this is not a fair apporach to your users. We, installers almost all the time are using some frameworks, or LUA codes in QAs. Push and simplePush have thousands of appereances in our installations.

This is not the way we can coopeprate. Nothing mentioned in changeLogs, nowhere any warning about this.

If the system will show such base function syntax changes, you ruin everyone's existing work.

What can we do now?

Revert all the systems to previous versions? I think this is not the way we should go.

Please, fix the push and simplePush functions syntax, back as it was before. This shouild have a top priority as it affects every single customer.

See below a snippet from our discussion from another toipc regarding this issue from @jgab

You can see what is the situation now.

 

So at the moment

fibaro.alert('simplePush', {[1] = 923, }, 'hello')

works from scenes for me but not from QAs.

'push' does not work in either scenes or QAs for me.

The extra false arguments are strange/inconsistent as the device structure's action definition says it should only have one argument...

Please login or register to see this link.

For some reasons they have different fibaro.*/hub.* api implementations for scenes and QAs and now they don't seem to do the same thing...

 

 

Working on a fix. 

 

57 minutes ago, Oddi_78 said:

@m.roszak In the new Mobil View, is CSS3, Bootstrap supported?. Is it posible to link in any way to use links (html), so that we can link to our web app, heatit renergy. I see the old one works. See video

Please login or register to see this link.

New view, no.
You get what you see in the editor in web.

If you are in need of custom implementation old views are the way to go. 

[Oddi_78 16]

2 hours ago, m.roszak said:

Working on a fix. 

 

New view, no.
You get what you see in the editor in web.

If you are in need of custom implementation old views are the way to go. 

Thx. Can you make the view full size, se pictures. 

Please login or register to see this attachment.

Please login or register to see this attachment.

Please login or register to see this attachment.

[m.roszak 765]

Update the app to newest version (released 2h ago)

Size will scale automatically depending on the content. 

[Oddi_78 16]

6 minutes ago, m.roszak said:

Update the app to newest version (released 2h ago)

Size will scale automatically depending on the content. 

Thank you for the extremely quick response. I love the new mobile app. Have a nice day. 😃

[SmartHomeEddy 1,006]

@m.roszak The new Yubii Home app, should it show the QuickApp labels/content now if you run your HC3 on the stable firmware version?

 

Edited February 26, 2024 by SmartHomeEddy