(29.10.2018, 16:56)buuuudzik Wrote: Could you define what means "not working"? What is current state of your system?

But probably I've found the source of problem Please log in "Object logs" valve status because for 99% you are updating your valve every minute(not only on change) so the timestamp is updated and is still too fresh and is recognized as not fully open.

Looks in logs:
[valvesInSummer]
     * table:
      [1]
       * table:
        [value]
         * bool: true
        [firstTimestamp]
         * number: 1540829552
        [name]
         * string: T7 FB Heating floor attic valve
        [opened]
         * bool: true

[valvesInSummer]
     * table:
      [1]
       * table:
        [value]
         * bool: true
        [firstTimestamp]
         * number: 1540829612
        [name]
         * string: T7 FB Heating floor attic valve
        [opened]
         * bool: true

[valvesInSummer]
     * table:
      [1]
       * table:
        [value]
         * bool: true
        [firstTimestamp]
         * number: 1540829672
        [name]
         * string: T7 FB Heating floor attic valve
        [opened]
         * bool: true

Everytime script runs there is different firstTimestamp which is equal to updatetime of valve with alias 'T7 FB Heating floor attic valve'. So the status of this valve is updated every minute. But this is not by this script because this script only controls the pump based on valve statuses.


I think you are upodating state of valve every minute. Please log

(29.10.2018, 20:33)buuuudzik Wrote: No, it should be send only on change.

For monitoring of the device you can use heartbeat object or something similar. If you don't want change this repetition then you must create new object(could be virtual) and valve status must update its  value by grp.checkupdate() method, but there is no reason and if you are working in automation then you must learn how to right use devices and then trust them Especially if it is about LM

(29.10.2018, 21:44)buuuudzik Wrote: You're welcome

(30.10.2018, 15:13)buuuudzik Wrote: You've probably confused threads, but ok

I very like JS. This is very modern, fast(fast among script languages) and expressive language with a lot of staff which Lua doesn't have.

I mean:
nice, fast, chainable array methods, and a few characters shortcuts (arrow functions)

Code:

// Javascript
const users = [{id: 1, balance: 100}, {id: 2, balance: 30}, {id: 3, balance: 80}]
users.find(u => u.id == 2).balance += 20;

-- Lua
users = {{id = 1, balance = 100}, {id = 2, balance = 30}, {id = 3, balance = 80}}
for i,u in ipairs(users) do
  if u.id == 2 then users[i].balance = users[i].balance + 20 end
end

Maybe this is stupid example but I like this array methods in JS and also that array are passed by reference.
Creating objects is also very easy (also without classes).

Another advantage of JS is its community and thousands of libraries.

But unfortunately LuaJIT is faster so JS could be(but now it is not possible) only used via NODEJS only as a support for this main technology on server.

But on client you have now JS and you can use it. And when you generate something via .lp file you can via Lua prepare raw data and in JS do most of work.

But also without JS on server I will like LM because this is very, very nice device for creating powerful logic in a lot of powerful ways