search

kk7ds / pynx584

Python library and server for talking to NX584/NX8E interfaces
GNU General Public License v3.0
29 stars 26 forks source link

timeout error #19

Closed zipperten closed 6 years ago

zipperten commented 6 years ago

Hi i have a a lot events timeouts in my log, where should i start to fix this, is it a configuration parameter in my alarm panel? I think this is is whay my config file did not autocreate.

8-04-08 15:10:33,854 _internal INFO 127.0.0.1 - - [08/Apr/2018 15:10:33] "GET /events?index=126&timeout=60 HTTP/1.1" 200 - 2018-04-08 15:10:35,798 _internal INFO 127.0.0.1 - - [08/Apr/2018 15:10:35] "GET /events?index=127&timeout=60 HTTP/1.1" 200 - 2018-04-08 15:10:36,092 controller INFO Zone 3 (ir kontor inre) state is NORMAL 2018-04-08 15:10:36,097 _internal INFO 127.0.0.1 - - [08/Apr/2018 15:10:36] "GET /events?index=128&timeout=60 HTTP/1.1" 200 -

zipperten commented 6 years ago

i got it, i should not use parameter localhost to start the server after changing to real ip it works!

zipperten commented 6 years ago

I thought i got rid of this error but every time i connect with Home Assistant plugin i starting to get timeouts.

It is probably the Home Assistant plugin that needs to be fixed but, but what courses this symptom, is it a status request from home assistant that is invalid?

Here is some log, the bottom half is when i turned off Home Assistant plugin

2018-04-17 16:12:37,220 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:12:37] "GET /events?index=923&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:12:37,522 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:12:37] "GET /events?index=924&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:12:37,821 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:12:37] "GET /events?index=925&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:12:38,120 controller INFO Zone 14 (ir sov2) state is FAULT 2018-04-17 16:12:38,126 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:12:38] "GET /events?index=926&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:12:40,126 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:12:40] "GET /events?index=927&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:12:40,443 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:12:40] "GET /events?index=928&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:12:40,772 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:12:40] "GET /events?index=929&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:12:41,069 controller INFO Zone 14 (ir sov2) state is NORMAL 2018-04-17 16:12:41,074 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:12:41] "GET /events?index=930&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:13:18,701 _internal INFO 127.0.0.1 - - [17/Apr/2018 16:13:18] "GET /events?index=931&timeout=60 HTTP/1.1" 200 - 2018-04-17 16:13:19,599 controller INFO Zone 14 (ir sov2) state is FAULT 2018-04-17 16:13:22,100 controller INFO Zone 14 (ir sov2) state is NORMAL 2018-04-17 16:13:23,002 controller INFO Zone 14 (ir sov2) state is FAULT 2018-04-17 16:13:26,056 controller INFO Zone 14 (ir sov2) state is NORMAL 2018-04-17 16:13:30,659 controller INFO Zone 14 (ir sov2) state is FAULT 2018-04-17 16:13:33,308 controller INFO Zone 14 (ir sov2) state is NORMAL 2018-04-17 16:14:23,650 controller INFO Zone 14 (ir sov2) state is FAULT 2018-04-17 16:14:27,050 controller INFO Zone 14 (ir sov2) state is NORMAL 2018-04-17 16:14:27,972 controller INFO Zone 14 (ir sov2) state is FAULT

kk7ds commented 6 years ago

I don't see any errors in that log. The only timeout above is the long-poll timeout that HA is providing when waiting for events from the nx584 server. It does them in 60-second batches, which is why that timeout is specified. That log looks completely normal to me.

zipperten commented 6 years ago

Thanks, I tested now and realise that I get one each time someone do a status request same when I do "nx584_client summary" So I think I have to figure out how to change log level instead.

Thank for your patience with my questions.