Contactsensor doesn't change state

---

Maybe I’m doing something wrong, but my (kaku) contactsensor can only change to state ‘Open’ or ‘Closed’.
I have several contactsensors, and I have added them by ‘Discovery mode’ (excellent feature!). I use the class HomeduinoRFContact and protocol Contact1.
The contact sensor works, but only one time. It change the state to open, and it stays open.

I also added the contact sensor manually, but with the same result.

Use autoreset?

“Reset the state after resetTime. Useful for contact sensors, that only emit open or close events”

It is in the contact settings page.

In this case, it’s not a solution. Sometimes the door is not closed well, and then we get a warning ‘The door is still open’.

Also, the contact sensor has an open/close statement. For now, I use another Pi (with the old Pimatic) to control the sensors. But I want to update also this rpi.

“The door is not closed well” as in it isnt closed? Then close the door?

Maybe try the info in this thread:

Contact sensor

The point is, after the upgrade to 0.9, the state of a contact sensor is not correct. The contact sensor gives a closed or open state. Pimatic 0.8 assigned this correctly. In 0.9 only one state (open or close) works. Sure, it’s possible to reset after a period. But this worked before.

I also have problems with contact sensors. In debug mode i always receive the codes properly but in the gui the state doesn’t change from open to close or vice versa. When i edit the contact device it will work once, after that it’s not working anymore.

I just found a kaku contact and indeed, it works once. Resetting is also not a option. I have tried some other suggestions like using it as pir5 or as a switch, non of them work.

@Gleno0h It worked on version 0.8.x, so there might be another solution instead of changing the protocol.

@kenci

Tried some things but didnt get it to work. Debug is indeed good. Opened and closed state show up. Maybe the dev’s can look into it cause it seems broken.

Yeah, please @developer can you look at it.

@kenci please try following.

Update pimatic homeduino to version 0.9.8.

Use auto discovery… It should find 3 kaku devices and there should be 1 PIR kaku. Select that one, that one works for me after a update of homeduino.

Let me know.

I will try that later today. But it is not a PIR it’s a contact sensor.

@kenci i know, but now, with the update, it is pir5.

Uses present and absent.

@Frank Can you please post the device config of your contact sensor? Thanks

@mwittig Here is my config

{
      "class": "HomeduinoRFContactSensor",
      "protocols": [
        {
          "name": "contact1",
          "options": {
            "id": 10348018,
            "contact": true,
            "unit": 9
          }
        }
      ],
      "id": "wz-terrassentuer-links",
      "name": "WZ Terrassentuer Links"
    }

That device was autodiscovered. After that if i closed the door it worked once, but when i open again it doesn’t work anymore.

@Frank
Last week I got this 2 way door/window contact sensors and I have the same issue. They are detected as contact2 / contact3. After pimatic start they change once to open or close and than happens nothing.
The state bit doesnt matchs with the protocol. After changing the state bit in the protocol it works.
can you post your debug messages (open and close state).

@magic-tune Hereby the debug. This debugging is made in Pimatic 8.x (I’ve made a workaround on a second Pi to control Pimatic 9.) If there’s a difference debugging between version 8 and 9, I hope @mwittig can send you his debugging.

