Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[peg-leg]

I've created 2 simple garage door macros triggered by a DS10A sensor.  I'm using a false appliance switch set to A3. 

Marcro 1: DS10A triggered, turn on A3, BVC listener anounces "garage door open"

Macro 2: DS10A closed, turns off A3, and BVC anounces, "garage door closed".

First, how do I stop the normal sensor reporting from triggered the garage door closed macro?

Macro 2 also issues an "All lights off" command to solve the issue of my wife leaving lights on when she leaves the house.
So, how do I stop Macro 2 from shutting off all lights while we're at home?  This particular garage door is the one I use when moving my mower in and out of the garage.

Thanks.

[Puck]

Flags

[peg-leg]

I think I can create a flag to handle the All Lights Off issue, but how do I use flags to keep AHP from viewing an automatic report from the sensor as an actual door closing event?

[HA Dave]

Macro 2 also issues an "All lights off" command to solve the issue of my wife leaving lights on when she leaves the house.
So, how do I stop Macro 2 from shutting off all lights while we're at home? 

I've played around a bit with "Occupancy Sensing".

[HA Dave]

how do I use flags to keep AHP from viewing an automatic report from the sensor as an actual door closing event?

OH... the heartbeat issue! About once an hour... the DS10A will report it's status. That report is the same as the actual event. This "feature" can be really cool as an additional notice.... so you don't need worry about any missed events... you'll be reminded of the status again within the hour. However if the action of that event is an ALL OFF.... that could be a real nuisance.

I'd find another "trigger" for the all off... or convert the garage macro to a powerflash.

I am not saying you can't do this with a DS10A... I just can't think of how to. Unless you use an option (maybe from Occupancy Sensing) as a condition within your macro (or as a separate macro).

[peg-leg]

The "heartbeat" report seems to only be giving the "sensor closed" signal, which triggers my Garage Door Closed macro and corresponding listener in BVC.  I'm doing a little test with flags to prevent the false Garage Door Closed signal  from triggering the door closed macro.

I added a flag to my Garage Door open macro, Flag 1.  It goes like this:

Garage DS10a Sensor triggered
Set Flag 1
False module A3 on

Then I edited the Garage Door Closed macro:

Sensor closed,
Clear Flag 1
False module A3 off.

My thought is that the Garage Door closed macro won't run if it doesn't see Flag 1 set.  Of course I could be misunderstanding the way flags work.

[peg-leg]

The above test did not work.  I misunderstood the use of flags.  Here's another try:

I edited Garage Door Open macro above:

Garage Door  DS10A triggered
Set flag 1
Turn on false module A3
Clear flag 1

Garage Door Closed Macro:

Garage Door DS10A closed
Condition: check is Flag 1 is Off or "cleared"
Turn off false module A3
All lights off.

My theory is that since the hourly heartbeat seems to be only issuing a "Closed Sensor" report, The Garage Door Closed macro won't run, because the Garage Door Open macro did not occur and Flag 1 was not set and then cleared.

We'll see what happens this time.

[Puck]

My theory is that since the hourly heartbeat seems to be only issuing a "Closed Sensor" report, ...

The hourly heart beat should be issuing the current state regardless if it is open or closed. If it is only issuing a heart beat when the state is closed, then this is another change to a device by X10 without a part  number change.

Could you please comfirm this is the way it is operating and how long ago did you purchase them?

I have 2 concerns if this is true:

1) X10 is continuously making it more difficult to support the end users when a common knowledge is no long universally applicable.

2) Those that have an established system that relies on these type of functions, can no longer maintain that if a new replacement purchase is required.

Your help in confirming this would be appreciated.

[peg-leg]

Puck,

I don't believe anything has changed.  The heartbeat I see is when the sensor is closed and that's the report coming from the sensor.  I have not tried leaving the sensor open, but I imagine the heartbeat would then be "sensor open".

[peg-leg]

I solved this issue.

Here's the set up.

Garage Door Open Macro
Garage Door Closed Macro
False Flag 1 Macro
Garage False appliance module A3
False appliance module B3 sets Flag 1

Garage Door Open Macro
Turns on A3
Trigger is DS10A open
Clear Flag 1
Delay 45 minutes
Turn on B3

Garage Door Closed Macro
Trigger is DS10A closed
Check is Flag 1 is off/cleared
Turn off A3

False Flag 1 Macro
Trigger is B3 on
Set Flag 1

Garage door open triggers A3 on and BVC anounces garage door open.  Flag 1 is cleared. After 45 minutes B3 is turned on with sets Flag 1.

The Garage Door Closed macro runs correctly and allows BVC to anounce the door is closed, since the Garage door open macro just cleared Flag 1.  Around 44 minutes later B3 turns on setting Flag 1 and preventing the hourly heartbeat from anouncing in BVC since the Flag condition is set.

These macros have been running perfectly for 3 days.  Hopefully this will help others with similar heartbeat reporting issues.

[HA Dave]

I solved this issue. Here's the set up.
......... These macros have been running perfectly for 3 days.  Hopefully this will help others with similar heartbeat reporting issues.

Awesome (and helpful) You should post this in "User-Designed working macros".

[peg-leg]

Thanks Dave.  I'll move it over this week.