grp.checkwrite / grp.checkupdate - Printable Version +- Logic Machine Forum (https://forum.logicmachine.net) +-- Forum: LogicMachine eco-system (https://forum.logicmachine.net/forumdisplay.php?fid=1) +--- Forum: Scripting (https://forum.logicmachine.net/forumdisplay.php?fid=8) +--- Thread: grp.checkwrite / grp.checkupdate (/showthread.php?tid=4472) |
grp.checkwrite / grp.checkupdate - Dré - 30.12.2022 I had the idea grp.checkwrite / grp.checkupdate don't work always. Are there limitation about when I can use it and when not? Maybe not all datatype? It looks like it doesn't always update the new value or do I look wrong? I understand grp.checkwrite is when it has to write to the KNX bus and grp.checkupdate if it is just local for the LM. RE: grp.checkwrite / grp.checkupdate - Daniel - 30.12.2022 grp.checkwrite is sending to TP and IP but on change of value. grp.checkupdate is sending only to IP but also on change of value. RE: grp.checkwrite / grp.checkupdate - Dré - 30.12.2022 Oké thanks. I think my problem was also not the right data type. RE: grp.checkwrite / grp.checkupdate - sx3 - 02.01.2023 and grp.write always send the value on TP and IP, even if the value inside LM is up to date? RE: grp.checkwrite / grp.checkupdate - admin - 02.01.2023 (02.01.2023, 11:39)sx3 Wrote: and grp.write always send the value on TP and IP, even if the value inside LM is up to date? Yes RE: grp.checkwrite / grp.checkupdate - Dré - 02.01.2023 No I remember what was going on, on my site; This is my line in my log this is what the current logs said about the value Code: P1 HomeWizzard [new and updated] 02.01.2023 12:57:03 this is a part of the script I use Code: --Reading electricity delivered by client (Tariff 2) in 0,001 kWh 14.4 byte My question is, is there a reason why he doesn't update the value? It looks like they are not the same, behind the dot. RE: grp.checkwrite / grp.checkupdate - admin - 02.01.2023 For floating point values default delta is 0.1. The difference between values is lower in your case. RE: grp.checkwrite / grp.checkupdate - Dré - 02.01.2023 Oké thanks, does it means I need to take another data type for solving this problem? RE: grp.checkwrite / grp.checkupdate - admin - 02.01.2023 The value will update when the difference is large enough. You can also specify delta manually as the third argument. Try 0.01 or 0.001 RE: grp.checkwrite / grp.checkupdate - Dré - 02.01.2023 Sounds interesting, do you have an example of this? RE: grp.checkwrite / grp.checkupdate - admin - 02.01.2023 Code: grp.checkupdate('51/0/10', returned_tarrif2, 0.01) RE: grp.checkwrite / grp.checkupdate - Dré - 02.01.2023 Great tanks, that was what I was looking for ? RE: grp.checkwrite / grp.checkupdate - 2MAX - 29.07.2024 Hi, where is error i my checkwrite, because if status objekt ChlazeniSGN (bool) is diference from 11/1/13, there is no write to bus Code: Antizamrz=grp.getvalue("11/1/120") RE: grp.checkwrite / grp.checkupdate - admin - 29.07.2024 Status object must be passed as the 4th argument. You need to pass status group address not value: Code: value = not Antizamrz and INtemp > 21.5 and VZT and Outtemp > 20 Some notes on your script: 1. Passing datatype to grp.getvalue() is not needed in most cases. 2. INtemp is converted to integer via math.ceil but then compared with a floating point value (21.5). You can either remove math.ceil or compare with an integer value (INtemp >= 22) 3. Instead of comparing with true/false you can simply use if Porucha1 and Porucha2 then 4. Generally it is recommended to use all lowercase variable names as mixed case can lead to errors due to typos because variables in Lua are case-sensitive. |