QuickApp - SolarEdge Live (Modbus) version 1.2

[SmartHomeEddy 1,005]

This is the next version 1.2 of the SolarEdge Live (Modbus) QuickApp.

The SolarEdge Live (Modbus) QuickApp represents an advanced integration that provides instant, real-time access to local inverter data without the limitations of cloud-based API’s. This QuickApp uses the Modbus of your SolarEdge Inverter to get the real-time information about your SolarEdge setup. The QuickApp reads the SolarEdge SunSpec Modbus registers and shows the with QuickApp variables requested register values in child devices and labels. The QuickApp runs at an interval setup in the QuickApp variables. A special button is available to adjust the speed up the interval. 

 

Please login or register to see this attachment.

 

Please login or register to see this attachment.

 

Example QuickApp Variables with register addresses and devicetypes:

Please login or register to see this attachment.

 

 

Enabling Modbus on SolarEdge Inverters: 
To enable Modbus communication on a SolarEdge inverter, follow these general steps:

• Access the inverter’s configuration menu, either via its control panel or through the manufacturer’s configuration app.
• Navigate to the communication settings.
• Enable Modbus support, selecting TCP/IP for network connections.
• Adjust Modbus parameters as needed, such as device ID and communication port.
• Save your changes and restart the inverter if required.

After activation, the inverter is ready to communicate with external systems or monitoring solutions using the Modbus protocol. Always consult your inverter’s user manual for detailed instructions specific to your model.

 

Important documentation for the right register addresses (use the base 1 address): 

Please login or register to see this link.

 

Disclaimer:

Use this QuickApp at your own risk. You are responsible for ensuring that the information provided via this QuickApp do not contain errors. SolarEdge is a registered trademark being the property of SolarEdge. SolarEdge reserves all rights to the registered trademarks. Information which is published on SolarEdge’s websites belongs to SolarEdge or is used with the permission of the rights holder. Making of copies, presentations, distribution, display or any other transfer of the information on the website to the public is, except for strictly private use, prohibited unless done with the consent of SolarEdge. Published material on dedicated SolarEdge press websites, intended for public use, is exempt from the consent requirement.

 

Changes version 1.2 (2nd September 2025)

• Changed the main device type to com.fibaro.powerMeter, so it can contain the AC Power value. 
• Added QuickApp variable for the main device register, mainRegister (default = 40084 AC Power). 
• Added default don't 'Save events to History' (saveLogs = false) to the setup of every child device. 
• Disabled the warnings for READ, WRITE and Invalid response. Users can't prevent those errors and to display them as warnings only clutters the logging. 
• Changed the text of the interval speed buttons to the content of the quickapp variables intervalChildsS, intervalChildsM and intervalChildsF. 
• Found a few old SolarEdge Modbus QuickApp names in the code and changed them also to SolarEdge Live. 
• Optimised the register mapping. 
• Changed the default interval timing to 60, 10 and 5 seconds. Of course, you can use your own settings. 
• Removed the expiration date. 

 

Changes version 1.1 (9th August 2025)

• Renamed the QuickApp from SolarEdge Modbus to SolarEdge Live. SolarEdge Live represents the QuickApp in a better way. Of course the Modbus is still used as protocol.
• Added button for 'Inverter' with support for SunSpec model type 101 (single phase), 102 (split phase) or 103 (three phase). 
• Added QuickApp variable inverterType for the model type of your Inverter (101 (single phase), 102 (split phase) or 103 (three phase), default type 101 (single phase). Also see the value of register 40070.)
• Added optimisation with re-use of the already connected Modbus socket. 
• Improved memory usage with more variables as local variable. 
• Changed the maximum retries to a maximum consecutive time no response. 
• Changed the interval to three speeds, Slow, Medium and Fast. With QuickApp variables the speeds setting can be made for the interval and child updates. 
• Added an indicator (*) to most of the buttons to show what selection is active. 
• Added 'Disconnect' (or 're-connect') button to manually disconnect the QuickApp and Modbus. 
• Added extra check for the amount of addresses (including the extra scale factor addresses) not to exceed 125 (Modbus spec: max 125 registers per request). 
• Added extra check for the addresses being in the 40001-49999 range. 
• Changed the register table to indexed, so the addresses (and scale factors) can be selected directly and fast from the table. 
• Removed a double warning for CONNECT issue. 
• Added in case of a device type 'com.fibaro.energyMeter' the property 'storeEnergyData = false' is added to the setup of that child device. By default the energyMeter won't save energy to the energy database.  
• Added in case of a device type 'com.fibaro.powerMeter' the property 'includeInEnergyPanel = false' is added to the setup of that child device. By default the powerMeter won't be used for instantaneous power in Energy Panel calculations.  
• Added the current time to the log text of the main device. 
• Added the register address to the log text of all the child devices. The log text was empty. This will help to get more acquainted with the register addresses. 
• Placed the register address in front of the label text to make it more readable. 
• Improved the message of the retry warnings, show seconds to maxResponseTime. 
• Improved some register description text. 
• Rounded all the values to two decimal places. 

 

