Oregon-THGR328N via RFXCOM not working with meteohub

This is intended for discussion and information about the rfxcom receiver module

Moderator: Mattk

Post Reply
wfpost
Platinum Boarder
Platinum Boarder
Posts: 588
Joined: Thu Jun 12, 2008 2:24 pm
Location: HONSOLGEN
Contact:

Oregon-THGR328N via RFXCOM not working with meteohub

Post by wfpost » Thu May 07, 2009 11:37 am

Today I got three Oregon-THGR328N sensors, that I wanted to add to my RFXCOM device.

But none of the three are shown up with meteohubs sensor list. I tried all 5 channels to no success either ...

Anything I can do to get it to work?

Additional info:
Every 60s when the red LED on the Oregon sensor lits up showing the broadcast impulse simultaneously the green LED with the back of the RFXCOM lits up also.
From that, it seems connection and communication between the THGR328N sensors and RFXCOM is working well.

Cheers,

P.S: my already connected 3-ch sensors still working w/o any problems, but none of the new THGR328N. Image

wfpost
Platinum Boarder
Platinum Boarder
Posts: 588
Joined: Thu Jun 12, 2008 2:24 pm
Location: HONSOLGEN
Contact:

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by wfpost » Thu May 07, 2009 12:33 pm

I´ve now removed and re-added all weather stations, but still the Oregon-THGR328N sensors are not working or recognized :(

Image

skyewright
Platinum Boarder
Platinum Boarder
Posts: 873
Joined: Fri Jan 25, 2008 6:27 pm
Location: Isle of Skye, Scotland

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by skyewright » Thu May 07, 2009 4:26 pm

Have you tried using the RFXCOM tool called RFreceiver?

You can use that view the data coming into Meteohub via the "serial to ethernet bridge" pass through port 5500.

There is a switch in RFreceiver to either view the data raw, or with interpretation. That should let you see if the sensors are at least getting that far...

wfpost
Platinum Boarder
Platinum Boarder
Posts: 588
Joined: Thu Jun 12, 2008 2:24 pm
Location: HONSOLGEN
Contact:

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by wfpost » Thu May 07, 2009 5:08 pm

skyewright wrote:Have you tried using the RFXCOM tool called RFreceiver?

You can use that view the data coming into Meteohub via the "serial to ethernet bridge" pass through port 5500.

There is a switch in RFreceiver to either view the data raw, or with interpretation. That should let you see if the sensors are at least getting that far...
Thanks for your reply,

I tried that, and getting attached output.
There´s this entry showing up, but it doesn´t look like my Oregon sensors. Maybe something in reach of my RFXCOM? my own VP2 or something with a neighbour?

2CC7020606C900 DIGIMAX[711]TY Digimax addr:C702 ID: 711 No Set temp available Temp:6ºC | 42,8ºF Set:9ºC | 393,8ºF Parity error on address/status SB:A Parity error on temp/set SB:4 bits=44 [file name=RFreceiver.txt size=18305]http://www.meteohub.de/joomla/images/fb ... ceiver.txt[/file]

wfpost
Platinum Boarder
Platinum Boarder
Posts: 588
Joined: Thu Jun 12, 2008 2:24 pm
Location: HONSOLGEN
Contact:

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by wfpost » Thu May 07, 2009 6:47 pm

Are those the entries representing the Oregon Sensors?

Code: Select all

07.05.2009 18:39:22= FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF1C bits=127 from SLAVE 
07.05.2009 18:39:22= FFFFFFFFFFFFFF0000001D010000FFFF bits=127 from SLAVE 
07.05.2009 18:39:22= FFFFFF00000000000000000000000000 bits=127 from SLAVE 

07.05.2009 18:40:10= FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF1B bits=127 from SLAVE 
07.05.2009 18:40:10= FFFFFFFFFFFFFF0000001B010000FFFF bits=127 from SLAVE 
07.05.2009 18:40:11= FFFFFF00000000000000000000000000 bits=127 from SLAVE 

skyewright
Platinum Boarder
Platinum Boarder
Posts: 873
Joined: Fri Jan 25, 2008 6:27 pm
Location: Isle of Skye, Scotland

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by skyewright » Thu May 07, 2009 7:08 pm

wfpost wrote:Are those the entries representing the Oregon Sensors?
That's not at all like the output I see from OS sensors.

Attached is a small sample I grabbed about a year ago with a mixture of WMR200 and WMR928 sensors. That was with a USB RFXCOM, but I doubt that makes any difference.

So far as I'm aware the VP2 should not be relevant - it broadcasts with a different protocol. [file name=rfxcom_20080509.txt size=4269]http://www.meteohub.de/joomla/images/fb ... 080509.txt[/file]

User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 5362
Joined: Mon Oct 01, 2007 10:51 pm

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by admin » Thu May 07, 2009 7:22 pm

Meteohub supports THGR328N. I have one that is recorded fine with RFXCOM

Image

The system works on the actual Meteohub version, but all 4.2x versions should behave the same for this (I have not changed that part of the code).

wfpost
Platinum Boarder
Platinum Boarder
Posts: 588
Joined: Thu Jun 12, 2008 2:24 pm
Location: HONSOLGEN
Contact:

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by wfpost » Thu May 07, 2009 7:39 pm

I´ve connected RFXCOM with my PC´s USB Port.
The RFreceiver reading looking good now:

Connected back to Ebox-4300 RFreceiver prints out rubbish, and only the 3ch sensors are recognized with meteohub!

Code: Select all

07.05.2009 19:30:12= 501A2D20772220208131F6   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,2°C | 68,36°F hum:12 Dry     bits=80 
07.05.2009 19:30:12= 501A2D20772220208131F6   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,2°C | 68,36°F hum:12 Dry     bits=80 
07.05.2009 19:30:13= 501A2D40C930180084414E   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:30:13= 501A2D40C930180084414E   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:30:21= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:30:21= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:30:24= 500A4D1008002000001C00   TEMP1[2049] THR128,THx138 CH 1 addr:08 temp:20°C | 68°F bits=80 
07.05.2009 19:30:29= 50CA2C433A601830144565   TH4[14852] THGR328 CH 3 counter:12 addr:3A temp:18,6°C | 65,48°F hum:43 Normal  bits=80 
07.05.2009 19:30:29= 50CA2C433A601830144565   TH4[14852] THGR328 CH 3 counter:12 addr:3A temp:18,6°C | 65,48°F hum:43 Normal  bits=80 
07.05.2009 19:30:53= 501A2D20772220208131F6   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,2°C | 68,36°F hum:12 Dry     bits=80 
07.05.2009 19:30:53= 501A2D20772220208131F6   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,2°C | 68,36°F hum:12 Dry     bits=80 
07.05.2009 19:30:56= 501A2D40C9321800844380   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:30:56= 501A2D40C9321800844380   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:31:00= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:31:00= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:31:12= 50CA2C53E6402590835553   TH4[58885] THGR328 CH ? = 53 counter:12 addr:E6 temp:25,4°C | 77,72°F hum:39 Dry     bits=80 
07.05.2009 19:31:12= 50CA2C53E6402590835553   TH4[58885] THGR328 CH ? = 53 counter:12 addr:E6 temp:25,4°C | 77,72°F hum:39 Dry     bits=80 
07.05.2009 19:31:34= 501A2D20772220208131F6   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,2°C | 68,36°F hum:12 Dry     bits=80 
07.05.2009 19:31:34= 501A2D20772220208131F6   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,2°C | 68,36°F hum:12 Dry     bits=80 
07.05.2009 19:31:36= 50CA2C433A601830144565   TH4[14852] THGR328 CH 3 counter:12 addr:3A temp:18,6°C | 65,48°F hum:43 Normal  bits=80 
07.05.2009 19:31:36= 50CA2C433A601830144565   TH4[14852] THGR328 CH 3 counter:12 addr:3A temp:18,6°C | 65,48°F hum:43 Normal  bits=80 
07.05.2009 19:31:54= 500A4D1008901900002D00   TEMP1[2049] THR128,THx138 CH 1 addr:08 temp:19,9°C | 67,82°F bits=80 
07.05.2009 19:32:15= 501A2D20771220208130CC   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,1°C | 68,18°F hum:12 Dry     bits=80 
07.05.2009 19:32:15= 501A2D20771220208130CC   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,1°C | 68,18°F hum:12 Dry     bits=80 
07.05.2009 19:32:18= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:32:18= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:32:22= 501A2D40C9321800844380   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:32:23= 50CA2C53E6402590835553   TH4[58885] THGR328 CH ? = 53 counter:12 addr:E6 temp:25,4°C | 77,72°F hum:39 Dry     bits=80 
07.05.2009 19:32:43= 50CA2C433A601830144565   TH4[14852] THGR328 CH 3 counter:12 addr:3A temp:18,6°C | 65,48°F hum:43 Normal  bits=80 
07.05.2009 19:32:43= 50CA2C433A601830144565   TH4[14852] THGR328 CH 3 counter:12 addr:3A temp:18,6°C | 65,48°F hum:43 Normal  bits=80 
07.05.2009 19:32:56= 501A2D20771220208130CC   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,1°C | 68,18°F hum:12 Dry     bits=80 
07.05.2009 19:32:56= 501A2D20771220208130CC   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,1°C | 68,18°F hum:12 Dry     bits=80 
07.05.2009 19:32:57= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:32:57= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:33:05= 501A2D40C9321800844380   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:33:05= 501A2D40C9321800844380   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:33:34= 50CA2C53E6402590835553   TH4[58885] THGR328 CH ? = 53 counter:12 addr:E6 temp:25,4°C | 77,72°F hum:39 Dry     bits=80 
07.05.2009 19:33:34= 50CA2C53E6402590835553   TH4[58885] THGR328 CH ? = 53 counter:12 addr:E6 temp:25,4°C | 77,72°F hum:39 Dry     bits=80 
07.05.2009 19:33:36= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:33:36= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:33:37= 501A2D20771220208130CC   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,1°C | 68,18°F hum:12 Dry     bits=80 
07.05.2009 19:33:37= 501A2D20771220208130CC   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:20,1°C | 68,18°F hum:12 Dry     bits=80 
07.05.2009 19:33:48= 501A2D40C9321800844380   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:33:48= 501A2D40C9321800844380   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:40 Dry     bits=80 
07.05.2009 19:33:50= 50CA2C433A60184014460E   TH4[14852] THGR328 CH 3 counter:12 addr:3A temp:18,6°C | 65,48°F hum:44 Normal  bits=80 
07.05.2009 19:33:50= 50CA2C433A60184014460E   TH4[14852] THGR328 CH 3 counter:12 addr:3A temp:18,6°C | 65,48°F hum:44 Normal  bits=80 
07.05.2009 19:34:15= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 
07.05.2009 19:34:15= 50EA4C103A901060B30600   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:10,9°C | 51,62°F bits=80 

User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 5362
Joined: Mon Oct 01, 2007 10:51 pm

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by admin » Thu May 07, 2009 8:01 pm

These are the bytes Meteohub reads for my thgr-328n sensor:

Code: Select all

(0:50) (0:9a) (0:cc) (0:13) (0:77) (0:21) (0:24) (0:90) (0:83) (0:50) (0:7e) [checksum 50:50] 
Thu May  7 19:49:57 2009
station 0 (RFXCOM), thermo hygro sensor, raw id: 0x9acc77, id: 6, temp 24.2°C, hum 39%, dew 9.4°C
The model id of your thgr328 seems to be 0xca2c while mine is 0x9acc (is that the difference of 328 vs 328n... I don't kow). I will add you sensor model id to Meteohub and send you a test version, if you drop me a note at "info(at)meteohub.de".

Acki
Junior Boarder
Junior Boarder
Posts: 23
Joined: Thu Jan 24, 2008 11:27 pm
Location: Germany

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by Acki » Fri May 08, 2009 11:19 pm

Hi,

try only one of them.

They are built to deliver a time-signal to their os-station (built-in rf-clock).

So 3 sensors sent a signal at the same moment...

Would be too much for good old rfxcom-unit

wfpost
Platinum Boarder
Platinum Boarder
Posts: 588
Joined: Thu Jun 12, 2008 2:24 pm
Location: HONSOLGEN
Contact:

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by wfpost » Sat May 09, 2009 7:08 pm

skyewright wrote:
wfpost wrote:Are those the entries representing the Oregon Sensors?
That's not at all like the output I see from OS sensors.
Now I know why the RFreceiver output wasn´t correct:
Yesterday the day1 min/max values for th0, sol and uv disappeared from the list of variables. Data re-processing didn´t help. The variables kept missing.

Then I removed all the weather station and re-added all of them and the missing values returned.

What I saw now, was this:
If RFXCOM is the first weather station then
RFreceiver prints out correct records for the connected sensors:



Code: Select all

08.05.2009 23:21:37= 501A2D2077101370043090   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:13,1°C | 55,58°F hum:47 Normal  bits=80 
08.05.2009 23:21:37= 501A2D2077101370043090   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:13,1°C | 55,58°F hum:47 Normal  bits=80 
08.05.2009 23:22:03= 78CA2C53E6901720054EDBFFFF9559A6   TH4[58885] THGR328 CH ? = 53 counter:12 addr:E6 temp:17,9°C | 64,22°F hum:52 Normal  bits=120 
08.05.2009 23:22:10= 50EA4C103A501240C30A00   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:12,5°C | 54,5°F bits=80 
08.05.2009 23:22:10= 50EA4C103A501240C30A00   TEMP2[14849] THN132N,THWR288,AW131 CH 1 addr:3A temp:12,5°C | 54,5°F bits=80 
08.05.2009 23:22:11= 501A2D40C9301800053A06   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:50 Normal  bits=80 
08.05.2009 23:22:12= 501A2D40C9301800053A06   TH1[51460] THGN122N,THGR122NX,THGR228N,THGR268 CH 3 addr:C9 temp:18,3°C | 64,94°F hum:50 Normal  bits=80 
08.05.2009 23:22:18= 501A2D2077101370043090   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:13,1°C | 55,58°F hum:47 Normal  bits=80 
08.05.2009 23:22:18= 501A2D2077101370043090   TH1[30466] THGN122N,THGR122NX,THGR228N,THGR268 CH 2 addr:77 temp:13,1°C | 55,58°F hum:47 Normal  bits=80 


But in case the VP2 is assigned the first ID for weather stations then the RFReceiver ourput reads like this:


Code: Select all

09.05.2009 00:58:11= 000908140001640000020200FF0A000A           noise or an unknown data packet received 
09.05.2009 00:58:12= FF0AFF0AFF0AFF0AFF0AFFBE41DA0101 bits=127 from SLAVE 
09.05.2009 00:58:12= C7C4 Buffer flushed due to timeout
09.05.2009 00:58:13= 4C4F4F14005E00B8759B02 bits=76 
09.05.2009 00:58:13= 330E020101EB00FF           noise or an unknown data packet received bits=51 
09.05.2009 00:58:13= FFFFFFFFFFFFFFFFFFFFFFFFFFFF5EFF bits=127 from SLAVE 
09.05.2009 00:58:13= FFFFFFFFFFFF00000000001B00095400 bits=127 from SLAVE 
09.05.2009 00:58:14= 00A300CF0200006200E802FFFFFFFFFF           noise or an unknown data packet received 
09.05.2009 00:58:14= FFFF0000000000000000000000000000 bits=127 from SLAVE 
09.05.2009 00:58:14= 00000001F70208012202F9070A0DC720           noise or an unknown data packet received 
09.05.2009 00:58:15= 4C4F4F14005E00B8759B02 bits=76 
09.05.2009 00:58:15= 330E020101EB00FF           noise or an unknown data packet received bits=51 
09.05.2009 00:58:15= FFFFFFFFFFFFFFFFFFFFFFFFFFFF5EFF bits=127 from SLAVE 
09.05.2009 00:58:15= FFFFFFFFFFFF00000000001B00095400 bits=127 from SLAVE 
09.05.2009 00:58:16= 00A300CF0200006200E802FFFFFFFFFF           noise or an unknown data packet received 
09.05.2009 00:58:16= FFFF0000000000000000000000000000 bits=127 from SLAVE 
09.05.2009 00:58:16= 00000001F70208012202F9070A0DC720           noise or an unknown data packet received 



Could it be that the 1:1 copy feature on port 5500 is still considering an one station operating mode and does only transmit the USB-data from the 1st weather station to port 5500.

Then it would be pretty much clear that RFreceiver isn´t capable of reading the VP2 data?



Image

User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 5362
Joined: Mon Oct 01, 2007 10:51 pm

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by admin » Sat May 09, 2009 7:30 pm

In your setup where VP2 is station 0 and RFXCOM is station 1 data of VP2 will be reflected on port 5500 and RFXCOM data will be reflected on port 5501.

Or to say it more general, you will get data of weather station number X on port 5500 + X.

wfpost
Platinum Boarder
Platinum Boarder
Posts: 588
Joined: Thu Jun 12, 2008 2:24 pm
Location: HONSOLGEN
Contact:

Re:Oregon-THGR328N via RFXCOM not working with meteohub

Post by wfpost » Sat May 09, 2009 7:34 pm

admin wrote:In your setup where VP2 is station 0 and RFXCOM is station 1 data of VP2 will be reflected on port 5500 and RFXCOM data will be reflected on port 5501.

Or to say it more general, you will get data of weather station number X on port 5500 + X.
I see, thanks. That works perfect!

ZPC2THLgate
Fresh Boarder
Fresh Boarder
Posts: 3
Joined: Tue Jul 16, 2013 11:13 am

Re: Oregon-THGR328N via RFXCOM not working with meteohub

Post by ZPC2THLgate » Fri Jul 19, 2013 9:07 am

That might help you see what is going on.

Post Reply