• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Oregon Protocol V2.1: THGR122NX
@florent: The latest stable version of pilight (v7.0) doesn't include this protocol. It is still under development, and only included in a developmental version. You will need to compile pilight manually from wo_rasp's branch to test this protocol.
 
Reply
I do not think that it is included in the nightly Version.

You do need to use the link provided in the wiki and manually compile pilight.

There are no further special requirements.


send from tapatalk
 
Reply
Ok thanks it works ! I have manually compiled the v7_oregon from wo_rasp branch.
 
Reply
Dervice ID 4096:
The raw data received indicate that there is a probability that it may be an Oregon pulsetrain, however AFAIK this is not a valid Device ID for Oregon devices.

Please do not mix up two different devices in one thread, remove your request for teh TFA devie and open another thread on the subject.
 
Reply
(02-21-2017, 01:02 AM)wo_rasp Wrote: Dervice ID 4096:
The raw data received indicate that there is a probability that it may be an Oregon pulsetrain, however AFAIK this is not a valid Device ID for Oregon devices.

Please do not mix up two different devices in one thread, remove your request for teh TFA devie and open another thread on the subject.

Thanks - I'm sorry and I have removed the post.
The Wiki about Oregon points to this thread for questions.
Another Home Automation Systems indicates the device as Oregon.
Can I see valid Device ID's?
 
Reply
Please check the WIKI for a list of currently supported device ID's.

Can you post moire details regarding your device ? (the WIKI should give you an idea with regard to the requried data to identify a device).

Typically Device ID: 4096 is reported id errors in the pulsetrain was found.

Below are two examples for debug data when you run "pilight-daemon -D".

In the 1st example the 1st pulsetrain was properly decoded, but not the 2nd one:
Code:
[ Feb 26 21:25:24:31568] pilight-daemon: DEBUG: possible oregon_21 protocol
[ Feb 26 21:25:24:31750] pilight-daemon: DEBUG: recevied pulse length of 324
[ Feb 26 21:25:24:31834] pilight-daemon: DEBUG: caught minimum # of repeats 1 of oregon_21
[ Feb 26 21:25:24:31909] pilight-daemon: DEBUG: called oregon_21 parseRaw()
[ Feb 26 21:25:24:32079] pilight-daemon: DEBUG: OREGON: Decoded binary data. Last bit at pBin: 64
--- 00 04 08 12 16 20 24 28 32 36 40 44 48 52 56 60 64 68 72 76 80 84 88 92 96
000  e  c  4  0  1  e  3  0  2  9  1  0  c  3  9  9  1  0  0  0  0  0  0  0  0
100  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0
200  0  0  0  0  0  0
[ Feb 26 21:25:24:33361] pilight-daemon: DEBUG: OREGON: device: 60480 - id: 1 - unit: 227 - batt: 1 - temp: 1920.000000 - humi: -1.000000 - uv: -1
[ Feb 26 21:25:24:33534] pilight-daemon: DEBUG: OREGON: wind_dir: -1 - wind_speed: -1 - wind_avg: -1 - rain: -1 - rain_total: -1 - pressure: -1
[ Feb 26 21:25:24:33626] pilight-daemon: DEBUG: OREGON: pChksum at: 48, calc: 3c, expected: 3c, bin end at: 64, crc: 99
[ Feb 26 21:25:24:39257] pilight-daemon: DEBUG: socket write succeeded: {"message":{"device_id":60480,"id":1,"unit":227,"battery":1,"temperature":19.20},"origin":"receiver","protocol":"oregon_21","uuid":"0000-80-3f-5d-22639b","repeats":1}

[ Feb 26 21:25:24:46519] pilight-daemon: DEBUG: broadcasted: {"message":{"device_id":60480,"id":1,"unit":227,"battery":1,"temperature":19.20},"origin":"receiver","protocol":"oregon_21","uuid":"0000-80-3f-5d-22639b","repeats":1}
[Feb 26 21:25:24:312442] pilight-daemon: DEBUG: possible oregon_21 protocol
[Feb 26 21:25:24:312622] pilight-daemon: DEBUG: recevied pulse length of 0
[Feb 26 21:25:24:312698] pilight-daemon: DEBUG: caught minimum # of repeats 2 of oregon_21
[Feb 26 21:25:24:312862] pilight-daemon: DEBUG: called oregon_21 parseRaw()
[Feb 26 21:25:24:312963] pilight-daemon: DEBUG: OREGON: Unknown device_id: 4096