Changes version 1.0  (27th July 2025)

• Initial version with child devices to configure in QuickApp variables. 

 

Variables (mandatory and created automatically): 

• host = Modbus TCP IP address of your target device (default 192.168.1.145)
• port = Modbus TCP port (default 1502)
• unitId = Modbus slave/unit address (default 1)
• inverterType = Type of your Inverter (101, 102 or 103, default type 101. Also see the value of register 40070.)
• intervalS = How fast the Modbus will refresh the data (Slow default 60 seconds) 
• intervalM = How fast the Modbus will refresh the data (Medium default 10 seconds) 
• intervalF = How fast the Modbus will refresh the data (default 5 seconds) 
• intervalChildsS = How fast the Childs will update (Slow default 60 seconds)
• intervalChildsM = How fast the Childs will update (Medium default 10 seconds) 
• intervalChildsF = How fast the Childs will update (default 5 seconds) 
• maxResponseTime = Maximum time in seconds for response of the Modbus to disconnect (default = 60)
• debugLevel = Number (1=some, 2=few, 3=all) (default 1)
• Also with the QuickApp variables child devices can be created. Insert a QuickApp variabel with the address as 'variable' and the deviceType as 'value'. By default the values from the childs will show in the labels (except Scalefactor values). You can use all kinds of devicesTypes, for example: 
• com.fibaro.energyMeter (Wh) (by default no storage to energy database)
• com.fibaro.powerMeter (Watt) (by default not used for instantaneous power in Energy Panel calculations)
• com.fibaro.electricMeter (Volt and Ampere)
• com.fibaro.multilevelSensor (Number values)
• com.fibaro.temperatureSensor (Temperature)

Please login or register to see this image.

/monthly_2025_08/image.png.5b9eef364bb7da6bc971e8e0671eb3f2.png" />

Download the QuickApp here:

Please login or register to see this attachment.

 

or from the Fibaro Marketplace: 

Please login or register to see this link.

 

How to install:

• Open the Configuration Interface
• Go to Settings > Devices
• Click  +
• Choose Other Device
• Choose Upload File
• Choose file from your computer with .fqax

(This download contains several example register addresses, but you can choose you own register addresses to create your child devices) 

 

 

 

 

 

 

Edited September 11, 2025 by SmartHomeEddy

[SmartHomeEddy 1,005]

I had fun building this brand new SolarEdge Modbus QuickApp. I hope you have fun using this QuickApp and exploring all kinds of register addresses and realtime values to monitor your SolarEdge Setup, Solar production and Energy usage. 
 

Please share your experiences with the Modbus values with all of us. You can use the values to monitor the production of your inverter, monitor the import and export of your production from your SolarEdge Inline Energymeter, monitor your SolarEdge Storage load and health and of course you can monitor the technical shape of your SolarEdge setup. 

 

Edited July 28, 2025 by SmartHomeEddy

[SmartHomeEddy 1,005]

Why SolarEdge Modbus?
 

Benefits

1. No Cloud Dependency: Local operation means your system is not affected by outages or rate limits on SolarEdge’s monitoring. 
2. Enhanced Automation: Real-time inverter data can trigger home automation scenarios, such as optimizing energy use or alerting you to equipment issues.
3. Scalability: The QuickApp supports installations with multiple inverters or meters, provided each is addressable via Modbus.

 

This QuickApp is distinct from those that only provide aggregated or delayed data through SolarEdge’s cloud and offers robust, customizable monitoring integrated directly into your Homecenter.

 

 

Edited July 28, 2025 by SmartHomeEddy

[Brors94 115]

1 minute ago, SmartHomeEddy said:

