• 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

TFA 30.3208.02
Attached there are the log dbg_21 .. dbg_25

Attached Files
.txt   dbg_21.txt (Size: 1.82 KB / Downloads: 2)
.txt   dbg_22.txt (Size: 765 bytes / Downloads: 1)
.txt   dbg_23.txt (Size: 764 bytes / Downloads: 0)
.txt   dbg_24.txt (Size: 415 bytes / Downloads: 0)
.txt   dbg_25.txt (Size: 1.21 KB / Downloads: 0)
Attached there are the log dbg_31 .. dbg_35

Attached Files
.txt   dbg_31.txt (Size: 1.65 KB / Downloads: 1)
.txt   dbg_32.txt (Size: 2.54 KB / Downloads: 0)
.txt   dbg_33.txt (Size: 294 bytes / Downloads: 0)
.txt   dbg_34.txt (Size: 334 bytes / Downloads: 0)
.txt   dbg_35.txt (Size: 1.04 KB / Downloads: 1)
i use the same sensors and can read them out  successfully with this tool:

github: alex-konshin/f007thrpi

I think the TFA 30.3208.02 is identical to the F007TH.  
is there now a solution for this sensor, so that I can use it with pilight?

best regards,
I implemented a solution in the tfa2017 branch of github.com/behrisch/pilight. It is currently a pull request under review but you can give it a try already. I am not sure about the name though. I named it tfa2017 because the tfa30 was already taken but the number still starts with TFA 30 and I did not want to use the full number as the name. I chose the 2017 because there is a revision 08/17 printed on the device. Do you think we should name it F007TH because that seems to be the original implementation? But then TFA users will have a harder time finding it. Or is there a better name?

Forum Jump:

Browsing: 1 Guest(s)