• 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
RSL366 receive fine, can't send?
#1
Hey guys.

Sorry for two quick threads, I'm not usually like this but I'm banging my head on a wall.

So I've successfully setup pilight, running on a generic usb-nano that i've had for a while, connected to a Rpi3 that's running a HA installation amongst other things.

I've got a superhet receiver the same as yours in the shop and a fs1000a sender, here's a datasheet for it: http://www.mantech.co.za/Datasheets/Prod...-TX&RX.pdf

I'm trying to talk to a generic set of RF sockets that I bought from Maplin a while ago: http://www.maplin.co.uk/p/remote-control...pack-n79ka

I've previously used the sender and receiver without issues, but for some reason this isn't doing as I expect it, perhaps I'm missreading something here.

Running pilight-receive I'm getting a nice output when pressing buttons on the remote:
Code:
puk@Pi2:~ $ pilight-receive
{
    "message": {
        "systemcode": 2,
        "programcode": 1,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
{
    "message": {
        "systemcode": 2,
        "programcode": 1,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
{
    "message": {
        "systemcode": 2,
        "programcode": 2,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
{
    "message": {
        "systemcode": 2,
        "programcode": 2,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
{
    "message": {
        "systemcode": 2,
        "programcode": 3,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
{
    "message": {
        "systemcode": 2,
        "programcode": 3,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
{
    "message": {
        "systemcode": 2,
        "programcode": 4,
        "state": "on"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
{
    "message": {
        "systemcode": 2,
        "programcode": 4,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
So to test this before clogging up my config.json I tried using:
Code:
pilight-send -p rsl366 -s 2 -u 1 -t
Nothing from the remote socket.  I thought I'd test the sender signal, so installed a LED between the data and gnd, and I get a nice burst of flashing when I run the command again.

I've tried every variation of systemcode and programcode nothing happens other than an LED flashing.  I read the wiki and tried both promax and brennenstuhl protocols, then randomly I got a different socket to what I was expecting to operate using:
Code:
pilight-send -p brennenstuhl -s 2 -u 1 -t
pilight-send -p brennenstuhl -s 2 -u 1 -f
I'm a little lost, as I thought if the receiver finds this:
Code:
{
    "message": {
        "systemcode": 2,
        "programcode": 1,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "rsl366",
    "uuid": "0000-b8-27-eb-09d9a5",
    "repeats": 1
}
 
Then a command of:

Code:
pilight-send -p rsl366 -s 2 -u 1 -t

Should operate the socket?
Am i doing something wrong?  I'd appreciate any input, cheers!
 
Reply
#2
Although you're suggesting differently, your TX/RX are not supported.
 
Reply
#3
(02-15-2018, 07:21 AM)curlymo Wrote: Although you're suggesting differently, your TX/RX are not supported.

If that's the problem then I'll replace them, £13 isn't the end of the world but its annoying as I already have hardware that seems to function elsewhere and I'll have to wait on postage. 

I'm surprised though, what makes pilight use something different from what is a generic tx?  My rx is exactly the same as in your shop, identical placement of all components et all, I agree my tx is different.  I'm surprised it makes such a difference as all it's doing is sending a radio signal?  As I said, the transmitter happily sent commands to my sockets previously using rpi_rf.

If you're certain it's down to that, then I'll replace them.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight-receive Filteroption not working Alex 2 558 07-14-2019, 08:35 AM
Last Post: Alex
  pilight-send does not stop (terminate) va13 3 680 05-15-2019, 06:06 PM
Last Post: curlymo
  pilight-receive not found Pikeman 7 977 07-06-2018, 10:44 AM
Last Post: curlymo
  pilight-receive is not working for me oxi 0 487 04-26-2018, 07:32 PM
Last Post: oxi
  pilight-receive does not work RP3 UniCorny 9 2,828 04-10-2018, 07:03 AM
Last Post: honselbonsel
  pilight-receive not getting anything, but pilight-debug does geokscott 2 1,286 03-09-2018, 04:05 PM
Last Post: geokscott
Thumbs Up Newbie problems, usbnano connection and rsl366 pukington 1 500 02-14-2018, 07:36 PM
Last Post: pukington
  pilight-send for like rc-switch "send" mindau 1 1,463 01-18-2018, 07:46 AM
Last Post: madmoses
  pilight-receive and pilight-raw with no results Bernd2310 4 2,020 01-06-2018, 11:03 PM
Last Post: Bernd2310
  pilight-receive does not work correctly docingo 4 1,083 12-11-2017, 08:34 PM
Last Post: docingo

Forum Jump:


Browsing: 1 Guest(s)