• 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
tfa30 parseRaw failure with Auriol
#1
Hello,
I have an Auriol weather station.

The outside sensor is sending data which pilight receives as tfa30 pulses.

However, it seems not to be able to decode it.

See log:

Code:
[Jan 02 10:52:35:445243] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:35:445308] pilight-daemon: DEBUG: recevied pulse length of 1802
[Jan 02 10:52:35:445349] pilight-daemon: DEBUG: caught minimum # of repeats 1 of tfa30
[Jan 02 10:52:35:445395] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:35:546249] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:35:546522] pilight-daemon: DEBUG: recevied pulse length of 1797
[Jan 02 10:52:35:546617] pilight-daemon: DEBUG: caught minimum # of repeats 2 of tfa30
[Jan 02 10:52:35:546700] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:35:647333] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:35:647435] pilight-daemon: DEBUG: recevied pulse length of 1801
[Jan 02 10:52:35:647514] pilight-daemon: DEBUG: caught minimum # of repeats 3 of tfa30
[Jan 02 10:52:35:647595] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:35:748467] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:35:748519] pilight-daemon: DEBUG: recevied pulse length of 1801
[Jan 02 10:52:35:748560] pilight-daemon: DEBUG: caught minimum # of repeats 4 of tfa30
[Jan 02 10:52:35:748615] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:35:849596] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:35:849644] pilight-daemon: DEBUG: recevied pulse length of 1801
[Jan 02 10:52:35:849692] pilight-daemon: DEBUG: caught minimum # of repeats 5 of tfa30
[Jan 02 10:52:35:849723] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:35:950737] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:35:951006] pilight-daemon: DEBUG: recevied pulse length of 1801
[Jan 02 10:52:35:951093] pilight-daemon: DEBUG: caught minimum # of repeats 6 of tfa30
[Jan 02 10:52:35:951324] pilight-daemon: DEBUG: called tfa30 parseRaw()
[ Jan 02 10:52:36:51863] pilight-daemon: DEBUG: possible tfa30 protocol
[ Jan 02 10:52:36:51965] pilight-daemon: DEBUG: recevied pulse length of 1801
[ Jan 02 10:52:36:52046] pilight-daemon: DEBUG: caught minimum # of repeats 7 of tfa30
[ Jan 02 10:52:36:52301] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:36:152988] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:36:153089] pilight-daemon: DEBUG: recevied pulse length of 1801
[Jan 02 10:52:36:153169] pilight-daemon: DEBUG: caught minimum # of repeats 8 of tfa30
[Jan 02 10:52:36:153430] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:36:324619] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:36:324669] pilight-daemon: DEBUG: recevied pulse length of 3874
[Jan 02 10:52:36:324707] pilight-daemon: DEBUG: caught minimum # of repeats 9 of tfa30
[Jan 02 10:52:36:324742] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:36:632552] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:36:632843] pilight-daemon: DEBUG: recevied pulse length of 1215
[Jan 02 10:52:36:632928] pilight-daemon: DEBUG: caught minimum # of repeats 10 of tfa30
[Jan 02 10:52:36:633160] pilight-daemon: DEBUG: called tfa30 parseRaw()
[Jan 02 10:52:37:876401] pilight-daemon: DEBUG: possible tfa30 protocol
[Jan 02 10:52:37:876481] pilight-daemon: DEBUG: recevied pulse length of 1840
[Jan 02 10:52:37:876512] pilight-daemon: DEBUG: caught minimum # of repeats 1 of tfa30
[Jan 02 10:52:37:876545] pilight-daemon: DEBUG: called tfa30 parseRaw()


How can I debug it further?

Best Regards,

Petr
 
Reply
#2
It seems that your device isn't supported by existing protocols. It tries to decode it using TFA30, but fails eventually. If that conclusion is not correct, i would love to see the changes necessary for it to work.
 
Reply
#3
It seems that these are the pulse trains sent by the sensors. They all seem to have a similar structure. What can I do with them? How to start interpreting them?


