How does this: DeviceID = {10, 12, 24} work?

[Guest jschun]

Does anybody have a short and sweet example how to use the {xx, xx, xx} in LUA?

I want to arm multiple DoorSensors, but I don't want to do it like:

Please login or register to see this code.

But I want to do it like:

Please login or register to see this code.

But I do not know the exact syntax to get all three sensors to be armed

Please login or register to see this image.

/emoticons/default_sad.png" alt=":(" srcset="https://forum.fibaro.com/uploads/emoticons/[email protected] 2x" width="20" height="20" />

Can anyone help please?

Thanks!!

[Krikroff 199]

jschun,

DoorSensorID[1] give you the first value in the table... [2] the second ...

Regards

[Guest jschun]

Thank you for your quick and clear response Krikroff!

[robmac 173]

two loops possible i is index v is value in table element

Please login or register to see this code.

Please login or register to see this code.

[Guest jschun]

Thanks RobMac! I used the first example in my scripts and it works like a charm! ッ

I'm not quite sure what to do with the index / value example though. Can you explain a bit more on that?

Thanks in advance ッ

[robmac 173]

Thanks RobMac! I used the first example in my scripts and it works like a charm! ッ

I'm not quite sure what to do with the index / value example though. Can you explain a bit more on that?

Thanks in advance ッ

The enumerator is just a nice way to get the integer index and the table value in variables to use within a loop rather than creating a counter.

Also you can index with a string and that is nice as you can use notify function with the device name or just debug without having to look up the device... notice pairs not ipairs when you use string index

as you can store tables in tables the second part of the code is possible and then you have room and device.

you could of course get the strings from calls to functions in the first place in the table declaration rather then using strings like "Drawing" (if fibaro API had function)

Please login or register to see this code.

you can also store actual functions in tables so lots of uses but I will leave that for another post

[richo 4]

robmac,

Thanks a lot for your programming tips in LUA. I like the following piece, however wonder why the results are in such a strange sequence?

local devices = { ["main"] = 184,

                  ["side"] = 185,

                  ["other"] = 186 }

for i,v in pairs(devices ) do

 

          fibaro:debug(i)

          fibaro:debug(v)

 end

results:

Please login or register to see this code.

[Krikroff 199]

richo, pairs(table) allow iteration but the order that items are returned is not defined. You must use ipairs, with ipairs(table) the order in which elements are returned is guaranteed to be in the numeric order of the indices, but non-integer keys are simply skipped (your example certainly does not work).

if robmac wants complete

Please login or register to see this image.

/emoticons/default_icon_biggrin.gif" alt=":-D" /> (thank to him for his good advice)

[robmac 173]

from the luascheduler... see the table.sort that makes sure that the catchup events are played in the correct sequence by time

Please login or register to see this code.