• 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
433nano stops receiving
#11
I'll watch it and give you feedback in the next days.
 
Reply
#12
Okay, so the problem still exists. 

Code:
(/home/pilight/source/daemon-dev/daemon.c #3082) [Nov 10 22:30:43:600490] INFO: version v8.1.5
(/home/pilight/source/daemon-dev/daemon.c #3151) [Nov 10 22:30:43:730827] INFO: no pilight daemon found, daemonizing
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #168) [Nov 10 22:30:43:971400] INFO: daemon listening to port: 5003
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:30:44:108830] INFO: new client, ip: 127.0.0.1, port: 53938
(/home/pilight/source/daemon-dev/libs/pilight/core/webserver.c #1889) [Nov 10 22:30:44:274062] INFO: secured webserver started on port: 5002 (fd 16)
(/home/pilight/source/daemon-dev/libs/pilight/core/webserver.c #1892) [Nov 10 22:30:44:283473] INFO: regular webserver started on port: 5001 (fd 17)
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:30:44:382576] INFO: new client, ip: 192.168.150.25, port: 50230
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:31:30:567818] INFO: new client, ip: 127.0.0.1, port: 53942
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:50:23:117111] INFO: new client, ip: 127.0.0.1, port: 53986
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:50:23:748100] INFO: new client, ip: 127.0.0.1, port: 53990
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:50:24:258454] INFO: new client, ip: 127.0.0.1, port: 53994
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:51:11:396933] INFO: new client, ip: 127.0.0.1, port: 54014
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:51:11:902937] INFO: new client, ip: 127.0.0.1, port: 54018
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:51:12:375545] INFO: new client, ip: 127.0.0.1, port: 54022
(/home/pilight/source/daemon-dev/libs/pilight/core/socket.c #577) [Nov 10 22:51:12:892612] INFO: new client, ip: 127.0.0.1, port: 54026
(/home/pilight/source/daemon-dev/libs/pilight/lua_c/log.c #73) [Nov 10 23:03:59:491860] NOTICE: 433nano: received invalid stream 'c:11111231341112311221341314333413121112232156;p:470,1950'
FHEM indicates that the last valid data received was at 23:00:04, so after receiving the invalid stream pilight stopped receiving.
 
Reply
#13
Can you add the last dump line again so i can see what data is coming in?
 
Reply
#14
I'm running pilight on an RPi (buster) with 433nano. I've been running nightlies in the hope that the problem described in this other thread would go away:

forum.pilight.org/showthread.php?tid=3606

Along with some update before Xmas a bigger problem appeared. Reception doesn't work at all. pilight-receive doesn't show a peep, pilight-debug says "Invalid pulse train" whenever I click any of my Nexa remotes.
I downgraded to base 8.1.5 and all works again, until the reception invariably dies some time later (see that other thread).

Any ideas?
 
Reply
#15
There is no need to start a new thread.

Can you do as described in post 4 and let me know the output?
 
Reply
#16
(01-05-2020, 08:09 PM)curlymo Wrote: There is no need to start a new thread.

Can you do as described in post 4 and let me know the output?

Well, I thought "not working at all" would be different enough from "working for a while", but anyway...

I installed the latest nightly and added that dump line. It takes a lot of repeats to actually get there (meanwhile there are a lot of "433nano: discarded invalid pulse train" messages). Here's an excerpt.
Code:
[Jan 06 10:26:10:133750] NOTICE: 433nano: discarded invalid pulse train
[Jan 06 10:26:10:144287] DEBUG: lua serial read on state #0
[Jan 06 10:26:10:357148] DEBUG: lua serial read on state #0
[Jan 06 10:26:10:375581] NOTICE: 433nano: discarded invalid pulse train
[Jan 06 10:26:10:378632] DEBUG: lua serial read on state #0
[Jan 06 10:26:10:615494] DEBUG: lua serial read on state #0
{
       [1] = 1,
       [2] = 0,
       [3] = 2,
       [4] = 0,
       [5] = 3,
       [6] = 2,
       [7] = 4,
       [8] = 0,
       [9] = 3,
       [10] = 0,
       [11] = 3,
       [12] = 0,
       [13] = 3,
       [14] = 4,
       [15] = 3,
       [16] = 0,
       [17] = 3,
       [18] = 4,
       [19] = 3,
       [20] = 4,
       [21] = 3,
       [22] = 3,
       [23] = 4,
       [24] = 4,
       [25] = 3,
       [26] = 4,
       [27] = 3,
       [28] = 0,
       [29] = 3,
       [30] = 4,
       [31] = 3,
       [32] = 3,
       [33] = 4,
       [34] = 3,
       [35] = 4,
       [36] = 3,
       [37] = 4,
       [38] = 4,
       [39] = 3,
       [40] = 4,
       [41] = 3,
       [42] = 4,
       [43] = 3,
       [44] = 3,
       [45] = 4,
       [46] = 4,
       [47] = 3,
       [48] = 3,
       [49] = 4,
       [50] = 3,
       [51] = 4,
       [52] = 4,
       [53] = 3,
       [54] = 4,
       [55] = 3,
       [56] = 3,
       [57] = 4,
       [58] = 4,
       [59] = 3,
       [60] = 4,
       [61] = 3,
       [62] = 4,
       [63] = 3,
       [64] = 4,
       [65] = 3,
       [66] = 5,
}
[Jan 06 10:26:10:828254] DEBUG: lua serial read on state #0
[Jan 06 10:26:10:848281] NOTICE: 433nano: discarded invalid pulse train
[Jan 06 10:26:10:857242] DEBUG: lua serial read on state #0
[Jan 06 10:26:10:906310] DEBUG: lua serial read on state #0
[Jan 06 10:26:10:924800] NOTICE: 433nano: discarded invalid pulse train
EDIT: I don't think the execution ever reaches that dump line if I press the Nexa buttons "nicely". I get that dump after keeping the button down or clicking it repeatedly very fast.
 
Reply
#17
Meanwhile, I have bracketed the nightly that broke the reception for me:

8.1.5-65-gc0e1cbcc works (for a while)
8.1.5-66-g317b2833 when I press a Nexa key, "lua serial read on state #0", no other messages at all
8.1.5-68-gaca36192 same as above
8.1.5-71-gc6ae912d problem as described in my original post ("invalid pulse train")
 
Reply
#18
Really great you tested the different versions! That's really helpful.

The line i asked to test, was not in the right place. My bad, sorry.

Can you put this dumpline on line #85:
PHP Code:
print(dump(data)); 

Can you post the output again?
 
Reply
#19
This is from the latest nightly and that dump line (a lot of output, I hope this is a relevant bit):

Code:
[Jan 06 19:22:20:953039] DEBUG: lua serial read on state #0
{
       ["write"] = 2,
       ["hardware"] = 433nano,
       ["content"] =











c:102022002020202020202200202020220202002020220022020020220020202203;p:,
       ["length"] = 0,
       ["pulses"] = {
       },
}
[Jan 06 19:22:21:674083] DEBUG: cpu: 1.003955%
[Jan 06 19:22:21:706122] DEBUG: lua serial read on state #0
{
       ["write"] = 2,
       ["hardware"] = 433nano,
       ["content"] =











c:102022002020202020202200202020220202002020220022020020220020202203;p:280,2610,1250,10070@,
       ["length"] = 0,
       ["pulses"] = {
       },
}
[Jan 06 19:22:21:727312] NOTICE: 433nano: discarded invalid pulse train
[Jan 06 19:22:22:704985] DEBUG: lua serial read on state #0
{
       ["write"] = 2,
       ["hardware"] = 433nano,
       ["content"] =
,
       ["length"] = 0,
       ["pulses"] = {
       },
}
[Jan 06 19:22:23:703812] DEBUG: lua serial read on state #0
{
       ["write"] = 2,
       ["hardware"] = 433nano,
       ["content"] =

,
       ["length"] = 0,
       ["pulses"] = {
       },
}
^C[Jan 06 19:22:24:351754] INFO: Interrupt signal received. Please wait while pilight is shutting down
 
Reply
#20
Can you also post output when the error messages are seen?
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  433nano stops receiving with FHEM RichiG 1 35 03-27-2020, 07:36 PM
Last Post: curlymo
  communication between main daemon and clientized daemon stops tomk 29 3,137 05-06-2019, 08:57 PM
Last Post: curlymo
Bug Bug report: WIFI dongle stops when gpio_switch.gpio = 20 woutput 16 6,044 01-03-2018, 10:11 PM
Last Post: zackdvd
  pilight for dummies? receiving door contact state DazRave 7 4,617 10-03-2014, 10:01 PM
Last Post: creamers
  Sending and receiving at the same time geerttttt 2 1,901 07-09-2014, 01:12 AM
Last Post: scorpydude

Forum Jump:


Browsing: 1 Guest(s)