Domoticz version: v3.5877
I'm having strange behaviour from the Eventsystem. After working fine for several weeks, suddenly (out of the blue) the EvenSystem starts triggering one specific event at 00:00 and keeps doing this every minute:
OpenZWave: Domoticz has send a Switch command!, Level: 0, NodeID: 2 (0x02)
In this case it's my Fibaro Roller Shutter2. Every minute it's become triggered to open. And will not stop, until I de-activate the blocky event.
I've attached the blocky event. What it does is looking at the day of week and time, opens the shutter and send a notification to Telegram.
I cannot figure out, why this events suddenly starts doing this after working fine for several weeks. Other events (2 more) are working fine and do not have this behavioure.
Eventsystem starts at 00:00 and execute event every minute
Moderators: leecollings, remb0
- htilburgs
- Posts: 464
- Joined: Tuesday 03 November 2015 11:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Eventsystem starts at 00:00 and execute event every minute
Hardware:
RPi3 - Aeon Labs Z-Stick GEN5 - Fibaro Dimmer 2 - Fibaro Roller Shutter 2 - Fibaro Smoke Sensor - Yeelight RGBW Led bulb - Yeelight Smart LED Light Strip - Neo Coolcam PIR Motion Sensor - Neo Coolcam PowerPlug - Nest Thermostat v3
RPi3 - Aeon Labs Z-Stick GEN5 - Fibaro Dimmer 2 - Fibaro Roller Shutter 2 - Fibaro Smoke Sensor - Yeelight RGBW Led bulb - Yeelight Smart LED Light Strip - Neo Coolcam PIR Motion Sensor - Neo Coolcam PowerPlug - Nest Thermostat v3
- jvdz
- Posts: 2445
- Joined: Tuesday 30 December 2014 19:25
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 4.107
- Location: Netherlands
- Contact:
Re: Eventsystem starts at 00:00 and execute event every minute
I am not a fan of Blockly and always use LUA scripts for logic, but guess that the AND relation in the second test is connected to Sunday only.
So the test ends up being:
If Saturday then do this
or if Sunday and 7:45 then also do this
Jos
So the test ends up being:
If Saturday then do this
or if Sunday and 7:45 then also do this
Jos
- htilburgs
- Posts: 464
- Joined: Tuesday 03 November 2015 11:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: Eventsystem starts at 00:00 and execute event every minute
Ok, sounds logic, because it started at 00:00 (change from friday to saterday). I've changed it to:
You say that you always use LUA scripts for logic.
I've never worked with LUA. Do you have an example for me (for example this situation), so I can take a look at LUA if this is an option for me?
You say that you always use LUA scripts for logic.
I've never worked with LUA. Do you have an example for me (for example this situation), so I can take a look at LUA if this is an option for me?
Hardware:
RPi3 - Aeon Labs Z-Stick GEN5 - Fibaro Dimmer 2 - Fibaro Roller Shutter 2 - Fibaro Smoke Sensor - Yeelight RGBW Led bulb - Yeelight Smart LED Light Strip - Neo Coolcam PIR Motion Sensor - Neo Coolcam PowerPlug - Nest Thermostat v3
RPi3 - Aeon Labs Z-Stick GEN5 - Fibaro Dimmer 2 - Fibaro Roller Shutter 2 - Fibaro Smoke Sensor - Yeelight RGBW Led bulb - Yeelight Smart LED Light Strip - Neo Coolcam PIR Motion Sensor - Neo Coolcam PowerPlug - Nest Thermostat v3
- Domosapiens
- Posts: 232
- Joined: Wednesday 20 August 2014 12:08
- Target OS: Windows
- Domoticz version: V3.5981
- Location: NL
- Contact:
Re: Eventsystem starts at 00:00 and execute event every minute
No need for LUA.
Blockly is great and can even be maintained by my children.
(one day you pass away and then they have to!)
Maintenance is underestimated by most of the board members.
Blockly:
- at 00:00 the Event system is reset (I think a recent change, not seen it before)
- If all conditions are met, Blockly will start over and over (that's what you see also)
- Choose Blockly and below that Device (right side of the Event editor)
- build balance in your Blockly: start with a top AND and add left and right additional AND's
- add the current condition of your screens to the AND structure
- in case of Time: use > instead of = for robust programming
I think something like this will work:
Look at the ((..)..(..)) pairs for balance
Success
Blockly is great and can even be maintained by my children.
(one day you pass away and then they have to!)
Maintenance is underestimated by most of the board members.
Blockly:
- at 00:00 the Event system is reset (I think a recent change, not seen it before)
- If all conditions are met, Blockly will start over and over (that's what you see also)
- Choose Blockly and below that Device (right side of the Event editor)
- build balance in your Blockly: start with a top AND and add left and right additional AND's
- add the current condition of your screens to the AND structure
- in case of Time: use > instead of = for robust programming
I think something like this will work:
Code: Select all
IF ((NOT Saturday AND NOT Sunday) AND (Time > 07:45 AND Rolluik NOT Level 0%))
DO
Set Rolluik = Level 0%
Else IF ....Success
Win Vista&7; 1#Aeon Z-Stick S2; 1#Aeotec Z-Sick Gen5, 6#Fib.FGBS001; 24#DS18B20; 8#Everspr.AN158-2; 3#Philio PAN04; 1#Philio PAN06, 1#YouLess El; 1#Fib.FGWPE; 1#ZME_RC2; 2#FAK_ZWS230, 2#Quib.ZMNHCDx, 1#Quib.ZMNHDD1, 7#EM6555
-
tozzke
- Posts: 135
- Joined: Friday 02 January 2015 9:22
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Stable
- Location: Netherlands
- Contact:
Re: Eventsystem starts at 00:00 and execute event every minute

should do the trick (if your 'Rolluik' is actually set with 'level (%)' and not just On/Off)
Although this will trigger every second of 7:45 (so 7:45:00. 7:45:01, 7:45:02 etc).
This could be prevented by adding a variable so you'll get something like this:

- htilburgs
- Posts: 464
- Joined: Tuesday 03 November 2015 11:01
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: Eventsystem starts at 00:00 and execute event every minute
My Shutter "Rolluik" is using %. At evening (Time=Sunset) I set the level to 100%
At morning it should completely open, that's why I set the level to 0%. This works even if the level is >0% and <100% (I have children....
)
But using a user-variable is also good thinking. Thanks for all the help.
Problem is solved, but executing can be on different ways.
Playtime for the next couples of days
and trying different methods!
At morning it should completely open, that's why I set the level to 0%. This works even if the level is >0% and <100% (I have children....
But using a user-variable is also good thinking. Thanks for all the help.
Problem is solved, but executing can be on different ways.
Playtime for the next couples of days
Hardware:
RPi3 - Aeon Labs Z-Stick GEN5 - Fibaro Dimmer 2 - Fibaro Roller Shutter 2 - Fibaro Smoke Sensor - Yeelight RGBW Led bulb - Yeelight Smart LED Light Strip - Neo Coolcam PIR Motion Sensor - Neo Coolcam PowerPlug - Nest Thermostat v3
RPi3 - Aeon Labs Z-Stick GEN5 - Fibaro Dimmer 2 - Fibaro Roller Shutter 2 - Fibaro Smoke Sensor - Yeelight RGBW Led bulb - Yeelight Smart LED Light Strip - Neo Coolcam PIR Motion Sensor - Neo Coolcam PowerPlug - Nest Thermostat v3
Who is online
Users browsing this forum: No registered users and 1 guest