To na pewno nie jest problem THW, mam u siebie dużo czujników temp i wilgotności od ds18b20 dht22, sht30, bme280 i tez czasami są takie braki i jak one wystąpią to na każdym wykresie, tłumaczę sobie to że wtedy był jakiś problem z serwerem albo z netem u mnie..
W załączniku kilka przykładów z data zaznaczona.
svr8 jak coś
Thw-01
-
kurus
- Posts: 1312
- Joined: Wed Jan 15, 2020 8:17 pm
You do not have the required permissions to view the files attached to this post.
-
3DPiCiU
- Posts: 26
- Joined: Sat Feb 01, 2020 5:34 pm
Domyślnie u mnie samo się włączyło PMF (Protected Management Frames) dla sieci dla tych urządzeń.
Wyłączyłem i jest przez noc lepiej ale niedoskonale, zobaczymy
Podobne problemy opisują LINKhttps://community.ui.com/questions/PMF- ... 972f6575c0
@klew w jednym z postów opisywał coś, że moduły WiFi są robione od dawna (w skrócie) dało mi to coś do myślenia na temat mojej sieci.
Urządzenia widoczne połączone, ale nie mogą zestawić / wysłać pakietu jak to opisał @pzygmunt do tego dochodzi Moja INEA i Niemieckie serwery = katastrofa
Kolejne gubienie pakietów bowiem man na INEA kilka niemieckich firm, które maja co jakiś czas problemy z różnymi usługami wiem z doświadczenia współpracy wieloletniej. Przy czym problem nie leży po stronie INEA.
Ok czekamy co odpowie @pzygmunt
-
pzygmunt
- Posts: 20302
- Joined: Tue Jan 19, 2016 9:26 am
- Location: Paczków
- Been thanked: 59 times
@ramar analizując logi to czujnik "SALON" ma w bazie następujące luki (data + 10 min spodziewany jest zapis pomiaru w bazie, którego nie ma):
Widać, że po 14-tym wyraźnie się uspokoiło. Poniżej połączenia dla ostatnich dat.
Widać, że THW nie zawsze łączy się co 30 sek. Czasami łączy się co 2 min. Czas życia pomiaru to obecnie jedna minuta. Jeśli zapis do bazy akurat trafia w tą wąską lukę gdzie THW z jakiegoś powodu spóźnia się z nawiązaniem połączenia to mamy lukę na wykresie. W Twoim przypadku stawiam na jakieś limity w Twojej sieci. Rozwiązaniem byłoby zwiększenie czasu życia pomiaru np. min 2 min.
THW SYPIALNIA wygląda podobnie.
Code: Select all
2022-12-14 07:01:00
2022-12-14 09:01:00
2022-12-14 20:51:00
2022-12-14 21:21:00
2022-12-14 22:31:00
2022-12-14 23:31:00
2022-12-14 23:51:00
2022-12-15 01:01:00
2022-12-15 01:41:00
2022-12-15 02:51:00
2022-12-15 04:11:00
2022-12-16 23:01:00
2022-12-17 13:40:59
2022-12-18 13:00:59
2022-12-19 15:17:33
2022-12-19 15:47:34Code: Select all
Dec 19 15:16:05 svr49 supla-server: Device registered. ID: 7604, ClientSD: 5779 Protocol Version: 18 ThreadID: 26179 GUID: 95D223E5 ResultCode: 3
Dec 19 15:16:38 svr49 supla-server: Device registered. ID: 7604, ClientSD: 2159 Protocol Version: 18 ThreadID: 26688 GUID: 95D223E5 ResultCode: 3
Dec 19 15:19:00 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4395 Protocol Version: 18 ThreadID: 28408 GUID: 95D223E5 ResultCode: 3
Dec 19 15:19:33 svr49 supla-server: Device registered. ID: 7604, ClientSD: 2001 Protocol Version: 18 ThreadID: 28815 GUID: 95D223E5 ResultCode: 3
Dec 19 15:20:07 svr49 supla-server: Device registered. ID: 7604, ClientSD: 3788 Protocol Version: 18 ThreadID: 29217 GUID: 95D223E5 ResultCode: 3
Dec 19 15:20:41 svr49 supla-server: Device registered. ID: 7604, ClientSD: 6194 Protocol Version: 18 ThreadID: 29575 GUID: 95D223E5 ResultCode: 3
Dec 19 15:21:15 svr49 supla-server: Device registered. ID: 7604, ClientSD: 5710 Protocol Version: 18 ThreadID: 29969 GUID: 95D223E5 ResultCode: 3
Dec 19 15:21:49 svr49 supla-server: Device registered. ID: 7604, ClientSD: 3190 Protocol Version: 18 ThreadID: 30356 GUID: 95D223E5 ResultCode: 3
Dec 19 15:22:24 svr49 supla-server: Device registered. ID: 7604, ClientSD: 1191 Protocol Version: 18 ThreadID: 30752 GUID: 95D223E5 ResultCode: 3
Dec 19 15:24:56 svr49 supla-server: Device registered. ID: 7604, ClientSD: 5067 Protocol Version: 18 ThreadID: 32461 GUID: 95D223E5 ResultCode: 3
Dec 19 15:28:12 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4323 Protocol Version: 18 ThreadID: 2261 GUID: 95D223E5 ResultCode: 3
Dec 19 15:28:44 svr49 supla-server: Device registered. ID: 7604, ClientSD: 1454 Protocol Version: 18 ThreadID: 2616 GUID: 95D223E5 ResultCode: 3
Dec 19 15:29:18 svr49 supla-server: Device registered. ID: 7604, ClientSD: 2948 Protocol Version: 18 ThreadID: 3010 GUID: 95D223E5 ResultCode: 3
Dec 19 15:29:52 svr49 supla-server: Device registered. ID: 7604, ClientSD: 1903 Protocol Version: 18 ThreadID: 3361 GUID: 95D223E5 ResultCode: 3
Dec 19 15:30:26 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4041 Protocol Version: 18 ThreadID: 3810 GUID: 95D223E5 ResultCode: 3
Dec 19 15:31:04 svr49 supla-server: Device registered. ID: 7604, ClientSD: 2210 Protocol Version: 18 ThreadID: 4237 GUID: 95D223E5 ResultCode: 3
Dec 19 15:31:37 svr49 supla-server: Device registered. ID: 7604, ClientSD: 5212 Protocol Version: 18 ThreadID: 4588 GUID: 95D223E5 ResultCode: 3
Dec 19 15:32:11 svr49 supla-server: Device registered. ID: 7604, ClientSD: 1065 Protocol Version: 18 ThreadID: 4980 GUID: 95D223E5 ResultCode: 3
Dec 19 15:32:45 svr49 supla-server: Device registered. ID: 7604, ClientSD: 5212 Protocol Version: 18 ThreadID: 5333 GUID: 95D223E5 ResultCode: 3
Dec 19 15:35:06 svr49 supla-server: Device registered. ID: 7604, ClientSD: 2562 Protocol Version: 18 ThreadID: 6969 GUID: 95D223E5 ResultCode: 3
Dec 19 15:35:40 svr49 supla-server: Device registered. ID: 7604, ClientSD: 733 Protocol Version: 18 ThreadID: 7397 GUID: 95D223E5 ResultCode: 3
Dec 19 15:36:13 svr49 supla-server: Device registered. ID: 7604, ClientSD: 1333 Protocol Version: 18 ThreadID: 7765 GUID: 95D223E5 ResultCode: 3
Dec 19 15:36:48 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4170 Protocol Version: 18 ThreadID: 8113 GUID: 95D223E5 ResultCode: 3
Dec 19 15:37:22 svr49 supla-server: Device registered. ID: 7604, ClientSD: 1454 Protocol Version: 18 ThreadID: 8490 GUID: 95D223E5 ResultCode: 3
Dec 19 15:39:42 svr49 supla-server: Device registered. ID: 7604, ClientSD: 1156 Protocol Version: 18 ThreadID: 10173 GUID: 95D223E5 ResultCode: 3
Dec 19 15:40:16 svr49 supla-server: Device registered. ID: 7604, ClientSD: 3190 Protocol Version: 18 ThreadID: 10830 GUID: 95D223E5 ResultCode: 3
Dec 19 15:40:50 svr49 supla-server: Device registered. ID: 7604, ClientSD: 3435 Protocol Version: 18 ThreadID: 11415 GUID: 95D223E5 ResultCode: 3
Dec 19 15:41:25 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4322 Protocol Version: 18 ThreadID: 12294 GUID: 95D223E5 ResultCode: 3
Dec 19 15:43:46 svr49 supla-server: Device registered. ID: 7604, ClientSD: 739 Protocol Version: 18 ThreadID: 14604 GUID: 95D223E5 ResultCode: 3
Dec 19 15:44:20 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4041 Protocol Version: 18 ThreadID: 15177 GUID: 95D223E5 ResultCode: 3
Dec 19 15:44:54 svr49 supla-server: Device registered. ID: 7604, ClientSD: 946 Protocol Version: 18 ThreadID: 15583 GUID: 95D223E5 ResultCode: 3
Dec 19 15:45:28 svr49 supla-server: Device registered. ID: 7604, ClientSD: 6398 Protocol Version: 18 ThreadID: 16032 GUID: 95D223E5 ResultCode: 3
Dec 19 15:46:16 svr49 supla-server: Device registered. ID: 7604, ClientSD: 1355 Protocol Version: 18 ThreadID: 16605 GUID: 95D223E5 ResultCode: 3
Dec 19 15:46:48 svr49 supla-server: Device registered. ID: 7604, ClientSD: 607 Protocol Version: 18 ThreadID: 16923 GUID: 95D223E5 ResultCode: 3
Dec 19 15:47:32 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4672 Protocol Version: 18 ThreadID: 17432 GUID: 95D223E5 ResultCode: 3
Dec 19 15:48:35 svr49 supla-server: Device registered. ID: 7604, ClientSD: 840 Protocol Version: 18 ThreadID: 18187 GUID: 95D223E5 ResultCode: 3
Dec 19 15:49:08 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4981 Protocol Version: 18 ThreadID: 18583 GUID: 95D223E5 ResultCode: 3
Dec 19 15:52:11 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4011 Protocol Version: 18 ThreadID: 20839 GUID: 95D223E5 ResultCode: 3
Dec 19 15:52:43 svr49 supla-server: Device registered. ID: 7604, ClientSD: 4753 Protocol Version: 18 ThreadID: 21182 GUID: 95D223E5 ResultCode: 3
Dec 19 15:53:17 svr49 supla-server: Device registered. ID: 7604, ClientSD: 3822 Protocol Version: 18 ThreadID: 21635 GUID: 95D223E5 ResultCode: 3
Dec 19 15:53:51 svr49 supla-server: Device registered. ID: 7604, ClientSD: 3730 Protocol Version: 18 ThreadID: 22019 GUID: 95D223E5 ResultCode: 3
Dec 19 15:54:25 svr49 supla-server: Device registered. ID: 7604, ClientSD: 2643 Protocol Version: 18 ThreadID: 22816 GUID: 95D223E5 ResultCode: 3
Dec 19 15:54:59 svr49 supla-server: Device registered. ID: 7604, ClientSD: 6110 Protocol Version: 18 ThreadID: 23239 GUID: 95D223E5 ResultCode: 3
Dec 19 15:55:34 svr49 supla-server: Device registered. ID: 7604, ClientSD: 3770 Protocol Version: 18 ThreadID: 23669 GUID: 95D223E5 ResultCode: 3
Dec 19 15:59:42 svr49 supla-server: Device registered. ID: 7604, ClientSD: 5517 Protocol Version: 18 ThreadID: 26670 GUID: 95D223E5 ResultCode: 3
THW SYPIALNIA wygląda podobnie.
SUPLA.... Nareszcie w domu.
-
pzygmunt
- Posts: 20302
- Joined: Tue Jan 19, 2016 9:26 am
- Location: Paczków
- Been thanked: 59 times
@3DPiCiU u Ciebie luki wygadają następująco.
2446
2441
Sprawdzając ostatnią lukę dla 2446 widać następujące połączenia:
Zapis do bazy odbył się ~ 2022-12-20 07:46:50
Jak widać z logów THW połączył się o 07:45:14 co oznacza, że czas życia pomiaru został ustawiony na 07:46:14 i THW zamiast połączyć się do tego czasu, połączyło o 07:46:53 przez co logger trafił w wąskie okno niedostępności.
Być może jest tak, że WiFi nie radzą sobie z jakiegoś powodu z urządzeniami, które często zestawiają połączenia i je zrywają.
Rozwiązaniem i w Twoim przypadku byłoby ustawienia czasu życia pomiaru na min 2 min.
Przemyślimy temat i zaproponujemy rozwiązanie.
2446
Code: Select all
2022-12-16 02:49:42
2022-12-16 03:29:42
2022-12-16 04:29:42
2022-12-16 04:59:43
2022-12-16 06:19:42
2022-12-16 06:59:42
2022-12-16 07:19:42
2022-12-16 07:49:42
2022-12-16 08:29:42
2022-12-16 08:49:43
2022-12-16 09:49:42
2022-12-16 10:29:43
2022-12-16 11:09:42
2022-12-16 11:29:43
2022-12-16 12:19:42
2022-12-16 13:29:42
2022-12-16 15:19:42
2022-12-16 15:39:43
2022-12-16 16:49:42
2022-12-16 17:39:42
2022-12-16 18:09:42
2022-12-16 18:39:42
2022-12-17 04:59:42
2022-12-19 22:02:43
2022-12-20 07:36:50
Code: Select all
2022-12-15 11:49:42
2022-12-15 23:59:42
2022-12-16 00:29:42
2022-12-16 00:59:42
2022-12-16 08:39:42
2022-12-16 09:29:42
2022-12-16 10:49:42
2022-12-16 13:19:42
2022-12-16 17:19:42
2022-12-16 17:39:42
2022-12-16 18:49:43
2022-12-17 17:09:42
2022-12-18 00:59:42
2022-12-18 01:19:42
2022-12-18 01:39:43
2022-12-18 02:09:43
2022-12-18 03:59:42
2022-12-18 05:49:43
2022-12-18 07:59:42
2022-12-19 20:42:42
2022-12-19 21:22:42
2022-12-19 22:02:43
2022-12-19 22:42:42
2022-12-19 23:02:42
2022-12-20 04:26:50
Code: Select all
Dec 20 07:00:54 svr82 supla-server: Device registered. ID: 881, ClientSD: 407 Protocol Version: 18 ThreadID: 4090111 GUID: EA9F82FF ResultCode: 3
Dec 20 07:01:29 svr82 supla-server: Device registered. ID: 881, ClientSD: 1797 Protocol Version: 18 ThreadID: 4090314 GUID: EA9F82FF ResultCode: 3
Dec 20 07:02:02 svr82 supla-server: Device registered. ID: 881, ClientSD: 1766 Protocol Version: 18 ThreadID: 4090510 GUID: EA9F82FF ResultCode: 3
Dec 20 07:02:52 svr82 supla-server: Device registered. ID: 881, ClientSD: 1716 Protocol Version: 18 ThreadID: 4090722 GUID: EA9F82FF ResultCode: 3
Dec 20 07:03:24 svr82 supla-server: Device registered. ID: 881, ClientSD: 1797 Protocol Version: 18 ThreadID: 4090926 GUID: EA9F82FF ResultCode: 3
Dec 20 07:03:57 svr82 supla-server: Device registered. ID: 881, ClientSD: 1806 Protocol Version: 18 ThreadID: 4091066 GUID: EA9F82FF ResultCode: 3
Dec 20 07:04:31 svr82 supla-server: Device registered. ID: 881, ClientSD: 1445 Protocol Version: 18 ThreadID: 4091261 GUID: EA9F82FF ResultCode: 3
Dec 20 07:05:34 svr82 supla-server: Device registered. ID: 881, ClientSD: 1744 Protocol Version: 18 ThreadID: 4091562 GUID: EA9F82FF ResultCode: 3
Dec 20 07:06:06 svr82 supla-server: Device registered. ID: 881, ClientSD: 1850 Protocol Version: 18 ThreadID: 4091772 GUID: EA9F82FF ResultCode: 3
Dec 20 07:06:41 svr82 supla-server: Device registered. ID: 881, ClientSD: 1083 Protocol Version: 18 ThreadID: 4091932 GUID: EA9F82FF ResultCode: 3
Dec 20 07:07:15 svr82 supla-server: Device registered. ID: 881, ClientSD: 1858 Protocol Version: 18 ThreadID: 4092123 GUID: EA9F82FF ResultCode: 3
Dec 20 07:07:53 svr82 supla-server: Device registered. ID: 881, ClientSD: 1438 Protocol Version: 18 ThreadID: 4092277 GUID: EA9F82FF ResultCode: 3
Dec 20 07:08:55 svr82 supla-server: Device registered. ID: 881, ClientSD: 1134 Protocol Version: 18 ThreadID: 4092593 GUID: EA9F82FF ResultCode: 3
Dec 20 07:10:46 svr82 supla-server: Device registered. ID: 881, ClientSD: 1744 Protocol Version: 18 ThreadID: 4093221 GUID: EA9F82FF ResultCode: 3
Dec 20 07:11:21 svr82 supla-server: Device registered. ID: 881, ClientSD: 521 Protocol Version: 18 ThreadID: 4093410 GUID: EA9F82FF ResultCode: 3
Dec 20 07:11:54 svr82 supla-server: Device registered. ID: 881, ClientSD: 1797 Protocol Version: 18 ThreadID: 4093554 GUID: EA9F82FF ResultCode: 3
Dec 20 07:12:30 svr82 supla-server: Device registered. ID: 881, ClientSD: 1207 Protocol Version: 18 ThreadID: 4093740 GUID: EA9F82FF ResultCode: 3
Dec 20 07:13:02 svr82 supla-server: Device registered. ID: 881, ClientSD: 1817 Protocol Version: 18 ThreadID: 4093925 GUID: EA9F82FF ResultCode: 3
Dec 20 07:13:37 svr82 supla-server: Device registered. ID: 881, ClientSD: 1704 Protocol Version: 18 ThreadID: 4094075 GUID: EA9F82FF ResultCode: 3
Dec 20 07:14:11 svr82 supla-server: Device registered. ID: 881, ClientSD: 1207 Protocol Version: 18 ThreadID: 4094264 GUID: EA9F82FF ResultCode: 3
Dec 20 07:14:44 svr82 supla-server: Device registered. ID: 881, ClientSD: 1438 Protocol Version: 18 ThreadID: 4094407 GUID: EA9F82FF ResultCode: 3
Dec 20 07:15:20 svr82 supla-server: Device registered. ID: 881, ClientSD: 1207 Protocol Version: 18 ThreadID: 4094590 GUID: EA9F82FF ResultCode: 3
Dec 20 07:15:55 svr82 supla-server: Device registered. ID: 881, ClientSD: 1207 Protocol Version: 18 ThreadID: 4094732 GUID: EA9F82FF ResultCode: 3
Dec 20 07:16:49 svr82 supla-server: Device registered. ID: 881, ClientSD: 718 Protocol Version: 18 ThreadID: 4095009 GUID: EA9F82FF ResultCode: 3
Dec 20 07:17:23 svr82 supla-server: Device registered. ID: 881, ClientSD: 1135 Protocol Version: 18 ThreadID: 4095188 GUID: EA9F82FF ResultCode: 3
Dec 20 07:17:55 svr82 supla-server: Device registered. ID: 881, ClientSD: 262 Protocol Version: 18 ThreadID: 4095328 GUID: EA9F82FF ResultCode: 3
Dec 20 07:18:29 svr82 supla-server: Device registered. ID: 881, ClientSD: 1135 Protocol Version: 18 ThreadID: 4095535 GUID: EA9F82FF ResultCode: 3
Dec 20 07:19:06 svr82 supla-server: Device registered. ID: 881, ClientSD: 718 Protocol Version: 18 ThreadID: 4095778 GUID: EA9F82FF ResultCode: 3
Dec 20 07:19:39 svr82 supla-server: Device registered. ID: 881, ClientSD: 1262 Protocol Version: 18 ThreadID: 4095915 GUID: EA9F82FF ResultCode: 3
Dec 20 07:20:12 svr82 supla-server: Device registered. ID: 881, ClientSD: 1744 Protocol Version: 18 ThreadID: 4096113 GUID: EA9F82FF ResultCode: 3
Dec 20 07:20:47 svr82 supla-server: Device registered. ID: 881, ClientSD: 1714 Protocol Version: 18 ThreadID: 4096261 GUID: EA9F82FF ResultCode: 3
Dec 20 07:21:20 svr82 supla-server: Device registered. ID: 881, ClientSD: 1766 Protocol Version: 18 ThreadID: 4096444 GUID: EA9F82FF ResultCode: 3
Dec 20 07:21:55 svr82 supla-server: Device registered. ID: 881, ClientSD: 1703 Protocol Version: 18 ThreadID: 4096586 GUID: EA9F82FF ResultCode: 3
Dec 20 07:22:29 svr82 supla-server: Device registered. ID: 881, ClientSD: 1047 Protocol Version: 18 ThreadID: 4096780 GUID: EA9F82FF ResultCode: 3
Dec 20 07:23:03 svr82 supla-server: Device registered. ID: 881, ClientSD: 1057 Protocol Version: 18 ThreadID: 4096968 GUID: EA9F82FF ResultCode: 3
Dec 20 07:24:51 svr82 supla-server: Device registered. ID: 881, ClientSD: 1742 Protocol Version: 18 ThreadID: 4097472 GUID: EA9F82FF ResultCode: 3
Dec 20 07:25:27 svr82 supla-server: Device registered. ID: 881, ClientSD: 1014 Protocol Version: 18 ThreadID: 4097665 GUID: EA9F82FF ResultCode: 3
Dec 20 07:25:59 svr82 supla-server: Device registered. ID: 881, ClientSD: 1459 Protocol Version: 18 ThreadID: 4097807 GUID: EA9F82FF ResultCode: 3
Dec 20 07:26:33 svr82 supla-server: Device registered. ID: 881, ClientSD: 574 Protocol Version: 18 ThreadID: 4097988 GUID: EA9F82FF ResultCode: 3
Dec 20 07:27:10 svr82 supla-server: Device registered. ID: 881, ClientSD: 346 Protocol Version: 18 ThreadID: 4098190 GUID: EA9F82FF ResultCode: 3
Dec 20 07:27:56 svr82 supla-server: Device registered. ID: 881, ClientSD: 1704 Protocol Version: 18 ThreadID: 4098394 GUID: EA9F82FF ResultCode: 3
Dec 20 07:28:53 svr82 supla-server: Device registered. ID: 881, ClientSD: 1295 Protocol Version: 18 ThreadID: 4098684 GUID: EA9F82FF ResultCode: 3
Dec 20 07:29:25 svr82 supla-server: Device registered. ID: 881, ClientSD: 606 Protocol Version: 18 ThreadID: 4098868 GUID: EA9F82FF ResultCode: 3
Dec 20 07:30:14 svr82 supla-server: Device registered. ID: 881, ClientSD: 1717 Protocol Version: 18 ThreadID: 4099131 GUID: EA9F82FF ResultCode: 3
Dec 20 07:30:46 svr82 supla-server: Device registered. ID: 881, ClientSD: 1013 Protocol Version: 18 ThreadID: 4099270 GUID: EA9F82FF ResultCode: 3
Dec 20 07:31:35 svr82 supla-server: Device registered. ID: 881, ClientSD: 1704 Protocol Version: 18 ThreadID: 4099516 GUID: EA9F82FF ResultCode: 3
Dec 20 07:32:06 svr82 supla-server: Device registered. ID: 881, ClientSD: 1088 Protocol Version: 18 ThreadID: 4099707 GUID: EA9F82FF ResultCode: 3
Dec 20 07:32:51 svr82 supla-server: Device registered. ID: 881, ClientSD: 1737 Protocol Version: 18 ThreadID: 4099911 GUID: EA9F82FF ResultCode: 3
Dec 20 07:34:42 svr82 supla-server: Device registered. ID: 881, ClientSD: 1744 Protocol Version: 18 ThreadID: 4100502 GUID: EA9F82FF ResultCode: 3
Dec 20 07:35:14 svr82 supla-server: Device registered. ID: 881, ClientSD: 1841 Protocol Version: 18 ThreadID: 4100683 GUID: EA9F82FF ResultCode: 3
Dec 20 07:35:59 svr82 supla-server: Device registered. ID: 881, ClientSD: 850 Protocol Version: 18 ThreadID: 4100883 GUID: EA9F82FF ResultCode: 3
Dec 20 07:36:32 svr82 supla-server: Device registered. ID: 881, ClientSD: 1057 Protocol Version: 18 ThreadID: 4101067 GUID: EA9F82FF ResultCode: 3
Dec 20 07:37:06 svr82 supla-server: Device registered. ID: 881, ClientSD: 764 Protocol Version: 18 ThreadID: 4101265 GUID: EA9F82FF ResultCode: 3
Dec 20 07:37:46 svr82 supla-server: Device registered. ID: 881, ClientSD: 755 Protocol Version: 18 ThreadID: 4101434 GUID: EA9F82FF ResultCode: 3
Dec 20 07:38:22 svr82 supla-server: Device registered. ID: 881, ClientSD: 1459 Protocol Version: 18 ThreadID: 4101654 GUID: EA9F82FF ResultCode: 3
Dec 20 07:38:56 svr82 supla-server: Device registered. ID: 881, ClientSD: 765 Protocol Version: 18 ThreadID: 4101815 GUID: EA9F82FF ResultCode: 3
Dec 20 07:39:28 svr82 supla-server: Device registered. ID: 881, ClientSD: 1056 Protocol Version: 18 ThreadID: 4102056 GUID: EA9F82FF ResultCode: 3
Dec 20 07:40:02 svr82 supla-server: Device registered. ID: 881, ClientSD: 1828 Protocol Version: 18 ThreadID: 4102263 GUID: EA9F82FF ResultCode: 3
Dec 20 07:40:36 svr82 supla-server: Device registered. ID: 881, ClientSD: 407 Protocol Version: 18 ThreadID: 4102459 GUID: EA9F82FF ResultCode: 3
Dec 20 07:41:10 svr82 supla-server: Device registered. ID: 881, ClientSD: 1065 Protocol Version: 18 ThreadID: 4102643 GUID: EA9F82FF ResultCode: 3
Dec 20 07:41:44 svr82 supla-server: Device registered. ID: 881, ClientSD: 718 Protocol Version: 18 ThreadID: 4102786 GUID: EA9F82FF ResultCode: 3
Dec 20 07:42:18 svr82 supla-server: Device registered. ID: 881, ClientSD: 1744 Protocol Version: 18 ThreadID: 4102991 GUID: EA9F82FF ResultCode: 3
Dec 20 07:42:52 svr82 supla-server: Device registered. ID: 881, ClientSD: 764 Protocol Version: 18 ThreadID: 4103136 GUID: EA9F82FF ResultCode: 3
Dec 20 07:43:26 svr82 supla-server: Device registered. ID: 881, ClientSD: 1714 Protocol Version: 18 ThreadID: 4103323 GUID: EA9F82FF ResultCode: 3
Dec 20 07:44:01 svr82 supla-server: Device registered. ID: 881, ClientSD: 731 Protocol Version: 18 ThreadID: 4103477 GUID: EA9F82FF ResultCode: 3
Dec 20 07:44:42 svr82 supla-server: Device registered. ID: 881, ClientSD: 1744 Protocol Version: 18 ThreadID: 4103693 GUID: EA9F82FF ResultCode: 3
Dec 20 07:45:14 svr82 supla-server: Device registered. ID: 881, ClientSD: 541 Protocol Version: 18 ThreadID: 4103876 GUID: EA9F82FF ResultCode: 3
Dec 20 07:46:53 svr82 supla-server: Device registered. ID: 881, ClientSD: 763 Protocol Version: 18 ThreadID: 4104381 GUID: EA9F82FF ResultCode: 3
Dec 20 07:47:26 svr82 supla-server: Device registered. ID: 881, ClientSD: 261 Protocol Version: 18 ThreadID: 4104592 GUID: EA9F82FF ResultCode: 3
Dec 20 07:48:00 svr82 supla-server: Device registered. ID: 881, ClientSD: 1207 Protocol Version: 18 ThreadID: 4104898 GUID: EA9F82FF ResultCode: 3
Dec 20 07:48:34 svr82 supla-server: Device registered. ID: 881, ClientSD: 1817 Protocol Version: 18 ThreadID: 4105115 GUID: EA9F82FF ResultCode: 3
Dec 20 07:49:09 svr82 supla-server: Device registered. ID: 881, ClientSD: 1852 Protocol Version: 18 ThreadID: 4105316 GUID: EA9F82FF ResultCode: 3
Dec 20 07:49:42 svr82 supla-server: Device registered. ID: 881, ClientSD: 1207 Protocol Version: 18 ThreadID: 4105464 GUID: EA9F82FF ResultCode: 3
Dec 20 07:50:19 svr82 supla-server: Device registered. ID: 881, ClientSD: 731 Protocol Version: 18 ThreadID: 4105664 GUID: EA9F82FF ResultCode: 3
Dec 20 07:50:53 svr82 supla-server: Device registered. ID: 881, ClientSD: 776 Protocol Version: 18 ThreadID: 4105835 GUID: EA9F82FF ResultCode: 3
Dec 20 07:51:26 svr82 supla-server: Device registered. ID: 881, ClientSD: 643 Protocol Version: 18 ThreadID: 4106046 GUID: EA9F82FF ResultCode: 3
Dec 20 07:52:00 svr82 supla-server: Device registered. ID: 881, ClientSD: 574 Protocol Version: 18 ThreadID: 4106192 GUID: EA9F82FF ResultCode: 3
Dec 20 07:52:34 svr82 supla-server: Device registered. ID: 881, ClientSD: 1703 Protocol Version: 18 ThreadID: 4106388 GUID: EA9F82FF ResultCode: 3
Dec 20 07:53:13 svr82 supla-server: Device registered. ID: 881, ClientSD: 1704 Protocol Version: 18 ThreadID: 4106591 GUID: EA9F82FF ResultCode: 3
Dec 20 07:53:50 svr82 supla-server: Device registered. ID: 881, ClientSD: 1841 Protocol Version: 18 ThreadID: 4106768 GUID: EA9F82FF ResultCode: 3
Dec 20 07:54:23 svr82 supla-server: Device registered. ID: 881, ClientSD: 1065 Protocol Version: 18 ThreadID: 4107000 GUID: EA9F82FF ResultCode: 3
Dec 20 07:54:57 svr82 supla-server: Device registered. ID: 881, ClientSD: 718 Protocol Version: 18 ThreadID: 4107172 GUID: EA9F82FF ResultCode: 3
Dec 20 07:55:31 svr82 supla-server: Device registered. ID: 881, ClientSD: 1738 Protocol Version: 18 ThreadID: 4107379 GUID: EA9F82FF ResultCode: 3
Dec 20 07:56:04 svr82 supla-server: Device registered. ID: 881, ClientSD: 1649 Protocol Version: 18 ThreadID: 4107598 GUID: EA9F82FF ResultCode: 3
Dec 20 07:56:38 svr82 supla-server: Device registered. ID: 881, ClientSD: 1025 Protocol Version: 18 ThreadID: 4107755 GUID: EA9F82FF ResultCode: 3
Dec 20 07:57:13 svr82 supla-server: Device registered. ID: 881, ClientSD: 1255 Protocol Version: 18 ThreadID: 4107968 GUID: EA9F82FF ResultCode: 3
Dec 20 07:57:48 svr82 supla-server: Device registered. ID: 881, ClientSD: 1719 Protocol Version: 18 ThreadID: 4108125 GUID: EA9F82FF ResultCode: 3
Dec 20 07:58:21 svr82 supla-server: Device registered. ID: 881, ClientSD: 1703 Protocol Version: 18 ThreadID: 4108320 GUID: EA9F82FF ResultCode: 3
Dec 20 07:58:55 svr82 supla-server: Device registered. ID: 881, ClientSD: 1766 Protocol Version: 18 ThreadID: 4108488 GUID: EA9F82FF ResultCode: 3
Dec 20 07:59:29 svr82 supla-server: Device registered. ID: 881, ClientSD: 1829 Protocol Version: 18 ThreadID: 4108712 GUID: EA9F82FF ResultCode: 3
Jak widać z logów THW połączył się o 07:45:14 co oznacza, że czas życia pomiaru został ustawiony na 07:46:14 i THW zamiast połączyć się do tego czasu, połączyło o 07:46:53 przez co logger trafił w wąskie okno niedostępności.
Być może jest tak, że WiFi nie radzą sobie z jakiegoś powodu z urządzeniami, które często zestawiają połączenia i je zrywają.
Rozwiązaniem i w Twoim przypadku byłoby ustawienia czasu życia pomiaru na min 2 min.
Przemyślimy temat i zaproponujemy rozwiązanie.
SUPLA.... Nareszcie w domu.
-
ramar4
- Posts: 929
- Joined: Mon Dec 28, 2020 7:56 pm
- Location: Szydłowiec
Ok dzięki czekam na info
2×ROW-01-ROP-01
2×ROW-01/16A
1×ROW-O1-RWS311J/Z
1×SLW-01
1×SLW-02
5×THW-01p
5×DS18B20
1×LIW-01
1×LEW-02
1×MEW-01
1×GMB-03
3×MSLW-02
1xPNW-01
2×mRow-02
2xLEW-01
1xSGW-01
1xmSLW-01
2×ROW-01/16A
1×ROW-O1-RWS311J/Z
1×SLW-01
1×SLW-02
5×THW-01p
5×DS18B20
1×LIW-01
1×LEW-02
1×MEW-01
1×GMB-03
3×MSLW-02
1xPNW-01
2×mRow-02
2xLEW-01
1xSGW-01
1xmSLW-01
-
3DPiCiU
- Posts: 26
- Joined: Sat Feb 01, 2020 5:34 pm
Ok czekam za decyzją bo potrzebuję jeszcze 15 takich w tej firmie i kolejnych 30 w innych.
A nie chce się zbłaźnić i korzystać z Rumuńskich czy o zgrozo Chińskich rozwiązań.
Moje mają nadal chwilowe przerwy.
Sieć jest nowiutka wszystko we wrześniu było zakładane. Z nowych komponentów.
A nie chce się zbłaźnić i korzystać z Rumuńskich czy o zgrozo Chińskich rozwiązań.
Moje mają nadal chwilowe przerwy.
Sieć jest nowiutka wszystko we wrześniu było zakładane. Z nowych komponentów.
-
pzygmunt
- Posts: 20302
- Joined: Tue Jan 19, 2016 9:26 am
- Location: Paczków
- Been thanked: 59 times
Do pobrania jest aktualizacja do wersji 22.12, która wprowadza dłuższy czas życia pojedynczego pomiaru oraz usprawnia wyszukiwanie najbliższego AP. Dajcie znać czy po aktualizacji zmniejszy się ilość luk.
SUPLA.... Nareszcie w domu.
-
tomekk87
- Posts: 192
- Joined: Fri Aug 02, 2019 12:19 pm
Mam problem z aktualizacją do najnowszej wersji. Takie info się pojawiapzygmunt wrote: Thu Dec 22, 2022 2:48 pm Do pobrania jest aktualizacja do wersji 22.12, która wprowadza dłuższy czas życia pojedynczego pomiaru oraz usprawnia wyszukiwanie najbliższego AP. Dajcie znać czy po aktualizacji zmniejszy się ilość luk.
Code: Select all
LAST STATE: Config mode, Registered and ready, SW update: image corrupted - invalid magic byte, SW update url: "https://updates.supla.org/download/zamel_thw_01_2212.bin", SW update new version: 22.12, SW update status: Update available, SW update in progress...
Firmware: 22.11.03