In the 2nd example both pulsetrains were corrupted:
Code:
[ Feb 26 21:29:57:31620] pilight-daemon: DEBUG: possible oregon_21 protocol
[ Feb 26 21:29:57:31801] pilight-daemon: DEBUG: recevied pulse length of 277
[ Feb 26 21:29:57:31883] pilight-daemon: DEBUG: caught minimum # of repeats 1 of oregon_21
[ Feb 26 21:29:57:31962] pilight-daemon: DEBUG: called oregon_21 parseRaw()
[ Feb 26 21:29:57:32056] pilight-daemon: DEBUG: OREGON: Unknown device_id: 4096
[Feb 26 21:29:57:298045] pilight-daemon: DEBUG: possible oregon_21 protocol
[Feb 26 21:29:57:298223] pilight-daemon: DEBUG: recevied pulse length of 324
[Feb 26 21:29:57:298301] pilight-daemon: DEBUG: caught minimum # of repeats 2 of oregon_21
[Feb 26 21:29:57:298377] pilight-daemon: DEBUG: called oregon_21 parseRaw()
[Feb 26 21:29:57:298481] pilight-daemon: DEBUG: OREGON: Decoded binary data. Last bit at pBin: 12
--- 00 04 08 12 16 20 24 28 32 36 40 44 48 52 56 60 64 68 72 76 80 84 88 92 96
000  e  c  4  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0
100  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0
200  0  0  0  0  0  0
[Feb 26 21:29:57:303602] pilight-daemon: DEBUG: OREGON: device: 60480 - id: 0 - unit: 0 - batt: 1 - temp: 0.000000 - humi: -1.000000 - uv: -1
[Feb 26 21:29:57:303778] pilight-daemon: DEBUG: OREGON: wind_dir: -1 - wind_speed: -1 - wind_avg: -1 - rain: -1 - rain_total: -1 - pressure: -1
[Feb 26 21:29:57:303869] pilight-daemon: DEBUG: OREGON: pChksum at: 48, calc: 3c, expected: 0, bin end at: 12, crc: 0
The 3rd example shows a pulsetrain with Chksum error in the first part, but the 2nd one is correct:
Code:
[ Feb 26 21:24:06:31571] pilight-daemon: DEBUG: possible oregon_21 protocol
[ Feb 26 21:24:06:31755] pilight-daemon: DEBUG: recevied pulse length of 324
[ Feb 26 21:24:06:31837] pilight-daemon: DEBUG: caught minimum # of repeats 1 of oregon_21
[ Feb 26 21:24:06:31913] pilight-daemon: DEBUG: called oregon_21 parseRaw()
[ Feb 26 21:24:06:32040] pilight-daemon: DEBUG: OREGON: Decoded binary data. Last bit at pBin: 49
--- 00 04 08 12 16 20 24 28 32 36 40 44 48 52 56 60 64 68 72 76 80 84 88 92 96
000  e  c  4  0  1  e  3  0  2  9  1  0  2  0  0  0  0  0  0  0  0  0  0  0  0
100  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0
200  0  0  0  0  0  0
[ Feb 26 21:24:06:33294] pilight-daemon: DEBUG: OREGON: device: 60480 - id: 1 - unit: 227 - batt: 1 - temp: 1920.000000 - humi: -1.000000 - uv: -1
[ Feb 26 21:24:06:33468] pilight-daemon: DEBUG: OREGON: wind_dir: -1 - wind_speed: -1 - wind_avg: -1 - rain: -1 - rain_total: -1 - pressure: -1
[ Feb 26 21:24:06:33562] pilight-daemon: DEBUG: OREGON: pChksum at: 48, calc: 3c, expected: 2, bin end at: 49, crc: 0
[Feb 26 21:24:06:281749] pilight-daemon: DEBUG: possible oregon_21 protocol
[Feb 26 21:24:06:281928] pilight-daemon: DEBUG: recevied pulse length of 324
[Feb 26 21:24:06:282008] pilight-daemon: DEBUG: caught minimum # of repeats 2 of oregon_21
[Feb 26 21:24:06:282180] pilight-daemon: DEBUG: called oregon_21 parseRaw()
[Feb 26 21:24:06:282358] pilight-daemon: DEBUG: OREGON: Decoded binary data. Last bit at pBin: 64
--- 00 04 08 12 16 20 24 28 32 36 40 44 48 52 56 60 64 68 72 76 80 84 88 92 96
000  e  c  4  0  1  e  3  0  2  9  1  0  c  3  9  9  1  0  0  0  0  0  0  0  0
100  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0
200  0  0  0  0  0  0
[Feb 26 21:24:06:283430] pilight-daemon: DEBUG: OREGON: device: 60480 - id: 1 - unit: 227 - batt: 1 - temp: 1920.000000 - humi: -1.000000 - uv: -1
[Feb 26 21:24:06:283593] pilight-daemon: DEBUG: OREGON: wind_dir: -1 - wind_speed: -1 - wind_avg: -1 - rain: -1 - rain_total: -1 - pressure: -1
[Feb 26 21:24:06:283683] pilight-daemon: DEBUG: OREGON: pChksum at: 48, calc: 3c, expected: 3c, bin end at: 64, crc: 99
[Feb 26 21:24:06:288637] pilight-daemon: DEBUG: socket write succeeded: {"message":{"device_id":60480,"id":1,"unit":227,"battery":1,"temperature":19.20},"origin":"receiver","protocol":"oregon_21","uuid":"0000-80-3f-5d-22639b","repeats":2}

