OO programming with dzEvents

[garethhowell]

I’m working up a design for a “better” central heating controller for Domoticz. (Please don’t flame because you think somebody has already been there).
Coming from an OO background, I am thinking in terms of objects for thermostats, boiler controls, timers, timer plans etc. However, the challenge is persisting their values over the event/timer-driven approach adopted by Domoticz/dzEvents et al.
Has anybody successfully used the global storage capabilities of dzEvents to persist complex table variables?

[dannybloe]

You can persist table data with dzVents. Nothing is preventing you from doing this. The only thing is that functions are not persisted and removed from the table.

[garethhowell]

The only thing is that functions are not persisted and removed from the table.

Thanks. Any suggestions on how to get around this?

[waaren]

The only thing is that functions are not persisted and removed from the table.

Thanks. Any suggestions on how to get around this?

Yes, load your functions from a file like

Code: Select all

    local function getFunctions()
        fn = require("commonFunctions")
    end

    if pcall(getFunctions) then
        dz.log("getFunctions loaded",dz.LOG_DEBUG)
    end	        

I used this here. Although nothing to do with OO it might just prove to be useful for your requirements.

[garethhowell]

Thanks

[dannybloe]

Well, we are dealing with plain Lua and Lua offers way to create objects. What you should do is pass the persisted data to the constructor of you object and then initialise all the internal data of the object. All this is not dzVents related. I suggest to read the Lua documentation and how to require modules in your code.

Actually, dzVents object model does exactly that. I receives a Lua table from Domoticz and passes that along to the proper object constructors.