Smartthings with AD2PI Network appliance

[wesgurn]

Thanks Scott!

Question - I have a couple motion and glass break sensors. What are your thoughts on those types? It seems off to lump them as a contact sensor, but wasn't sure if those types were available.

I'll be installing this after work today and can provide some feedback.

Wes

[Scott]

Thanks Scott!

Question - I have a couple motion and glass break sensors. What are your thoughts on those types? It seems off to lump them as a contact sensor, but wasn't sure if those types were available.

I'll be installing this after work today and can provide some feedback.

Wes

They should report as regular zones if they're configured in your panel. I'd imagine the motion sensor might be a little spammy when it comes to faults though. I'd eventually like to add support for watching !RFX messages and have SmartThings use those to take advantage of it's motion capabilities.

[JJsLegacy]

I can't seem to get any event subscriptions no matter how many times I reinstall this with the latest code.

Uninstalling everything was quite painful but hopefully now that I don't have much customization I won't have to do that again but no idea why they aren't getting created.

[terryhonn]

I can't seem to get any event subscriptions no matter how many times I reinstall this.

I'm in the same boat. I think I might try going back to an install I had with v1 of the ST hub, with a custom Python script on the AD device and an endpoint smart app in ST. Was getting real-time events with that, too.

[JJsLegacy]

about 17 reinstalls and a hub reboot I finally got the subscriptions.

Now things seems backwards - when I open a window it shows closed and default is open for all the zones.

[JJsLegacy]

Scott - this code is backwards:

def zoneOn(evt) {
log.trace("zoneOn: desc=${evt.value}")

def d = getChildDevices().find { it.deviceNetworkId.contains("switch${evt.value}") }
if (d)
d.sendEvent(name: "contact", value: "close", isStateChange: true, filtered: true)
}

def zoneOff(evt) {
log.trace("zoneOff: desc=${evt.value}")

def d = getChildDevices().find { it.deviceNetworkId.contains("switch${evt.value}") }
if (d)
d.sendEvent(name: "contact", value: "open", isStateChange: true, filtered: true)
}


The "open" and "closed" need switched

[JJsLegacy]

Also this appears wrong in the smartapp

// Default contact to closed.
zone_switch.sendEvent(name: "contact", value: "open", isStateChange: true, displayed: false);

The default should be "closed" I assume?

[Scott]

Thanks for the feedback guys. I'll see if I can narrow down those darn subscription issues.

As for the sensors, the open/close thing has it's roots in electronic components. 'Open', when talking about contacts/relays, means the circuit is open and no current flows through it, which means it's 'off'. Closed contacts allow electricity to flow and is considered the 'on' state. That logic can typically be switched somewhere (panel, smartapp, whatever) but I'm conforming to the standard definition for sanity's sake. Hope that makes sense!

[JJsLegacy]

From my logging of it - I am guessing the device isn't being created fast enough and so the subscribes fails.

I switched all my open/close - makes sense what you said but from a use standpoint with apps in smartthings I think it all needs switched.

Easy changes but maybe worth documenting somewhere for folks that aren't as code savy.

Thanks for the updates!

[slockner]

so finally got a couple sensors fixed so I could start arming via smarthings and I noticed a couple things..

when I disarm.. I loose the ability to see individual sensor status until I go and hit * on one of the key pads.

the pad says to see faults press *.

also I am not able to activate the siren from smartthings..

for reference I have a 20SE panel.