DS10A transmit "Normal"

[Thickman]

Why would a DS10a transmit "Normal" at random times? The batteries are new.

[Uncle Michael]

I believe that is a mechanism to "close the loop" on an otherwise open loop system. These devices were designed to be part of a security system, so they need a way to verify that they are in place and working properly. If the DS10 were damaged or stolen, the only way for the system to know is that a 'normal' state transmission had not been received. That said, it's not a very robust solution to the problem, but probably better than nothing.

[Thickman]

What would be the best way to set one up to monitor a freezer door? I have created two events triggered by "Device Value Change", one when value = alert and one when value = normal. Both fire this script.


'1 is open, 2 is closed
sub main()
dim value
value = hs.devicevalue("]5")
hs.writelog "Freezer", value
if value = "1" then
hs.WriteLog "Freezer","Freezer door is open"
hs.Speak "The freezer door is open."
hs.SetDeviceString "]5", "<img src='images\dooropen.gif' align=absmiddle> Open"
else
hs.WriteLog "Freezer","Freezer door is closed."
hs.Speak "The freezer door is closed."
hs.SetDeviceString "]5", "<img src='images\doorclose.gif' align=absmiddle> Closed"
end if
end sub

But the problem is with the DS10 receiving "normal" the script get fired every so often. Is there a better way to achieve this?

[nsisman]

My ds10's are set up in the acrf plug in as "Supervised Door/Win/Glass Sensor ".

They are "alert" when separated from the magnet and "normal" when close to the magnet.

I don't have the problem here at all so maybe you need a little different setup ?

Good luck

[Uncle Michael]

How are you receiving the DS10 transmissions into HS? I use ACRF2, which doesn't change the HS device value unless the open/closed state of the DS10 changes.

If the state of the DS10 hasn't changed I'm having trouble understanding why your event triggers. Can you post a screen shot of the event?

[Thickman]

I'm still using W800 RF (32 bit) controller hspi_W800RF.ocx. Here is a picture of the event.

[nsisman]

Your "normal" event is speaking because the ds10 sends out a heartbeat signal with a "normal" signal - I think mine is about every 45 minutes or so.

One way to fix it would be to take out the speak line for freezer door "closed" and set up warning event for the "open" freezer door with a device condition that if the ds10 has been alert for x minutes then advise you (sound the siren, bark the dog, email everybody and flash all the house lights 4 times, etc. )

Works well for fridge doors as well - actually any door you want to keep closed.

You likely only really need to be advised if the door is left open too long anyway ! Don't really care as long as it is closed ?

I do this for big and small garage doors, shed door, gates etc so if they are left open I am made aware by Homeseer.

Good luck...........

[Uncle Michael]

I'm still puzzled, but I don't have any events that explicitly take an action when a DS10 changes to normal.

I do have events, though, that are triggered when the value changes to 'Any'. I then use a script to sort out what the change was. Those events do not trigger from the heartbeat transmission. I always assumed that was because that didn't signal a change of the device value.

If I were seeing the kind of behavior you are I would create an event to check the device value of the DS10 periodically, probably about every 15 minutes and write the value to the log. I'd also write the value whenever the 'normal' and 'alert' events triggered. That ought to make clear if the device value is actually changing and, if so, maybe even provide a clue as to why.

[Thickman]

Your "normal" event is speaking because the ds10 sends out a heartbeat signal with a "normal" signal - I think mine is about every 45 minutes or so.

One way to fix it would be to take out the speak line for freezer door "closed" and set up warning event for the "open" freezer door with a device condition that if the ds10 has been alert for x minutes then advise you (sound the siren, bark the dog, email everybody and flash all the house lights 4 times, etc. )

Works well for fridge doors as well - actually any door you want to keep closed.

You likely only really need to be advised if the door is left open too long anyway ! Don't really care as long as it is closed ?

I do this for big and small garage doors, shed door, gates etc so if they are left open I am made aware by Homeseer.

Good luck...........

I'm wanting to do the same thing you are checking to see if my single garage door, double garage door, shed door, shed window, and freezer door is open or closed then if open at dusk run a script to tell me to shut the door. Sounds like you're doing the same thing. Do you keep track if they're closed or just open?

[Thickman]

I'm still puzzled, but I don't have any events that explicitly take an action when a DS10 changes to normal.

I do have events, though, that are triggered when the value changes to 'Any'. I then use a script to sort out what the change was. Those events do not trigger from the heartbeat transmission. I always assumed that was because that didn't signal a change of the device value.

If I were seeing the kind of behavior you are I would create an event to check the device value of the DS10 periodically, probably about every 15 minutes and write the value to the log. I'd also write the value whenever the 'normal' and 'alert' events triggered. That ought to make clear if the device value is actually changing and, if so, maybe even provide a clue as to why.

Thanks for the suggestion! I sent up some events to track what's going on. I think 'Any' may be the way to go and sort out with a script. I'll let it run for a while and see what I get.

[nsisman]

I am only concerned if open too long but I can get the status by checking the device on the Homeseer status page.

[Thickman]

I am only concerned if open too long but I can get the status by checking the device on the Homeseer status page.

Thanks Neil a picture is worth a thousand words! I'll give that a try on one of them should work fine on my shed.

[outbackrob]

Doing the same thing

I have a very similar setup as you. I check to see when it BECOMES normal. When it does, it plays a sound so you know you have closed the frig door. If it doesn't close (become normal) after 2 minutes, then the alarm goes off.

It only BECOMES normal after it has been open and then closed again. Have not had ANY issues with the DS10A transmitting a "normal condition" causing the event to fire.

The alarm sounds provide GREAT WAF and gets your attention!

We originally set this up after we put a big frozen turkey in the frig and left the door open. It thawed, but got warm and we had to toss it... More importantly, all the beer got warm too!

[snedecor]

Love the autopilot disconnect wav. I set it up for:

1) Washer has been done for 30 minutes (clothes are getting stinky)

2) Dryer has been done for 1 hr. (clothes are getting wrinkly).

I've got a more polite alert tone (sort of like "be-doop") for the initial reminder...

[Thickman]

I'm even more confused! I don't have any events firing for the freezer but the "Last Change" is updating.