• 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
[Solved] pilight nightly not sending codes
#1
I have freshly installed a new Raspian and the latest Nightly on my RaspberryPi2.
Also, added 'gpio-platform': 'raspberrypi2' as suggested in the recent post.

pilight seems to work. But when I send a command I get a success message back, but the switch is doing nothing.

The config.json is untouched besides the gpio-platform entry.
 
Reply
#2
Can you post the output of the following command when sending codes?
Code:
pilight-daemon -D
 
Reply
#3
Code:
[Aug 22 17:27:21:611848] pilight-daemon: DEBUG: socket recv: {"action":"send","code":{"systemcode":9,"unitcode":2,"on":1,"protocol":["elro_400_switch"]}}
[Aug 22 17:27:21:612380] pilight-daemon: DEBUG: socket write succeeded: {"action":"send","code":{"systemcode":9,"unitcode":2,"on":1,"protocol":["elro_400_switch"]}}

[Aug 22 17:27:21:612520] pilight-daemon: DEBUG: socket write succeeded: {"action":"send","code":{"systemcode":9,"unitcode":2,"on":1,"protocol":["elro_400_switch"]}}

[Aug 22 17:27:21:613173] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}

[Aug 22 17:27:21:613511] pilight-daemon: DEBUG: client disconnected, ip 192.168.90.58, port 35774
[Aug 22 17:27:21:614259] pilight-daemon: DEBUG: socket write succeeded: {"origin":"sender","protocol":"elro_400_switch","message":{"systemcode":9,"unitcode":2,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-f48e70"}

[Aug 22 17:27:21:614358] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"elro_400_switch","message":{"systemcode":9,"unitcode":2,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-f48e70"}
[Aug 22 17:27:21:624787] pilight-daemon: DEBUG: socket recv: {"status":"success"}
[Aug 22 17:27:21:624996] pilight-daemon: DEBUG: client "0000-74-da-38-0267e7" successfully executed our latest request
[Aug 22 17:27:21:631682] pilight-daemon: DEBUG: socket recv: {"status":"success"}
[Aug 22 17:27:21:631874] pilight-daemon: DEBUG: client "0000-74-da-38-6e4849" successfully executed our latest request
[Aug 22 17:27:21:683894] pilight-daemon: DEBUG: cpu: 0.308508%
[Aug 22 17:27:21:684063] pilight-daemon: DEBUG: - client: 0000-74-da-38-6e4849 cpu: 46.938216%
[Aug 22 17:27:21:684144] pilight-daemon: DEBUG: - client: 0000-74-da-38-0267e7 cpu: 0.172852%
[Aug 22 17:27:21:898254] pilight-daemon: DEBUG: socket recv: {"values":{"cpu":36.9776887442568238,"ram":0.6524611084649190},"origin":"core","type":-1,"uuid":"0000-74-da-38-6e4849","action":"update"}
[ Aug 22 17:27:22:25469] pilight-daemon: DEBUG: socket recv: {"origin":"sender","protocol":"elro_400_switch","message":{"systemcode":9,"unitcode":2,"state":"on"},"repeat":1,"uuid":"0000-74-da-38-6e4849","action":"update"}
[ Aug 22 17:27:22:26707] pilight-daemon: DEBUG: socket write succeeded: {"origin":"sender","protocol":"elro_400_switch","message":{"systemcode":9,"unitcode":2,"state":"on"},"repeat":1,"uuid":"0000-74-da-38-6e4849"}

[ Aug 22 17:27:22:26872] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"elro_400_switch","message":{"systemcode":9,"unitcode":2,"state":"on"},"repeat":1,"uuid":"0000-74-da-38-6e4849"}
[ Aug 22 17:27:22:34286] pilight-daemon: DEBUG: socket recv: {"origin":"sender","protocol":"elro_400_switch","message":{"systemcode":9,"unitcode":2,"state":"on"},"repeat":1,"uuid":"0000-74-da-38-0267e7","action":"update"}
[ Aug 22 17:27:22:35342] pilight-daemon: DEBUG: socket write succeeded: {"origin":"sender","protocol":"elro_400_switch","message":{"systemcode":9,"unitcode":2,"state":"on"},"repeat":1,"uuid":"0000-74-da-38-0267e7"}

[ Aug 22 17:27:22:35436] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"elro_400_switch","message":{"systemcode":9,"unitcode":2,"state":"on"},"repeat":1,"uuid":"0000-74-da-38-0267e7"}
[Aug 22 17:27:23:969940] pilight-daemon: DEBUG: socket recv: {"values":{"cpu":0.1534205467931626,"ram":0.5949438757627774},"origin":"core","type":-1,"uuid":"0000-74-da-38-0267e7","action":"update"}
[Aug 22 17:27:24:686470] pilight-daemon: DEBUG: cpu: 0.201797%
[Aug 22 17:27:24:686617] pilight-daemon: DEBUG: - client: 0000-74-da-38-6e4849 cpu: 36.977689%
[Aug 22 17:27:24:686696] pilight-daemon: DEBUG: - client: 0000-74-da-38-0267e7 cpu: 0.153421%
[Aug 22 17:27:24:894933] pilight-daemon: DEBUG: socket recv: {"values":{"cpu":47.1904593118454372,"ram":0.6524611084649190},"origin":"core","type":-1,"uuid":"0000-74-da-38-6e4849","action":"update"}
[Aug 22 17:27:26:984400] pilight-daemon: DEBUG: socket recv: {"values":{"cpu":0.1786472967037778,"ram":0.5949438757627774},"origin":"core","type":-1,"uuid":"0000-74-da-38-0267e7","action":"update"}
[Aug 22 17:27:27:689342] pilight-daemon: DEBUG: cpu: 0.086436%
[Aug 22 17:27:27:689518] pilight-daemon: DEBUG: - client: 0000-74-da-38-6e4849 cpu: 47.190459%
[Aug 22 17:27:27:689599] pilight-daemon: DEBUG: - client: 0000-74-da-38-0267e7 cpu: 0.178647%
[Aug 22 17:27:27:898895] pilight-daemon: DEBUG: socket recv: {"values":{"cpu":43.4054787530034929,"ram":0.6524611084649190},"origin":"core","type":-1,"uuid":"0000-74-da-38-6e4849","action":"update"}
^C[Aug 22 17:27:29:155836] pilight-daemon: INFO: Interrupt signal received. Please wait while pilight is shutting down

Now, I uninstalled the Nightly. Removed the nightly repository and installed the stable pilight version.
Downgraded rpi kernel to 4.4 and everything works (because of the hardware compatibility issue).

So, there is definitely something wrong with the nightly. :/

I tried downgrading the kernel with the nightly as well, but this did not help either.
 
Reply
#4
Do you want to debug this further or not now you've downgraded?
 
Reply
#5
We can debug this further. Just tell me what I can do.
 
Reply
#6
Post your config. It seems that no codes are being sent.
 
Reply
#7
Code:
pi@rpi2:~ $ more /etc/pilight/config.json
{
        "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/",
                "webserver-http-port": 5001,
                "webserver-cache": 1,
                "gpio-platform": "raspberrypi2"
        },
        "hardware": {
                "433gpio": {
                        "sender": 1,
                        "receiver": 1
                }
        },
        "registry": {
                "pilight": {
                        "firmware": {
                                "version": 3,
                                "lpf": 80,
                                "hpf": 16000
                        },
                        "version": {
                                "current": "7.0"
                        }
                }
        }
}
 
