LinuxMCE Forums
General => Installation issues => Topic started by: brononius on June 05, 2015, 08:41:53 am
-
Hey,
For several lights, I built in an event that delayed some minutes, and power off the lights. (fe cellar, attick, outside lights triggered by sonar...).
But with version 14.04 / 12.04, it seems that the delay isn't working anymore? I inserted the exact same command as in 8.10, but my lights keep on.
Any idea how/where I could solve this?
-
Delayed events? We have those? ??? I didn't think we actually had those. Provide some more specifics about the event, how you set it up, and your expected/actual behaviour.
Thanks brononius! We haven't changed anything in regards to how events are handled so I'm lost atm.
J.
-
Hey,
What i do fe to let my lights turn on for 3 minutes:
Create an advanced event.
My criteria:
PK_device = Sensor1
PK_EvenParameter = Tripped
State = Light1 = OFF/0
Time of Day = NIGHT
My commands:
command1: Light1 = ON
command2: Light2 = ON
command3: DCEROUTER = delay = 180
command4: Light1 = OFF
command5: Light2 = OFF
My lights come on, so command 1,2 is working, but afterwards, nothing...
-
The delay event is problematic. iirc it stops the whole event engine for that amount of time.
-
The delay event is problematic. iirc it stops the whole event engine for that amount of time.
Does it stops - stops, or holds for the amount of time?
Shouldn't the event 'go on' after the amount of time?
-
The event might continue after the amount of time, but during the delay, no other event is processed. Again, this is how I remember it being in the past. It might be that sambuca has changed stuff in that area.
-
The event might continue after the amount of time, but during the delay, no other event is processed.
I confirm that this worked in 8.10.
But in 14.04, it seems to get stuck somewhere. :-[
-
I haven't intentionally changed anything regarding delayed events.. or rather delayed commands. Because it is the command that is delayed not the event :)
br,
sambuca
-
I can confirm that the delay command is still working in 12.04.
Its being used in my install every day.
I attached a screenshot from one of those events.
br,
Raymond
-
Damned, guess I've got another problem. It seems that some events work, some don't.
Strange thing is that most of the events are rather simple once, and exactly the same. So it's not linked with the eib convertion, or with a 'complex' event. When i check the eib log file, it seems to enters when sensors are pushed. But for some events, it works, for others it don't.
ps RayBe, nice to see that other dutch speaking people are also using LinuxMCE. ;)
-
Not sure why, but this isn't working 100% correctly in my case. :'(
I've noticed in my logs, that the events keeps on being triggered. When I tried to write my own script for this, I've noticed that my bash script also kept on running. After the exit command, it just reopens a new process. So i can image that after pushing a few time the sensor, a lot of process where shutting down my lights.
I've solved this with following script (notice the pkill):
#! /bin/sh
sleep 180
groupswrite ip:127.0.0.1 4/1/11 0
pkill AutoUIT_Kelder
exit
And I run this script with the event 'App Server' and Spawn Application...