Why SolarEdge Modbus?
 

Benefits

1. No Cloud Dependency: Local operation means your system is not affected by outages or rate limits on SolarEdge’s monitoring. 
2. Enhanced Automation: Real-time inverter data can trigger home automation scenarios, such as optimizing energy use or alerting you to equipment issues.
3. Scalability: The QuickApp supports installations with multiple inverters or meters, provided each is addressable via Modbus.

Always better with local control 😄👍 


 

[SmartHomeEddy 1,005]

To enable Modbus (TCP) on your SolarEdge inverter, ask your Installer or follow the steps below. The method depends on whether your model uses the SetApp (mobile app) or an onboard LCD display.

For Inverters With SetApp (Mobile App)

1. Connect to Your Inverter: Use WiFi Direct to connect your phone to the inverter. Toggle the switch on the inverter to “P” briefly, then connect to the inverter’s WiFi using the password listed on the side.

2. Open SetApp: Launch the SolarEdge SetApp on your device. (You maybe need some extra authorisations from your installer.)

3. Go to Communication Settings: Navigate to the Site Communication menu.

4. Enable Modbus TCP:

    •   Find “Modbus TCP.”

    •   Set to “Enable.”

    •   Default port is usually 1502 (sometimes 502).

 

For Inverters With an LCD Display

1. Access Installer Menu:

    •  Long-hold the “OK” (rightmost) button.

    •  Enter the password “Up Down OK, Up Down OK, Up Down” (screen will show 12312312).

2. Go to Communication → LAN Conf → Modbus TCP.

3. Enable Modbus TCP:

    •  Select Modbus TCP.
    •  Enable it.
    •  Change the TCP port if needed (default is usually 502).

 

With Wifi Module

1. Enable wifi direct on the inverter by switching the red toggle switch on the inverter to "P" position for less than 5 seconds.

2. Connect to the inverter access point like you would for a normal wifi network. The wifi password is published at the right side of the inverter.

3. Open up a browser and go to http://172.16.0.1 > Site Communication. From this webpage you can enable modbus TCP without setApp or installer account.

 

Additional Tips
•  Make sure your inverter is on recent firmware—SetApp models and display models with v3.xxxx or later firmware support SunSpec/Modbus.
•  For network stability, assign a static IP to your inverter in your router.
•  For systems not connected to a router, configure static network settings directly.

 

 

 

Edited July 31, 2025 by SmartHomeEddy

[SmartHomeEddy 1,005]

SolarEdge inverters with more recent firmware (from mid-2022 onward) support Modbus communication not only via Ethernet (Modbus TCP) and RS485 but also via WiFi.

 

This is relatively unique because, while Modbus RTU (serial over RS485) and TCP (Ethernet) are standard, native WiFi support for Modbus is uncommon among inverter manufacturers.
 

This feature makes it much easier to integrate SolarEdge inverters into wireless home automation solutions or monitoring platforms without needing to run additional cables or adapters.

 

Notably, older SolarEdge models with a display (from around 2015 onward) can also gain this functionality by performing a firmware update via USB, upon which Modbus communication over WiFi is unlocked.

[SmartHomeEddy 1,005]

The new 1.1 version of the SolarEdge Live (Modbus) quickapp is available with lots of very nice new functions!

 

 

Changes version 1.1 (9th August 2025)

• Renamed the QuickApp from SolarEdge Modbus to SolarEdge Live. SolarEdge Live represents the QuickApp in a better way. Of course the Modbus is still used as protocol.
• Added button for 'Inverter' with support for SunSpec model type 101 (single phase), 102 (split phase) or 103 (three phase). 
• Added QuickApp variable inverterType for the model type of your Inverter (101 (single phase), 102 (split phase) or 103 (three phase), default type 101 (single phase). Also see the value of register 40070.)
• Added optimisation with re-use of the already connected Modbus socket. 
• Improved memory usage with more variables as local variable. 
• Changed the maximum retries to a maximum consecutive time no response. 
• Changed the interval to three speeds, Slow, Medium and Fast. With QuickApp variables the speeds setting can be made for the interval and child updates. 
• Added an indicator (*) to most of the buttons to show what selection is active. 
• Added 'Disconnect' (or 're-connect') button to manually disconnect the QuickApp and Modbus. 
• Added extra check for the amount of addresses (including the extra scale factor addresses) not to exceed 125 (Modbus spec: max 125 registers per request). 
• Added extra check for the addresses being in the 40001-49999 range. 
• Changed the register table to indexed, so the addresses (and scale factors) can be selected directly and fast from the table. 
• Removed a double warning for CONNECT issue. 
• Added in case of a device type 'com.fibaro.energyMeter' the property 'storeEnergyData = false' is added to the setup of that child device. By default the energyMeter won't save energy to the energy database.  
• Added in case of a device type 'com.fibaro.powerMeter' the property 'includeInEnergyPanel = false' is added to the setup of that child device. By default the powerMeter won't be used for instantaneous power in Energy Panel calculations.  
• Added the current time to the log text of the main device. 
• Added the register address to the log text of all the child devices. The log text was empty. This will help to get more acquainted with the register addresses. 
• Placed the register address in front of the label text to make it more readable. 
• Improved the message of the retry warnings, show seconds to maxResponseTime. 
• Improved some register description text. 
• Rounded all the values to two decimal places. 

 

 

