Oregon OSV3 protocol - wrong ID

Post here about devices that are not yet or not fully supported

Moderators: rtenklooster, Voyager, BertB, Stuntteam

Post Reply
Message
Author
Synthex
New user
Posts: 2
Joined: 02 Feb 2017, 23:25

Oregon OSV3 protocol - wrong ID

#1 Post by Synthex » 02 Feb 2017, 23:43

Hello,

I use several Oregon Scientific THGR810 sensor.

The ID that is returned always starts with 28,
and the choice of the channel (4 switches) is not available in the frame.

For example :
20;18;Oregon TempHygro;ID=28E8;TEMP=006a;HUM=84;HSTATUS=3;BAT=OK;
20;1A;Oregon TempHygro;ID=28F5;TEMP=00c9;HUM=50;HSTATUS=1;BAT=OK;
20;26;Oregon TempHygro;ID=28FA;TEMP=00ba;HUM=53;HSTATUS=0;BAT=OK;
20;2A;Oregon TempHygro;ID=28FA;TEMP=00c1;HUM=55;HSTATUS=0;BAT=OK;

The last two sensors have the same id, while they are two different sensors ...

Could you investigate this bug?
Thank you in advance!

Best Regards,
Antoine

User avatar
Stuntteam
Site Beheer
Posts: 787
Joined: 27 Jan 2016, 16:46

Re: Oregon OSV3 protocol - wrong ID

#2 Post by Stuntteam » 03 Feb 2017, 00:39

I have send you a mail..
-=# RFLink Gateway Development Team #=-
Introduction: http://www.nemcon.nl/blog2/
Generic Support forum: http://www.esp8266.nu/forum/viewforum.php?f=8

Synthex
New user
Posts: 2
Joined: 02 Feb 2017, 23:25

Re: Oregon OSV3 protocol - wrong ID

#3 Post by Synthex » 03 Feb 2017, 08:11

Here are frames.

For each :
1) rfxcom frame
2) rfxcom decoded
3) rflink pulses
4) rflink decoded

----------------------------------------------------------------------------------

0A520221FA0200BE390069

Packettype = TEMP_HUM
subtype = TH2 - THGN800,TGHN801,THGR810
channel 2
Sequence nbr = 33
ID = 64002 (FA02)
Temperature = 19 °C
Humidity = 57
Status = Normal
Signal level = 6 -72dBm
Battery = OK

20;C4;DEBUG;Pulses=178;Pulses(uSec)=30,420,420,420,420,390,420,390,420,420,420,420,420,390,420,420,390,420,420,420,420,420,420,390,420,420,420,390,420,390,420,420,390,420,420,420,420,420,420,390,420,390,420,420,420,420,420,900,900,900,900,390,420,420,390,420,390,420,390,900,420,390,420,390,900,900,900,900,420,390,420,390,420,390,900,900,420,390,900,900,420,390,420,390,900,900,900,420,390,420,390,420,390,420,420,900,420,390,420,390,900,900,420,390,420,390,420,390,930,900,420,390,900,420,390,900,420,390,420,390,420,390,420,390,420,390,420,390,900,390,420,420,420,900,930,900,900,900,420,390,420,390,420,390,420,390,420,390,900,420,390,900,900,900,900,900,420,390,420,390,420,390,420,390,420,390,420,390,420,390,420,390,420,390,420,390,420,6990;

20;C5;Oregon TempHygro;ID=28FA;TEMP=00be;HUM=57;HSTATUS=0;BAT=OK;

----------------------------------------------------------------------------------

0A520222E803004C580369

Packettype = TEMP_HUM
subtype = TH2 - THGN800,TGHN801,THGR810
channel 3
Sequence nbr = 34
ID = 59395 (E803)
Temperature = 7,6 °C
Humidity = 88
Status = Wet
Signal level = 6 -72dBm
Battery = OK

20;C6;DEBUG;Pulses=178;Pulses(uSec)=480,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,840,930,840,900,360,420,360,420,360,420,360,420,870,420,360,420,360,900,840,900,870,420,360,420,360,420,360,900,870,900,360,420,840,420,360,420,360,420,360,420,360,900,870,900,360,420,360,420,840,420,360,420,360,420,360,420,360,930,360,420,870,900,360,420,360,420,870,420,360,420,390,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,900,840,420,360,420,360,900,840,420,360,900,360,420,360,420,360,420,360,420,360,420,360,420,840,900,870,420,360,420,360,900,360,420,840,420,360,420,360,420,360,270,6990;

