Contact04

chrizzz86

Hi @ll,

I’ve ordered some of these contact sensors:
http://www.lightinthebox.com/de/gs-iwds07-drahtlosen-intelligenten-tuer-fenster-magnetkontakt_p4766217.html
They send open and close signals!
Powered with a single AAA battery.

Unfortunately no protocol matched…
So I tried myself to develop the contact4 protocol.
Please have a look if everything ist fine (Contact sensor is working without problems, maybe the code design is not the best?)

module.exports = function(helper) {
  var binaryToPulse, protocolInfo, pulsesToBinaryMapping;
  pulsesToBinaryMapping = {
    '10': '1',
    '01': '0',
    '02': ''
  };
  binaryToPulse = {
    '1': '10',
    '0': '01'
  };
  return protocolInfo = {
    name: 'contact4',
    type: 'contact',
    values: {
      id: {
        type: "number"
      },
      contact: {
        type: "boolean"
      }
    },
    brands: ["GS-IWDS07"],
    pulseLengths: [468, 1364, 14096],
    pulseCount: 50,
    decodePulses: function(pulses) {
      var binary, result;
      binary = helper.map(pulses, pulsesToBinaryMapping);
      return result = {
        id: helper.binaryToNumber(binary, 0, 19),
        contact: helper.binaryToBoolean(binary, 21)
      };
    }
  };
};

How can I publish this code to the pimatic repository?

mwittig

@chrizzz86 said in Contact04:

How can I publish this code to the pimatic repository?

See https://github.com/pimatic/rfcontroljs#adding-a-new-protocol

The source code needs to be written in CoffeeScript by convention and one should also add some tests. If you are not familiar with CoffeeScript I am happy to transform the code for you. Please also post some debug messages for “open” and “close” which we can use to add some protocol tests.

chrizzz86

Would be nice if you can transform the code.

OPEN:

received: [ 464, 1368, 14104 ] 10101001100110011001011010100101010101011001100102
data: "RF receive 1368 464 14104 0 0 0 0 01010110011001100110100101011010101010100110011012"

contact4:  { id: 960960, contact: false }


CLOSE:

received: [ 464, 1368, 14040 ] 10101001100110011001011010100101010101011010100102
data: "RF receive 1368 464 14040 0 0 0 0 0 01010110011001100110100101011010101010100101011012"

contact4:  { id: 960960, contact: true }

mwittig

@chrizzz86 Done. To be released soon

leader21

wow!! only appr. 6 euro for the sensor with open / close detection is really cheap!
thx for your efforts and for the information on this sensor

chrizzz86

The sensors have been working flawless for two weeks now.

With Home Easy HE HE852 I’ve got often problems: Only in 8 of 10 closing processes they work correct.

magic-tune

@chrizzz86 Hey chrizzz86,
i bought 10 of this window/door contact-sensors. The same as yours. I have tested your protocol to day and it works so far. The range is great and they works reliable. But when i add a device with autodiscovery function in pimatic 9, the new device doesn`t work. The aotodiscovery sets “contact”: true as a part of the config. I deleted the following part in the protocol, then it works.

,
      contact: {
        type: "boolean"
      }

The id of my 10 sensors differs in the bits 0-15. I hope one of the bits behind 16-20 is for empty battery.

Partovic

@magic-tune anyone figured out if there is an indicator bit for empty battery yet?

mwittig

@Partovic No, as far as I know. See also related feature request along with a request for debug messages covering the “normal battery” and the “low battery” case. Maybe you can help?

https://forum.pimatic.org/topic/2371/lowbattery-for-all-homeduino-rf-devices

magic-tune

@Partovic
This sensor idicates the lowBattery with slow blinking. At this point I couldn`t see any changes in the debug. But when the battery gets empty (<0,8V) the led blinks fast and the sensor sends a code with change in Bit20.

0--1--2--3--4--5--6--7--8--9--10-11-12-13-14-15-16-17-18-19-20-21-22-23
10 01 10 01 10 10 01 01 10 10 10 01 01 10 01 10 01 01 01 01 10 01 10 01 02 <---open
10 01 10 01 10 10 01 01 10 10 10 01 01 10 01 10 01 01 01 01 10 10 10 01 02 <---close
10 01 10 01 10 10 01 01 10 10 10 01 01 10 01 10 01 01 01 01 01 10 10 01 02 <---empty Battery < 0,8V

I added the bit 20 as lowBattery to the protocol, but without sucsses. The debug looks good. But there is no icon in the GUI and no variable with batterystatus.

