• 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


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
pilight-receive not getting anything, but pilight-debug does
#1
I've installed the latest Stable version of pilight-deamon on a Pi3 running the most current disto of Debian 9


I'm using Superheterodyne transmitter and receiver, connected to GPIO 17 and 27. 
http://www.amazon.com/gp/product/B00HEDRHG6/

Here is my config.json:

Code:
{
       "devices": {},
       "rules": {},
       "gui": {},
       "settings": {
               "log-level": 6,
               "pid-file": "/var/run/pilight.pid",
               "log-file": "/var/log/pilight.log",
               "webserver-enable": 1,
               "webserver-root": "/usr/local/share/pilight/webgui",
               "webserver-http-port": 5001,
               "webserver-cache": 1,
               "gpio-platform": "raspberrypi3",
               "port": 5000
       },
       "hardware": {
               "433gpio": {
                       "sender": 0,
                       "receiver": 2
               }
       },
       "registry": {
               "webserver": {
                       "ssl": {
                               "certificate": {
                                       "secure": 0,
                                       "location": "/etc/pilight/pilight.pem"
                               }
                       }
               },
               "pilight": {
                       "version": {
                               "current": "8.0.8"
                       }
               }
       }
}

I'm using Etekcity 5LXS switches:
http://www.amazon.com/gp/product/B01N5JSAHM/

One time at one point in my setup and testing while running pilight-receive I captured the output from my remote:

Code:
   "message": {
           "id": "E3",
           "unit": 7,
           "state": "on"
   },
   "origin": "receiver",
   "protocol": "clarus_switch",
   "uuid": "0000-b8-27-eb-6cd028",
   "repeats": 1

But since that one time, I cannot get anything to report from my remotes while running pilight-receive!  But if I stop the pilight service and run pilight-debug I do get output from the remote:



Code:
time:           Thu Mar  8 20:51:26 2018
hardware:       433gpio
pulse:          3
rawlen:         29
pulselen:       153

Raw code:
153 459 153 153 459 459 153 153 459 459 153 153 459 153 459 153 459 153 459 153 459 153 459 459 153 459 153 153 5202

So what gives?  I think I've done everything right and triple checked everything.  What is wrong with my configuration or hardware that pilight-receive will not report my remote information???

One more thing, if I let pilight-receive run for a while I pick up various other codes from neighbors devices - so it seams.
 
Reply
#2
It seems that your switch isn't supported and is therefor not decoded by pilight. The debugger always shows undecoded raw output so it's logical that that does output.
 
Reply
#3
(03-09-2018, 09:04 AM)curlymo Wrote: It seems that your switch isn't supported and is therefor not decoded by pilight. The debugger always shows undecoded raw output so it's logical that that does output.

Are sending and receiving decoding encoding completely different from each other?  I can use the pilight-send command with the parameters I got the one time and turn the switch on and off.
pilight-send -p clarus_switch -i E3 -u 7 -t
pilight-send -p clarus_switch -i E3 -u 7 -f

Here's more info.  If I open two terminals, run pilight-receive in one and pilight-send in the other, I can send the on off commands which toggles the switch and the pilight-receive terminal shows all the decoded commands.  BUT my remote control is still not picked my by my receiver.  So it seems like something is off with my receiver, it works with the transmitter, but not with my remotes. EDIT: no, I just noticed the info is not coming from the receiver, rather origin is sender
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight for Raspbian Buster (raspberry pi 4) ? starob 30 7,120 1 hour ago
Last Post: simanuel
  pilight switch node in node-red framp 0 228 06-24-2020, 10:01 PM
Last Post: framp
  pilight-control TML 13 890 05-27-2020, 07:51 AM
Last Post: curlymo
  API Requests by HTTP from other devices fore use in pilight scootermacro 2 397 05-10-2020, 08:19 AM
Last Post: scootermacro
  Can't send or receive on Raspberry Pi Zero W ChristophH 12 815 04-09-2020, 06:34 PM
Last Post: curlymo
  pilight-send seems successful but doesn't actually send RF signal ayeyebrazov 37 3,072 03-31-2020, 01:02 PM
Last Post: curlymo
  pilight 8.1.5 not working on Raspberry pi after reboot beejayf 4 838 03-08-2020, 12:14 AM
Last Post: beejayf
  pilight cpu usage possibly associated with noticeable sluggishness? hepcat72 4 892 01-28-2020, 08:02 PM
Last Post: hepcat72
  apt.pilight.org stable Release' is not signed. thomasol 2 939 01-23-2020, 11:34 PM
Last Post: thomasol
  pilight and SIGNALduino cc1101 Caleus 0 685 01-19-2020, 09:13 AM
Last Post: Caleus

Forum Jump:


Browsing: 1 Guest(s)