• 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
Sending does not work under Linux, only under Windows
#1
Good Evening,

I have a problem with pilight, that does not work correctly under Linux.
Sending doesn't work, only receiving works.

When I connect the 433nano to a Windows PC, with pilight 6, then works send and receive. So with the same device and the same devices entries in config.json.

I tried this on two Linux systems. First Raspberry 1 with Rasbian and the latest GIT.
Second under Debian in a virtual machine. Only receiving works. Transmission does not work, on the SF-501 socket.

At first I thought the transmitter was defective.
But meanwhile I tried 4 different transmitters: 2x FS1000A and 2x STX882.
Until I got the idea to try it with Windows and all the transmitters are going there.

These sockets are SF-501 (from action for under 10 euro): https://www.amazon.de/Flamingo-Funksteck...B01LWWSNS7

Windows config (version 6.0):
Code:
{
    "devices": {
        "Switch1": {
            "protocol": [ "kaku_switch" ],
            "id": [{
                "id": 37475328,
                "unit": 1
            }],
            "state": "off"
        }
    },
    "rules": {},
    "gui": {
        "Switch1": {
            "name": "Switch Nr 1",
            "group": [ "MeineSwitches" ],
            "media": [ "all" ]
        }
    },
    "settings": {
        "log-level": 4,
        "log-file": "c:/pilight/pilight.log",
        "send-repeats": 10,
        "receive-repeats": 1,
        "webserver-enable": 1,
        "webserver-root": "c:/pilight/web/",
        "webserver-port": 9999,
        "webserver-cache": 1
    },
    "hardware": {
        "433nano": {
            "comport": "COM2"
        }
    },
    "registry": {}
}

Linux config - version 3e8b2d0 (virtual box) and on the pi, the newest v8.0.4
:
Code:
{
        "devices": {
                "Switch1": {
                        "protocol": [ "kaku_switch" ],
                        "id": [{
                                "id": 37475328,
                                "unit": 1
                        }],
                        "state": "off"
                }
        },
        "rules": {},
        "gui": {
                "Switch1": {
                        "name": "Switch Nr 1",
                        "group": [ "MeineSwitches" ],
                        "media": [ "all" ]
                }
        },
        "settings": {
                "log-level": 6,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "port": 5000,
                "webserver-enable": 1,
                "webserver-root": "/usr/local/pilight/webgui",
                "webserver-http-port": 5001,
                "webserver-cache": 1
        },
        "hardware": {
                "433nano": {
                        "comport": "/dev/serial/by-id/usb-FTDI_FT232R_USB_UART_A9A9LB7V-if00-port0"
                }
        },
        "registry": {
                "webserver": {
                        "ssl": {
                                "certificate": {
                                        "secure": 0,
                                        "location": "/etc/pilight/pilight.pem"
                                }
                        }
                },
                "pilight": {
                        "version": {
                                "current": "7.0"
                        }
                }
        }


Greetings
Mark
 
Reply
#2
Does no one have an idea why sending with 433nano on Linux does not work?

Under Windows the transmitter runs, but not on rpi1 with raspbian. What only goes is receiving.

I have already connected it directly to the usb of the raspberry and to an active USB hub.
 
Reply
#3
No really i don't. So version 7 stable also doesn't work?
 
Reply
#4
(12-07-2017, 05:56 PM)curlymo Wrote: No really i don't. So version 7 stable also doesn't work?

I tried it again today, with version 7 from 25 May 2015 on Debian Stretch.

No sending doesn't work. Crying 

I take the socket out of power for a moment, then it's in learning mode. I send a command with: "pilight-send -p kaku_switch -t -i 37475328 -u 1"  ...but there seems to be no signal coming in.

Same string, with the same nano, even PC only with Windows with pilight 6, there the sending works. That's crazy.....


Receiving works on both systems.

Could it be Debian Stretch?
 
Reply
#5
What user are you running pilight-send from and are you getting any output at all?

As you are trying to make it learn try using this:


Code:
pilight-send -p kaku_switch -t -i 37475328 -u 1 -l
 
Reply
#6
Can you connect a LED instead of the sender. Does it blink when sending?
 
Reply
#7
(12-21-2017, 06:56 PM)curlymo Wrote: Can you connect a LED instead of the sender. Does it blink when sending?

I did something wrong and now the nano is dead. Crying
How do I connect the LED exactly? Then I'll solder another nano together.

I have connected a SMD Led to the transmitter of the gnd > gpio. After that again the same with gpio > vcc. 
The led lit up both of them.
 
Reply
#8
You need GPIO > GND. And it needs to be blinking, not just burning.
 
Reply
#9
New nano new luck.

I have another receiver module (nanoCUL) for Fhem: https://wiki.fhem.de/wiki/Selbstbau_CUL

When I execute the send command with pilight Windows, the nanoCUL receives this:

Code:
2017.12.21 22:28:03 4: CUL_Parse: miniCUL i95A9AA665555565634 -48
2017.12.21 22:28:03 5: miniCUL: dispatch i95a9aa6655555656
2017.12.21 22:28:03 4: miniCUL IT: message "i95a9aa6655555656" (17)
2017.12.21 22:28:03 4: miniCUL ITv3: bin message "1001010110101001101010100110011001010101010101010101011001010110" (64)
2017.12.21 22:28:03 4: miniCUL IT: msgcode "10001110111101010000000000010001" (32) bin = 1001010110101001101010100110011001010101010101010101011001010110
2017.12.21 22:28:03 2: miniCUL IT: IT_V3_477a8001 (1000111011110101000000000000001) not defined (Address: 10001110111101010000000000 Group: 0 Unit: 0001 Switch code: 1)
2017.12.21 22:28:11 5: CUL/RAW: /i95A
2017.12.21 22:28:11 5: CUL/RAW: i95A/9AA665555565632


If I send it with pilight under Debian, then nothing comes to nanoCUL. 
And this is so on two different machines, x86 and Raspberry.


(12-21-2017, 10:52 PM)curlymo Wrote: You need GPIO > GND. And it needs to be blinking, not just burning.

Okay, thanks. I'll try again.
 
Reply
#10
The LED flashes at the same speed on both systems, if pilight sends something. So there seems to be something being sent under Debian....

I have the debug log of both systems. The raw output is different. 
I'll do it again to make sure that i sent the same commands.

EDIT: more Debug Logs: https://nopaste.linux-dev.org/?1171322

pilight Debug on Windows:

Code:
[ Dec 21 22:50:22:20659] pilight-daemon: DEBUG: socket write succeeded: {"action":"control","code":{"device":"Switch1","state":"on"}}
[ Dec 21 22:50:22:21660] pilight-daemon: DEBUG: socket recv: {"action":"control","code":{"device":"Switch1","state":"on"}}
[ Dec 21 22:50:22:21660] pilight-daemon: DEBUG: **** RAW CODE **** 279 
[ Dec 21 22:50:22:21660] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}