module.exports = function(helper) {
  var binaryToPulse, protocolInfo, pulsesToBinaryMapping;
  pulsesToBinaryMapping = {
    '10': '1',
    '01': '0',
    '02': ''
  };
  binaryToPulse = {
    '0': '01',
    '1': '10'
  };
  return protocolInfo = {
    name: 'contact5',
    type: 'contact',
    values: {
      id: {
        type: "number"
      },
      contact: {
        type: "boolean"
      },
      lowBattery: {
        type: "boolean"
      }
    },
    brands: ["DoorWindowConract"],
    pulseLengths: [310, 950, 9644],
    pulseCount: 50,
    decodePulses: function(pulses) {
      var binary, result;
      binary = helper.map(pulses, pulsesToBinaryMapping);
      return result = {
        id: helper.binaryToNumber(binary, 0, 19),
        contact: helper.binaryToBoolean(binary, 21),
	lowBattery: helper.binaryToNumberLSBMSB(binary, 20, 20) !== 1
      };
    }
  };
};

    {
      "id": "contact",
      "name": "Door",
      "class": "HomeduinoRFContactSensor",
      "protocols": [
        {
          "name": "contact5",
          "options": {
            "id": 44261
          }
        }
      ],
      "xClosedLabel": "Zu",
      "xOpenedLabel": "Auf"
    },

debug: contact5:  { id: 44261, contact: true, lowBattery: false }
debug: contact5:  { id: 44261, contact: true, lowBattery: true }

chrizzz86

At the moment maybe it’s possible to generate an alarm with a rule?

By the way: I bought my sensors in June 2016 and it hasn’t been necessary till today to replace a battery.

mwittig

I have already implemented the necessary changes, but they are currently on hold due to stability issues with the development branch

fennsen

@mwittig said in Contact04:

I have already implemented the necessary changes, but they are currently on hold due to stability issues with the development branch

Hi,
which update do I have to make to get these protocol changes for this contact? pimatic-homeduino or pimatic core?
THX in advice!

mwittig

@fennsen In my posted I refered to the protocol snippted sent by @chrizzz86 in post 1. This can be found on master at https://github.com/pimatic/rfcontroljs/blob/master/src/protocols/contact4.coffee

Fabian

Hi,

the contact sensor (gs-iwds07) is working perfectly. No Problems at all! The device discovery function detected the sensor after only opening or closeing the contact once.

But is it also possible to show the low battery information in the frontend? Right now i have a HomduinoRFContactSensor which is showing the state of th contact.

Thank you.

fennsen

I’ve also the ‘issue’ with the missing low battery information in the frontend. In the protocol it’s implemented but not shown in GUI.
Anny hints on this?

Thanks in advice!

mwittig

Ok, I got confused myself as I had implemented the feature a couple of months ago, but never released it due to some issue with node serialport. I’ll publish a new release soon.

If you want to trial the feature you can install the v0.9.x branch, sudo npm i pimatic/pimatic-homeduino#v0.9.x --unsafe-perm. See method 2 at https://forum.pimatic.org/topic/1114/updated-how-to-install-a-plugin-from-github-using-npm-or-git for details.

Fabian

Hi,

maybe I had no luck or I’m not smart enough…

pi@raspberrypi:~ $ cd /home/pi/pimatic-app/node_modules/
pi@raspberrypi:~/pimatic-app/node_modules $ sudo rm -rf pimatic-homeduino
pi@raspberrypi:~/pimatic-app/node_modules $ sudo npm i pimatic/pimatic-homeduino#v0.9.x --unsafe-perm
/
> serialport@2.0.6 install /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport
> node-pre-gyp install --fallback-to-build

make: Entering directory '/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
  CXX(target) Release/obj.target/serialport/src/serialport_unix.o
  CXX(target) Release/obj.target/serialport/src/serialport_poller.o
  SOLINK_MODULE(target) Release/obj.target/serialport.node
  COPY Release/serialport.node
  COPY /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build/Release/node-v46-linux-arm/serialport.node
  TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build'

> homeduino@0.0.64 postinstall /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino
> node -e "require('fs').chmodSync('bin/vhduino', '755')"

npm ERR! Linux 4.4.49-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "pimatic/pimatic-homeduino#v0.9.x" "--unsafe-perm"
npm ERR! node v4.6.2
npm ERR! npm  v2.15.11
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package pimatic@0.9.42 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer pimatic-cron@0.8.8 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-denon-avr@0.9.9 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-dht-sensors@0.9.3 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-easybox@0.1.2 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-filebrowser@0.9.0 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-filter@0.9.3 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-gpio@0.9.0 wants pimatic@>=0.9.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-homeduino@0.9.11 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-iframe@0.3.1 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-links@0.8.6 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-mobile-frontend@0.9.12 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-mythermostat@0.0.3 wants pimatic@0.8.* && >=0.8.31
npm ERR! peerinvalid Peer pimatic-openweather@0.9.4 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-ping@0.9.5 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-samsung-tv@0.9.0 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-shell-execute@0.9.11 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-sunrise@0.8.7 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-sysinfo@0.9.4 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-telegram@1.1.6 wants pimatic@>=0.9.*
npm ERR! peerinvalid Peer pimatic-upnp-root@0.8.9 wants pimatic@>0.8.19
npm ERR! peerinvalid Peer pimatic-wakeonlan@0.9.4 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-watchdog-unix@0.0.1 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-wemo@0.0.3 wants pimatic@0.8.*

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/pimatic-app/node_modules/npm-debug.log
pi@raspberrypi:~/pimatic-app/node_modules $ cd
pi@raspberrypi:~ $ sudo service pimatic start

