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


  • 0

Has something changed in QAs recently?


Question

Posted

I'm getting the following error:

timer handler failed with error: no static 'properties' in class 'QuickApp'

Please login or register to see this code.

The onInit code runs fine the first time around but not when scheduled. The Message "getDeviceHistory function is scheduled to run now." prints out okay.

3 answers to this question

Recommended Posts

  • 0
Posted
43 minutes ago, zedmeister said:

I'm getting the following error:

timer handler failed with error: no static 'properties' in class 'QuickApp'

Please login or register to see this code.

The onInit code runs fine the first time around but not when scheduled. The Message "getDeviceHistory function is scheduled to run now." prints out okay.

This is an error

Please login or register to see this code.

you are calling :onInit on the class QuickApp - when that happens, inside :onInit() the self points to the class, not the object that have been instantiated from the class.

I don't know the context of your code, is all of it inside QuickApp:onInit() ? or does it live somewhere else?
Theoretically, if the code you quote is inside an QuickApp function you could do

Please login or register to see this code.

....however it's generally a bad idea to call :onInit() repeatedly. Instead do the initializations there and call some other function to do the work (looping)

Lastly, don't mix setTimeout and sleep in the same code. In general it's bad to use sleep in a QA as everything stop while it sleeps (buttons, UI updates etc)

  • Like 2
  • 0
  • Inquirer
  • Posted

    Thanks for your help. I am more familiar with Python than LUA. What do you suggest is the correct way for scheduling a function to run at say 2am every day, inside a QA?

    • 0
    Posted

    A generalized loop function that takes a start time and an interval , without drifting, looks like
     

    Please login or register to see this code.

     

    • Like 2

    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...