Please login or register to see this image.

/monthly_2025_08/image.png.efbbf692bbc08931a9637fd5103e6162.png" />

 

Please login or register to see this attachment.

Edited August 9, 2025 by SmartHomeEddy

[SmartHomeEddy 1,005]

@m.roszak Can you have someone give the SolarEdge Live quickapp in de Marketplace a push?

[m.roszak 763]

Already pushed

[SmartHomeEddy 1,005]

Thanks

[SmartHomeEddy 1,005]

So I put some interesting registers as example in the quickapp. Each address gets a childs device and the value is also shown in the labels. But if you want to look for any other interesting addresses, look in this document:

Please login or register to see this link.

 

 

You can add other addresses via the quickapp variables. Just insert the base-1 address from the documentation as 'variable' and the wanted device type as 'value' and push 'save'. 

You can choose any device type, for example:
  - com.fibaro.energyMeter (Wh)
  - com.fibaro.powerMeter (Watt)
  - com.fibaro.electricMeter (Volt and Ampere)
  - com.fibaro.multilevelSensor (Number values)
  - com.fibaro.temperatureSensor (Temperature)

 

Just as simple as that 😃

[SmartHomeEddy 1,005]

To put one of the registers in the spotlight, “operating status” with address 40108. You can monitor your SolarEdge Inverter with (for example) a simple blockscene. 
 

Please login or register to see this attachment.

Especially status 1,  5, 7 and 8 are the statuses to monitor. 

 

 

 

Edited August 28, 2025 by SmartHomeEddy

[SmartHomeEddy 1,005]

The new SolarEdge Live version 1.2 has some really nice new features:

 

Changes version 1.2 (2nd September 2025)

• Changed the main device type to com.fibaro.powerMeter, so it can contain the AC Power value. 
• Added QuickApp variable for the main device register, mainRegister (default = 40084 AC Power). 
• Added default don't 'Save events to History' (saveLogs = false) to the setup of every child device. 
• Disabled the warnings for READ, WRITE and Invalid response. Users can't prevent those errors and to display them as warnings only clutters the logging. 
• Changed the text of the interval speed buttons to the content of the quickapp variables intervalChildsS, intervalChildsM and intervalChildsF. 
• Found a few old SolarEdge Modbus QuickApp names in the code and changed them also to SolarEdge Live. 
• Optimised the register mapping. 
• Changed the default interval timing to 60, 10 and 5 seconds. Of course, you can use your own settings. 
• Removed the expiration date. 

Please login or register to see this attachment.

 

Please login or register to see this attachment.

[reso007 0]

On 7/27/2025 at 2:01 PM, SmartHomeEddy said:

This is the next version 1.2 of the SolarEdge Live (Modbus) QuickApp.

The SolarEdge Live (Modbus) QuickApp represents an advanced integration that provides instant, real-time access to local inverter data without the limitations of cloud-based API’s. This QuickApp uses the Modbus of your SolarEdge Inverter to get the real-time information about your SolarEdge setup. The QuickApp reads the SolarEdge SunSpec Modbus registers and shows the with QuickApp variables requested register values in child devices and labels. The QuickApp runs at an interval setup in the QuickApp variables. A special button is available to adjust the speed up the interval. 

 

Please login or register to see this attachment.

 

Please login or register to see this attachment.

 