debug [pimatic-homeduino]: received: [ 492, 1944, 4504, 9508 ] 0201020101020102020101020101010101020101010102020102020103
10:40:47debug [pimatic-homeduino]: data: "RF receive 492 4504 1944 9508 0 0 0 0 0102010202010201010202010202020202010202020201010201010203"
10:40:47debug [pimatic-homeduino]: received: [ 492, 1940, 4504, 9500 ] 0201020101020102020101020101010101020101010102020102020103
10:40:47debug [pimatic-homeduino]: data: "RF receive 492 4504 1940 9500 0 0 0 0 0102010202010201010202010202020202010202020201010201010203"
10:40:46debug [pimatic-homeduino]: contact1:  { id: 18166510, all: false, contact: false, unit: 9 }
10:40:46debug [pimatic-homeduino]: pir5:  { id: 18166510, all: false, presence: true, unit: 9 }
10:40:46debug [pimatic-homeduino]: dimmer1:  { id: 18166510, all: false, unit: 9, dimlevel: 7, state: true }
10:40:46debug [pimatic-homeduino]: received: [ 264, 1316, 2684, 10356 ] 0200010100000100010001010000010100000101000001000101000100000100010100000101000100010000010100010001000001000101000100000100010100000101000100010003
10:40:46debug [pimatic-homeduino]: data: "RF receive 264 2684 1316 10356 0 0 0 0 0100020200000200020002020000020200000202000002000202000200000200020200000202000200020000020200020002000002000202000200000200020200000202000200020003"
10:40:46debug [pimatic-homeduino]: contact1:  { id: 18166510, all: false, contact: false, unit: 9 }
10:40:46debug [pimatic-homeduino]: pir5:  { id: 18166510, all: false, presence: true, unit: 9 }
10:40:46debug [pimatic-homeduino]: dimmer1:  { id: 18166510, all: false, unit: 9, dimlevel: 7, state: true }
10:40:46debug [pimatic-homeduino]: received: [ 168, 264, 376, 1320, 2696, 10372 ] 1411131311111311131113131111131311111313111113111313111311111311131311111313111311131111131311131113111113120313111311111311131311111313111311131115
10:40:46debug [pimatic-homeduino]: data: "RF receive 264 2696 1320 376 168 10372 0 0 0100020200000200020002020000020200000202000002000202000200000200020200000202000200020000020200020002000002034202000200000200020200000202000200020005"
10:40:45debug [pimatic-homeduino]: contact1:  { id: 18166510, all: false, contact: false, unit: 9 }
10:40:45debug [pimatic-homeduino]: pir5:  { id: 18166510, all: false, presence: true, unit: 9 }
10:40:45debug [pimatic-homeduino]: dimmer1:  { id: 18166510, all: false, unit: 9, dimlevel: 7, state: true }
10:40:45debug [pimatic-homeduino]: received: [ 264, 1320, 2712, 10380 ] 0200010100000100010001010000010100000101000001000101000100000100010100000101000100010000010100010001000001000101000100000100010100000101000100010003
10:40:45debug [pimatic-homeduino]: data: "RF receive 264 2712 1320 10380 0 0 0 0 0100020200000200020002020000020200000202000002000202000200000200020200000202000200020000020200020002000002000202000200000200020200000202000200020003"
10:40:43debug [pimatic-homeduino]: contact1:  { id: 18166510, all: false, contact: true, unit: 9 }
10:40:43debug [pimatic-homeduino]: pir5:  { id: 18166510, all: false, presence: false, unit: 9 }
10:40:43debug [pimatic-homeduino]: switch1:  { id: 18166510, all: false, state: false, unit: 9 }
10:40:43debug [pimatic-homeduino]: received: [ 176, 264, 392, 1316, 2672, 10376 ] 141113131111131113111313111113131111131311111311131311131111131113131111131311131113111113131113111312011311131113131111131113131115
10:40:43debug [pimatic-homeduino]: data: "RF receive 264 2672 1316 392 176 10376 0 0 010002020000020002000202000002020000020200000200020200020000020002020000020200020002000002020002000203400200020002020000020002020005"

What looks odd to me is the “contact” property as part of the device configuration.
Can anybody explain what this is good for in the context of the contact1 protocol?

@Frank @magic-tune @kenci My suggestion is to remove this property from the configuration and to give it another try. You need the Configutaion Editor to remove it as the Device Editor won’t let you do this.

@mwittig
Ok I have tested autodiscovery and it doesn`t work.
I removed the following part from the protocol, then it works. Tested with contact3 and contact4

,
      contact: {
        type: "boolean"
      }

@magic-tune
The issue is contact1.

Why not just use pir5? Absent - present is for me the same as opened and closed.