Code:
time:        Wed Jan  2 11:14:09 2019
hardware:    433gpio
pulse:        34
rawlen:        88
pulselen:    1739

Raw code:
340 836 877 835 867 841 866 842 258 600 622 232 624 228 261 598 626 226 252 600 624 233 258 602 248 600 256 598 621 236 620 233 256 600 632 222 255 599 627 233 250 597 257 596 624 232 256 600 257 599 254 601 252 603 252 603 617 237 250 604 621 238 617 231 618 239 616 237 252 604 618 238 260 594 250 604 250 605 250 601 618 236 252 604 254 607 246 59142
--[RESULTS]--

time:        Wed Jan  2 11:14:09 2019
hardware:    433gpio
pulse:        34
rawlen:        88
pulselen:    1801

Raw code:
340 835 871 838 870 839 869 840 258 597 625 230 625 229 257 603 619 233 254 600 620 237 252 602 253 599 256 600 622 228 623 233 255 599 624 231 257 599 627 232 250 599 257 600 620 234 254 597 254 602 254 602 252 605 253 606 611 235 253 604 620 233 624 234 619 232 619 237 250 604 618 244 244 602 256 600 253 602 252 599 621 234 251 603 253 605 252 61244
--[RESULTS]--

time:        Wed Jan  2 11:14:10 2019
hardware:    433gpio
pulse:        34
rawlen:        88
pulselen:    1801

Raw code:
344 836 870 838 869 840 869 838 261 596 624 230 625 232 257 609 610 230 257 601 625 229 256 601 251 601 253 602 623 226 628 231 256 597 625 231 254 602 625 229 253 600 257 597 627 225 255 601 254 603 252 601 256 603 252 603 618 233 253 603 618 238 615 234 620 236 621 236 251 606 616 243 245 603 251 604 251 599 260 596 619 238 251 602 252 607 247 61248
--[RESULTS]--

time:        Wed Jan  2 11:14:10 2019
hardware:    433gpio
pulse:        34
rawlen:        88
pulselen:    2292

Raw code:
341 836 870 838 867 840 871 840 259 602 621 228 631 224 257 596 623 229 261 597 624 233 257 602 249 597 257 599 624 227 625 232 256 603 619 233 256 595 624 237 253 600 255 595 625 231 259 600 251 600 254 602 253 600 256 602 620 232 253 603 617 236 619 238 618 233 619 236 255 601 619 239 247 602 253 602 252 603 253 602 616 238 252 601 253 604 250 77930
--[RESULTS]--

--[RESULTS]--

time:        Wed Jan  2 11:22:02 2019
hardware:    433gpio
pulse:        34
rawlen:        88
pulselen:    1801

Raw code:
333 840 866 848 861 839 870 840 254 603 617 237 620 234 253 601 620 238 252 599 621 235 251 614 249 598 255 598 622 231 624 231 252 606 252 602 252 601 620 239 250 602 251 603 619 239 249 604 250 599 255 604 250 605 251 608 610 240 615 240 249 603 619 235 620 234 253 603 637 223 245 611 609 236 619 242 612 237 251 607 246 609 244 610 247 603 252 61258
--[RESULTS]--

time:        Wed Jan  2 11:22:03 2019
hardware:    433gpio
pulse:        34
rawlen:        91
pulselen:    1801

Raw code:
154 2978 336 152 685 863 846 869 842 867 842 256 596 625 230 628 223 259 602 618 238 252 603 618 233 251 607 252 599 257 595 624 233 619 235 254 603 249 607 249 601 623 238 251 597 254 603 616 239 251 605 251 605 247 602 255 601 256 604 615 233 621 236 251 601 615 239 620 236 250 604 619 239 248 611 611 233 626 232 618 236 253 603 251 602 252 603 248 608 251 61254
 
Reply
#4
I would advice you to read similar topics about protocol decoding or pilight weather station manual pages on how it was done before.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  tfa30 temperature-offset not working wseifert 0 203 04-29-2018, 06:12 PM
Last Post: wseifert

Forum Jump:


Browsing: 1 Guest(s)