• 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
Problems after upgrade with switching on and off multiple lamps consecutively
#21
I only updated the Raspbian OS including the kernel, and of course, the pilight, to the current version. I didn't any changes to the hardware.

Before that, I saved the old installation on a second SD card. So I'm able to switch between the two software configurations. I think these are the best conditions to find the problem. Let's start with the .sh script (see my first post). I call pilight-send several times in a row (obviously based on the socket API) to turn on different lights. In pilight's logs, I do not see anything problematic. Nevertheless, a maximum of one lamp is switched on. With the old configuration (Jessie and pilight 7.0) everything worked to about 99.5%. How can I get more information to help you identify if pilight is the problem?

If it's better, we also can work with the Openhab2 configuration.
 
Reply
#22
But calling pilight-send several times generates unnecessary overhead and possible bugs in pilight-send itself that I want to rule out. We need to know if only the daemon is to blame.
 
Reply
#23
(03-18-2019, 03:50 PM)curlymo Wrote: But calling pilight-send several times generates unnecessary overhead and possible bugs in pilight-send itself that I want to rule out. We need to know if only the daemon is to blame.

And the only way to do this, is to use one of the client examples which is adapted to my environment?

It is possible to change the debug level of the daemon in the event of starting it with -D parameter? If I remember right, I only saw information about the connected port.
 
Reply
#24
What info do you want?
 
Reply
#25
I just tested it myself. Running the daemon in debug mode:
Code:
[Mar 18 20:21:56:539543] pilight-daemon: DEBUG: socket recv: {"action":"send","code":{"on":1,"unit":2,"id":123456,"protocol":["kaku_switch"]}}

[Mar 18 20:21:56:540053] pilight-daemon: DEBUG: **** RAW CODE ****
[Mar 18 20:21:56:540056] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}
315 2835 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 315 315 1260 315 10710
[Mar 18 20:21:56:540320] pilight-daemon: DEBUG: **** RAW CODE ****

[Mar 18 20:21:56:543355] pilight-daemon: DEBUG: lua async on state #0

[Mar 18 20:21:56:544430] pilight-daemon: DEBUG: socket write succeeded: {"origin":"sender","protocol":"arctech_switch","message":{"id":123456,"unit":2,"state":"on"},"repeat":1,"uuid":"xxxx-xx-xx-xx-xxxxxx"}
[Mar 18 20:21:56:544496] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"arctech_switch","message":{"id":123456,"unit":2,"state":"on"},"repeat":1,"uuid":"xxxx-xx-xx-xx-xxxxxx"}

[Mar 18 20:21:56:694440] pilight-daemon: DEBUG: ssdp sent notify
[Mar 18 20:21:56:707773] pilight-daemon: DEBUG: lua wiringx on state #1

[Mar 18 20:21:56:724694] pilight-daemon: DEBUG: possible arctech_switch protocol
[Mar 18 20:21:56:724795] pilight-daemon: DEBUG: recevied pulse length of 319
[Mar 18 20:21:56:724830] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_switch
[Mar 18 20:21:56:724859] pilight-daemon: DEBUG: called arctech_switch parseRaw()

[Mar 18 20:21:56:725202] pilight-daemon: DEBUG: possible arctech_screen protocol
[Mar 18 20:21:56:725237] pilight-daemon: DEBUG: recevied pulse length of 319
[Mar 18 20:21:56:725263] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_screen
[Mar 18 20:21:56:725306] pilight-daemon: DEBUG: called arctech_screen parseRaw()

[Mar 18 20:21:56:725779] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":123456,"unit":2,"state":"on"},"origin":"receiver","protocol":"arctech_switch","uuid":"xxxx-xx-xx-xx-xxxxxx","repeats":1}
[Mar 18 20:21:56:725838] pilight-daemon: DEBUG: broadcasted: {"message":{"id":123456,"unit":2,"state":"on"},"origin":"receiver","protocol":"arctech_switch","uuid":"xxxx-xx-xx-xx-xxxxxx","repeats":1}

[Mar 18 20:21:56:726132] pilight-daemon: DEBUG: possible arctech_dimmer protocol
[Mar 18 20:21:56:726170] pilight-daemon: DEBUG: recevied pulse length of 319
[Mar 18 20:21:56:726209] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_dimmer
[Mar 18 20:21:56:726250] pilight-daemon: DEBUG: called arctech_dimmer parseRaw()

