Oregon sensorer

Moderator: Telldus

Post Reply
esse
Posts: 2
Joined: Fri Mar 17, 2023 9:45 am

Oregon sensorer

Post by esse »

Har bl.a. några Oregon sensorer och en TellStick Net. Nu vill jag logga temp och fukt och lagra det i en RRDB så att man såsmånigom kan skriva ut grafer.
Att hitta udp paketen på nätet är inte så svårt men det är RAW data. Var kan jag hitta hur man tyder data som ser ut såhär.

esse@Track:~$ sudo tcpdump -i eth0 -A -n 'src 192.168.150.156'
[sudo] password for esse:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
18:00:27.711709 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 77
E..i....d.b..............U..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliEA4Cs4:datai10271220D0B2ss
18:00:27.883996 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 77
E..i....d.b..............U..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliEA4Cs4:datai10271220D0B2ss
18:00:38.314474 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.b..............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002360443D32ss
18:00:38.554118 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.b..............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002360443D32ss
18:00:52.583572 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.b..............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai10F5011680063B40ss
18:00:52.825463 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.b..............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai10F5011680063B40ss
18:01:06.712303 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 77
E..i....d.b..............U..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliEA4Cs4:datai10272220E022ss
18:01:06.884531 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 77
E..i....d.b..............U..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliEA4Cs4:datai10272220E022ss
18:01:12.036086 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 66
E..^....d.b..............J..7:RawDatah5:class6:sensor8:protocolA:fineoffset4:datai4050A2FF3Css
18:01:19.313878 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.b..............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002360443D32ss
18:01:19.553465 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.b..............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002360443D32ss
18:01:31.582900 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.b~.............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai10F5011680063B40ss
18:01:31.824560 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.b|.............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai10F5011680063B40ss
18:01:45.711855 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 77
E..i....d.b}.............U..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliEA4Cs4:datai10273220F052ss
18:01:45.884379 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 77
E..i....d.b{.............U..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliEA4Cs4:datai10273220F052ss
18:02:00.038538 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 66
E..^....d.b..............J..7:RawDatah5:class6:sensor8:protocolA:fineoffset4:datai4050A2FF3Css
18:02:00.366362 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.bq.............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002360443D32ss
18:02:00.552663 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.bo.............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002360443D32ss
18:02:10.582097 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.bm.............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai10F5011680063B40ss
18:02:10.823660 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.bk.............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai10F5011680063B40ss
18:02:24.712781 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 77
E..i....d.bl.............U..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliEA4Cs4:datai102742200073ss
18:02:24.885386 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 77
E..i....d.bj.............U..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliEA4Cs4:datai102742200073ss
18:02:41.312686 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.bc.............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002360443D32ss
18:02:41.551953 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 81
E..m....d.ba.............Y..7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002360443D32ss
18:02:48.041019 IP 192.168.150.156.4098 > 0.0.0.0.0: UDP, length 66
E..^....d.bn.............J..7:RawDatah5:class6:sensor8:protocolA:fineoffset4:datai4050A2FF3Css
esse
Posts: 2
Joined: Fri Mar 17, 2023 9:45 am

Re: Oregon sensorer

Post by esse »

Det löste sig så småningom

Här är ett exempel läst från vänster till höger

7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002460443E55ss

1A2D >> modell THGN132N Termo-hygro sensor
20 >> Chanel. 10=1, 20=2, 40=3
F9 >> ID. 0xF9 = 249
246 >> Temp. 246/10 = 24.6 grader
0 >> Plus/Minus 0= plusgrader, <>0 = minusgrader
43 >> Humidity 43%
GummansGubbe
Posts: 4
Joined: Fri Mar 17, 2023 9:45 am

Re: Oregon sensorer

Post by GummansGubbe »

Fikk akkurat en slik sensor selv, protokollen er beskrevet i "#source:telldus-core/service/ProtocolOregon.cpp"
Her har du tallene fra din streng:

Code: Select all

7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai20F9002460443E55ss
checksum2  85
checksum1  62
hum1  4
neg  0
hum2  6
temp2  4
temp1  2
temp3  0
rollingcode  249
channel  2
battery  0
checksum  62
temp/hum  24.0 / 46.0
Post Reply