Example QuickApp Variables with register addresses and devicetypes:

Please login or register to see this attachment.

 

 

Enabling Modbus on SolarEdge Inverters: 
To enable Modbus communication on a SolarEdge inverter, follow these general steps:

• Access the inverter’s configuration menu, either via its control panel or through the manufacturer’s configuration app.
• Navigate to the communication settings.
• Enable Modbus support, selecting TCP/IP for network connections.
• Adjust Modbus parameters as needed, such as device ID and communication port.
• Save your changes and restart the inverter if required.

After activation, the inverter is ready to communicate with external systems or monitoring solutions using the Modbus protocol. Always consult your inverter’s user manual for detailed instructions specific to your model.

 

Important documentation for the right register addresses (use the base 1 address): 

Please login or register to see this link.

 

Disclaimer:

Use this QuickApp at your own risk. You are responsible for ensuring that the information provided via this QuickApp do not contain errors. SolarEdge is a registered trademark being the property of SolarEdge. SolarEdge reserves all rights to the registered trademarks. Information which is published on SolarEdge’s websites belongs to SolarEdge or is used with the permission of the rights holder. Making of copies, presentations, distribution, display or any other transfer of the information on the website to the public is, except for strictly private use, prohibited unless done with the consent of SolarEdge. Published material on dedicated SolarEdge press websites, intended for public use, is exempt from the consent requirement.

 

Changes version 1.2 (2nd September 2025)

• Changed the main device type to com.fibaro.powerMeter, so it can contain the AC Power value. 
• Added QuickApp variable for the main device register, mainRegister (default = 40084 AC Power). 
• Added default don't 'Save events to History' (saveLogs = false) to the setup of every child device. 
• Disabled the warnings for READ, WRITE and Invalid response. Users can't prevent those errors and to display them as warnings only clutters the logging. 
• Changed the text of the interval speed buttons to the content of the quickapp variables intervalChildsS, intervalChildsM and intervalChildsF. 
• Found a few old SolarEdge Modbus QuickApp names in the code and changed them also to SolarEdge Live. 
• Optimised the register mapping. 
• Changed the default interval timing to 60, 10 and 5 seconds. Of course, you can use your own settings. 
• Removed the expiration date. 

 

Changes version 1.1 (9th August 2025)

• Renamed the QuickApp from SolarEdge Modbus to SolarEdge Live. SolarEdge Live represents the QuickApp in a better way. Of course the Modbus is still used as protocol.
• Added button for 'Inverter' with support for SunSpec model type 101 (single phase), 102 (split phase) or 103 (three phase). 
• Added QuickApp variable inverterType for the model type of your Inverter (101 (single phase), 102 (split phase) or 103 (three phase), default type 101 (single phase). Also see the value of register 40070.)
• Added optimisation with re-use of the already connected Modbus socket. 
• Improved memory usage with more variables as local variable. 
• Changed the maximum retries to a maximum consecutive time no response. 
• Changed the interval to three speeds, Slow, Medium and Fast. With QuickApp variables the speeds setting can be made for the interval and child updates. 
• Added an indicator (*) to most of the buttons to show what selection is active. 
• Added 'Disconnect' (or 're-connect') button to manually disconnect the QuickApp and Modbus. 
• Added extra check for the amount of addresses (including the extra scale factor addresses) not to exceed 125 (Modbus spec: max 125 registers per request). 
• Added extra check for the addresses being in the 40001-49999 range. 
• Changed the register table to indexed, so the addresses (and scale factors) can be selected directly and fast from the table. 
• Removed a double warning for CONNECT issue. 
• Added in case of a device type 'com.fibaro.energyMeter' the property 'storeEnergyData = false' is added to the setup of that child device. By default the energyMeter won't save energy to the energy database.  
• Added in case of a device type 'com.fibaro.powerMeter' the property 'includeInEnergyPanel = false' is added to the setup of that child device. By default the powerMeter won't be used for instantaneous power in Energy Panel calculations.  
• Added the current time to the log text of the main device. 
• Added the register address to the log text of all the child devices. The log text was empty. This will help to get more acquainted with the register addresses. 
• Placed the register address in front of the label text to make it more readable. 
• Improved the message of the retry warnings, show seconds to maxResponseTime. 
• Improved some register description text. 
• Rounded all the values to two decimal places. 

 

Changes version 1.0  (27th July 2025)