[Mar 18 20:21:56:726580] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":123456,"unit":2,"state":"up"},"origin":"receiver","protocol":"arctech_screen","uuid":"xxxx-xx-xx-xx-xxxxxx","repeats":1}
[Mar 18 20:21:56:726633] pilight-daemon: DEBUG: broadcasted: {"message":{"id":123456,"unit":2,"state":"up"},"origin":"receiver","protocol":"arctech_screen","uuid":"xxxx-xx-xx-xx-xxxxxx","repeats":1}

[Mar 18 20:21:56:726843] pilight-daemon: DEBUG: possible arctech_contact protocol
[Mar 18 20:21:56:726881] pilight-daemon: DEBUG: recevied pulse length of 319
[Mar 18 20:21:56:726914] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_contact
[Mar 18 20:21:56:726954] pilight-daemon: DEBUG: called arctech_contact parseRaw()

[Mar 18 20:21:56:727232] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":123456,"unit":2,"state":"on"},"origin":"receiver","protocol":"arctech_dimmer","uuid":"xxxx-xx-xx-xx-xxxxxx","repeats":1}
[Mar 18 20:21:56:727283] pilight-daemon: DEBUG: broadcasted: {"message":{"id":123456,"unit":2,"state":"on"},"origin":"receiver","protocol":"arctech_dimmer","uuid":"xxxx-xx-xx-xx-xxxxxx","repeats":1}

[Mar 18 20:21:56:727819] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":123456,"unit":2,"state":"opened"},"origin":"receiver","protocol":"arctech_contact","uuid":"xxxx-xx-xx-xx-xxxxxx","repeats":1}
[Mar 18 20:21:56:727872] pilight-daemon: DEBUG: broadcasted: {"message":{"id":123456,"unit":2,"state":"opened"},"origin":"receiver","protocol":"arctech_contact","uuid":"xxxx-xx-xx-xx-xxxxxx","repeats":1}

[Mar 18 20:21:56:802042] pilight-daemon: INFO: new client, ip: 10.0.0.141, port: 55682
[Mar 18 20:21:56:802142] pilight-daemon: DEBUG: client fd: 22
[Mar 18 20:21:56:802213] pilight-daemon: DEBUG: client id: 3
[Mar 18 20:21:56:802329] pilight-daemon: DEBUG: socket recv: {"action":"identify"}
[Mar 18 20:21:56:802502] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}
[Mar 18 20:21:56:802747] pilight-daemon: DEBUG: socket recv: {"action":"send","code":{"off":1,"unit":2,"id":123456,"protocol":["kaku_switch"]}}

[Mar 18 20:21:56:803249] pilight-daemon: DEBUG: **** RAW CODE ****
[Mar 18 20:21:56:803258] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}
315 2835 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 315 315 1260 315 1260 315 315 315 315 315 1260 315 10710
[Mar 18 20:21:56:803535] pilight-daemon: DEBUG: **** RAW CODE ****

[Mar 18 20:21:56:803559] pilight-daemon: DEBUG: client disconnected, ip 10.0.0.141, port 55682
[Mar 18 20:21:56:806339] pilight-daemon: DEBUG: lua async on state #1

[Mar 18 20:21:56:807418] pilight-daemon: DEBUG: socket write succeeded: {"origin":"sender","protocol":"arctech_switch","message":{"id":123456,"unit":2,"state":"off"},"repeat":1,"uuid":"xxxx-xx-xx-xx-xxxxxx"}
[Mar 18 20:21:56:807469] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"arctech_switch","message":{"id":123456,"unit":2,"state":"off"},"repeat":1,"uuid":"xxxx-xx-xx-xx-xxxxxx"}

[Mar 18 20:21:56:957665] pilight-daemon: DEBUG: lua wiringx on state #2
[Mar 18 20:21:57:207735] pilight-daemon: DEBUG: lua wiringx on state #2

[Mar 18 20:21:57:315028] pilight-daemon: DEBUG: cpu: 15.078859%

The pilight-send command given was:
Code:
./pilight-send -p kaku_switch -i 123456 -u 2 -t && sleep 0.1 && ./pilight-send -p kaku_switch -i 123456 -u 2 -f

