• 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
odd behaviour of kaku dimmers in GUI
#1
I have a number of kaku dimmers and switches. All of them can be controlled both with a remote (only on/of, no dim) and via the GUI. In addition I am using some kaku sensors.

One of the switches is used as a "slave" that follows the on/off state of a dimmer via a rule.
To prevent interference, I did put a delay of 500 millisecond in the rule that switches the "slave".

Code:
"IF hk3.state == on OR hk3.state == off THEN switch DEVICE hk3b TO hk3.state AFTER '500 MILLISECOND'",

Now quite often the actual delay is much longer (several seconds). This is not a very serious issue, but it may point to some bug or overload.

A really annoying issue is that when I switch off a dimmer via the GUI, sometimes  the lamp goes off indeed, but the toggle button in the GUI immediately reverts to ON and sometimes the dimlevel then gets changed to some "random" value. This happens only in the GUI, nothing is actually being sent, so the lamp stays off. 
Even worse, in some cases, when I switch off one dimmer via the GUI, the toggle and the dimlevel of other kaku dimmers are getting changed in the GUI too, also without anything really being sent. 

In the debug output, I can see many broadcasts and socket writes after switching off just one kaku dimmer via the GUI, but no other raw codes than the one for switching off that dimmer. As said, I am using several kaku protocols and for every one of those there are broadcasts and socket writes. Also I can see that the cpu usage increases to above 50% (normally  that is around 14% on my raspi B+).
 
I noticed this effect before only when my kaku sensors are changing state, but now it happens for every kaku device. This imho is due to the fact that pilight now can send and receive at the same time and thus is receiving also what it is sendeng itself. 

Sometimes the cpu load goes up to 80% or more. That happens especially when multiple kaku devices are being switched around the same time and it seems that sometimes the raw code received in this situation is not parsed correctly. Maybe due to some kind of "overrun"?

It is not easy to reproduce this behaviour, because it happens randomly, but I caught this one. I switched the dimmer (hk2) first to on (at 10:52:51:525210) and when it was on I switched it back to off (at 10:52:52:29394). As you can see the cpu load went up to 100% when I switched back to off, but the dimmer was actually switched to off correctly. Without me doing anything else, you can see a socket write at the end (at 10:52:52:765716)  that sets the state to on and the dimlevel to 2.

This is the config of the device involved:

Code:
               "hk2": {
                       "protocol": [ "kaku_dimmer", "kaku_switch" ],
                       "id": [{
                               "id": 16286374,
                               "unit": 5
                       }],
                       "state": "off",
                       "dimlevel": 11
                },

And this is the relevant part of the pilight-deamon debug output

Code:
[Jun 05 10:52:51:525210] pilight-daemon: DEBUG: socket recv: {"action":"control","code":{"device":"hk2","state":"on","values":{"dimlevel":11}}}
worker 1, executed REASON_SOCKET_RECEIVED in 0.001355 sec using 0.000000% CPU
[Jun 05 10:52:51:526754] pilight-daemon: DEBUG: **** RAW CODE ****
300 3000 300 300 300 1200 300 300 300 1200 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 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 300 300 1200 300 300 300 1200 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 1200 300 300 300 1200 300 300 300 300 300 1200 300 300 300 1200 300 300 300 300 300 300 300 1200 300 1200 300 300 300 300 300 1200 300 1200 300 300 300 1200 300 300 300 300 300 1200 300 1200 300 300 300 1200 300 300 300 10200
[Jun 05 10:52:51:527347] pilight-daemon: DEBUG: **** RAW CODE ****
[Jun 05 10:52:51:529586] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":2,"uuid":"0000-b8-27-eb-aefa8e","devices":["hk2"],"values":{"timestamp":1528195971,"state":"on","dimlevel":11}}

