Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Switch off Device after Delay
#1
Hello and first of all scuse me for my bad english.

This is the fact:
In my home i am using Homeseer, X10 and Comfort.
I unfortunately have seen Homeseer Comfort plugin id really really unreliable, so, i am trying to convert all the \'Homeseer events\' in \'Comfort events\'.
.....well, i have to tell Homeseer is very \'user-friendly\'..... Comfort is a little bit more difficult, so i hope i can have some help....


The first \'step\' i am trying to do is this:

I have a rain-sensor connected to zone17. When it is raining, the sensor is closed.
When it is a little raining, often the sensor goes on and off.
I need to find a way to tell:

- when it becomes raining, send X10 H7 On
- when rain contact HAS BEEN OPENED FOR 40 MINUTES consecutiveness without  \'close\', send X10 H7 Off

Can someone suggest me some reliable solution?

Thank you

Ema from Italy



#2
This is done quite easily in Comfort with Timers which is a very powerful tool once you know how to use it

Zone 17 is programmed as Zone Type Switch Normally Open

The Zone ON Response is
RainSensorOn:
  Do X10H7On
  Stop Timer RainTimer ! stop Rain timer

Zone Off Response is
Do X10H7Off After 2400 Seconds Using RainTimer ! X10 H7 Off after 40 minutes

How it works is;
When the Rain sensor goes on. the X10 H7 is turned on and the Rain Timer is stopped

When the Rain Sensor goes off, the Rain  timer is started for 40 minutes which will turn off X10 H7.
If the Rain sensors turns on again, X10 H7 On signal is sent again (which is no change) but the Rain Timer is stopped so the timer will not count down until the rain sensor is off

Hence the X10H7 goes off only when Rain sensor is off for 40 minutes

This is a good example of how to use the new Scenarios feature in Comfigurator  3.2.7, still in Beta at the moment http://www.comfortforums.com/view_topic.php?id=2161&forum_id=20

A scenario is a set of events and  Responses which implement something like what you require. A Scenario has been created which is attached as  RainsensorX10.crsx file. Do File > Import Scenario and select the .crsx file. This will import the zone, Responses, and Timer into your program. It will ask for the zone number to be assigned to the imported zone








Attached Files
.crsx   RainsensorX10.crsx (Size: 3.06 KB / Downloads: 1)
#3
Ok, but i don\'t want to send an \'X10 H7 On\' everytime the zone17 turns on again, because when it is raining a little, this turns on and off very often and this means much traffic on powerline.
I need only one \'on\' command when the zone turns on the first time and an \'off\' command when it was \'off\' for 40 minutes.
Do you think it can be done?
#4
This can be done by extending our logic

The Zone On Response is changed to
RainSensorOn
If Timer RainTimer <> 0 Then
    Stop Timer RainTimer ! stop Rain timer
Else
    Do X10H7On
End If

Hence if the timer is running, stop the timer so the X10 does not get switched off while the rain sensor detects rain

if the timer is OFF, that means the X10 Off signal has been sent, so the X10 can be switched on

The modified Scenario file is attached


Attached Files
.crsx   RainsensorX10.crsx (Size: 3.2 KB / Downloads: 2)
#5
[user=1]slychiu[/user] wrote:
Quote:This can be done by extending our logic

The Zone On Response is changed to
RainSensorOn
If Timer RainTimer <> 0 Then
    Stop Timer RainTimer ! stop Rain timer
Else
    Do X10H7On
End If

Hence if the timer is running, stop the timer so the X10 does not get switched off while the rain sensor detects rain

if the timer is OFF, that means the X10 Off signal has been sent, so the X10 can be switched on

The modified Scenario file is attached
Sure, great idea! I will try it as soon as possible, many thanks!


Forum Jump:


Users browsing this thread: 1 Guest(s)