Update 5.072.25 (Beta)

[Fireman 7]

Dear Fibaro Users,

 

FYI

 

I have updated HC 3 with  5.072.25 (Beta).

 

The plugins/QA in the app works now oke.

 

After update with 5.072.14 plugins crashes.

 

 

[ppeterr 202]

Uhmmm i dont understand

 

current beta is 5.072.14

 

Do you mean you downgraded to 5.071.52 ?

[ericl780 0]

Dear all

 

I have updated from the last stable version.

All seems to be OK

App works fine, I tested.

 

 

[ppeterr 202]

1 hour ago, Fireman said:

Dear Fibaro Users,

 

FYI

 

I have updated HC 3 with  5.072.25 (Beta).

 

The plugins/QA in the app works now oke.

 

After update with 5.072.14 plugins crashes.

 

 

 

If you ask me, there is no 5.072.25 the latest is 72.14

 

17 minutes ago, ericl780 said:

Dear all

 

I have updated from the last stable version.

All seems to be OK

App works fine, I tested.

 

 

 

Good, so your on 5.072.14 (beta) now ?

[afendikov 35]

1 hour ago, Fireman said:

Dear Fibaro Users,

 

FYI

 

I have updated HC 3 with  5.072.25 (Beta).

 

The plugins/QA in the app works now oke.

 

After update with 5.072.14 plugins crashes.

 

 

 

In my case it was opposite - one QA re-staring in loop with error:

 

" ./include/main.lua:918: attempt to index a function value (field 'powerUsedHour') "

 

But this is simple - in latest beta 5.072.25 there is new function appeared, which have same name that I used before in variable...

 

Changed my variable name to other and all works good now

 

@ppeterr - there is new beta available from today - 5.072.25

 

Maybe you will get it later today or tomorrow. Try to open manually - Settings - 2. Update

[ppeterr 202]

@afendikov

Ahh new update  Thanks for informing me.

 

 

[A.Socha 112]

Yes new update, info on forum should be soon

[Guest]

For the last few updates my UI has been so slow that it is (almost) useless.

Opening a tab on the device settings, selecting a text fields-radio button or similar or pushing the save button has quite a few seconds each of delay.

 

[m.roszak 478]

@tortho how much devices do you have on the gateway?

We are working on some optimizations but those will take some time. 

[Guest]

@m.roszak 115 devices

 

It is the same in the android app. Opening "whole house" and then to select a room and then device you can see it loads bit by bit..

Edited July 27, 2021 by tortho

[m.roszak 478]

Just to be sure, tiles in interface or physical devices with generate much more tiles in interface? 

[Guest]

Please login or register to see this attachment.

[m.roszak 478]

Ok, only Z-Wave devices.
Thats some

Thanks for clarification. 

[Sjakie 135]

I can underscribe this too.

I have no idea when its happening but now its back after update.

If I change view I get the screen to select to close or wait. This is a long time ago I had that screen.

//Sjakie

 

 

[ppeterr 202]

Well, totally not sure if what i noticed is anything like the problems above. 

 

But, when the update was finished here. The UI was also very unresponsive.

I always reboot my devices a extra time. Leave it for a couple of extra minutes so

the services are done starting  and also close the browser or app. So it clears the cache.

 

That helped for me.

[flacon030 0]

Hello

 

Personally I have abominable slowness (like more than 10 seconds to open the properties of a module) if I display all the modules including those hidden in the devices

on the other hand if I only display the lights for example (about 25 modules), without the hidden modules of these, all is well

It is impossible for me to display all of them, while in the stable version this is no problem

Edited July 27, 2021 by flacon030

[Sjakie 135]

@torthojust try >>

check mem

backing up without history

check mem

or when its still high restore that back up

In my case it freeing up, 10% memory

Succes,

//Sjakie

[seiken 0]

well it crashes less then previews beta, the interface docent respond as slow as with previews beta, but the commands to tun on/off are way slower now 

i have 110 z-wave devices connected (only version 5 and 7) running a scene takes several seconds before it start. Before my system responded directly, on the stable branch i could blink with the light many times a second, now im glad if 1 light turn on once within 3-5 seconds.

 

im using 5.072.25