[Jun 05 10:52:51:529751] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":2,"uuid":"0000-b8-27-eb-aefa8e","devices":["hk2"],"values":{"timestamp":1528195971,"state":"on","dimlevel":11}}
[Jun 05 10:52:51:530440] pilight-daemon: DEBUG: socket write succeeded: {"origin":"sender","protocol":"arctech_dimmer","message":{"id":16286374,"unit":5,"dimlevel":11,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-aefa8e"}

[Jun 05 10:52:51:530581] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"arctech_dimmer","message":{"id":16286374,"unit":5,"dimlevel":11,"state":"on"},"repeat":1,"uuid":"0000-b8-27-eb-aefa8e"}
worker 2, executed REASON_SOCKET_SEND in 0.000101 sec using 0.000000% CPU
worker 3, executed REASON_BROADCAST_CORE in 0.000065 sec using 0.000000% CPU
worker 3, executed REASON_BROADCAST_CORE in 0.000026 sec using 0.000000% CPU
[Jun 05 10:52:51:546283] pilight-daemon: DEBUG: rule #30 hk2log was parsed in 0.001731 seconds
[Jun 05 10:52:51:578610] pilight-daemon: DEBUG: rule #92 vakantie_hk3_on was parsed in 0.000323 seconds
[Jun 05 10:52:51:583562] pilight-daemon: DEBUG: rule #93 vakantie_hk1_off was parsed in 0.000317 seconds
[Jun 05 10:52:51:593919] pilight-daemon: DEBUG: cpu: 49.773444%
[Jun 05 10:52:51:597074] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":8,"uuid":"0000-b8-27-eb-aefa8e","devices":["dt"],"values":{"timestamp":1528195971,"year":2018,"month":6,"day":5,"weekday":3,"hour":12,"minute":52,"second":51,"dst":1}}

[Jun 05 10:52:51:597242] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":8,"uuid":"0000-b8-27-eb-aefa8e","devices":["dt"],"values":{"timestamp":1528195971,"year":2018,"month":6,"day":5,"weekday":3,"hour":12,"minute":52,"second":51,"dst":1}}
[Jun 05 10:52:51:598171] pilight-daemon: DEBUG: socket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":4.600000,"latitude":52.300000,"year":2018,"month":6,"day":5,"weekday":3,"hour":12,"minute":52,"second":51,"dst":1},"uuid":"0000-b8-27-eb-aefa8e"}

[Jun 05 10:52:51:598325] pilight-daemon: DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":4.600000,"latitude":52.300000,"year":2018,"month":6,"day":5,"weekday":3,"hour":12,"minute":52,"second":51,"dst":1},"uuid":"0000-b8-27-eb-aefa8e"}
worker 0, executed REASON_BROADCAST_CORE in 0.000099 sec using 0.000000% CPU
worker 0, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 0, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 0, executed REASON_RECEIVED_PULSETRAIN in 0.000083 sec using 0.000000% CPU
worker 3, executed REASON_RECEIVED_PULSETRAIN in 0.000093 sec using 0.000000% CPU
[Jun 05 10:52:51:663344] pilight-daemon: DEBUG: rule #3 ping_request was parsed in 0.000960 seconds
[Jun 05 10:52:51:668487] pilight-daemon: DEBUG: rule #4 beep_request was parsed in 0.000647 seconds
[Jun 05 10:52:51:717282] pilight-daemon: DEBUG: rule #65 portiek_on_kerst was parsed in 0.002545 seconds
[Jun 05 10:52:51:724408] pilight-daemon: DEBUG: rule #67 toilet_open_sunset was parsed in 0.001999 seconds
[Jun 05 10:52:51:728523] pilight-daemon: DEBUG: rule #71 tuin1_on_kerst1 was parsed in 0.001047 seconds
[Jun 05 10:52:51:732458] pilight-daemon: DEBUG: rule #73 tuin1_off_kerst was parsed in 0.000914 seconds
worker 1, executed REASON_RECEIVED_PULSETRAIN in 0.000366 sec using 0.000000% CPU
[Jun 05 10:52:51:739434] pilight-daemon: DEBUG: rule #75 tuin2_on_vijver was parsed in 0.002072 seconds
[Jun 05 10:52:51:744851] pilight-daemon: DEBUG: rule #76 tuin2_off_vijver was parsed in 0.001109 seconds
[Jun 05 10:52:51:758352] pilight-daemon: DEBUG: rule #85 vakantie_zk1 was parsed in 0.002020 seconds
[Jun 05 10:52:51:764518] pilight-daemon: DEBUG: rule #86 vakantie_zk2 was parsed in 0.002307 seconds
[Jun 05 10:52:51:770782] pilight-daemon: DEBUG: rule #87 vakantie_sk was parsed in 0.001020 seconds
[Jun 05 10:52:51:776835] pilight-daemon: DEBUG: rule #88 vakantie_kantoor was parsed in 0.001375 seconds
[Jun 05 10:52:51:782432] pilight-daemon: DEBUG: rule #89 vakantie_bk was parsed in 0.001505 seconds
[Jun 05 10:52:51:793266] pilight-daemon: DEBUG: rule #95 vakantie_zonnescherm1 was parsed in 0.002540 seconds
[Jun 05 10:52:51:800516] pilight-daemon: DEBUG: rule #96 vakantie_zonnescherm2 was parsed in 0.003353 seconds
[Jun 05 10:52:51:812970] pilight-daemon: DEBUG: rule #105 geenregen was parsed in 0.001738 seconds
[Jun 05 10:52:51:819571] pilight-daemon: DEBUG: rule #106 regen was parsed in 0.001282 seconds
[Jun 05 10:52:51:827018] pilight-daemon: DEBUG: rule #107 bewatering_nodig was parsed in 0.003678 seconds
[Jun 05 10:52:51:831594] pilight-daemon: DEBUG: rule #108 bewatering_niet_nodig was parsed in 0.002380 seconds
worker 0, executed REASON_RECEIVED_PULSETRAIN in 0.000103 sec using 0.000000% CPU
[Jun 05 10:52:51:841137] pilight-daemon: DEBUG: rule #109 extra_bewatering_nodig was parsed in 0.006949 seconds
[Jun 05 10:52:51:852234] pilight-daemon: DEBUG: rule #110 extra_bewatering_niet_nodig was parsed in 0.007367 seconds
[Jun 05 10:52:51:860021] pilight-daemon: DEBUG: rule #111 bewateringdagelijks was parsed in 0.002405 seconds
[Jun 05 10:52:51:867014] pilight-daemon: DEBUG: rule #112 bewateringextra was parsed in 0.003052 seconds
[Jun 05 10:52:51:875127] pilight-daemon: DEBUG: rule #115 bewateringovergeslagen1 was parsed in 0.001968 seconds
[Jun 05 10:52:51:881815] pilight-daemon: DEBUG: rule #116 bewateringovergeslagen2 was parsed in 0.002801 seconds
[Jun 05 10:52:51:894062] pilight-daemon: DEBUG: rule #121 flowlog was parsed in 0.005777 seconds
[Jun 05 10:52:51:906117] pilight-daemon: DEBUG: rule #122 moistlog was parsed in 0.008034 seconds
[Jun 05 10:52:51:912022] pilight-daemon: DEBUG: rule #123 bewateringstatus_request was parsed in 0.000522 seconds
worker 3, executed REASON_RECEIVED_PULSETRAIN in 0.000100 sec using 0.000000% CPU
[Jun 05 10:52:51:937619] pilight-daemon: DEBUG: possible arctech_contact_switch protocol
[Jun 05 10:52:51:940339] pilight-daemon: DEBUG: recevied pulse length of 299
[Jun 05 10:52:51:943796] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_contact_switch
[Jun 05 10:52:51:944717] pilight-daemon: DEBUG: called arctech_contact_switch parseRaw()
[Jun 05 10:52:51:949293] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":16351910,"unit":5,"state":"off"},"origin":"receiver","protocol":"arctech_contact_switch","uuid":"0000-b8-27-eb-aefa8e","repeats":1}

[Jun 05 10:52:51:949548] pilight-daemon: DEBUG: broadcasted: {"message":{"id":16351910,"unit":5,"state":"off"},"origin":"receiver","protocol":"arctech_contact_switch","uuid":"0000-b8-27-eb-aefa8e","repeats":1}
worker 1, executed REASON_BROADCAST_CORE in 0.000069 sec using 0.000000% CPU
[Jun 05 10:52:51:953145] pilight-daemon: DEBUG: possible arctech_dimmer protocol
[Jun 05 10:52:51:953920] pilight-daemon: DEBUG: recevied pulse length of 299
[Jun 05 10:52:51:955141] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_dimmer
[Jun 05 10:52:51:956083] pilight-daemon: DEBUG: called arctech_dimmer parseRaw()
[Jun 05 10:52:51:964043] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":16351910,"unit":5,"dimlevel":11,"state":"on"},"origin":"receiver","protocol":"arctech_dimmer","uuid":"0000-b8-27-eb-aefa8e","repeats":1}

[Jun 05 10:52:51:964249] pilight-daemon: DEBUG: broadcasted: {"message":{"id":16351910,"unit":5,"dimlevel":11,"state":"on"},"origin":"receiver","protocol":"arctech_dimmer","uuid":"0000-b8-27-eb-aefa8e","repeats":1}
worker 0, executed REASON_BROADCAST_CORE in 0.000070 sec using 0.000000% CPU
[Jun 05 10:52:51:967910] pilight-daemon: DEBUG: possible arctech_contact protocol
[Jun 05 10:52:51:973807] pilight-daemon: DEBUG: recevied pulse length of 299
[Jun 05 10:52:51:974243] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_contact
[Jun 05 10:52:51:988730] pilight-daemon: DEBUG: called arctech_contact parseRaw()
[  Jun 05 10:52:52:9202] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":13664422,"unit":0,"state":"closed"},"origin":"receiver","protocol":"arctech_contact","uuid":"0000-b8-27-eb-aefa8e","repeats":1}

[  Jun 05 10:52:52:9391] pilight-daemon: DEBUG: broadcasted: {"message":{"id":13664422,"unit":0,"state":"closed"},"origin":"receiver","protocol":"arctech_contact","uuid":"0000-b8-27-eb-aefa8e","repeats":1}
worker 3, executed REASON_BROADCAST_CORE in 0.000064 sec using 0.000000% CPU
[ Jun 05 10:52:52:29394] pilight-daemon: DEBUG: socket recv: {"action":"control","code":{"device":"hk2","state":"off"}}
worker 1, executed REASON_SOCKET_RECEIVED in 0.001312 sec using 99.996652% CPU
[ Jun 05 10:52:52:30984] pilight-daemon: DEBUG: **** RAW CODE ****
300 3000 300 300 300 1200 300 300 300 1200 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 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 300 300 1200 300 300 300 1200 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 1200 300 300 300 1200 300 300 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 1200 300 300 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 300 300 1200 300 10200
[ Jun 05 10:52:52:31646] pilight-daemon: DEBUG: **** RAW CODE ****
[ Jun 05 10:52:52:33775] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":2,"uuid":"0000-b8-27-eb-aefa8e","devices":["hk2"],"values":{"timestamp":1528195972,"state":"off"}}

[ Jun 05 10:52:52:33933] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":2,"uuid":"0000-b8-27-eb-aefa8e","devices":["hk2"],"values":{"timestamp":1528195972,"state":"off"}}
[ Jun 05 10:52:52:34554] pilight-daemon: DEBUG: socket write succeeded: {"origin":"sender","protocol":"arctech_dimmer","message":{"id":16286374,"unit":5,"state":"off"},"repeat":1,"uuid":"0000-b8-27-eb-aefa8e"}

[ Jun 05 10:52:52:34696] pilight-daemon: DEBUG: broadcasted: {"origin":"sender","protocol":"arctech_dimmer","message":{"id":16286374,"unit":5,"state":"off"},"repeat":1,"uuid":"0000-b8-27-eb-aefa8e"}
worker 0, executed REASON_SOCKET_SEND in 0.000048 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000094 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_RECEIVED_PULSETRAIN in 0.000063 sec using 0.000000% CPU
[Jun 05 10:52:52:334908] pilight-daemon: DEBUG: rule #30 hk2log was parsed in 0.000464 seconds
[Jun 05 10:52:52:366071] pilight-daemon: DEBUG: rule #92 vakantie_hk3_on was parsed in 0.000809 seconds
[Jun 05 10:52:52:370432] pilight-daemon: DEBUG: rule #93 vakantie_hk1_off was parsed in 0.000908 seconds
worker 3, executed REASON_RECEIVED_PULSETRAIN in 0.000083 sec using 0.000000% CPU
worker 2, executed REASON_SEND_CODE in 1.010796 sec using 6.647269% CPU
[Jun 05 10:52:52:596382] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":8,"uuid":"0000-b8-27-eb-aefa8e","devices":["dt"],"values":{"timestamp":1528195972,"year":2018,"month":6,"day":5,"weekday":3,"hour":12,"minute":52,"second":52,"dst":1}}

[Jun 05 10:52:52:596571] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":8,"uuid":"0000-b8-27-eb-aefa8e","devices":["dt"],"values":{"timestamp":1528195972,"year":2018,"month":6,"day":5,"weekday":3,"hour":12,"minute":52,"second":52,"dst":1}}
[Jun 05 10:52:52:597480] pilight-daemon: DEBUG: socket write succeeded: {"origin":"receiver","protocol":"datetime","message":{"longitude":4.600000,"latitude":52.300000,"year":2018,"month":6,"day":5,"weekday":3,"hour":12,"minute":52,"second":52,"dst":1},"uuid":"0000-b8-27-eb-aefa8e"}

[Jun 05 10:52:52:597684] pilight-daemon: DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":4.600000,"latitude":52.300000,"year":2018,"month":6,"day":5,"weekday":3,"hour":12,"minute":52,"second":52,"dst":1},"uuid":"0000-b8-27-eb-aefa8e"}
worker 1, executed REASON_BROADCAST_CORE in 0.000086 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
[Jun 05 10:52:52:602700] pilight-daemon: DEBUG: rule #3 ping_request was parsed in 0.002050 seconds
[Jun 05 10:52:52:605801] pilight-daemon: DEBUG: rule #4 beep_request was parsed in 0.000193 seconds
[Jun 05 10:52:52:683052] pilight-daemon: DEBUG: rule #65 portiek_on_kerst was parsed in 0.001595 seconds
[Jun 05 10:52:52:690925] pilight-daemon: DEBUG: rule #67 toilet_open_sunset was parsed in 0.002690 seconds
[Jun 05 10:52:52:700500] pilight-daemon: DEBUG: rule #71 tuin1_on_kerst1 was parsed in 0.003025 seconds
[Jun 05 10:52:52:708038] pilight-daemon: DEBUG: rule #73 tuin1_off_kerst was parsed in 0.002220 seconds
[Jun 05 10:52:52:714740] pilight-daemon: DEBUG: rule #75 tuin2_on_vijver was parsed in 0.001422 seconds
[Jun 05 10:52:52:720923] pilight-daemon: DEBUG: rule #76 tuin2_off_vijver was parsed in 0.001209 seconds
[Jun 05 10:52:52:729818] pilight-daemon: DEBUG: rule #85 vakantie_zk1 was parsed in 0.000663 seconds
[Jun 05 10:52:52:732871] pilight-daemon: DEBUG: rule #86 vakantie_zk2 was parsed in 0.000999 seconds
[Jun 05 10:52:52:736008] pilight-daemon: DEBUG: rule #87 vakantie_sk was parsed in 0.000998 seconds
worker 2, executed REASON_RECEIVED_PULSETRAIN in 0.000171 sec using 0.000000% CPU
[Jun 05 10:52:52:739900] pilight-daemon: DEBUG: possible arctech_contact_switch protocol
[Jun 05 10:52:52:743258] pilight-daemon: DEBUG: recevied pulse length of 307
[Jun 05 10:52:52:744606] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_contact_switch
[Jun 05 10:52:52:746392] pilight-daemon: DEBUG: called arctech_contact_switch parseRaw()
[Jun 05 10:52:52:748916] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":16286374,"unit":5,"state":"off"},"origin":"receiver","protocol":"arctech_contact_switch","uuid":"0000-b8-27-eb-aefa8e","repeats":1}

[Jun 05 10:52:52:749108] pilight-daemon: DEBUG: broadcasted: {"message":{"id":16286374,"unit":5,"state":"off"},"origin":"receiver","protocol":"arctech_contact_switch","uuid":"0000-b8-27-eb-aefa8e","repeats":1}
worker 1, executed REASON_BROADCAST_CORE in 0.000075 sec using 0.000000% CPU
[Jun 05 10:52:52:752749] pilight-daemon: DEBUG: possible arctech_dimmer protocol
[Jun 05 10:52:52:754408] pilight-daemon: DEBUG: recevied pulse length of 307
[Jun 05 10:52:52:755050] pilight-daemon: DEBUG: caught minimum # of repeats 1 of arctech_dimmer
[Jun 05 10:52:52:755767] pilight-daemon: DEBUG: called arctech_dimmer parseRaw()
[Jun 05 10:52:52:765716] pilight-daemon: DEBUG: socket write succeeded: {"origin":"update","type":2,"uuid":"0000-b8-27-eb-aefa8e","devices":["hk2"],"values":{"timestamp":1528195972,"state":"on","dimlevel":2}}

[Jun 05 10:52:52:765903] pilight-daemon: DEBUG: broadcasted: {"origin":"update","type":2,"uuid":"0000-b8-27-eb-aefa8e","devices":["hk2"],"values":{"timestamp":1528195972,"state":"on","dimlevel":2}}
[Jun 05 10:52:52:766575] pilight-daemon: DEBUG: socket write succeeded: {"message":{"id":16286374,"unit":5,"dimlevel":2,"state":"on"},"origin":"receiver","protocol":"arctech_dimmer","uuid":"0000-b8-27-eb-aefa8e","repeats":1}

[Jun 05 10:52:52:766719] pilight-daemon: DEBUG: broadcasted: {"message":{"id":16286374,"unit":5,"dimlevel":2,"state":"on"},"origin":"receiver","protocol":"arctech_dimmer","uuid":"0000-b8-27-eb-aefa8e","repeats":1}
worker 3, executed REASON_BROADCAST_CORE in 0.000068 sec using 0.000000% CPU
worker 3, executed REASON_BROADCAST_CORE in 0.000026 sec using 0.000000% CPU

Sorry for this rather long post, but I wanted to give you as much info I could get.
 
Reply
#2
Indeed, thanks for the extensive post.

I think this is indeed due to the receiving and sending at the same time. This should be fixed for the arctech_dimmers, but i'm not aware of issues with the switches.

https://github.com/pilight/pilight/commi...b97d1f6b5d
https://github.com/pilight/pilight/commi...b19b4b7baa
https://github.com/pilight/pilight/commi...85ce9f341a
https://github.com/pilight/pilight/commi...55dac33501
https://github.com/pilight/pilight/commi...ea96424598
https://github.com/pilight/pilight/commi...430cac95eb
https://github.com/pilight/pilight/commi...07437b94a0

Can you check this with the arctech_dimmers in an isolated environment to see if the fix was correct?

I wouldn't care about the CPU usage, because the spikes are just for a short while.
 
Reply
#3
Have those fixes not been applied to version 8 then?

I had been focussing on what I saw happening in the gui, but I know now that the state and dimlevel in the config are actually changed when it happens. So it is not just a gui issue. I didn't see that before, because I was using the same config file every time.

So what happens is that the dimmer device is requested to update its state due to receiving back what it was sending itself. If it works normally, the update will be ignored, because the dimmer already is in that state.  But when it goes wrong, the state (and sometimes also dimlevel) in the update request are wrong, making the state different from the actual state and thus the update will be applied.

The high cpu load as such doesn't worry me so much, but there seems to be a correlation between the odd behaviour of the dimmers and the high cpu load. It only happens when the cpu load is very high.

I don't think there is a problem with kaku_switch itself. What I wrote is, that although I applied a delay of 500 millisecond, the actual delay is much longer (up to 3 seconds). Because the switch action is triggered by a state change of a dimmer, I think that this also could be related to the high cpu load.

I have been using the same config (apart from the mandatory quotes) with version 7 for a long time without problems with the dimmers.
 
Reply
#4
Quote:Have those fixes not been applied to version 8 then?
Those are version 8 commits Wink

Quote:I don't think there is a problem with kaku_switch itself. What I wrote is, that although I applied a delay of 500 millisecond, the actual delay is much longer (up to 3 seconds). Because the switch action is triggered by a state change of a dimmer, I think that this also could be related to the high cpu load.
That's because the rule is cancelled due to the new dimlevel change until the last one.

What we need to do is making sure that pilight receives the same thing as it sends. The commits i posted were the effort to get to that for the dimmers. Maybe we need more tweaking still.
 
Reply
#5
Yes indeed. As it is now, I cannot keep using version 8 for unattended operation. For now I will put my working version 7 card back in. That ofc. also has some drawbacks, but at least works fairly reliable.

If you have found a tweak, I will be happy to test it.
 
Reply
#6
In an isolated environment, can you check if you can send and receive kaku devices correctly with version 8. Switches and dimmer seperately. When pilight send, can you check if the receive data is the same as the sent one?
 
Reply
#7
I will do that, but I already saw that when the cpu load is "normal" every kaku dimmer and switch works as expected. This is the case more than 90%  of the time.

Only when the cpu load gets extremely high, it goes wrong. I wouldn't be surprised if the cpu simply cannot handle the receive interrupts properly in that  situation.

It is just a guess, but possibly misinterpretating the duration of one or more pulses will still result in a technically valid pulsetrain for the dimmer. The dimlevel is in  the last four bits of the protocol. If the spike occurs at that moment, the dimlevel can be corrupted. If the number of affected pulses is even more, also the unit (just before the dimlevel in the protocol) can be corrupted and that would explain why sometimes other kaku dimmers also are affected.
 
Reply
#8
I've added a new feature to the staging code that disables the loopback by default. Can you check if that fixes the dimmer, failing events and cpu spike issue?

The eventing issue will be next.
 
Reply
#9
Do I need to add setings for this version to work?

What I see now something seems to be sent once when I switch a kaku device in the gui, but the sockets are not reacting. Also the pilight kaku devices are not listening to the remote anymore. 

I noticed that sometimes the sockets themselves were responding poorly to the remote, when pilight was running. I saw no raw codes in the debug output at that time, but pilight seemed to be sending continiously, causing interference with the remote. After some time the sockets are responding to the remote normally again.

At some other point the demon seemed to get crazy, spitting out "rule parsed" messages continuously at huge speed.

Finally this snippet from the debug output after trying to stop the daemon with ctrl C seems to indicate some "endless loop".

Code:
[Jun 08 10:43:49:950851] pilight-daemon: DEBUG: broadcasted: {"origin":"update",                                                                                                             "type":8,"uuid":"0000-b8-27-eb-aefa8e","devices":["dt"],"values":{"timestamp":15                                                                                                             28454629,"year":2018,"month":6,"day":8,"weekday":6,"hour":12,"minute":43,"second                                                                                                             ":49,"dst":1}}
[Jun 08 10:43:49:951700] pilight-daemon: DEBUG: socket write succeeded: {"origin                                                                                                             ":"receiver","protocol":"datetime","message":{"longitude":4.600000,"latitude":52                                                                                                             .300000,"year":2018,"month":6,"day":8,"weekday":6,"hour":12,"minute":43,"second"                                                                                                             :49,"dst":1},"uuid":"0000-b8-27-eb-aefa8e"}

[Jun 08 10:43:49:951876] pilight-daemon: DEBUG: broadcasted: {"origin":"receiver                                                                                                             ","protocol":"datetime","message":{"longitude":4.600000,"latitude":52.300000,"ye                                                                                                             ar":2018,"month":6,"day":8,"weekday":6,"hour":12,"minute":43,"second":49,"dst":1                                                                                                             },"uuid":"0000-b8-27-eb-aefa8e"}
[Jun 08 10:43:50:871795] pilight-daemon: DEBUG: rule #111 bewateringdagelijks wa                                                                                                             s parsed in 0.950796 seconds
[Jun 08 10:43:50:890961] pilight-daemon: DEBUG: rule #112 bewateringextra was pa                                                                                                             rsed in 0.000820 seconds
[Jun 08 10:43:50:911758] pilight-daemon: DEBUG: rule #115 bewateringovergeslagen                                                                                                             1 was parsed in 0.000998 seconds
[Jun 08 10:43:50:923853] pilight-daemon: cpu usage too high 96.074982%, will abo                                                                                                             rt when this persists
[   Jun 08 10:43:51:609] pilight-daemon: DEBUG: socket write succeeded: {"origin                                                                                                             ":"update","type":8,"uuid":"0000-b8-27-eb-aefa8e","devices":["dt"],"values":{"ti                                                                                                             mestamp":1528454630,"year":2018,"month":6,"day":8,"weekday":6,"hour":12,"minute"                                                                                                             :43,"second":50,"dst":1}}

[   Jun 08 10:43:51:787] pilight-daemon: DEBUG: broadcasted: {"origin":"update",                                                                                                             "type":8,"uuid":"0000-b8-27-eb-aefa8e","devices":["dt"],"values":{"timestamp":15                                                                                                             28454630,"year":2018,"month":6,"day":8,"weekday":6,"hour":12,"minute":43,"second                                                                                                             ":50,"dst":1}}
[  Jun 08 10:43:51:1623] pilight-daemon: DEBUG: socket write succeeded: {"origin                                                                                                             ":"receiver","protocol":"datetime","message":{"longitude":4.600000,"latitude":52                                                                                                             .300000,"year":2018,"month":6,"day":8,"weekday":6,"hour":12,"minute":43,"second"                                                                                                             :50,"dst":1},"uuid":"0000-b8-27-eb-aefa8e"}

[  Jun 08 10:43:51:1795] pilight-daemon: DEBUG: broadcasted: {"origin":"receiver                                                                                                             ","protocol":"datetime","message":{"longitude":4.600000,"latitude":52.300000,"ye                                                                                                             ar":2018,"month":6,"day":8,"weekday":6,"hour":12,"minute":43,"second":50,"dst":1                                                                                                             },"uuid":"0000-b8-27-eb-aefa8e"}
^C[Jun 08 10:43:51:881478] pilight-daemon: DEBUG: unexpected status reply: 3 cod                                                                                                             e: 1 at: 192.168.1.14 from: 192.168.1.9
[Jun 08 10:43:51:885819] pilight-daemon: DEBUG: rule #116 bewateringovergeslagen                                                                                                             2 was parsed in 0.000980 seconds
[Jun 08 10:43:51:903537] pilight-daemon: DEBUG: rule #119 flowlog was parsed in                                                                                                              0.002372 seconds
[Jun 08 10:43:51:921349] pilight-daemon: INFO: Interrupt signal received. Please                                                                                                              wait while pilight is shutting down
worker 0, executed REASON_SEND_CODE in 81.720508 sec using 0.044137% CPU
worker 1, executed REASON_SEND_CODE in 81.721400 sec using 0.033111% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000057 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000026 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000027 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000026 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000024 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000026 sec using 0.000000% CPU
worker 3, executed REASON_SEND_CODE in 81.107660 sec using 0.056997% CPU
worker 3, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 3, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 3, executed REASON_SOCKET_SEND in 0.000031 sec using 0.000000% CPU
worker 3, executed REASON_SOCKET_SEND in 0.000029 sec using 0.000000% CPU
worker 3, executed REASON_SOCKET_SEND in 0.000028 sec using 0.000000% CPU
worker 2, executed REASON_SEND_CODE in 71.973591 sec using 0.062916% CPU
worker 0, executed REASON_SEND_CODE in 0.928554 sec using 4.231410% CPU
worker 1, executed REASON_SEND_CODE in 0.931746 sec using 4.221668% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000027 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000028 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000027 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000028 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000027 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000027 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000028 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000076 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000055 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000028 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000028 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000056 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000055 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000055 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000057 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000058 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000028 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000028 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000054 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000060 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000035 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000057 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000092 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000029 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000076 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000074 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000030 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000093 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000084 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000087 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000076 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000035 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000075 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000031 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000078 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000078 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000080 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000032 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000076 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000035 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000076 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000038 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000116 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000087 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000033 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000082 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000080 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000035 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000078 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000038 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000089 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000035 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000035 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000098 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000080 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000039 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000034 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000081 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000035 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000080 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000079 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000038 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000094 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000039 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000035 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000081 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000036 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000039 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000040 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000080 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000040 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000037 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000038 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000087 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000039 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000038 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000039 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000080 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000041 sec using 0.000000% CPU
worker 1, executed REASON_BROADCAST_CORE in 0.000068 sec using 0.000000% CPU
worker 3, executed REASON_SEND_CODE in 0.960892 sec using 4.164798% CPU
worker 2, executed REASON_SEND_CODE in 0.959234 sec using 3.958785% CPU
[Jun 08 10:43:53:696525] pilight-daemon: DEBUG: rule #120 moistlog was parsed in                                                                                                              1.460209 seconds
[  Jun 08 10:43:54:3481] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.21
worker 0, executed REASON_SEND_CODE in 0.953503 sec using 4.384668% CPU
[ Jun 08 10:43:54:87931] pilight-daemon: DEBUG: rule #121 bewateringstatus_reque                                                                                                             st was parsed in 0.126651 seconds
[ Jun 08 10:43:57:40594] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.9
[   Jun 08 10:43:58:757] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.20
[   Jun 08 10:44:00:357] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.21
[Jun 08 10:44:02:160480] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.9
[Jun 08 10:44:05:200497] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.21
[Jun 08 10:44:07:437957] pilight-daemon: DEBUG: unexpected status reply: 0 code:                                                                                                              0 at: 192.168.1.222 from: 192.168.1.7
[Jun 08 10:44:08:162091] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.9
[Jun 08 10:44:10:560702] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.21
[Jun 08 10:44:13:360562] pilight-daemon: DEBUG: unexpected status reply: 3 code:                                                                                                              1 at: 192.168.1.14 from: 192.168.1.7
^C[Jun 08 10:44:15:600511] pilight-daemon: DEBUG: unexpected status reply: 3 cod                                                                                                             e: 1 at: 192.168.1.14 from: 192.168.1.21
[Jun 08 10:44:18:720439] pilight-daemon: DEBUG: unexpected status reply: 3 code: 1 at: 192.168.1.14 from: 192.168.1.7
[Jun 08 10:44:21:520460] pilight-daemon: DEBUG: unexpected status reply: 3 code: 1 at: 192.168.1.14 from: 192.168.1.21
 
Reply
#10
No, the loopback is now disabled by default and can be enabled with a:
Code:
"loopback": 1

In the settings.

Can we also please focus on one issue at the time and open separate topics for each of them. Can you do that still.

The first issue i'm trying to fix is pilight wrongly receiving codes sent by pilight at the same time. That should be fixed with disabling the loopback feature by default.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Wrong description for KAKU protocols Niek 5 725 06-17-2018, 09:00 AM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)