hub.call(QA_ID,"setVariable","debug","2") still sets Quick app variable value as number

[Sankotronic 2,370]

Hi @m.roszak,

 

No matter if above call to change Quick app variable is executed from scene or from Quick app it still converts string with numerical value to number.

Since Quick app variables can store numbers, but then edit button is gone and can't be changed by user anymore on Variables tab of the Quick app that is actually problem.

 

Here is QA debug variable value before this call:

Please login or register to see this attachment.

 

After executing this command:

Please login or register to see this code.

This is a result:

Please login or register to see this attachment.

 

As you can see variable value is changed, but with number, not string and button to edit variable is gone.

 

Since QA variables are string only values, why above command does conversion of string into number?

Or even better question is why QA variables if hold number value can't be edited?

 

[SmartHomeEddy 1,005]

18 minutes ago, Sankotronic said:

Since Quick app variables can store numbers, but then edit button is gone and can't be changed by user anymore on Variables tab of the Quick app that is actually problem.

 

 

I use this "option" to store values for example for workarounds, that I don't want users to edit. (I could also use the internal storage)

[jgab 2,641]

Not just string and numbers - it's the unpacking of call arguments that are buggy. And it's slightly different between scenes and quickapps.
Noted already 4 years ago...

 

 

[jgab 2,641]

Just running it within the same QA produces funny results, that's why always call the self:method(...) inside a qa, never fibaro.call(self.id,...)
 

Please login or register to see this code.

 

Edited September 4, 2025 by jgab

[Sankotronic 2,370]

2 hours ago, jgab said:

Just running it within the same QA produces funny results, that's why always call the self:method(...) inside a qa, never fibaro.call(self.id,...)

 

Hi @jgab,

above suggestion is not applicable when code of one Quick app needs to change variable of another Quick app. True?

 

4 hours ago, SmartHomeEddy said:

I use this "option" to store values for example for workarounds, that I don't want users to edit. (I could also use the internal storage)

 

Hi @SmartHomeEddy,

at the beginning of my journey with HC3 I did the same, but now I think I will go for internal storage to have clean list of Quick app variables for users to setup.

 

[jgab 2,641]

2 hours ago, Sankotronic said:

 

Hi @jgab,

above suggestion is not applicable when code of one Quick app needs to change variable of another Quick app. True?

 

 

Hi @SmartHomeEddy,

at the beginning of my journey with HC3 I did the same, but now I think I will go for internal storage to have clean list of Quick app variables for users to setup.

 

No, calling another QA requires fibaro.call or API rest. The 2021 post shows some ways to overcome it...

[m.roszak 763]

On 9/4/2025 at 12:26 PM, Sankotronic said:

Hi @m.roszak,

 

No matter if above call to change Quick app variable is executed from scene or from Quick app it still converts string with numerical value to number.

Since Quick app variables can store numbers, but then edit button is gone and can't be changed by user anymore on Variables tab of the Quick app that is actually problem.

 

Here is QA debug variable value before this call:

Please login or register to see this attachment.

 

After executing this command:

Please login or register to see this code.

This is a result:

Please login or register to see this attachment.

 

As you can see variable value is changed, but with number, not string and button to edit variable is gone.

 

Since QA variables are string only values, why above command does conversion of string into number?

Or even better question is why QA variables if hold number value can't be edited?

 

It always been like that, but we got a task for allowing different variables types edit in webUI.