Quickapp variable length limited????

[Neo Andersson 230]

Hello

Is the qcuikapp variable length limited?

I am not able to use some longer JSON string inside.
I dont think i experienced this in the past.

Has that changed???

If so this would make some troubles for developing..i hope this is some termporary stuff

[jgab 2,642]

You mean the web input for variables? I guess a 200+ characters. :setVariable will probably take longer values.

How come the user of your QA needs to dump so big json in a var using the ui?

[Neo Andersson 230]

It is more than 200 chars..It is a QA for installers, not the end users. So eventually they can set it up inside the code, but it is better to have it in QA var, so noone needs to mess aroound the code.

[Brors94 115]

1 hour ago, Neo Andersson said:

It is more than 200 chars..It is a QA for installers, not the end users. So eventually they can set it up inside the code, but it is better to have it in QA var, so noone needs to mess aroound the code.

May I ask what the QA for installers do? Just out of curiosity  

[Neo Andersson 230]

There are several scenarios when a customer wants us to control heating. Thermostats on the wall - direct wired, Thermostats on the wall - not wired to actors, Virtual thermostats, radiators etc. So this plugin takes control over exising thermostats, what heat pum should they control (if any), and there are many many scenarios

if all heat pump off, turn off the boiler, 
If any pump on, turnon the boiler

If any thermotat in zone requires heat - turn on corresponding heat pump -> any heat pum on -> turn on the boiler

It monitors some known proeprties of some brands (Fibaro, Heltun, MCO) that provide a property that tells us if the thermostat actually needs heat or not.

Like in Fibaro radiator heads "heatRequired", in case of Heltun thermostats "thermostatOperatingState" etc and decides upon those values. If there is no such property provided (in case of virtual thermostats) it falls back to setpoint vs temperature + hysteresis controlling.

etc

we had some similar plugin, way more simplicistic, and now we developed this more complex one, but it needs a JSON as an input value that holds all the informations needed for functioning
Not a big deal, my technicians can set it up manually in the code, but i wanted rather tho avoid that
Plugin is still under developing but seems to work fine

usually in bigger installations i am using ER5 for all these stuff, but when it comes to an installation with 20 devices top, it is overkill to use ER5, and in other hand, using this plugin, technicians, and even the end user has some visual information about all the stuffs happening, and all at one place.

It is also monitoring power consumtion of heat pumps (picolos), because it happend some time in some installations, that our system handled correctly the heating pumps, and they got turned ON when it was needed, but customer kept calling that they are cold, so we started investigating and realized, that the heat pump was faulty. So now, if our plugin asks to turn ON the pump, but the pump itself does not cumsuome any power, it could mean that there is some problem with the pump, and we can inform customer about this in time, so they wont get a non functioning heating in freezing weather, and wont need days while they realize that there is something wrong with the pump..

So in nut shell this is the core functionality

Please login or register to see this image.

/monthly_2025_10/image.png.47a93c58055da12b0d1825e8f23a4265.png" />

Edited October 8, 2025 by Neo Andersson

[Brors94 115]

4 minutes ago, Neo Andersson said:

There are several scenarios when a customer wants us to control heating. Thermostats on the wall - direct wired, Thermostats on the wall - not wired to actors, Virtual thermostats, radiators etc. So this plugin takes control over exising thermostats, what heat pum should they control (if any), and there are many many scenarios

if all heat pump off, turn off the boiler, 
If any pump on, turnon the boiler

If any thermotat in zone requires heat - turn on corresponding heat pump -> any heat pum on -> turn on the boiler

It monitors some known proeprties of some brands (Fibaro, Heltun, MCO) that provide a property that tells us if the thermostat actually needs heat or not.

Like in Fibaro radiator heads "heatRequired", in case of Heltun thermostats "thermostatOperatingState" etc and decides upon those values. If there is no such property provided (in case of virtual thermostats) it falls back to setpoint vs temperature + hysteresis controlling.

etc

we had some similar, way more simplicistic, and now we developed this moree complex, but it needs a JSON as an input value that holds all the informations needed for functioning
Not a big deal, my technicians can set it up manually in the code, but i wanted rather tho avoid that
Plugin is still under developing but seems to work fine

usually in bigger installations i am using ER5 for all these stuff, but when it comes to an installation with 20 devices top, it is overkill to use ER5, and in other hand, using this plugin, technicians, and even the end user has some visual information about all the stuffs happening, and all at one place.

It is also monitoring power consumtion of heat pumps (picolos), because it happend some time in some installations, that our system handled correctly the heating pumps, and they got turned ON when it was needed, but customer kept calling that they are cold, so we started investigating and realized, that the heat pump was faulty. So now, if our plugin asks to turn ON the pump, but the pump itself does not cumsuome any power, it could mean that there is some problem with the pump, and we can inform customer about this in time, so they wont get a non functioning heating in freezing weather, and wont need days while they realize that there is something wrong with the pump..

So in nut shell this is the core functionality

Please login or register to see this link.

Aha  Nice work 👍