Use a single contact to monitor the door each time it open/closes then use a proxy item in a rule to indicate IN/OUT? If so, you would only need to set the proxy item to the correct state once it’s created, after that it should change each time the door changes.
Another option is using an inside motion detector with a single contact and rule. If motion, then contact change, a cat has left the building. If contact, then motion, a cat has arrived. Minor tweaking on the timing but should work.
But back to the OP, @Topsurfer, how are you using the two contacts?
I would imagine that any of the door/window sensors would work. If you have power nearby or are up for building a complete DIY system with a case, wiring up reed senors to ESP8266s or RPis is about as easy as it gets for the DIY front.
If going the DIY and no power close by, use 22 gauge twisted pair (or two pair if needing two sensors) shielded wire. Assuming no huge interference you can have the reed switch and Esp/RPI located on different ends of the home. I use a similar setup with a reed switch and the only modification needed was to add a small decoupling capacitor to prevent false triggers.
Probably what I should have done, but I can say that I get good connection/reception on two reed sensors on a run of about 40 feet with speaker wire (it’s what I had). The garage controller is on one side of the garage and the sensors are on the other, 12 foot ceilings with a bump out in the ceiling I needed to go around makes for a pretty long run.
I don’t have a capacitor but I do have a resistor. No false triggers so far.
The finished product. Expensive.
The flap reads common ID chips implanted in the animal for access control.
(I have the cheaper dumb non-communicating version to keep out the local Tom, our two queens use it reliably, battery life is good)
This is the smarter version, which requires a separate “hub” to talk over WiFi to the app.
App allows individual cat control, scheduled in or out times, and reporting.
I don’t know of an API.
My guess is the flap uses zwave or similar, hence the hub. I wonder if it is hackable to avoid the hub.
You could add contacts to the dumb version, to determine in / out, but I can’t see any ready means to get at the ID of the “user”.
You ‘program’ it by by pressing a button and, uh, “introducing” the cat to it. That’s fun, if a little bloody for the instructor.
[joking] quick, hide this post with this Cat Flat Connect… my wife will read the forum and I will be in trouble… I can already hear her say “this is a real Home Automation device that you should have installed… not the other DIY crap” ! [/joking]
I have build in two contacts inside the Catflap axis, so if the Catflap open more than 60 degress in direction outside contact A is closed, when Catflap open more than 60 degress in direction inside contact B is closed.
And yes, I know the RFID solution, but actual not a topic: I will use my “unsecure” solution.
I check the ZD2102, there is the option to use a second contact, but I on a german page I read the second contact will not trigger a second event, use the same “way” as the first contact (parallel switch).
But I need two different signals …
Or is the info wrong? Here is a PDF, maybe you can read is “correctly”. (Update: Link fixed, thx)
I have a Devolo Homecontact, which has a Alarm contact (tamper) and brightness.
From Alarm switch I never see a entry in log (Devolo LED goes red), and the brightness is send not very often (I thought I can use the brightness sensor as signal for the 2nd contact, connect a resistor to the brightness sensor (=verby bright=contact 2 is closed) …) (Hint: DoorContact is send immediately).
So if you you know a “normal” door contact which send quickly Alarm info I can try to use this contact outside as 2nd contact.
Or when the brightness is send in real time I can also try to use this modefied “signal” …
When using the WADWAZ-1 as a door sensor, I configure the Item to use the alarm_entry channel. When using the WADWAZ-1 as a leak sensor (using the external switch), I configure the Item to use the sensor_binary channel. One unfortunate functional gap is that the sensor_binary channel needs to be linked to the BASIC CC, but @chris decided to remove polling for the BASIC CC, so the channel does not get polled. This “feature” also rendered the scene_number channel useless in most (all?) Leviton dimmers and switches.
I only have WADWAZ-1s, but I believe that all of the devices in the table Angelos linked to in the second post can use external switches connected to terminal posts inside the device with a knockout in the cover. They are all the some device, except some have zwave plus, so the behavior of the external switch could be different. I only added the channel to the WADWAZ-1, so if you can verify that your device has the terminal posts, then add the channel in the db. If you have trouble, just let me know which device, and I will add it for you.
Do I missunderstood it, or is the result that the status from second contact will not be send in realtime to openHAB? At the end I need two contacts which are sending every change in real time (as the original door contacts are doing)