Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


Question

Posted

Hi

Anyone by chance have some closer info about a quickapp's internal storage? What is it for, how to use it? And some pro/contra against quickapp variables?
I see internal storage usage in some of @jgab 's quickapps but i could not find it.

6 answers to this question

Recommended Posts

  • 0
Posted

Well, I mostly use them because they are not cluttering up the quickAppVariables view for data that I want to persist between QA restarts.
They are also not saved with the QA as quickAppVars are.
That's the reason I use them.

As for efficiency and amount of data that can be stored I haven't tested - but in general, be careful about all types of resources on the HC3...

  • Like 1
  • Thanks 1
  • 0
Posted

Same as @jgab, using them to reduce number of needed quick app variables and that last data is available during the quick app restart process.

As for data type, I use them to store tables, strings and numbers and amount of stored data is always reduced to a minimum needed so don't know for any limits.

  • 0
  • Inquirer
  • Posted
    On 3/13/2026 at 12:01 AM, Sankotronic said:

    Same as @jgab, using them to reduce number of needed quick app variables and that last data is available during the quick app restart process.

    As for data type, I use them to store tables, strings and numbers and amount of stored data is always reduced to a minimum needed so don't know for any limits.

    Ohh, so i misunderstood something..Jgab said, it doesnt survive QA restart. Does it then? Becuase i would rather store table in internal storage too, if it survive QA restarts.

    • 0
    Posted

    No, I didn’t say that - I said the opposite.

    • 0
  • Inquirer
  • Posted
    7 minutes ago, jgab said:

    No, I didn’t say that - I said the opposite.

    I deducted this from this part of your answer.."They are also not saved with the QA as quickAppVars are."
    my bad, i misunderstood it

    Any help for the syntax? How to save them, how to read them?
    Would be verry helpful

    • 0
    Posted (edited)

    It's
    QuickApp:internalStorageGet(key)

    QuickApp:internalStorageSet(key, value)

    QuickApp:internalStorageRemove(key)

    ...and some tricks how to retrieve all keys and hide them...

    You can create a metatable in self.store and use that for your persistent values like this:
     

    Please login or register to see this code.

     

    Edited by jgab
    Fixed pairs function for metatable
    • Like 1
    • Thanks 1

    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Answer this question...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×
    ×
    • Create New...