• 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
window sensor's very first signal goes missing
#1
Question 
Hi there,

I am not getting behind an issue with the reception of a signal of a "gs-iwds07" window sensor.

My setup:

I am running "Home Assistant" on a Raspberry PI 2. I set up pilight and used the corresponding component in HomeAssistant to receive events from pilight. Since my sensor "gs-iwds07" is not yet supported by the official pilight stream, I am using https://github.com/wo-rasp/pilight.git . Hardware-wise, I bought the components for a receiver (Superheterodyne) and low-pass filter (based on an Attiny45) as described on the pilight website, and assembled everything on a breadboard.

The problem:

In general this is working and I do get ALL state changes of my window sensor (opened/closed), except for the very first event (window opened) after the window was closed for hours.

An example:

The window was closed all night, then in the morning I open it at 8:00am, close it at 8:01, open it at 8:02, close it at 8:03. The resulting received events are these:

Code:
8:01 closed
8:02 opened
8:03 closed

I am not yet sure, how much time needs to pass without an window state change to reproduce this again. I think it has to be several hour (like leaving in the morning for work, then trying again in the evening).

Debugging:

Here is the protocol description: https://wiki.pilight.org/doku.php/gs-iwds07. The sensor is supposed to send 50 pulses. I took some pilight-debug data, which looks like this, however:

Window opened:

Code:
time:        Mon Nov 13 22:34:06 2017
hardware:    433gpio
pulse:        12
rawlen:        43
pulselen:    388
  
Raw code:
456 1368 418 1368 1406 456 1406 456 1406 456 418 1368 494 1368 1330 494 1330 494 456 1406 1368 494 456 1406 456 1368 456 1368 1368 494 124336 494 1330 1368 418 532 1330 1368 418 494 1330 456 13224  

--[RESULTS]--

time:        Mon Nov 13 22:34:06 2017
hardware:    433gpio
pulse:        11
rawlen:        38
pulselen:    411

Raw code:
451 1353 1353 492 1312 451 492 1353 1394 451 492 1394 492 1353 451 1394 1353 451 492 1394 451 1394 451 1353 451 1353 492 1353 1353 451 492 1353 1353 492 451 1353 451 13981  

--[RESULTS]--

time:        Mon Nov 13 22:34:06 2017
hardware:    433gpio
pulse:        11
rawlen:        38
pulselen:    410

Raw code:
451 1394 1353 492 1353 451 492 1353 1353 451 492 1353 410 1353 451 1353 1312 451 492 1394 451 1435 451 1271 451 1394 451 1353 1312 451 492 1353 1353 451 451 1353 451 13981  

--[RESULTS]--

time:        Mon Nov 13 22:34:06 2017
hardware:    433gpio
pulse:        10
rawlen:        38
pulselen:    414

Raw code:
410 1353 1353 533 1394 451 492 1353 1353 451 492 1353 451 1353 492 1353 1394 451 492 1394 451 1353 492 1353 451 1353 492 1394 1312 451 492 1353 1353 451 492 1353 410 14104

Window closed:

Code:
--[RESULTS]--

time:        Mon Nov 13 22:34:16 2017
hardware:    433gpio
pulse:        11
rawlen:        50
pulselen:    413

Raw code:
492 1353 451 1353 1394 451 1394 451 1394 451 492 1353 492 1353 1312 492 1353 451 492 1353 1394 451 492 1353 492 1353 451 1353 1394 451 492 1394 451 1353 492 1394 451 1353 451 1353 1394 451 1394 451 1394 451 492 1353 451 14063  

--[RESULTS]--
  
time:        Mon Nov 13 22:34:16 2017
hardware:    433gpio
pulse:        11
rawlen:        50
pulselen:    411

Raw code:
492 1353 451 1353 1353 451 1394 451 1394 451 492 1353 451 1353 1394 492 1353 451 451 1353 1312 451 492 1353 451 1353 492 1353 1353 451 492 1394 451 1353 451 1353 492 1353 451 1353 1394 451 1394 451 1394 451 492 1353 451 13981  

--[RESULTS]--

time:        Mon Nov 13 22:34:16 2017
hardware:    433gpio
pulse:        11
rawlen:        50
pulselen:    414

Raw code:
492 1353 492 1353 1353 451 1394 451 1353 451 492 1353 451 1353 1353 492 1353 451 492 1353 1394 451 492 1353 451 1353 451 1353 1353 451 492 1394 451 1353 451 1353 451 1353 492 1353 1353 451 1394 451 1353 451 492 1353 451 14104

--> Interestingly, "window closed" shows exactly 50 pulses in all signal repetitions. However, for "window opened" the puls length is shorter and seems to vary a bit. Seems as if the "opened" signal is not as clear as it should be!? And I don't see how this fits into the picture of only missing out on the very first signal after a period of no window state change...

Thanks for any help!!
baf
 
Reply
#2
We need as much debug signals as possible. Various for first opened, various for first closed, and various for subsequent opened and closed.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Compile with Optimization fails / timedate missing fourty2 6 410 04-29-2019, 12:27 PM
Last Post: fourty2
  Plug not acting upon signal tulamidan 18 1,236 12-22-2018, 12:15 PM
Last Post: curlymo
  [solved] kwmobile: repeating the remote signal doesn't work dawncrow 9 938 10-25-2018, 03:46 PM
Last Post: dawncrow
  Looking for a cheap temperature and humidity sensor madmoses 10 1,649 03-11-2018, 03:47 PM
Last Post: geokscott
  arctech_contact protocol missing open/close signals Niek 2 638 12-23-2017, 07:16 PM
Last Post: Niek
  Signal decoded - how to go on? Rustimator 3 891 10-23-2017, 07:16 PM
Last Post: curlymo
  Looking for a 433Mhz soil moisture sensor (Plug´n Play) tomtom 0 703 04-10-2017, 12:34 PM
Last Post: tomtom
  temperature, humidity sensor from china? Twain 5 1,702 11-29-2016, 06:33 PM
Last Post: pilino1234
  pilight 7 and InterTechno ITT-1500: No Receiving signal pi_invi 9 2,645 11-29-2016, 01:47 PM
Last Post: wo_rasp
  config device #1 "living", missing protocol jjlf 5 1,949 11-08-2016, 11:55 PM
Last Post: jjlf

Forum Jump:


Browsing: 1 Guest(s)