[Feb 26 21:24:06:293155] pilight-daemon: DEBUG: broadcasted: {"message":{"device_id":60480,"id":1,"unit":227,"battery":1,"temperature":19.20},"origin":"receiver","protocol":"oregon_21","uuid":"0000-80-3f-5d-22639b","repeats":2}
 
Reply
I installed a fresh raspbian on a pi2. After that I compiled the v7_oregon branch from wo_rasp . 

With this I got a 'ERROR: hardware not supported'

/usr/local/sbin/pilight-daemon --version
pilight-daemon version v5.0-643-g2794d33b

 
Reply
Hallo i need the Oregon prototol, so i have try to install the pilight-test_dev but i become fault messages if i start manual complimation.


i go to the Floder and type ./setup.sh
then the pilight configuration starts and i push save and install

so now i become this...

Code:
- The C compiler identification is GNU 4.9.2
-- The CXX compiler identification is GNU 4.9.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
fatal: Not a git repository (or any of the parent directories): .git
-- Looking for libpcap - found (/usr/lib/arm-linux-gnueabihf/libpcap.so)
-- Looking for libunwind - found (/usr/lib/arm-linux-gnueabihf/libunwind.so)
-- Looking for pthread.h
-- Looking for pthread.h - not found
CMake Error at /usr/share/cmake-3.6/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
 Could NOT find Threads (missing: Threads_FOUND)
Call Stack (most recent call first):
 /usr/share/cmake-3.6/Modules/FindPackageHandleStandardArgs.cmake:388 (_FPHSA_FAILURE_MESSAGE)
 /usr/share/cmake-3.6/Modules/FindThreads.cmake:223 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
 CMakeLists.txt:275 (find_package)


-- Configuring incomplete, errors occurred!
See also "/root/pilight-test_dev/build/CMakeFiles/CMakeOutput.log".
See also "/root/pilight-test_dev/build/CMakeFiles/CMakeError.log".
make: *** No rule to make target 'install'.  Schluss.


i habe installed all needed Packs
somebody can help me??
 
Reply
hallo,
i have set up a new RPI3 for my Garden, the installation was no problem.

But if i will start pilight in the log i become this 
Code:
[Jul 04 12:37:38:431529] pilight-daemon: ERROR: hardware not supported
[Jul 04 12:37:38:431574] pilight-daemon: ERROR: could not initialize 433gpio hardware module


How can i use the oregon protokoll on Raspberry PI 3 b????
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  missing protocol of "date_and_time" in Wiki/Protocols fleisch 3 208 08-03-2019, 06:10 PM
Last Post: curlymo
Brick Protocol for FT0073 drobskind 5 3,087 07-25-2019, 10:44 PM
Last Post: fireball
  Brennenstuhl RCR CE1 1011 with QUIGG GT9000 Protocol scootermacro 1 240 06-27-2019, 06:20 PM
Last Post: scootermacro
  mumbi rcs-20gs protocol scootermacro 0 207 06-21-2019, 12:10 PM
Last Post: scootermacro
  How to introduce a new protocol folder? Phunkafizer 2 417 01-15-2019, 07:25 PM
Last Post: Phunkafizer
  rfcontroljs protocol implementation pisperate 0 246 01-13-2019, 11:07 AM
Last Post: pisperate
  MQTT protocol for pilight Chekov 11 3,142 11-03-2018, 04:21 PM
Last Post: curlymo
  getting started guide for implementing new protocol kaililleby 1 846 11-28-2017, 10:24 PM
Last Post: pilino1234
  Logilink EC0003 Protocol ehz 4 1,158 09-24-2017, 07:15 PM
Last Post: ehz
  Unkown protocol with Lidl Libra RC-710 HaselnuesseTo 0 1,050 09-11-2017, 08:30 PM
Last Post: HaselnuesseTo

Forum Jump:


Browsing: 1 Guest(s)