(05.07.2017, 12:38)admin Wrote: @rocfusion, there's virtually zero performance difference between built-in and a wrapper function. I don't want to change how check* functions work as your case is not so common.

@managementboy, thanks, we'll have a look.

(25.07.2017, 13:32)admin Wrote: Probably RC4 will be marked as final for now, next version is coming in 2-3 months with some minor changes and bugfixes.

(24.07.2017, 06:16)admin Wrote: event.getvalue() now returns the actual event value, not the current object value. Event value is not defined for read requests. For now you can use grp.getvalue(event.dst) instead, but for backward compatibility we will change is so it returns current object value for read requests.

check* will be kept unchanged for now.

(19.08.2017, 14:15)admin Wrote: The version should be 20170620 or similar. It's possible that SD card became read-only. You can try replacing it with a new one, there are recovery instructions on our website in firmware page.

(22.08.2017, 21:41)Arlequin Wrote:

(19.08.2017, 14:15)admin Wrote: The version should be 20170620 or similar. It's possible that SD card became read-only. You can try replacing it with a new one, there are recovery instructions on our website in firmware page.

This was indeed the case., thank you for your support. It also explains why some modifications were lost following a power failure
This is really an issue that this kind of failure is not notified in any way to the user or administrator. Is there any function that would allow a custom script to be written in order to notify when this state occurs ? I find it happened quite fast by the way, after less than 2 years of operation, with a very light usage: low number of objets, trends...

Is there anyway to take benefit of the entire storage size of the replacement SD card ? In my case I had no 8GB card so I used a 32GB one instead... This could be useful for more precise trends during a longer time.

Finally, I think you should make the SD card accessible from the outside of the device, without having to open the case, because it can be quite tedious when almost all the wires are connected... In my case, it's a LM4, I have no idea if it has changed on newer devices...

(22.09.2017, 05:24)phongvucba Wrote: Please help me !
I use LM3 reactor, I use 2017/6/1 version, but send mail is faulty. I still use that code with version 2016/4/24 still works error.
Does anyone have mail sending errors?
-------------------------
------------------- send an e-mail-----------------------------------------
function mail(to, subject, message)
 -- make sure these settings are correct
 local settings = {
   -- "from" field, only e-mail must be specified here
   from = 'abcdxyz@gmail.com',
   -- smtp username
   user = 'abcdxyz@gmail.com',
   -- smtp password
   password = 'password',
   -- smtp server
   server = 'smtp.gmail.com',
   -- smtp server port
   port = 465,
   -- enable ssl, required for gmail smtp
   secure = 'sslv23',
 }

 local smtp = require('socket.smtp')
 local escape = function(v)
   return '<' .. tostring(v) .. '>'
 end

 -- message headers and body
 settings.source = smtp.message({
   headers = {
     to = escape(to),
     subject = subject,
   },
   body = message
 })

-- fixup from field
 settings.from = escape(settings.from)
 settings.rcpt = { escape(to) }

 return smtp.send(settings)
end
-------------------------------