When I was looking for information about the mesh diagram I found conclusions that looks not right to me. This is my simple diagram https://i.imgur.com/oFMvWOI.png Node 24 is no Fibaro wall plug When we going from node 1 the controller to node 7 and further we see this: 1 blob node colour - bands in ...

Version: V4.10717 b386b49e5 Platform: Windows 10 RFXtrs433E Version: Ext2/1025 Z-Stick Gen 5 Version: 1.4.3244.gbb874f6a.dirty Fibaro Wall Plug 9x NodOn remote wall switch My number of Fibaro Wall Plug's is rising so there data dumping too. That is very annoying when you are looking for data of ...

The differences was this morning again 2 minutes by sunrise but that can be change.
By combination you can't account for this

Tests in the afternoon where OK . It working in shadow mode and if there are no problems tomorrow then it can take over the job. return { on = { devices = { Dev = "Lichtsensor " .. "Binnen" }, }, execute = function(domoticz, Dev ) local Doel = domoticz.devices('Kamer Schoorsteen Links') -- nog ...

Flowing your advice I looked up by Lua and found this and it's working. :D 3.4 – Concatenation Lua denotes the string concatenation operator by ".." (two dots). If any of its operands is a number, Lua converts that number to a string. print("Hello " .. "World") --> Hello World print(0 .. 1) --> 01 r ...

I am sorry to be the messenger of bad news but your solution will not do the job. Lua does not understand the idx = 25 the way you expect and will not trigger the script if device 25 changes state. If you want that to happen you will have to change that part to But ... Writing scripts devices ...

In the back of my head I know the risk that a name of a device could have. Misspelling is easy to make. This is my solution: return { on = { devices = { idx = 25 }, }, execute = function(domoticz, idx ) local ksr = domoticz.devices('Kamer Schoorsteen Rechts') if (idx.state == 'Off') then ksr ...

 
Lichtsensor Binnen is a normal switch with on/off. (KaKu/COCO type.)

What is then difference between 'Living' and 'Lichtsensor Binnen' the space.
How do we overcome this.

Nope. ;) 2019-10-07 19:07:00.187 Status: dzVents: Error (2.4.19): error loading module 'Lichtsensor binnen' from file 'C:\Program Files (x86)\Domoticz\scripts\dzVents\generated_scripts/Lichtsensor binnen.lua': 2019-10-07 19:07:00.187 ...scripts\dzVents\generated_scripts/Lichtsensor binnen.lua:7 ...

Again is taking an example from the video not working. 16:56 The difference's is the name of the device in the way that I have a space in that name. Also I have skipped the log part. return { on = { devices = { 'Lichtsensor Binnen' }, }, execute = function(domoticz, 'Lichtsensor Binnen') <-- error ...

 

Every problem solved.

In the https://www.domoticz.com/wiki/DzVents:_next_generation_LUA_scripting there are giving a lot of examples like: 'between aa and bb' -- aa/bb can be a time stamp like 15:44 -- aa/bb can be sunrise/sunset -- aa/bb can be 'xx minutes before/after sunrise/sunset ...

Resume. My problem is solved. 1) It was a group and it had to be put this way in 't script: domoticz.groups('Tuin Lantaarns').switchOn() 2) To be sure of the right spelling of the name I copied from the Devices list. Sadly we bumped to an other problem. The 'at dd/mm between hh:mm and hh:mm' rule ...

@waaren Why can Blockly events works on daily base with "Tuin Lantaarns" The I will try it on a device in the room. return { on = { timer = { 'at 6/10 between 15:42 and 15:43' }, }, execute = function(domoticz, dummy) domoticz.devices('Kamer Midden').switchOn() end } The device was switchOn but NOT ...

Looking further myself. Confusion: https://i.imgur.com/PLHuwJi.png Scene https://i.imgur.com/q52VP9G.png Group Result https://i.imgur.com/SLQJr7o.png 2019-10-06 15:20:00.400 Status: dzVents: Info: ------ Start internal script: 4 mei:, trigger: at 6/10 between 15:20 and 15:21 2019-10-06 15:20:00.401 ...

On this rainy Sunday a good moment for testing my first very little dzVents script. That was disappointing. Taken from the video 26:18: https://i.imgur.com/k2kwQDC.png Make this changes: https://i.imgur.com/fhzaMBZ.png But get this error: 2019-10-06 14:32:00.529 Status: dzVents: Info: ------ Start ...

Switching from my 433 MHz system to Z-wave I shall miss my wall-switches for a long while, I think. Try one to associated but I have it sending back. Sort this out later. To use Blockly to connect a 443Mhz switch with a Z-wave wall plug I try this. https://i.imgur.com/TW1Syqt.png The + is the Z ...

 
It is thus NOT Z-wave related.

Therefore I shall start a new tread.

Working till midnight to looked at this problem. New set timer rules sometimes worked mostly not. The old ones still do. Even on non Z-wave devices have this problem. Trying this morning on a KaKu/COCO device an most new timer rules are not executed. The only thing what I can still do is again ...

The post where I conclude that the timers where working have I deleted. After the successful weekend test I placed the wall plugs on there places. There was only 1 that reacted on the timer but only that time. In the search of the problem I hit a wrong link in the Node management so I decided to ...