Oregon Scientific RTHN318 Sensor Support

433Mhz opensource Receiver & Transmitter.

Moderators: leecollings, Stuntteam

Post Reply
RidingTheFlow
Posts: 72
Joined: Friday 11 March 2016 18:23
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: Essex, UK
Contact:

Oregon Scientific RTHN318 Sensor Support

Post by RidingTheFlow »

Hello,
I have a BAR339DP projection clock and it would be great if RFLink could pull the temperature from its external sensor.
From what I see, this sensor is combined Temperature + atomic time and uses protocol version 2.2 (http://global.oregonscientific.com/uplo ... bility.pdf)

Its not in supported device list, so I wasn't much surprised its not currently recognized via RFLink.

I can see undecoded packets in rflink monitor, so I suspect it may be a matter of fairly easy fix to recognize this sensor data since protocol should be not too different? I don't really care about date/time, but if at least temperature can be processed I would be very happy :)

Please let me know if you need any help/debug logs.

Thanks and best regards
deennoo
Posts: 784
Joined: Wednesday 10 December 2014 13:06
Target OS: Linux
Domoticz version: beta
Location: Bordeaux France
Contact:

Re: Oregon Scientific RTHN318 Sensor Support

Post by deennoo »

Please post your debug hère : http://www.esp8266.nu/forum/viewforum.p ... dec8b0ff01

And dont forget to give real temperature
Domoticz stable 3.5877 for real & Domoticz beta for test
Rfxtrxe / RFLink / Milight / Yeelight / Tasmota / MQTT / BLE / Zigate
http://domo-attitude.fr
RidingTheFlow
Posts: 72
Joined: Friday 11 March 2016 18:23
Target OS: Raspberry Pi / ODroid
Domoticz version:
Location: Essex, UK
Contact:

Re: Oregon Scientific RTHN318 Sensor Support

Post by RidingTheFlow »

Already received PM and emailed diags.

Just FYI, for now I've made a quick hack to source to make it work, maybe this will help to save some time:

- I had to increase OVERSIZED_LIMIT in Plugin_001 and OSV3_PULSECOUNT_MAX since this sensor sends a lot of data (due to datetime I assume)
- Added check for (id & 0xfff) == 0xADC to V2 temp-only sensor branch (since high nibble appear to change and contain some other flag, maybe again something to do with datetime)

After this I started receiving accurate temperatures. But obviously will still appreciate if proper fix added to mainline :)
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest