• 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
problem with alecto_wx500 protocol (pilight V7)
#11
Yes, seems fine.
 
Reply
#12
Hello, (now hopefully at the right place)

I just switched to the nightly build to get support for the 4.9 kernel.

Used version: v7.0-231-ge4b154d

Now I don't get any temperatures from my alecto_wx500 device.
It worked without problems using the last stable build.

There is no output, if I use pilight-receive.

If I use "pilight-daemon -D", I get:

Code:
[Sep 12 19:09:03:792239] pilight-daemon: DEBUG: cpu: 0.270436%
[Sep 12 19:09:04:204031] pilight-daemon: DEBUG: possible alecto_wx500 protocol
[Sep 12 19:09:04:204159] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:204196] pilight-daemon: DEBUG: caught minimum # of repeats 1 of alecto_wx500
[Sep 12 19:09:04:204228] pilight-daemon: DEBUG: called alecto_wx500 parseRaw()
[Sep 12 19:09:04:204276] pilight-daemon: DEBUG: possible alecto_ws1700 protocol
[Sep 12 19:09:04:204305] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:204336] pilight-daemon: DEBUG: caught minimum # of repeats 1 of alecto_ws1700
[Sep 12 19:09:04:204365] pilight-daemon: DEBUG: called alecto_ws1700 parseRaw()
[Sep 12 19:09:04:330514] pilight-daemon: DEBUG: possible alecto_wx500 protocol
[Sep 12 19:09:04:330590] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:330623] pilight-daemon: DEBUG: caught minimum # of repeats 2 of alecto_wx500
[Sep 12 19:09:04:330654] pilight-daemon: DEBUG: called alecto_wx500 parseRaw()
[Sep 12 19:09:04:330695] pilight-daemon: DEBUG: possible alecto_ws1700 protocol
[Sep 12 19:09:04:330724] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:330753] pilight-daemon: DEBUG: caught minimum # of repeats 2 of alecto_ws1700
[Sep 12 19:09:04:330782] pilight-daemon: DEBUG: called alecto_ws1700 parseRaw()
[Sep 12 19:09:04:456982] pilight-daemon: DEBUG: possible alecto_wx500 protocol
[Sep 12 19:09:04:457057] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:457094] pilight-daemon: DEBUG: caught minimum # of repeats 3 of alecto_wx500
[Sep 12 19:09:04:457125] pilight-daemon: DEBUG: called alecto_wx500 parseRaw()
[Sep 12 19:09:04:457165] pilight-daemon: DEBUG: possible alecto_ws1700 protocol
[Sep 12 19:09:04:457193] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:457219] pilight-daemon: DEBUG: caught minimum # of repeats 3 of alecto_ws1700
[Sep 12 19:09:04:457255] pilight-daemon: DEBUG: called alecto_ws1700 parseRaw()
[Sep 12 19:09:04:583432] pilight-daemon: DEBUG: possible alecto_wx500 protocol
[Sep 12 19:09:04:583508] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:583545] pilight-daemon: DEBUG: caught minimum # of repeats 4 of alecto_wx500
[Sep 12 19:09:04:583575] pilight-daemon: DEBUG: called alecto_wx500 parseRaw()
[Sep 12 19:09:04:583617] pilight-daemon: DEBUG: possible alecto_ws1700 protocol
[Sep 12 19:09:04:583645] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:583671] pilight-daemon: DEBUG: caught minimum # of repeats 4 of alecto_ws1700
[Sep 12 19:09:04:583703] pilight-daemon: DEBUG: called alecto_ws1700 parseRaw()
[Sep 12 19:09:04:709897] pilight-daemon: DEBUG: possible alecto_wx500 protocol
[Sep 12 19:09:04:709975] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:710009] pilight-daemon: DEBUG: caught minimum # of repeats 5 of alecto_wx500
[Sep 12 19:09:04:710064] pilight-daemon: DEBUG: called alecto_wx500 parseRaw()
[Sep 12 19:09:04:710108] pilight-daemon: DEBUG: possible alecto_ws1700 protocol
[Sep 12 19:09:04:710141] pilight-daemon: DEBUG: recevied pulse length of 261
[Sep 12 19:09:04:710171] pilight-daemon: DEBUG: caught minimum # of repeats 5 of alecto_ws1700
[Sep 12 19:09:04:710200] pilight-daemon: DEBUG: called alecto_ws1700 parseRaw()
[Sep 12 19:09:04:836362] pilight-daemon: DEBUG: possible alecto_wx500 protocol
[Sep 12 19:09:04:836437] pilight-daemon: DEBUG: recevied pulse length of 262
[Sep 12 19:09:04:836469] pilight-daemon: DEBUG: caught minimum # of repeats 6 of alecto_wx500
[Sep 12 19:09:04:836502] pilight-daemon: DEBUG: called alecto_wx500 parseRaw()
[Sep 12 19:09:04:836547] pilight-daemon: DEBUG: possible alecto_ws1700 protocol
[Sep 12 19:09:04:836579] pilight-daemon: DEBUG: recevied pulse length of 262
[Sep 12 19:09:04:836608] pilight-daemon: DEBUG: caught minimum # of repeats 6 of alecto_ws1700
[Sep 12 19:09:04:836640] pilight-daemon: DEBUG: called alecto_ws1700 parseRaw()
[Sep 12 19:09:06:792510] pilight-daemon: DEBUG: cpu: 0.927071%

So the alecto_wx500 protocol is detected, but can not be parsed?

