jdiazbb / rfxcmd

Automatically exported from code.google.com/p/rfxcmd
1 stars 0 forks source link

Problem with temperatures below 0 degrees Celsius #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Live in Norway
2. Receive data from Oregon temperature/humidity sensor
3. Wait for temperatures below 0 celsius

What is the expected output? What do you see instead?

The output from rfxcmd does not seem to take into account that the temperatures 
are below 0 degrees C

What version of the product are you using? On what operating system?
0.1g on Debian 2.6.18 kernel with python 2.6

Please provide any additional information below.

I am receiving the temperatures from my outside sensor on an Oregon Weather 
Station as well, there the temperature shows -0.6 C at the moment, but the 
output from rfxcmd shows 0.6 C. 

user@mainframe ~ $  /usr/local/bin/python /opt/rfxcmd/rfxcmd.py -d /dev/ttyUSB0
RFXCMD version 0.1g
------------------------------------------------
Received                = 0D 01 00 00 02 53 2E 00 0E 6F 01 00 00 00
Date/Time               = 2012-10-09 21:50:02
Packet Length           = 0D
Packettype              = Interface Message
Subtype                 = Interface response
Sequence nbr            = 00
Response on cmnd        = Get Status, return firmware versions and 
configuration of the interface.
Transceiver type        = 433.92MHz (Transceiver)
Firmware version        = 46
Display undecoded       = Off
Protocols:
Disabled                AE (433.92)
Disabled                Rubicson (433.92)
Disabled                FineOffset / Viking (433.92)
Disabled                RFU3
Disabled                RFU4
Disabled                RFU5
Disabled                RFU6
Disabled                Mertik (433.92)
Enabled                 AD (433.92)
Enabled                 Hideki/UPM (433.92)
Enabled                 La Crosse (433.92/868.30)
Disabled                FS20 (868.35)
Disabled                ProGuard (868.35 FSK)
Disabled                BlindsT0 (433.92)
Disabled                BlindsT1 (433.92)
Enabled                 X10 (310/433.92)
Enabled                 ARC (433.92)
Enabled                 AC (433.92)
Enabled                 HomeEasy EU (433.92)
Disabled                Meiantech (433.92)
Enabled                 Oregon Scientific (433.92)
Enabled                 ATI (433.92)
Disabled                Visonic (315/868.95)
------------------------------------------------
Received                = 0A 52 06 00 DE 01 80 06 4C 03 47
Date/Time               = 2012-10-09 21:50:12
Packet Length           = 0A
Packettype              = Temperature and humidity sensors
Subtype                 = THGR918, THGRN228, THGN500 (TH6)
Seqnbr                  = 00
Id 1 (House)            = DE
Id 2 (Channel)          = 01
Temperature             = 0.6 C
Humidity                = 76
Humidity Status         = Wet
Battery (0-9)           = 4
Signal level (0-15)     = 7

Original issue reported on code.google.com by wiigi...@gmail.com on 9 Oct 2012 at 7:59

GoogleCodeExporter commented 9 years ago
This will be fixed in the upcoming version. You can make a short term fix in 
current version by changing line 699
from "if polarity == 1:" to "if polarity == 128:". 

This issue exists on other sensor types as well, which will be fixed as well.

Original comment by sebastia...@gmail.com on 10 Oct 2012 at 3:13

GoogleCodeExporter commented 9 years ago
Thank you! 

Original comment by wiigi...@gmail.com on 10 Oct 2012 at 3:39

GoogleCodeExporter commented 9 years ago
Tested OK:

id datetime packettype subtype seqnbr id1 id2 temperature humidity 
humidity_status     
17878 2012-10-11 06:57:08 52 06 F9 DE 01 -4.70 84 3     

Original comment by wiigi...@gmail.com on 11 Oct 2012 at 5:08

GoogleCodeExporter commented 9 years ago
This is now fixed in the v0.1j-beta release

Original comment by sebastia...@gmail.com on 11 Oct 2012 at 7:47