Reply
#8
How are the sender and receiver GPIO the same?
 
Reply
#9
(08-22-2017, 09:05 PM)curlymo Wrote: How are the sender and receiver GPIO the same?

Ooops, my fault after quick re-installation. I corrected sender back to 0.
Now, it seems to work.

Switching works now with the nightly, as well.

Is it possible to set the gpio-platform parameter via a (REST)-API call?
 
Reply
#10
Quote:Is it possible to set the gpio-platform parameter via a (REST)-API call?
Nope
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  [SOLVED] Triggering generic_switch leads to segfault Ulrich.Arnold 19 1,273 10-23-2019, 09:03 AM
Last Post: Ulrich.Arnold
  [Fixed] Fast sending codes in a row not working apartmedia 12 3,756 08-19-2019, 04:58 PM
Last Post: curlymo
  ][solved]Segfault when retrieving big chunked http message Niek 21 6,079 11-29-2018, 03:17 PM
Last Post: curlymo
  pilight-control not able to connect with port and server setting apartmedia 10 4,286 10-22-2018, 08:00 AM
Last Post: apartmedia
  [Solved] config.json not updated Niek 6 1,594 12-31-2017, 03:19 PM
Last Post: curlymo
  [Solved] callback not executing when dns lookup fails Niek 1 717 10-08-2017, 11:44 AM
Last Post: curlymo
  [Solved] Rules switching state based on another device state not working apartmedia 6 2,547 09-27-2017, 01:41 PM
Last Post: apartmedia
  [Solved] connection to main pilight daemon lost TopdRob 20 4,439 09-17-2017, 04:30 PM
Last Post: curlymo
  homebridge and pilight with scenes ebini 2 1,359 09-16-2017, 10:37 PM
Last Post: apartmedia
  [Solved] dimmer protocol kaku_dimmer does not react on dimmervalue apartmedia 25 4,271 09-16-2017, 10:29 PM
Last Post: apartmedia

Forum Jump:


Browsing: 1 Guest(s)