2511 279 1395 279 279 279 279 279 1395 279 279 279 1395 279 279 279 1395 279 139
5 279 279 279 1395 279 279 279 1395 279 279 279 279 279 1395 279 1395 279 279 27
9 1395 279 279 279 1395 279 279 279 1395 279 279 279 279 279 1395 279 1395 279 2
79 279 279 279 1395 279 1395 279 279 279 279 279 1395 279 279 279 1395 279 279 2
79 1395 279 279 279 1395 279 279 279 1395 279 279 279 1395 279 279 279 1395 279
279 279 1395 279 279 279 1395 279 279 279 1395 279 279 279 1395 279 1395 279 279
 279 279 279 1395 279 279 279 1395 279 279 279 1395 279 1395 279 279 279 9486
[Dec 21 22:50:22:44162] pilight-daemon: DEBUG: **** RAW CODE ****
[Dec 21 22:50:23:593359] pilight-daemon: DEBUG: successfully send arctech_switch code
[Dec 21 22:50:23:594359] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":1,"devices":["Switch1"],"values":{"timestamp":1513889423,"state":"on"}}
[Dec 21 22:50:23:594859] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":1,"devices":["Switch1"],"values":{"timestamp":1513889423,"state":"on"}}
[Dec 21 22:50:23:595359] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":1,"devices":["Switch1"],"values":{"timestamp":1513889423,"state":"on"}}
[Dec 21 22:50:23:596860] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":1,"devices":["Switch1"],"values":{"timestamp":1513889423,"state":"on"}}



pilight Debug on Debian:

Code:
[Dec 21 21:48:36:971948] pilight-daemon: INFO: new client, ip: 192.168.1.119, port: 37300
[Dec 21 21:48:36:972046] pilight-daemon: DEBUG: client fd: 15
[Dec 21 21:48:36:972065] pilight-daemon: DEBUG: client id: 4
[Dec 21 21:48:36:972312] pilight-daemon: DEBUG: socket recv: {"action":"identify"}
[Dec 21 21:48:36:972369] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}

[Dec 21 21:48:36:972502] pilight-daemon: DEBUG: socket recv: {"action":"send","code":{"on":1,"unit":1,"id":37475328,"learn":1,"protocol":["kaku_switch"]}}
[Dec 21 21:48:36:972870] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}

[Dec 21 21:48:36:973054] pilight-daemon: DEBUG: **** RAW CODE ****
300 2700 300 1200 300 300 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 300 300 1200 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 300 300 1200 300 1200 300 300 300 300 300 1200 300 1200 300 300 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 1200 300 300 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 1200 300 300 300 10200
[Dec 21 21:48:36:973199] pilight-daemon: DEBUG: client disconnected, ip 192.168.1.119, port 37300
[Dec 21 21:48:36:973217] pilight-daemon: DEBUG: **** RAW CODE ****
[Dec 21 21:48:37:973620] pilight-daemon: DEBUG: successfully send arctech_switch code
[Dec 21 21:48:37:974186] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"arctech_switch","message":{"id":37475328,"unit":1,"state":"on"},"repeat":1,"uuid":"0000-08-00-27-e5069d"}
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight v8.0 - Current work in progress curlymo 32 28,888 12-06-2018, 10:06 PM
Last Post: curlymo
Exclamation Brennenstuhl 433MHz RC C1 - pilight not work pitje87 0 571 10-31-2018, 12:38 PM
Last Post: pitje87
  [solved] kwmobile: repeating the remote signal doesn't work dawncrow 9 943 10-25-2018, 03:46 PM
Last Post: dawncrow
  cannot get pilight-flash to work n.kooij 7 1,649 07-21-2018, 02:52 PM
Last Post: Tamadite
  pilight-receive does not work RP3 UniCorny 9 2,855 04-10-2018, 07:03 AM
Last Post: honselbonsel
  pilight no sending but Receiving works Tueftler1983 1 632 04-01-2018, 03:34 PM
Last Post: Ramirez
  pilight webGUI doesn't work - pilight not on a Pi carlos4018 11 1,832 01-23-2018, 10:18 PM
Last Post: morph027
  Windows HTTP connection andbehtls 1 1,087 01-14-2018, 02:24 PM
Last Post: bnk72
  pilight-receive does not work correctly docingo 4 1,091 12-11-2017, 08:34 PM
Last Post: docingo
  Problem with sending after plight (or raspberry?) update _Jens_ 5 2,006 09-08-2017, 03:14 PM
Last Post: pilino1234

Forum Jump:


Browsing: 1 Guest(s)