The output from pilight-debug is:
Code:
--[RESULTS]--

time:           Tue Sep 12 21:10:27 2017
hardware:       433gpio
pulse:          15
rawlen:         74
pulselen:       261

Raw code:
672 3854 515 4005 514 1912 521 1935 509 1922 514 4005 514 1927 512 1932 518 1920 508 1933 510 4017 503 4001 516 1936 500 1935 507 1934 508 4012 509 4004 515 1927 515 4006 503 4015 509 1930 504 1954 504 1920 505 1940 499 4019 501 1932 506 1943 501 1941 498 1940 512 4002 505 4010 506 1938 502 1940 503 4015 505 1936 502 2059 504 8892
--[RESULTS]--

time:           Tue Sep 12 21:10:27 2017
hardware:       433gpio
pulse:          15
rawlen:         74
pulselen:       262

Raw code:
503 4013 502 4004 514 1931 504 1938 501 1936 504 4016 514 1930 501 1942 502 1937 493 1954 486 4025 494 4025 494 1942 496 1956 490 1943 505 4010 494 4032 491 1945 495 4032 485 4029 489 1942 498 1954 492 1945 490 1951 488 4028 494 1954 483 1952 494 1945 495 1946 494 4024 493 4021 495 1950 490 1954 486 4039 483 1944 493 2090 473 8911
--[RESULTS]--

time:           Tue Sep 12 21:10:27 2017
hardware:       433gpio
pulse:          15
rawlen:         74
pulselen:       261

Raw code:
502 4011 504 4014 504 1935 504 1944 496 1956 482 4018 499 1949 494 1950 488 1952 485 1954 485 4033 491 4019 495 1953 496 1949 486 1953 495 4022 486 4036 490 1946 486 4026 502 4017 488 1952 488 1954 485 1963 480 1956 485 4030 488 1961 479 1953 491 1954 483 1960 483 4033 486 4025 495 1948 494 1952 482 4035 487 1947 493 2082 481 8907
--[RESULTS]--

time:           Tue Sep 12 21:10:27 2017
hardware:       433gpio
pulse:          15
rawlen:         74
pulselen:       261

Raw code:
500 4015 495 4016 502 1940 497 1946 493 1952 493 4023 495 1945 492 1950 492 1953 483 1954 485 4031 498 4018 493 1949 491 1953 485 1965 481 4029 493 4031 484 1954 486 4029 493 4027 485 1962 483 1954 484 1960 478 1959 482 4034 484 1956 484 1959 485 1961 478 1955 485 4047 471 4034 489 1953 484 1959 480 4032 485 1955 484 2082 486 8904

Is this a known problem with the nightly build?

Ciao

MiK
 
Reply
#13
Hello,

Does nobody know anything about this problem? This thread was moved, so I think it is at the right place now. Correct?

Ciao

MiK
 
Reply
#14
Please provide full debugging output as described in the protocol forum readme.
 
Reply
#15
Sorry, if I missed something. What additional debug output do you need, which is missing in post #12?
 
Reply
#16
Can somebody tell me, which additional data you need?
 
Reply
#17
I found a bug in the alecto_wx500.c on Github
That is the reason why I dint't receive my weather station data for a long time.

Because I don't know where to report it there, I'm trying to do it here.

In line 88 the end value of binToDec should be 35 an not 36.

Code:
86        n7=binToDec(binary, 28, 31);
87        n6=binToDec(binary, 24, 27);
88        n8=binToDec(binary, 32, 36); // <---------

Comparing the other lines you can see that each number consists of 4 bits (nibble)
When you correct the value to 35 the checksum matches and the protocol works for me.

Could someone confirm my suggestion?!
 
Reply
#18
If you can do a PR on github, i can integrate your fix.
 
Reply
#19
(04-12-2018, 05:27 PM)curlymo Wrote: If you can do a PR on github, i can integrate your fix.


Done! I had to read something about how it works, but that was easier than expected. Nice! Wink
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight-control TML 13 295 05-27-2020, 07:51 AM
Last Post: curlymo
  API Requests by HTTP from other devices fore use in pilight scootermacro 2 140 05-10-2020, 08:19 AM
Last Post: scootermacro
  pilight-send seems successful but doesn't actually send RF signal ayeyebrazov 37 1,989 03-31-2020, 01:02 PM
Last Post: curlymo
  pilight 8.1.5 not working on Raspberry pi after reboot beejayf 4 486 03-08-2020, 12:14 AM
Last Post: beejayf
  pilight cpu usage possibly associated with noticeable sluggishness? hepcat72 4 513 01-28-2020, 08:02 PM
Last Post: hepcat72
  apt.pilight.org stable Release' is not signed. thomasol 2 636 01-23-2020, 11:34 PM
Last Post: thomasol
  pilight and SIGNALduino cc1101 Caleus 0 429 01-19-2020, 09:13 AM
Last Post: Caleus
  filter stopped working after update to pilight 8.1.5 zlin50 19 1,308 01-03-2020, 02:15 PM
Last Post: curlymo
Question [Solved] Openweathermap with pilight 7.0-40 doesn't work Seebueb 2 502 01-01-2020, 06:45 PM
Last Post: Seebueb
  [Solved] Strange receive problem with 433Mhz Receiver and pilight 8.1.5 vanillaice30 15 1,393 12-18-2019, 11:09 AM
Last Post: vanillaice30

Forum Jump:


Browsing: 1 Guest(s)