Wstawiłem wyrzucanie wolnej pamięci przy każdej zmianie statusu w funkcji status_func:klew wrote: Mon Dec 16, 2019 12:22 pm Spróbuj dorzucić sobie do programu printowanie ilości wolnej pamięci. Wstaw też w "SuplaDevice.iterate()" - np przed wejściem w rejestrację . tam gdzie jest:Code: Select all
status(STATUS_REGISTER_IN_PROGRESS, "Register in progress");
Code: Select all
19:31:20.118 -> localIP: 192.168.2.175
19:31:20.118 -> subnetMask: 255.255.255.0
19:31:20.165 -> gatewayIP: 192.168.2.1
19:31:20.212 -> dnsServerIP: 192.168.2.1
19:31:20.212 -> Using protocol version 8
19:31:20.259 -> freeMemory: 3395
19:31:20.259 -> SuplaDevice initialized
19:31:20.306 -> freeMemory: 3395
19:31:20.306 -> Not connected
19:31:20.306 -> Establishing connection with: svr21.supla.org (port: 2015)
19:31:52.509 -> Connection fail. Server: svr21.supla.org
19:31:54.525 -> freeMemory: 3395
19:31:54.525 -> Not connected
19:31:54.571 -> Establishing connection with: svr21.supla.org (port: 2015)
19:31:54.665 -> Connected
19:31:54.665 -> freeMemory: 3395
19:31:54.712 -> Register in progress
19:33:54.794 -> freeMemory: 3395
19:33:54.828 -> Not connected
19:33:54.828 -> Establishing connection with: svr21.supla.org (port: 2015)
19:33:54.898 -> Connection fail. Server: svr21.supla.org
19:33:56.979 -> freeMemory: 3395
19:33:56.979 -> Not connected
19:33:57.014 -> Establishing connection with: svr21.supla.org (port: 2015)
19:33:57.083 -> Connected
19:33:57.118 -> freeMemory: 3395
19:33:57.118 -> Register in progress
Czy jest szansa na jakieś log'i od strony serwera? Może tam byłoby jakieś nakierowanie na problem.
