How to turn off a QuickApp?

[RH_Dreambox 189]

How to turn off a QuickApp for a while?
Activating Disable does not work, the QuickApp continues to run.

 

 

Please login or register to see this attachment.

[Sjakie 156]

I dont think it can be done.

Set your code between --[[   --]] and let it run so you keep your device number.

If thats not important than save as .fqa and delete

//Sjakie

[RH_Dreambox 189]

Yes, it can be done in that way, but it must also be possible to disable a QA.
Suppose I have a Profile that I call Winter.
There I want to deactivate all QuickApp's that regulate irrigation in greenhouses durung the winter.
It is also not possible to do, the QuickApp's continues to run even if they are turned off in the Winter Profile.

One might really wonder if Fibaro is checking its own software or if they are waiting for us users to report all the bugs?

 

 

Please login or register to see this attachment.

[lazer 41]

This checkbox has not other effect than modifying the "enable" field in the device's API.

 

You have to write your own LUA code to take this value into consideration.

 

Here is an example I use at the beginning in the onInit() function of my QAs :

Please login or register to see this code.

 

Edited November 21, 2021 by lazer

[RH_Dreambox 189]

Thanks @lazer, it worked perfectly!
But is this how Fibaro has intended it to work ???
It is so illogical that an extra code is needed to turn off a QA as you have already turned it off in the interface!
But that's probably how they think within Fibaro's walls!!!

[tinman 1,070]

48 minutes ago, RH_Dreambox said:

But is this how Fibaro has intended it to work ???

 

yes, because it is QA, you have to take care of the code inside.

 

[RH_Dreambox 189]

Quote

yes, because it is QA, you have to take care of the code inside.

Thanks for your explanation.

[jgab 2,646]

3 hours ago, lazer said:

This checkbox has not other effect than modifying the "enable" field in the device's API.

 

You have to write your own LUA code to take this value into consideration.

 

Here is an example I use at the beginning in the onInit() function of my QAs :

Please login or register to see this code.

 

In principle you need to disable UIEvent and onAction handlers too as other can call the QA and wreck havoc....

[lazer 41]

@jgab

You're right.

One can define an internal variable, such as self.isenabled = true / false inside onInit(), then check this variable upon every events (button/slider clicks, etc.). Then the QA can display a nice message in the log or a label to remind the user that the QA is disabled.

[jgab 2,646]

3 hours ago, lazer said:

@jgab

You're right.

One can define an internal variable, such as self.isenabled = true / false inside onInit(), then check this variable upon every events (button/slider clicks, etc.). Then the QA can display a nice message in the log or a label to remind the user that the QA is disabled.

or something like

Please login or register to see this code.

[RH_Dreambox 189]

@jgab

Is this function implemented in EventRunner?

 

EDIT

Unfortunately, this only works to 50%.
The setting in Profiles has no effect at all.
If my QA is Enabled but Turned Off in Profiles, my QA will continue to work.
Could this be a bug, or is it what Fibaro usually says "By design"?

Edited November 22, 2021 by RH_Dreambox

[jgab 2,646]

24 minutes ago, RH_Dreambox said:

@jgab

Is this function implemented in EventRunner?

No it's not implemented in ER - I probably should do that.

 

24 minutes ago, RH_Dreambox said:

EDIT

Unfortunately, this only works to 50%.
The setting in Profiles has no effect at all.
If my QA is Enabled but Turned Off in Profiles, my QA will continue to work.
Could this be a bug, or is it what Fibaro usually says "By design"?

 

Do the profile setting actually disable the QA or do they just exclude it from the profile? I believe the latter.

1 minute ago, jgab said:

No it's not implemented in ER - I probably should do that.

 

 

Do the profile setting actually disable the QA or do they just exclude it from the profile? I believe the latter.

You can't disable from the profile - only turn on and off?

[RH_Dreambox 189]

Hmmm, Fibaro, Fibaro, Fibaro
I thought that in Profiles you could enable or disable all types of scenes and devices, including QA.
This must be something they have missed, because what else is Profiles to be used for?

[tinman 1,070]

disable is to stop (more or less) the communication, which for QA would be operation. There is no disable for devices, for what? Create scene to disable / enable, and trigger it from Profiles (same can be done for other devices)

 

 

Edited November 22, 2021 by tinman