• Initial version with child devices to configure in QuickApp variables. 

 

Variables (mandatory and created automatically): 

• host = Modbus TCP IP address of your target device (default 192.168.1.145)
• port = Modbus TCP port (default 1502)
• unitId = Modbus slave/unit address (default 1)
• inverterType = Type of your Inverter (101, 102 or 103, default type 101. Also see the value of register 40070.)
• intervalS = How fast the Modbus will refresh the data (Slow default 60 seconds) 
• intervalM = How fast the Modbus will refresh the data (Medium default 10 seconds) 
• intervalF = How fast the Modbus will refresh the data (default 5 seconds) 
• intervalChildsS = How fast the Childs will update (Slow default 60 seconds)
• intervalChildsM = How fast the Childs will update (Medium default 10 seconds) 
• intervalChildsF = How fast the Childs will update (default 5 seconds) 
• maxResponseTime = Maximum time in seconds for response of the Modbus to disconnect (default = 60)
• debugLevel = Number (1=some, 2=few, 3=all) (default 1)
• Also with the QuickApp variables child devices can be created. Insert a QuickApp variabel with the address as 'variable' and the deviceType as 'value'. By default the values from the childs will show in the labels (except Scalefactor values). You can use all kinds of devicesTypes, for example: 
• com.fibaro.energyMeter (Wh) (by default no storage to energy database)
• com.fibaro.powerMeter (Watt) (by default not used for instantaneous power in Energy Panel calculations)
• com.fibaro.electricMeter (Volt and Ampere)
• com.fibaro.multilevelSensor (Number values)
• com.fibaro.temperatureSensor (Temperature)

Please login or register to see this link.

Download the QuickApp here:

Please login or register to see this attachment.

 

or from the Fibaro Marketplace: 

Please login or register to see this link.

 

How to install:

• Open the Configuration Interface
• Go to Settings > Devices
• Click  +
• Choose Other Device
• Choose Upload File
• Choose file from your computer with .fqax

(This download contains several example register addresses, but you can choose you own register addresses to create your child devices) 

 

 

 

 

 

 

• Can you explain inverter type
• inverterType = Type of your Inverter (101, 102 or 103, default type 101. Also see the value of register 40070.)

[SmartHomeEddy 1,005]

25 minutes ago, reso007 said:

• Can you explain inverter type
• inverterType = Type of your Inverter (101, 102 or 103, default type 101. Also see the value of register 40070.)

If you want to learn more, please have a look at the technical note from SolarEdge: 
 

Please login or register to see this link.

 

The inverter type stands for: 

101 = single phase

102 = split phase

103 = three phase
 

 

[reso007 0]

10 minutes ago, SmartHomeEddy said:

If you want to learn more, please have a look at the technical note from SolarEdge: 
 

Please login or register to see this link.

 

The inverter type stands for: 

101 = single phase

102 = split phase

103 = three phase
 

 

thx

 

[SmartHomeEddy 1,005]

@reso007 Your welcome. Have fun with the quickapp. So the quickapp already has the most wanted modbus registers, but you could add others. 

[reso007 0]

 

 

Hi 

 

I added variables for amp meter on phase B and C.

I can see data on preview, but not on dashboard.

 

THX

Please login or register to see this attachment.

Please login or register to see this attachment.

[SmartHomeEddy 1,005]

I presume you did save the variable, because you can see the values in the labels?

 

Could the child be created in another room, like the default room?

 

The child is created in my setup. 

 

Please login or register to see this attachment.

[reso007 0]

19 hours ago, reso007 said:

thx

 

 

46 minutes ago, SmartHomeEddy said:

I presume you did save the variable, because you can see the values in the labels?

 

Could the child be created in another room, like the default room?

 

The child is created in my setup. 

 

Please login or register to see this attachment.

There are no childs created. Also checked in default room.

Please login or register to see this attachment.

Please login or register to see this attachment.

[SmartHomeEddy 1,005]

Maybe check for spaces in front of the child device type (com.fibaro.electricMeter) in the quickapp variable. 

 

Try to restart the quickapp (by disable and enable the quickapp). 

 

Maybe you first added the quickapp variable with a wrong content and changed it later?

Delete the two quickapp variables and SAVE. 

And add them again. 

 

Otherwise I wouldn't know. Tested it extensively and the creation of the childs isn't rocketscience with the framework from jgab.