17:39:45.710 [pimatic] error: Startup error: ReferenceError: timeout is not defined
17:39:45.710 [pimatic] error:>    at Board.connect (/home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/lib/board.js:96:54)
17:39:45.710 [pimatic] error:>    at Framework.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-homeduino/homeduino.coffee:127:18)
17:39:45.710 [pimatic] error:>    at emitOne (events.js:82:20)
17:39:45.710 [pimatic] error:>    at Framework.emit (events.js:169:7)
17:39:45.710 [pimatic] error:>    at /home/pi/pimatic-app/node_modules/pimatic/lib/framework.coffee:948:12
17:39:45.710 [pimatic] error:>    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
17:39:45.710 [pimatic] error:>    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31)
17:39:45.710 [pimatic] error:>    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
17:39:45.710 [pimatic] error:>    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
17:39:45.710 [pimatic] error:>    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
17:39:45.710 [pimatic] error:>    at Promise._fulfill (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:638:18)
17:39:45.710 [pimatic] error:>    at Promise._resolveCallback (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:432:57)
17:39:45.710 [pimatic] error:>    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:524:17)
17:39:45.710 [pimatic] error:>    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
17:39:45.710 [pimatic] error:>    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
17:39:45.710 [pimatic] error:>    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
17:39:45.710 [pimatic] error:>    at Promise._fulfill (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:638:18)
17:39:45.710 [pimatic] error:>    at PromiseArray._resolve (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise_array.js:126:19)
17:39:45.710 [pimatic] error:>    at PromiseArray._promiseFulfilled (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise_array.js:144:14)
17:39:45.710 [pimatic] error:>    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:574:26)
17:39:45.710 [pimatic] error:>    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
17:39:45.710 [pimatic] error:>    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
17:39:45.710 [pimatic] error:>    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:133:16)
17:39:45.710 [pimatic] error:>    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
17:39:45.710 [pimatic] error:>    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
17:39:45.710 [pimatic] error:>    at processImmediate [as _immediateCallback] (timers.js:383:17)
17:39:45.719 [pimatic] info: exiting...

so I will wait until it is available as update…

fennsen

I have the same issue and errors here when trying to install from the 0.9.x branch

sudo npm i pimatic/pimatic-homeduino#v0.9.x --unsafe-perm
|
> serialport@2.0.6 install /usr/local/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport
> node-pre-gyp install --fallback-to-build

make: Entering directory '/usr/local/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
  CXX(target) Release/obj.target/serialport/src/serialport_unix.o
  CXX(target) Release/obj.target/serialport/src/serialport_poller.o
  SOLINK_MODULE(target) Release/obj.target/serialport.node
  COPY Release/serialport.node
  COPY /usr/local/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build/Release/node-v46-linux-arm/serialport.node
  TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory '/usr/local/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport/build'

> homeduino@0.0.64 postinstall /usr/local/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino
> node -e "require('fs').chmodSync('bin/vhduino', '755')"

npm WARN unmet dependency /usr/local/pimatic-app/node_modules/pimatic-echo/node_modules/hapi/node_modules/subtext/node_modules/pez requires boom@'3.x.x' but will load
npm WARN unmet dependency /usr/local/pimatic-app/node_modules/pimatic-echo/node_modules/hapi/node_modules/boom,
npm WARN unmet dependency which is version 4.0.0
npm ERR! Linux 4.1.19-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "pimatic/pimatic-homeduino#v0.9.x" "--unsafe-perm"
npm ERR! node v4.6.2
npm ERR! npm  v2.15.11
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package pimatic@0.9.38 does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer pimatic-cron@0.8.8 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-dewpoint@0.9.0 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-dht-sensors@0.9.3 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-echo@0.0.6 wants pimatic@~0.9.0
npm ERR! peerinvalid Peer pimatic-gpio@0.8.15 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-hap@0.9.5 wants pimatic@~0.9.0
npm ERR! peerinvalid Peer pimatic-harmonyhub@0.0.6 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-homeduino@0.9.11 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-hue-zll@0.3.1 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-iframe@0.2.0 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-lgtv@0.8.2 wants pimatic@0.8.*
npm ERR! peerinvalid Peer pimatic-lirc@0.1.1 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-mobile-frontend@0.9.11 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-mqtt@0.9.5 wants pimatic@>=0.9.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-ping@0.9.5 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-pushbullet@0.9.0 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-shell-execute@0.9.8 wants pimatic@0.9.*
npm ERR! peerinvalid Peer pimatic-sunrise@0.8.7 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-youless@0.5.0 wants pimatic@>=0.8.0 <1.0.0
npm ERR! peerinvalid Peer pimatic-youless-gas@0.5.0 wants pimatic@>=0.8.0 <1.0.0

npm ERR! Please include the following file with any support request:
npm ERR!     /usr/local/pimatic-app/node_modules/npm-debug.log

Fabian

@mwittig do you already have a date to publish the code? I didn’t get it working by installing the plugin manually.

Thank you in advance!