20;C7;Oregon TempHygro;ID=28E8;TEMP=004c;HUM=88;HSTATUS=3;BAT=OK;

----------------------------------------------------------------------------------

115A020488C20000000436000151594C7A79

Packettype = ENERGY
subtype = ELEC3 - OWL CM180
Sequence nbr = 4
ID = 35010 (88C2)
Count = 0
Instant usage = 1078 Watt
total usage = 25304579,5 Wh
Signal level = 7 -64dBm
Battery = OK

20;6D;DEBUG;Pulses=220;Pulses(uSec)=510,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,840,900,840,420,360,420,360,930,360,420,840,420,360,420,360,420,360,420,360,420,360,900,840,420,360,450,360,420,360,900,360,420,870,420,360,420,360,930,840,420,360,420,360,930,360,420,360,420,840,420,360,420,360,420,360,930,840,420,360,450,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,930,840,900,360,420,360,420,360,420,840,420,360,420,360,930,360,420,840,420,360,900,840,900,840,420,360,900,360,420,840,930,840,900,840,420,360,420,360,900,840,930,840,900,840,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,930,840,420,360,420,360,420,360,900,360,420,840,420,360,420,360,930,840,420,360,900,360,420,360,420,6990;

20;6E;Oregon CM180;ID=008C;WATT=0436;KWATT=01821e03;

----------------------------------------------------------------------------------

115A022088C2000000029300015159ABF679

Packettype = ENERGY
subtype = ELEC3 - OWL CM180
Sequence nbr = 32
ID = 35010 (88C2)
Count = 0
Instant usage = 659 Watt
total usage = 25304688,8 Wh
Signal level = 7 -64dBm
Battery = OK

20;C2;DEBUG;Pulses=218;Pulses(uSec)=510,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,870,930,840,420,360,420,360,930,360,420,840,420,360,420,360,420,360,420,360,420,360,930,840,420,360,420,360,420,360,900,360,420,840,420,360,420,360,930,840,420,360,420,360,900,360,420,840,420,360,930,840,930,840,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,900,360,420,840,900,360,420,360,420,360,420,360,420,360,420,840,930,840,900,870,900,360,420,840,420,360,930,360,420,840,930,840,930,840,420,360,420,360,930,840,900,840,900,840,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,420,360,930,360,420,360,420,840,930,360,420,840,420,360,930,360,420,840,420,360,420,360,900,840,420,6990;

20;C3;Oregon CM180;ID=008C;WATT=0293;KWATT=01821e70;

----------------------------------------------------------------------------------

fabien
New user
Posts: 1
Joined: 29 Oct 2017, 00:11

Re: Oregon OSV3 protocol - wrong ID

#4 Post by fabien » 29 Oct 2017, 01:06

Hello,

I'm currently evaluating your library for my personnal usage - meaning for my home automation project.

I saw you added the ChannelID for Oregon OSV3 protocol since R46: (10/03/2017) - "Fixed: Added channel number to device ID for THGR810"

For example here are some Device ID of my OSV3 sensors
* A28DF
* 728C6
* 328FD
* 528F3

As far as I understand, the first hex character is the channel number where "A" is channel "10", "7" is channel "7", and so on... - am I right ?

At home I use both OSV3 sensors and OSV2 sensors. Unfortunately, the OSV2 sensors have the same problem than OSV3. To be complete, I use THGR122N and THGN132N OSV2 sensors and THGR810 OSV3 sensors.

Indeed, because the channel number is displayed on the sensor itself, then the configuration would be much easier if it appears in the frame decoded by RFLink.

Can you also add the channel number, at the very beginning of the DeviceID (like you did for OSV3) ?

Here are 2 of the decoded frames
FRAME-1
Your decoding (in debug mode):

Code: Select all

20;1E;DEBUG;Pulses=222;Pulses(uSec)=930,900,840,930,840,930,810,960,810,960,810,990,780,990,750,990,750,990,750,1020,720,1080,660,1080,690,540,240,1080,180,570,690,540,240,1050,240,540,690,1080,690,600,180,1080,690,1080,720,1050,240,570,720,570,210,1050,240,570,690,1050,720,570,210,1020,240,570,690,540,210,1050,690,1050,720,1050,720,1050,750,1050,720,1050,720,1020,720,1050,240,570,720,540,240,1050,720,1020,240,540,720,1050,720,570,210,1020,750,1050,720,1020,750,1020,240,540,750,540,240,1020,750,1020,720,1050,720,1020,750,1020,240,540,750,540,240,1020,750,990,270,540,750,1020,720,540,240,1020,750,1020,240,510,750,540,240,1020,750,1020,750,1020,720,1020,720,1020,750,1020,750,1020,240,540,750,540,240,1020,750,1020,750,1020,750,990,750,1020,750,1020,270,540,750,540,240,1020,750,1020,240,540,750,990,750,1020,750,540,240,1020,240,510,750,990,750,1020,750,990,750,540,270,990,750,990,270,510,750,510,270,990,270,510,780,540,240,1020,270,510,750,990,780,990,750,990,750,6990;
20;1F;Oregon TempHygro;ID=2D86;TEMP=0084;HUM=81;HSTATUS=3;BAT=OK;
My decoding from arduino:

Code: Select all

Data to decode: '[OSV2] 1A2D4086201310C83DF5'
Decoded data: 'TemperatureSensor(super=AbstractSensor(sensorUid=null, location=null, host=null, timestamp=null), protocol=OSV2, sensorId=1A2D, channel=3, rollingCode=08, temperature=13.2, relativeHumidity=0.81, lowBattery=false)'
==> Protocol OSV2, Channel Number: 3 - it's the 5th character (indeed 4 according to the protocol itsef but displayed 3)
Your decoding of 1A2D4086201310C83DF5 is 2D86 and that would be great to have 32D86

FRAME-2
Your decoding (in debug mode):

Code: Select all

20;60;DEBUG;Pulses=210;Pulses(uSec)=750,840,810,840,810,840,810,870,870,900,870,900,870,420,390,900,360,420,870,420,360,900,360,420,870,900,870,420,360,900,870,900,870,900,390,420,870,420,360,900,390,420,870,900,870,390,390,900,390,420,870,420,360,900,870,900,870,900,870,900,870,900,870,900,390,420,870,420,390,900,870,900,870,900,870,900,360,420,870,420,360,900,360,420,870,420,390,900,390,420,870,900,870,900,870,420,360,900,870,900,870,900,870,900,870,900,870,900,870,900,870,900,870,900,870,900,870,900,870,900,870,900,360,420,870,390,390,900,870,900,870,900,870,900,870,900,870,900,390,390,870,420,360,900,870,900,360,420,870,900,870,420,360,900,360,420,870,420,360,900,870,900,870,900,360,390,870,420,360,900,390,420,840,420,390,900,360,420,870,900,870,900,870,900,870,390,390,900,870,900,870,900,360,420,870,900,870,420,360,900,870,900,870,900,360,420,870,900,870,6990;
20;61;Oregon TempHygro;ID=2DEA;TEMP=00c8;HUM=59;HSTATUS=1;BAT=OK;
My decoding from arduino:

Code: Select all

Data to decode: '[OSV2] 1A2D10EA002090453DC6'
Decoded data: 'TemperatureSensor(super=AbstractSensor(sensorUid=null, location=null, host=null, timestamp=null), protocol=OSV2, sensorId=1A2D, channel=1, rollingCode=0E, temperature=20.0, relativeHumidity=0.59, lowBattery=false)'
==> Protocol OSV2, Channel Number: 1 - it's the 5th character (indeed 0 according to the protocol itself but displayed 1)
Your decoding of 1A2D41EAA002090453DC6 is 2DEA and that would be great to have 12DEA

Regarding the channel number, THGR122N and THGN132N devices I use are sending a value of 1,2 or 4 for respectively channel number 1, 2 or 3 - I suppose it's due to the fact that it's a switch with 3 positions - one for each bit.

I realize this thread concerned OSV3 THGR810 sensor, but because the problem (and the solution) is the same I didn't want to create a new thread - don't hesitate to inform (blame?) me if you want me to do so.

Thank you in advance,
Kind regards,
Fabien.

DerekC
New user
Posts: 2
Joined: 26 Jun 2019, 20:55

Re: Oregon OSV3 protocol - wrong ID

#5 Post by DerekC » 26 Jun 2019, 23:47

Would you mind sharing your settings for the Oregon? I have not managed to get the signal decoded yet.

User avatar
Stuntteam
Site Beheer
Posts: 787
Joined: 27 Jan 2016, 16:46

Re: Oregon OSV3 protocol - wrong ID

#6 Post by Stuntteam » 27 Jun 2019, 01:05

Derek, first get a real RFLink..!
Then you will see that your devices are detected
-=# RFLink Gateway Development Team #=-
Introduction: http://www.nemcon.nl/blog2/
Generic Support forum: http://www.esp8266.nu/forum/viewforum.php?f=8

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 23 guests