quickapp keeps running after deleting

[jvde 0]

hi,

 

i use a quickapp to port all my sensors to a mqtt server.

because there was a newer version i deleted the old quickapp (in the console it runs as quickapp260)

and installed the new one.

The new quickapp gets a new number and is also running

 

in my deviced i only have the new quickapp.

 

i already tried delting it, rebooting hc3 but the old quickapp still runs.

 

Any way i can delete the old quickapp?

[Neo Andersson 230]

We noticed similar behaviour with some quikapps, but after gateway restart it seemed to be okay.

I have sent ticket for support. Please do the same too, so there will be more tickets about this, so support will get morew warnings...

[Neo Andersson 230]

@m.roszak@A.Socha Guys, this system seems to me that is hanging by a thread before collapsing entirely, and loosing the base customers and installers.. Would you be so kind, and help us installers or other users with such a big issues? Quickapps after changing the code keep running in the background with the code before the save, and also sometimes even after we delete the quickapp. This is a very big issue in my opinion. Would you be so kind to check on this issue, or inform us that you are aware of that at least please?

[jvde 0]

6 hours ago, Neo Andersson said:

We noticed similar behaviour with some quikapps, but after gateway restart it seemed to be okay.

I have sent ticket for support. Please do the same too, so there will be more tickets about this, so support will get morew warnings...

i did the following:

deleted new quickapp

rebooted hc3

checked console: old app still running

 

so reboot was not the solution for me

 

anyone any other idea's

[Milan Takacs 22]

1 hour ago, jvde said:

i did the following:

deleted new quickapp

rebooted hc3

checked console: old app still running

 

so reboot was not the solution for me

 

anyone any other idea's

Yes. [email protected] as @Neo Andersson suggested above.

[m.roszak 763]

On 12/27/2023 at 10:07 PM, jvde said:

hi,

 

i use a quickapp to port all my sensors to a mqtt server.

because there was a newer version i deleted the old quickapp (in the console it runs as quickapp260)

and installed the new one.

The new quickapp gets a new number and is also running

 

in my deviced i only have the new quickapp.

 

i already tried delting it, rebooting hc3 but the old quickapp still runs.

 

Any way i can delete the old quickapp?

The version of the hub firmware?

[jvde 0]

Versie 5.150

[Neo Andersson 230]

@jgab @m.roszak @A.Socha

I have recieved an answer from FIbaro support..

I don't really think that this is a step ahead, but anyway i share the answer with you.

I am still experiencing this issue on multiple systems using ER5 framework, and it is apparently not a framework fault.

Here is the support answer

 

Hello, 

 

Please make sure that you are removing "parent" of Quickapp device.
If you are not removing the main Quickapp device, but a subordinate component then Quickapp may be returning to the system.
If you are sure that you are removing the "parent" of the device and this problem still occurs then in this case I will need access to the system to analyze the problem.
Such a problem does not exist after testing this on my gateway.

[tinman 1,070]

46 minutes ago, Neo Andersson said:

@jgab @m.roszak @A.Socha

I am still experiencing this issue on multiple systems using ER5 framework, and it is apparently not a framework fault.

 

hmm, i have here multiple HC3 running, with all kind of wired QuickApps, none of them ER5 based, none of them developed on 3rd part device - no issues with multiple/ghost instances here.

 

Knowing how HC3 handles QuickApps on OS level, i wonder how they can survive after deletion(or parent deletion), that really feels like "ext dev file update issue" 

[jgab 2,642]

44 minutes ago, tinman said:

 

hmm, i have here multiple HC3 running, with all kind of wired QuickApps, none of them ER5 based, none of them developed on 3rd part device - no issues with multiple/ghost instances here.

 

Knowing how HC3 handles QuickApps on OS level, i wonder how they can survive after deletion(or parent deletion), that really feels like "ext dev file update issue" 

Yes, but it happens other QAs than ER5....

Yes, it seems (a theory) to be triggered by file updates of QAs with many large QA files.

However, it's also caused when the QA is updated in the Web UI editor (which I guess, technically is also a "ext dev file update issue" ).

...which seems to be @Neo Andersson's problem as he can't edit the QA and resave it without causing the problem on his system.

On the other hand I haven't been able to reproduce the problem with the same QA on my system, so I guess we need to add the condition of the system as another variable...

 

[jgab 2,642]

I have really tried to come up with an MVP (minimal viable problem) 

pondering the QA with file updates, the same QA as @Neo Andersson had issues with on his system) without
being able to reproduce it. However, it has happened me twice the last ~2years with an earlier QA and with ER5.

With ER5 that has many files and is quite large it has happened to @Neo Andersson, @Sjakie, and @ChristianSogaard the last month - to a varying degree. If it was only caused when updating the QA with the file apis I could understand it but it also happens just when they edit the QA in the WebUI and resaves it.

 

Anyway, I'm still on the lookout for an MVP.

What I have seen is that if you delete a file in the Web UI, the QA is not restarted so that can have some unexpected behaviour.

Ex. put a setInterval(function() print("PING") end,2000) in a second QA file, run the QA, see the PINGS, delete the second QA file, close QA editor, see PINGS still in the console. This is of course not the issue we discuss here, but it just surprised me.

So, the add, modify files that DO restart the QA... Could it be that if several add/modifies comes quickly in a sequence, there is some race condition that leaves the old Lua process running? restart fails to kill old before starting new?.

What is "quickly" could of course be dependent on how loaded the system is, which could explain why it happens on just some systems and at full moon...?

[Sjakie 156]

Just what I notice if I update QA ER5 with QA Updater.

I select the QA to update>>update QA.

If Updater finished I select  another QA but I see the previous updated QA still has the old version number.

So it's needing time to refresh the data.

In the mean time the QA is still active but it should have been shut down to update?

Can it be .....

 

[Neo Andersson 230]

guys, maybe i am seeing ghosts already, but on two of my systems, we restarted the gateway, and the ER5 based QA reloaded to a state before our last changes..

I am just pretty lost here..so we made some changes in the QA,saved it,  and after several days (while the QA was running without any problems), we restarted the system (FW update), and our ER5 QA reloaded to a state before our last changes that we made prior to restart.

Ehhh

 

 

 

 

 

[tinman 1,070]

@jgab one can easily break QuickApp, i managed already - by playing with API and some other magic - to break the database, so i had to reinstall everything.

 

My last broken-QA experience was based on stupid typo, created child devices with different class names than in init part / child var names, no runtime error, all good, the quickapp was running. But after first init with broken code, i wasn't able to edit/save code anymore and wasn't able to remove child devices anymore. So had to copy the code away, and delete the parent quick app first. Remember as well to killed QA by creating files with special character in sub file names, yeah. 

[jvde 0]

currently it looks like my quickapp260 disappeared in the first week of januari, only quickapp272 is now running, don't know what happened. got a few reboots but not really anything else

 

maybe it need some time to unload from memory or something?