Check the debug output:
  • 20:21:56:539543: First command arrived
  • 20:21:56:540056: Code was sent, actual light turned on
  • 20:21:56:725779: pilight itself received the sent code again
  • 20:21:56:802747: Second command was received (3 milliseconds later)
  • 20:21:56:803258: Code was sent, actual light turned off
I think it took about 1 second for the light to turn on and off. And 3 milliseconds to parse and sent both codes.

Can you do the same, post pilight-daemon debug output and tell me what happens with your lights at the different output moments.
 
Reply
#26
Hi,

hopefully I'll be able to check this out this evening. Therefore, first I have to bring my System to the current pilight version. Is it recommendable, first to remove the current pilight installation?

In comparison with your logs (see my first post), I can't see things like lua async on state #0, lua wiringx on state #1, arctech_switch protocol in my logs!?

And why, do you have have only one "client disconnect" in your logs? In my case, every pilight-send call seems to cause a new connection.
 
Reply
#27
The lua stuff depends on what version you tested. The arctech_switch is just the device i own.

The first client disconnect is missing because i stripped my logs too much Smile
 
Reply
#28
Hallo again,

sorry for the delay. In fact, I am only now able to continue with the investigations regarding my pilight issues.

I took another pi using the sd card with the updated system. I removed the version 7.0 of pilight and installed the current version (8.1.4).

Now I would like to continue my tests but first, I have to solve some new problems. I'm a little bit confuesd. Since I have been installed the new pilight version, i only can call the pilight-send command as sudo. Do you have an idea, why it is?

If I call the pilight-send as sudo, i get the following error in the pilight.log

[May 01 10:47:49:517540] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode.

Current conig.json:


Code:
{
       "devices": {},
       "rules": {},
       "gui": {},
       "settings": {
               "log-level": 6,
               "pid-file": "/var/run/pilight.pid",
               "log-file": "/var/log/pilight.log",
               "standalone": 0,
               "webserver-enable": 1,
               "webserver-root": "/usr/local/share/pilight/webgui",
               "webserver-http-port": 5001,
               "webserver-https-port": 5002,
               "webserver-cache": 1,
               "whitelist": "",
               "gpio-platform": "raspberrypi3"
       },
       "hardware": {
               "433gpio": {
                       "sender": 3,
                       "receiver": 4
               }
       },
       "registry": {
               "webserver": {
                       "ssl": {
                               "certificate": {
                                       "location": "/etc/pilight/pilight.pem"
                               }
                       }
               },
               "pilight": {
                       "version": {
                               "current": "8.1.4"
                       }
               },
               "hardware": {
                       "RF433": {
                               "mingaplen": 4420,
                               "maxgaplen": 72900,
                               "minrawlen": 26,
                               "maxrawlen": 400
                       }
               }
       }
}
 
Reply
#29
That error has already been posted here:
https://forum.pilight.org/showthread.php...1#pid24201

Please continue there about this issue.
 
Reply
#30
(05-01-2019, 05:22 PM)curlymo Wrote: That error has already been posted here:
https://forum.pilight.org/showthread.php...1#pid24201

Please continue there about this issue.

Ok, thanks.

What about the issue regarding sudo?
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  433gpio platform error after raspbian dist upgrade HuberDe 2 218 10-12-2019, 07:35 PM
Last Post: HuberDe
Information Switching speed? rajd 4 531 12-17-2018, 09:07 AM
Last Post: rajd
  Daemon problems: no apparant sudo access Surowa 3 658 08-14-2018, 06:21 AM
Last Post: curlymo
Thumbs Up Newbie problems, usbnano connection and rsl366 pukington 1 541 02-14-2018, 07:36 PM
Last Post: pukington
  Elro 800 issues after upgrade to 8.0.9 TomiB 2 682 01-29-2018, 10:12 PM
Last Post: TomiB
  Multiple screens/shutters Ulrich.Arnold 5 997 01-29-2018, 09:17 PM
Last Post: curlymo
  Upgrade to jessie+pilight+kernel failed witty 10 2,068 01-04-2018, 12:27 PM
Last Post: witty
  SSDP Problems stritzi 1 928 11-14-2017, 01:18 PM
Last Post: curlymo
  multiple uuid's, what's the syntax? hansrijn2 3 882 10-31-2017, 12:26 PM
Last Post: curlymo
  multiple 433mhz senders koos147 9 2,202 10-05-2017, 09:12 PM
Last Post: koos147

Forum Jump:


Browsing: 1 Guest(s)