The following warnings occurred:
Warning [2] count(): Parameter must be an array or an object that implements Countable - Line: 895 - File: showthread.php PHP 7.3.14-1~deb10u1 (Linux)
File Line Function
/showthread.php 895 errorHandler->error

  • 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
arctech_contact protocol missing open/close signals
A month or so ago my kaku contact sensors, working with the arctech_contact protocol, started to behave unreliably. Because they had been working quite well before, I first assumed that weak batteries were responsible for it, but with fresh batteries the problem persisted.

I searched the forum for posts reporting the same behaviour, but didn't find any.

Then I investigated the pulsetrains sent by the sensors and found that most of the time the duration of the startpulse was a bit less than the minimum required by the archtech_contact protocol (8*2*300=2400), while the endpulse was always within the defined range:
[ Dec 23 13:57:41:61798] pilight-daemon: INFO: startpulse=2348, endpulse=10386, PULSE_DIV=34
[Dec 23 13:57:41:224963] pilight-daemon: INFO: startpulse=1800, endpulse=10341, PULSE_DIV=34
[Dec 23 13:57:41:796007] pilight-daemon: INFO: startpulse=2243, endpulse=10415, PULSE_DIV=34
[Dec 23 13:57:41:959209] pilight-daemon: INFO: startpulse=2748, endpulse=10405, PULSE_DIV=34
[Dec 23 13:57:42:122250] pilight-daemon: INFO: startpulse=2376, endpulse=10404, PULSE_DIV=34
[Dec 23 13:57:42:448543] pilight-daemon: INFO: startpulse=2341, endpulse=10410, PULSE_DIV=34
[Dec 23 13:57:42:693153] pilight-daemon: INFO: startpulse=2374, endpulse=10414, PULSE_DIV=34
[Dec 23 14:27:25:230562] pilight-daemon: INFO: startpulse=2297, endpulse=10397, PULSE_DIV=34
[Dec 23 14:27:25:500892] pilight-daemon: INFO: startpulse=1747, endpulse=10407, PULSE_DIV=34
[Dec 23 14:27:25:860824] pilight-daemon: INFO: startpulse=2195, endpulse=10354, PULSE_DIV=34
[Dec 23 14:27:26:311124] pilight-daemon: INFO: startpulse=2324, endpulse=10370, PULSE_DIV=34
[Dec 23 14:27:26:491314] pilight-daemon: INFO: startpulse=2231, endpulse=10363, PULSE_DIV=34
[Dec 23 14:27:26:671365] pilight-daemon: INFO: startpulse=2285, endpulse=10376, PULSE_DIV=34
[Dec 23 14:27:26:851557] pilight-daemon: INFO: startpulse=2371, endpulse=10406, PULSE_DIV=34
[Dec 23 14:27:27:301823] pilight-daemon: INFO: startpulse=2340, endpulse=10352, PULSE_DIV=34
[Dec 23 14:27:27:481945] pilight-daemon: INFO: startpulse=2223, endpulse=10373, PULSE_DIV=34
[Dec 23 14:27:27:662097] pilight-daemon: INFO: startpulse=2281, endpulse=10368, PULSE_DIV=34

For testing I took one of the sensors from its place at the door to my workplace and after a while the response started to get better. 

I came to the conclusion that the ambient temperature somehow influences the duration of the start pulse of the sensor (shorter at low temperatures).  The fact that the sensors are mounted in places (on doors and windows) becoming colder when it is cold outside may explain why they worked well before and stopped doing that recently. 

I then modified the check for the start pulse length:

arctech_contact_switch->raw[1] >= AVG_PULSE_LENGTH*(PULSE_MULTIPLIER*2))


arctech_contact_switch->raw[1] >= AVG_PULSE_LENGTH*(PULSE_MULTIPLIER*1.9))

It now allows start pulses with a duration above 2280 instead of 2400, and now all of my sensors are all working well again. I don't know however if the pulse duration may even get less if it starts freezing. I will wait and see.

Messages In This Thread
arctech_contact protocol missing open/close signals - by Niek - 12-23-2017, 04:17 PM

Possibly Related Threads...
Thread Author Replies Views Last Post
  Compile with Optimization fails / timedate missing fourty2 6 873 04-29-2019, 12:27 PM
Last Post: fourty2
  Protocol Program PID AdHoc-Client Bigmama 12 1,609 01-26-2019, 07:36 PM
Last Post: Bigmama
Exclamation pilight detect wrong protocol quigg_gt9000 is not quigg_gt1000 PCT 1 1,237 08-12-2018, 11:13 AM
Last Post: Niek
  need some help with program protocol charlesjacob4695 1 672 05-15-2018, 05:58 PM
Last Post: curlymo
  problem with alecto_wx500 protocol (pilight V7) TheWheel 18 6,742 04-12-2018, 06:38 PM
Last Post: NevelS
  deleyCON remote plug socket (arctec_screen_old protocol) itsMe 6 1,601 04-01-2018, 08:35 PM
Last Post: itsMe
  Problem with Protocol gpio_switch engel035 15 3,766 03-19-2018, 06:46 PM
Last Post: curlymo
  Extend generic protocol mickey.lm 6 1,510 11-20-2017, 10:51 PM
Last Post: mickey.lm
Question window sensor's very first signal goes missing baf 1 1,066 11-14-2017, 10:36 PM
Last Post: curlymo
Star How to bind new protocol with GUI polo 11 2,791 11-12-2017, 10:12 PM
Last Post: curlymo

Forum Jump:

Browsing: 1 Guest(s)