• 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
"FOR '2 MINUTE' FROM off" resulting in error
#1
Hi,

Still enjoying pilight I dare to issue an report on the special feature you made available on my request some months ago. It is not working anymore, after a certain period an error kicks in.

My rule is:
Code:
"Schuur_achter2_a_u": {"rule": "IF  HarijnSF10move.state == on THEN switch DEVICE HarijnSF10 TO on FOR '2 MINUTE' FROM off"},
 
When I keep receiving updates form the sonoff that something is moving I would like to overrule the previously set "2 minutes" with  again  "2 minutes" from the last time the move was detected. Thus resulting the light in the garage remains on as long as I am around. 

The result is now an error after some time:
Code:
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:04:54:651594] INFO: new client, ip: 192.168.1.7, port: 49636
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:04:58:530465] INFO: new client, ip: 192.168.1.7, port: 49638
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:04:59:691851] INFO: new client, ip: 192.168.1.7, port: 49640
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:04:701864] INFO: new client, ip: 192.168.1.7, port: 49642
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:09:897361] INFO: new client, ip: 192.168.1.7, port: 49646
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:14:906063] INFO: new client, ip: 192.168.1.7, port: 49650
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:17:261272] INFO: new client, ip: 192.168.1.7, port: 49654
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:17:481296] INFO: new client, ip: 192.168.1.7, port: 49660
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:20:143042] INFO: new client, ip: 192.168.1.7, port: 49662
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:25:153695] INFO: new client, ip: 192.168.1.7, port: 49664
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:28:540502] INFO: new client, ip: 192.168.1.7, port: 49666
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:30:265288] INFO: new client, ip: 192.168.1.7, port: 49668
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:35:278085] INFO: new client, ip: 192.168.1.7, port: 49672
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:40:361689] INFO: new client, ip: 192.168.1.7, port: 49674
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:42:143865] INFO: new client, ip: 192.168.1.7, port: 49676
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:42:312161] INFO: new client, ip: 192.168.1.7, port: 49678
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:45:375559] INFO: new client, ip: 192.168.1.7, port: 49680
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:50:498479] INFO: new client, ip: 192.168.1.7, port: 49682
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:55:518955] INFO: new client, ip: 192.168.1.7, port: 49686
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:05:58:575311] INFO: new client, ip: 192.168.1.7, port: 49688
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:00:653445] INFO: new client, ip: 192.168.1.7, port: 49690
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:05:666614] INFO: new client, ip: 192.168.1.7, port: 49692
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:10:678372] INFO: new client, ip: 192.168.1.7, port: 49694
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:06:12:7214] INFO: executed rule: Doorbell_schuur-voor3
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:15:691947] INFO: new client, ip: 192.168.1.7, port: 49700
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:20:703367] INFO: new client, ip: 192.168.1.7, port: 49704
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:25:715214] INFO: new client, ip: 192.168.1.7, port: 49706
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:06:25:722502] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:06:25:724696] INFO: executed rule: Doorbell_schuur-achter4
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:28:610129] INFO: new client, ip: 192.168.1.7, port: 49708
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:30:725780] INFO: new client, ip: 192.168.1.7, port: 49710
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:35:741570] INFO: new client, ip: 192.168.1.7, port: 49714
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:40:756921] INFO: new client, ip: 192.168.1.7, port: 49716
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:45:770868] INFO: new client, ip: 192.168.1.7, port: 49718
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:50:783612] INFO: new client, ip: 192.168.1.7, port: 49720
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:55:797316] INFO: new client, ip: 192.168.1.7, port: 49724
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:06:55:803080] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:06:56:155107] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:06:57:154708] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:06:58:156797] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:06:58:645076] INFO: new client, ip: 192.168.1.7, port: 49728
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:06:59:155910] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:00:155735] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:00:812910] INFO: new client, ip: 192.168.1.7, port: 49730
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:01:155631] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:02:157383] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:03:156381] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:04:155009] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:05:156935] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:05:828513] INFO: new client, ip: 192.168.1.7, port: 49732
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:06:157319] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:07:159564] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:08:158250] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:09:157510] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:10:157114] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:10:840423] INFO: new client, ip: 192.168.1.7, port: 49734
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:11:160294] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:12:161708] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:13:161317] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:14:160311] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:15:163188] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:15:857715] INFO: new client, ip: 192.168.1.7, port: 49738
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:16:163192] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:17:162368] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:18:161900] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:19:163191] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:20:163466] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:20:872368] INFO: new client, ip: 192.168.1.7, port: 49740
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:21:163707] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:22:164539] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:23:167249] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:24:165307] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:07:25:158583] INFO: executed rule: Schuur_achter2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:25:882892] INFO: new client, ip: 192.168.1.7, port: 49742
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:28:680528] INFO: new client, ip: 192.168.1.7, port: 49744
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:30:898011] INFO: new client, ip: 192.168.1.7, port: 49746
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:35:909034] INFO: new client, ip: 192.168.1.7, port: 49750
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:40:923718] INFO: new client, ip: 192.168.1.7, port: 49752
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:45:935791] INFO: new client, ip: 192.168.1.7, port: 49756
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:50:948338] INFO: new client, ip: 192.168.1.7, port: 49758
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:55:961654] INFO: new client, ip: 192.168.1.7, port: 49762
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:07:58:685306] INFO: new client, ip: 192.168.1.7, port: 49764
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:00:975272] INFO: new client, ip: 192.168.1.7, port: 49766
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:05:989058] INFO: new client, ip: 192.168.1.7, port: 49768
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:10:998950] INFO: new client, ip: 192.168.1.7, port: 49772
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:08:12:16739] INFO: executed rule: Doorbell_schuur-voor3
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:22:960774] INFO: new client, ip: 192.168.1.7, port: 49778
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:08:25:723824] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2357

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:27:973658] INFO: new client, ip: 192.168.1.7, port: 49780
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:28:715138] INFO: new client, ip: 192.168.1.7, port: 49782
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:32:985887] INFO: new client, ip: 192.168.1.7, port: 49784
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:08:32:992174] INFO: executed rule: Afzuigkap2_a_u
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:08:32:994798] INFO: executed rule: Doorbell_keuken2
(/home/pilight/source/daemon-dev/libs/pilight/events/events.c #2043) [Nov 13 16:08:33:8353] INFO: executed rule: TinyRadio_aan-uit
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:37:998184] INFO: new client, ip: 192.168.1.7, port: 49788
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:43:7011] INFO: new client, ip: 192.168.1.7, port: 49790
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:48:18826] INFO: new client, ip: 192.168.1.7, port: 49792
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:53:34980] INFO: new client, ip: 192.168.1.7, port: 49794
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:08:55:804404] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2357

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:08:56:156570] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:08:57:156330] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:58:47856] INFO: new client, ip: 192.168.1.7, port: 49798
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:08:58:158126] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:08:58:750332] INFO: new client, ip: 192.168.1.7, port: 49800
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:08:59:159305] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:09:00:156806] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2357

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:09:01:157245] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:09:02:157769] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 13 16:09:03:56997] INFO: new client, ip: 192.168.1.7, port: 49802
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:09:03:158437] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:09:04:155995] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)
 [#002] /usr/local/lib/pilight/actions/switch.lua:105

 number of element on stack: 3

 1: function
 2: function
 3: function

---- LUA STACKTRACE ----
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/lua.c #2591) [Nov 13 16:09:05:158932] ERROR:
---- LUA STACKTRACE ----
 error: /usr/local/lib/pilight/actions/switch.lua:105: skipping overridden action switch for device HarijnSF10
 module: /home/pilight/source/daemon-dev/libs/pilight/lua_c/async.c #763

 [#000] [C]:-1
 [#001] [C]:-1  (global error)

Just to be complete, the data produced by the sonoff-tasmota was.

Code:
16:47:33 MQT: tele/HarijnSF10/LWT = Online (retained)
16:47:33 MQT: cmnd/HarijnSF10/POWER =
17:06:11 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:06:14 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:06:19 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:06:21 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:06:26 MQT: stat/HarijnSF10/RESULT = {"POWER":"ON"}
17:06:26 MQT: stat/HarijnSF10/POWER = ON
17:06:26 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:06:29 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:06:33 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:06:36 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:06:47 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:06:54 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:06:57 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:07:01 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:07:07 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:07:16 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:07:28 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:07:31 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:07:35 MQT: cmnd/HarijnSF10move/POWER2 = ON
17:07:39 MQT: cmnd/HarijnSF10move/POWER2 = OFF
17:09:25 MQT: stat/HarijnSF10/RESULT = {"POWER":"OFF"}
17:09:25 MQT: stat/HarijnSF10/POWER = OFF
 
Reply
#2
First of all, the pilight nightly now supports MQTT so you can directly control Sonoff. I'm controlling Sonoff (flashed with Tasmota) devices myself. You can check the manual for more info.

Secondly, what should happen is the following, can you tell me if that's what you expected as well? And does this fail?

Code:
[00:00:00.000] Sonoff goes on, pilight triggers rule for 2 minutes.
[00:00:00.500] Sonoff goes off, do nothing.
[00:00:01.000] Sonoff goes on, first rule aborts and pilight triggers same rule again for 2 minutes.
[00:00:02.000] Sonoff goes off, do nothing.
[00:00:02.500] Sonoff goes on, second rule aborts and pilight triggers same rule again for 2 minutes.
[00:00:04.000] Sonoff goes off, do nothing
[00:00:04.500] Sonoff is still off, third rule completes
 
Reply
#3
Hi Curlymo, great thing that MQTT is now supported. I did not check that anymore since our last chat where I understood that was not to be expected in the near future. I will certainly check it out asap. 

Indeed the behaviour I would like is just as you described. I will redefine the current config witht the native MQTT and see what happens and let you know asap.

Best Regards, Hans
 
Reply
#4
Hi Curlymo,

I tried to connect pilight with the existing mosquitto MQTT server. I seem to miss something, because I could not see anything appear.

This is my config:

Code:
{
    "devices": {
        "SF1": {
            "protocol": [ "tasmota_switch" ],
            "id": [{
                "id": "TasmotaSF1"
            }],
            "state": "off"
        }
    },
    "rules": {},
    "gui": {
        "SF1": {
            "name": "SF1",
            "group": [ "HANDBEDIENING" ],
            "media": [ "web" ]
        }
    },
    "settings": {
        "name": "harijnwebnew",
        "adhoc-mode": "server",
        "standalone": 1,
        "log-level": 6,
        "pid-file": "/var/run/pilight.pid",
        "log-file": "/var/log/pilight/pilight.log",
        "webserver-enable": 1,
        "webserver-root": "/usr/local/share/pilight/webgui",
        "webserver-http-port": 5001,
        "webserver-https-port": 5002,
        "gpio-platform": "raspberrypi3",
        "webserver-cache": 1,
        "stats-enable": 1,
        "mqtt-enable": 0
    },
    "hardware": {
        "433gpio": {
            "sender": 15,
            "receiver": 7
        }
    },
    "registry": {
        "pilight": {
            "version": {
                "current": "8.1.5"
            }
        },
        "webserver": {
            "ssl": {
                "certificate": {
                    "location": "/etc/pilight/pilight.pem"
                }
            }
        },
        "hardware": {
            "RF433": {
                "mingaplen": 4420,
                "maxgaplen": 72900,
                "minrawlen": 26,
                "maxrawlen": 400
            }
        }
    }
}

When I use the switch on the webpage I expected to see a topic and message with the command: 
Code:
mosquitto_sub -t "#" -v


The debug log:  
Code:
[Nov 14 14:32:09:960092] INFO: version v8.1.5-nightly-1a19ab62
[Nov 14 14:32:09:970334] INFO: daemon listening to port: 38939
[Nov 14 14:32:09:971039] DEBUG: new thread socket, 1 thread running
[Nov 14 14:32:09:971170] DEBUG: new thread sender, 2 threads running
[Nov 14 14:32:09:971245] DEBUG: new thread broadcaster, 3 threads running
[Nov 14 14:32:09:971580] INFO: new client, ip: 127.0.0.1, port: 60728
[Nov 14 14:32:09:971670] DEBUG: client fd: 14
[Nov 14 14:32:09:971704] DEBUG: client id: 1
[Nov 14 14:32:09:977718] DEBUG: new thread receive parser, 4 threads running
[Nov 14 14:32:09:977869] DEBUG: new thread events client, 5 threads running
[Nov 14 14:32:09:977987] DEBUG: new thread events loop, 6 threads running
[Nov 14 14:32:09:978448] DEBUG: ssdp sent search
[Nov 14 14:32:09:978529] INFO: secured webserver started on port: 5002 (fd 16)
[Nov 14 14:32:09:978704] INFO: regular webserver started on port: 5001 (fd 17)
[Nov 14 14:32:10:75006] DEBUG: lua wiringx on state #0
[Nov 14 14:32:10:87056] NOTICE: no pilight ssdp connections found
[Nov 14 14:32:10:87558] DEBUG: socket write succeeded: {"action":"identify","options":{"config":1,"receiver":1},"media":"all"}

[Nov 14 14:32:10:87622] INFO: new client, ip: 127.0.0.1, port: 60730
[Nov 14 14:32:10:87651] DEBUG: client fd: 18
[Nov 14 14:32:10:87670] DEBUG: client id: 2
[Nov 14 14:32:10:87741] DEBUG: socket recv: {"action":"identify","options":{"config":1,"receiver":1},"media":"all"}
[Nov 14 14:32:10:87877] DEBUG: socket write succeeded: {"status":"success"}

[Nov 14 14:32:10:825251] DEBUG: cpu: 0.000000%
[Nov 14 14:32:13:825046] DEBUG: cpu: 0.100519%
[Nov 14 14:32:16:824999] DEBUG: cpu: 0.067014%
[Nov 14 14:32:19:825008] DEBUG: cpu: 0.068129%
[Nov 14 14:32:22:825038] DEBUG: cpu: 0.068321%
[Nov 14 14:32:25:825068] DEBUG: cpu: 0.069448%
[Nov 14 14:32:28:825165] DEBUG: cpu: 0.070506%
[Nov 14 14:32:31:825202] DEBUG: cpu: 0.070156%
[Nov 14 14:32:32:482018] DEBUG: new client, ip: 192.168.1.8, port: 52682
[Nov 14 14:32:32:482107] DEBUG: client fd: 19
[Nov 14 14:32:32:587108] DEBUG: new client, ip: 192.168.1.8, port: 52683
[Nov 14 14:32:32:587206] DEBUG: client fd: 19
[Nov 14 14:32:32:588007] DEBUG: new client, ip: 192.168.1.8, port: 52684
[Nov 14 14:32:32:588081] DEBUG: client fd: 20
[Nov 14 14:32:32:589014] DEBUG: new client, ip: 192.168.1.8, port: 52685
[Nov 14 14:32:32:589080] DEBUG: client fd: 21
[Nov 14 14:32:32:589971] DEBUG: new client, ip: 192.168.1.8, port: 52686
[Nov 14 14:32:32:590034] DEBUG: client fd: 22
[Nov 14 14:32:32:591201] DEBUG: new client, ip: 192.168.1.8, port: 52687
[Nov 14 14:32:32:591262] DEBUG: client fd: 23
[Nov 14 14:32:32:599890] DEBUG: new client, ip: 192.168.1.8, port: 52688
[Nov 14 14:32:32:599984] DEBUG: client fd: 26
[Nov 14 14:32:32:627150] DEBUG: new client, ip: 192.168.1.8, port: 52689
[Nov 14 14:32:32:627242] DEBUG: client fd: 19
[Nov 14 14:32:32:993939] DEBUG: new client, ip: 192.168.1.8, port: 52691
[Nov 14 14:32:32:994031] DEBUG: client fd: 19
[Nov 14 14:32:33:54649] DEBUG: new client, ip: 192.168.1.8, port: 52692
[Nov 14 14:32:33:54740] DEBUG: client fd: 19
[Nov 14 14:32:33:88601] DEBUG: new client, ip: 192.168.1.8, port: 52693
[Nov 14 14:32:33:88689] DEBUG: client fd: 19
[Nov 14 14:32:33:234615] DEBUG: socket recv: {"action":"request config"}
[Nov 14 14:32:33:286657] DEBUG: socket recv: {"action":"request values"}
[Nov 14 14:32:34:825472] DEBUG: cpu: 1.451829%
[Nov 14 14:32:35:13540] DEBUG: socket recv: {"action":"control","code":{"device":"SF1","state":"on"}}
[Nov 14 14:32:35:13995] DEBUG: lua async on state #0
[Nov 14 14:32:37:825649] DEBUG: cpu: 0.117276%
[Nov 14 14:32:38:243759] DEBUG: socket recv: {"action":"control","code":{"device":"SF1","state":"off"}}
[Nov 14 14:32:38:244389] DEBUG: lua async on state #0
[Nov 14 14:32:39:875615] DEBUG: socket recv: {"action":"control","code":{"device":"SF1","state":"on"}}
[Nov 14 14:32:39:876319] DEBUG: lua async on state #0
[Nov 14 14:32:40:683713] DEBUG: socket recv: {"action":"control","code":{"device":"SF1","state":"off"}}
[Nov 14 14:32:40:684410] DEBUG: lua async on state #0
[Nov 14 14:32:40:825441] DEBUG: cpu: 0.222870%
[Nov 14 14:32:43:825558] DEBUG: cpu: 0.074486%
[Nov 14 14:32:46:825607] DEBUG: cpu: 0.072632%
[Nov 14 14:32:49:825669] DEBUG: cpu: 0.071876%


Please give me a hint on what I missed, can I not just connect pilight as a client to the existing Mosquitto server?

I also tried to use the pilight MQTT server, on an other port number. That too did not show a thing with a mosquitto_sub client listening to that port.

Code:
{
    "devices": {
        "SF1": {
            "protocol": [ "tasmota_switch" ],
            "id": [{
                "id": "TasmotaSF1"
            }],
            "state": "off"
        }
    },
    "rules": {},
    "gui": {
        "SF1": {
            "name": "SF1",
            "group": [ "HANDBEDIENING" ],
            "media": [ "web" ]
        }
    },
    "settings": {
        "name": "harijnwebnew",
        "adhoc-mode": "server",
        "standalone": 1,
        "log-level": 6,
        "pid-file": "/var/run/pilight.pid",
        "log-file": "/var/log/pilight/pilight.log",
        "webserver-enable": 1,
        "webserver-root": "/usr/local/share/pilight/webgui",
        "webserver-http-port": 5001,
        "webserver-https-port": 5002,
        "gpio-platform": "raspberrypi3",
        "webserver-cache": 1,
        "stats-enable": 1,
        "mqtt-enable": 1,
        "mqtt-port": 1884
    },
    "hardware": {
        "433gpio": {
            "sender": 15,
            "receiver": 7
        }
    },
    "registry": {
        "pilight": {
            "version": {
                "current": "8.1.5"
            }
        },
        "webserver": {
            "ssl": {
                "certificate": {
                    "location": "/etc/pilight/pilight.pem"
                }
            }
        },
        "hardware": {
            "RF433": {
                "mingaplen": 4420,
                "maxgaplen": 72900,
                "minrawlen": 26,
                "maxrawlen": 400
            }
        }
    }
}


Code:
[Nov 14 14:46:07:264778] INFO: version v8.1.5-nightly-1a19ab62
[Nov 14 14:46:07:275135] INFO: daemon listening to port: 38325
[Nov 14 14:46:07:275771] DEBUG: started MQTT broker on port 1884
[Nov 14 14:46:07:275775] DEBUG: new thread socket, 1 thread running
[Nov 14 14:46:07:275990] DEBUG: new thread sender, 2 threads running
[Nov 14 14:46:07:276072] DEBUG: new thread broadcaster, 3 threads running
[Nov 14 14:46:07:276391] INFO: new client, ip: 127.0.0.1, port: 41614
[Nov 14 14:46:07:276453] DEBUG: client fd: 15
[Nov 14 14:46:07:276492] DEBUG: client id: 1
[Nov 14 14:46:07:283246] DEBUG: new thread receive parser, 4 threads running
[Nov 14 14:46:07:283447] DEBUG: new thread events client, 5 threads running
[Nov 14 14:46:07:283573] DEBUG: new thread events loop, 6 threads running
[Nov 14 14:46:07:283984] DEBUG: ssdp sent search
[Nov 14 14:46:07:284195] INFO: secured webserver started on port: 5002 (fd 17)
[Nov 14 14:46:07:284304] INFO: regular webserver started on port: 5001 (fd 18)
[Nov 14 14:46:07:396679] DEBUG: lua wiringx on state #0
[Nov 14 14:46:07:397088] NOTICE: no pilight ssdp connections found
[Nov 14 14:46:07:397540] DEBUG: socket write succeeded: {"action":"identify","options":{"config":1,"receiver":1},"media":"all"}

[Nov 14 14:46:07:397562] INFO: new client, ip: 127.0.0.1, port: 41616
[Nov 14 14:46:07:397593] DEBUG: client fd: 19
[Nov 14 14:46:07:397618] DEBUG: client id: 2
[Nov 14 14:46:07:397738] DEBUG: socket recv: {"action":"identify","options":{"config":1,"receiver":1},"media":"all"}
[Nov 14 14:46:07:397892] DEBUG: socket write succeeded: {"status":"success"}

[Nov 14 14:46:08:147069] DEBUG: cpu: 0.000000%
[Nov 14 14:46:11:147658] DEBUG: cpu: 0.098390%
[Nov 14 14:46:14:147668] DEBUG: cpu: 0.071853%
[Nov 14 14:46:16:211924] DEBUG: new client, ip: 192.168.1.8, port: 53093
[Nov 14 14:46:16:212016] DEBUG: client fd: 20
[Nov 14 14:46:16:285061] DEBUG: new client, ip: 192.168.1.8, port: 53094
[Nov 14 14:46:16:285164] DEBUG: client fd: 20
[Nov 14 14:46:16:285540] DEBUG: new client, ip: 192.168.1.8, port: 53095
[Nov 14 14:46:16:285579] DEBUG: client fd: 21
[Nov 14 14:46:16:287477] DEBUG: new client, ip: 192.168.1.8, port: 53097
[Nov 14 14:46:16:287546] DEBUG: client fd: 22
[Nov 14 14:46:16:288600] DEBUG: new client, ip: 192.168.1.8, port: 53098
[Nov 14 14:46:16:288666] DEBUG: client fd: 23
[Nov 14 14:46:16:292360] DEBUG: new client, ip: 192.168.1.8, port: 53099
[Nov 14 14:46:16:292462] DEBUG: client fd: 21
[Nov 14 14:46:16:314090] DEBUG: new client, ip: 192.168.1.8, port: 53100
[Nov 14 14:46:16:314195] DEBUG: client fd: 21
[Nov 14 14:46:16:535603] DEBUG: new client, ip: 192.168.1.8, port: 53101
[Nov 14 14:46:16:535689] DEBUG: client fd: 20
[Nov 14 14:46:16:710540] DEBUG: new client, ip: 192.168.1.8, port: 53102
[Nov 14 14:46:16:710626] DEBUG: client fd: 20
[Nov 14 14:46:16:747411] DEBUG: new client, ip: 192.168.1.8, port: 53103
[Nov 14 14:46:16:747501] DEBUG: client fd: 20
[Nov 14 14:46:16:801711] DEBUG: new client, ip: 192.168.1.8, port: 53104
[Nov 14 14:46:16:801793] DEBUG: client fd: 20
[Nov 14 14:46:16:923040] DEBUG: socket recv: {"action":"request config"}
[Nov 14 14:46:16:972900] DEBUG: socket recv: {"action":"request values"}
[Nov 14 14:46:17:148230] DEBUG: cpu: 1.542838%
[Nov 14 14:46:18:31084] DEBUG: socket recv: {"action":"control","code":{"device":"SF1","state":"on"}}
[Nov 14 14:46:18:31542] DEBUG: lua async on state #0
[Nov 14 14:46:18:885974] DEBUG: socket recv: {"action":"control","code":{"device":"SF1","state":"off"}}
[Nov 14 14:46:18:886486] DEBUG: lua async on state #0
[Nov 14 14:46:19:286573] DEBUG: new client, ip: 192.168.1.8, port: 53096
[Nov 14 14:46:19:286661] DEBUG: client fd: 21
[Nov 14 14:46:19:835920] DEBUG: socket recv: {"action":"control","code":{"device":"SF1","state":"on"}}
[Nov 14 14:46:19:836369] DEBUG: lua async on state #0
[Nov 14 14:46:20:147720] DEBUG: cpu: 0.290810%
[Nov 14 14:46:20:317230] DEBUG: socket recv: {"action":"control","code":{"device":"SF1","state":"off"}}
[Nov 14 14:46:20:317659] DEBUG: lua async on state #0
[Nov 14 14:46:23:147408] DEBUG: cpu: 0.123195%
 
Reply
#5
(11-14-2019, 03:48 PM)hansrijn2 Wrote: Please give me a hint on what I missed, can I not just connect pilight as a client to the existing Mosquitto server?
At this moment you cannot connect pilight to another broker, however, pilight should be able to replace an existing broker.

Quote:I also tried to use the pilight MQTT server, on an other port number. That too did not show a thing with a mosquitto_sub client listening to that port.
At the moment pilight doesn't actively communicate activity. That's a feature i'm currently working on.

Code:
# mosquitto_sub -h 10.0.0.142 -t 'pilight/device/+/#' -v
pilight/device/time/timestamp 1573753790
pilight/device/time/year 2019
pilight/device/time/month 11
pilight/device/time/day 14
pilight/device/time/hour 18
pilight/device/time/minute 49
pilight/device/time/second 50
pilight/device/time/weekday 5
pilight/device/time/dst 0
pilight/device/time/timestamp 1573753791
pilight/device/time/year 2019
pilight/device/time/month 11
pilight/device/time/day 14
pilight/device/time/hour 18
pilight/device/time/minute 49
pilight/device/time/second 51
pilight/device/time/weekday 5
pilight/device/time/dst 0
pilight/device/time/timestamp 1573753792
pilight/device/time/year 2019
pilight/device/time/month 11
pilight/device/time/day 14
pilight/device/time/hour 18
pilight/device/time/minute 49
pilight/device/time/second 52
pilight/device/time/weekday 5
pilight/device/time/dst 0

However, you should already see data outputted by the Tasmota devices:
Code:
tele/living-speakers/LWT Online
tele/living-light/LWT Online
 
Reply
#6
Smile 
Thanks. It reminds me of the old days when IT firms claimed features they did not deliver. My firm CDC once obtained part of IBM after a court matter for this reason.  SurprisedSmile

I hope the completing part follows soon,

Regards, Hans
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Raspberry 4B installation error royw 3 223 12-05-2019, 10:58 AM
Last Post: royw
  pilight error after update to 8.1.5 on Odroid C2 WitchDoctor 3 296 11-29-2019, 09:56 PM
Last Post: curlymo
  433gpio platform error after raspbian dist upgrade HuberDe 2 348 10-12-2019, 07:35 PM
Last Post: HuberDe
  error pilightsend, recieve and control hansipi 2 558 11-04-2018, 03:46 PM
Last Post: hansipi
  Error with loading LPF firmware Rschnauzer 14 7,400 02-10-2018, 04:21 PM
Last Post: Rschnauzer
  generic_dimmer error / or not visible in 8.0.5 terrar 13 1,865 01-16-2018, 10:04 PM
Last Post: terrar
  pilight does no longer start because of hardware error stratege-0815 2 1,148 12-27-2017, 11:16 PM
Last Post: stratege-0815
  ERROR: uv_custom_poll_cb: bad file descriptor Gisto 6 1,729 12-19-2017, 03:03 PM
Last Post: Gisto
  [Solved] Error manual compiling Thuurke 2 1,344 09-02-2017, 05:06 PM
Last Post: Thuurke
  ERROR: config is not in a valid json format Sisko4 6 1,737 03-27-2017, 08:24 AM
Last Post: Sisko4

Forum Jump:


Browsing: 1 Guest(s)