Najczęstsze pytania i odpowiedzi [bramka ZigBee]

Moderator: vajera

Simono
Posts: 533
Joined: Mon Sep 17, 2018 5:26 pm
Been thanked: 6 times

Post

klew wrote: Wed Apr 08, 2026 7:46 am Chodziło mi o logi z urządzenia. Ewentualnie mogą też być logi z działania serwera (tam widać próby połączenia).
Odnośnie samej aktualizacji Clouda i serwera, to nie pomogę, bo nie mam pojęcia o tym
To z serwera logi mam takie:

Code: Select all

docker logs --since=5m supla-server
INFO[08:14:26.044034] Connection accepted: 192.168.1.206:59629 ClientSD: 16 Secure: 1
INFO[08:14:26.554083] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:14:27.596221] Connection accepted: 192.168.1.206:59630 ClientSD: 17 Secure: 1
INFO[08:14:28.090251] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:14:29.132364] Connection accepted: 192.168.1.206:59631 ClientSD: 16 Secure: 1
INFO[08:14:29.627143] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:14:30.667786] Connection accepted: 192.168.1.206:59632 ClientSD: 17 Secure: 1
INFO[08:14:31.162591] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:14:32.205079] Connection accepted: 192.168.1.206:59633 ClientSD: 16 Secure: 1
INFO[08:14:32.698409] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:14:33.742640] Connection accepted: 192.168.1.206:59634 ClientSD: 17 Secure: 1
INFO[08:14:34.234406] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:14:35.274790] Connection accepted: 192.168.1.206:59635 ClientSD: 16 Secure: 1
INFO[08:14:35.772029] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:14:36.826388] Connection accepted: 192.168.1.206:59636 ClientSD: 18 Secure: 1
INFO[08:14:37.348867] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:14:53.424260] Connection accepted: 192.168.1.206:59637 ClientSD: 16 Secure: 1
INFO[08:14:53.931194] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
ERR[08:15:04.353777] An attempt to obtain remote gateway token from the AD server failed. Result code: 403
INFO[08:15:12.555878] Connection accepted: 192.168.1.206:53367 ClientSD: 18 Secure: 1
INFO[08:15:12.958401] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:15:29.037174] Connection accepted: 192.168.1.206:53368 ClientSD: 21 Secure: 1
INFO[08:15:29.531459] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 21
INFO[08:15:30.576056] Connection accepted: 192.168.1.206:53369 ClientSD: 17 Secure: 1
INFO[08:15:31.068705] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:15:32.129856] Connection accepted: 192.168.1.206:53370 ClientSD: 18 Secure: 1
INFO[08:15:32.705087] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:15:33.747599] Connection accepted: 192.168.1.206:53371 ClientSD: 16 Secure: 1
INFO[08:15:34.268467] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:15:50.358672] Connection accepted: 192.168.1.206:53372 ClientSD: 18 Secure: 1
INFO[08:15:50.862840] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
ERR[08:16:04.502290] An attempt to obtain remote gateway token from the AD server failed. Result code: 403
INFO[08:16:07.011355] Connection accepted: 192.168.1.206:53373 ClientSD: 17 Secure: 1
INFO[08:16:07.520999] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:16:08.567957] Connection accepted: 192.168.1.206:53374 ClientSD: 18 Secure: 1
INFO[08:16:09.058541] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:16:10.108320] Connection accepted: 192.168.1.206:53375 ClientSD: 17 Secure: 1
INFO[08:16:10.593875] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:16:11.635488] Connection accepted: 192.168.1.206:53376 ClientSD: 18 Secure: 1
INFO[08:16:12.129229] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:16:13.172479] Connection accepted: 192.168.1.206:53377 ClientSD: 17 Secure: 1
INFO[08:16:13.665093] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:16:14.706552] Connection accepted: 192.168.1.206:53378 ClientSD: 18 Secure: 1
INFO[08:16:15.201210] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:16:16.242422] Connection accepted: 192.168.1.206:53379 ClientSD: 16 Secure: 1
INFO[08:16:16.754818] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:16:17.793506] Connection accepted: 192.168.1.206:53380 ClientSD: 17 Secure: 1
INFO[08:16:18.304267] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:16:34.391055] Connection accepted: 192.168.1.206:53381 ClientSD: 16 Secure: 1
INFO[08:16:34.967024] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:16:36.019410] Connection accepted: 192.168.1.206:53382 ClientSD: 17 Secure: 1
INFO[08:16:36.603127] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:16:37.643138] Connection accepted: 192.168.1.206:53383 ClientSD: 16 Secure: 1
INFO[08:16:38.142533] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:16:39.198369] Connection accepted: 192.168.1.206:53384 ClientSD: 17 Secure: 1
INFO[08:16:39.796526] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:16:40.835752] Connection accepted: 192.168.1.206:53385 ClientSD: 16 Secure: 1
INFO[08:16:41.432048] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:16:42.483059] Connection accepted: 192.168.1.206:53386 ClientSD: 17 Secure: 1
INFO[08:16:43.055243] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:16:44.098572] Connection accepted: 192.168.1.206:53387 ClientSD: 16 Secure: 1
INFO[08:16:44.590453] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:16:45.635024] Connection accepted: 192.168.1.206:53388 ClientSD: 17 Secure: 1
INFO[08:16:46.128382] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:16:47.185146] Connection accepted: 192.168.1.206:53389 ClientSD: 16 Secure: 1
INFO[08:16:47.788538] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
ERR[08:17:04.878409] An attempt to obtain remote gateway token from the AD server failed. Result code: 403
INFO[08:17:07.980735] Connection accepted: 192.168.1.206:56151 ClientSD: 17 Secure: 1
INFO[08:17:08.465249] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:17:09.507207] Connection accepted: 192.168.1.206:56152 ClientSD: 16 Secure: 1
INFO[08:17:10.020416] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:17:26.182035] Connection accepted: 192.168.1.206:56153 ClientSD: 17 Secure: 1
INFO[08:17:26.677294] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:17:27.720003] Connection accepted: 192.168.1.206:56154 ClientSD: 18 Secure: 1
INFO[08:17:28.215495] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:17:29.267457] Connection accepted: 192.168.1.206:56155 ClientSD: 16 Secure: 1
INFO[08:17:29.785967] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:17:45.929771] Connection accepted: 192.168.1.206:56156 ClientSD: 17 Secure: 1
INFO[08:17:46.382754] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:17:47.484483] Connection accepted: 192.168.1.206:56157 ClientSD: 16 Secure: 1
INFO[08:17:47.979199] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:17:49.026412] Connection accepted: 192.168.1.206:56158 ClientSD: 17 Secure: 1
INFO[08:17:49.550138] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
ERR[08:18:05.019998] An attempt to obtain remote gateway token from the AD server failed. Result code: 403
INFO[08:18:05.693950] Connection accepted: 192.168.1.206:56159 ClientSD: 16 Secure: 1
INFO[08:18:06.140019] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:18:22.221160] Connection accepted: 192.168.1.206:56160 ClientSD: 17 Secure: 1
INFO[08:18:22.792375] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:18:23.839079] Connection accepted: 192.168.1.206:56161 ClientSD: 16 Secure: 1
INFO[08:18:24.431216] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:18:25.476936] Connection accepted: 192.168.1.206:56162 ClientSD: 17 Secure: 1
INFO[08:18:25.967641] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:18:27.009588] Connection accepted: 192.168.1.206:56163 ClientSD: 16 Secure: 1
INFO[08:18:27.502835] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:18:28.545458] Connection accepted: 192.168.1.206:56164 ClientSD: 17 Secure: 1
INFO[08:18:29.041683] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:18:30.097619] Connection accepted: 192.168.1.206:56165 ClientSD: 16 Secure: 1
INFO[08:18:30.679582] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:18:31.741960] Connection accepted: 192.168.1.206:56166 ClientSD: 17 Secure: 1
INFO[08:18:32.318484] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:18:33.372654] Connection accepted: 192.168.1.206:56167 ClientSD: 18 Secure: 1
INFO[08:18:33.954113] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:18:34.996970] Connection accepted: 192.168.1.206:56168 ClientSD: 17 Secure: 1
INFO[08:18:35.490429] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:18:36.539431] Connection accepted: 192.168.1.206:56169 ClientSD: 18 Secure: 1
INFO[08:18:37.129263] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:18:38.170444] Connection accepted: 192.168.1.206:56170 ClientSD: 17 Secure: 1
INFO[08:18:38.678438] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:18:39.718781] Connection accepted: 192.168.1.206:56171 ClientSD: 18 Secure: 1
INFO[08:18:40.303345] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 18
INFO[08:18:41.348338] Connection accepted: 192.168.1.206:56172 ClientSD: 16 Secure: 1
INFO[08:18:41.941745] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:18:42.985389] Connection accepted: 192.168.1.206:56173 ClientSD: 17 Secure: 1
INFO[08:18:43.477747] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 17
INFO[08:18:44.521638] Connection accepted: 192.168.1.206:56174 ClientSD: 16 Secure: 1
INFO[08:18:45.030659] Cipher: ECDHE-RSA-AES256-GCM-SHA384, SSL Version: TLSv1.2, ClientSD: 16
INFO[08:18:46.170892] Connection accepted: 192.168.1.206:56175 ClientSD: 17 Secure: 1
INFO[08:19:03.773593] Connection accepted: 192.168.1.206:56210 ClientSD: 16 Secure: 1
ERR[08:19:04.153861] An attempt to obtain remote gateway token from the AD server failed. Result code: 403
INFO[08:19:04.793126] Connection accepted: 192.168.1.206:56211 ClientSD: 17 Secure: 1
INFO[08:19:14.730089] Connection accepted: 192.168.1.206:56212 ClientSD: 16 Secure: 1
Top
Simono
Posts: 533
Joined: Mon Sep 17, 2018 5:26 pm
Been thanked: 6 times

Post

@vajera miałeś poniekąd nosa chyba jak to u Ciebie często bywa.
Po walkach upgradu prywatnej instancji do 26.03 zakończonych sukcesem melduję, że po aktualizacji bramki do wersji 1.5.1 teraz bramka łączy się z moim serwerem Supla.
Top
User avatar
uchnast.michal
Posts: 1334
Joined: Tue Jun 04, 2019 11:37 am
Has thanked: 7 times

Post

Cześć,
Wgrałem dzisiaj na nowy moduł wersję Z2S-1.5.14-16/04/26 i po przywrócenia kopii z lutego bramka jest rozłączona. Gdy podłaczę "stary moduł" jest ok. Czy coś zmieniło? Wgrywam konfig tak:

Code: Select all

C:\GuiGenericBuilder\esptool.exe --chip esp32c6 --port COM5 write_flash 0x290000 C:\zigbee\strych\littlefs_zigbee.bin
Z góry dziękuję za podopwiedź.
PS
Modul Seeed Studio XIAO ESP32-C6 4MB

Edycja
Ok chyba popoełniłem błąd i nie wgrałem wersji update. Adres ten sam 0x290000?
Top
User avatar
vajera
Posts: 7293
Joined: Wed Oct 31, 2018 7:58 am
Location: Biedrusko
Has thanked: 291 times
Been thanked: 161 times

Post

uchnast.michal wrote: Thu Apr 16, 2026 3:51 pm Cześć,
Wgrałem dzisiaj na nowy moduł wersję Z2S-1.5.14-16/04/26 i po przywrócenia kopii z lutego bramka jest rozłączona. Gdy podłaczę "stary moduł" jest ok. Czy coś zmieniło? Wgrywam konfig tak:

Code: Select all

C:\GuiGenericBuilder\esptool.exe --chip esp32c6 --port COM5 write_flash 0x290000 C:\zigbee\strych\littlefs_zigbee.bin
Z góry dziękuję za podopwiedź.
PS
Modul Seeed Studio XIAO ESP32-C6 4MB

Edycja
Ok chyba popoełniłem błąd i nie wgrałem wersji update. Adres ten sam 0x290000?
viewtopic.php?p=233957#p233957
Bramka Zigbee <=> SUPLA
Więcej informacji tutaj:
https://forum.supla.org/viewforum.php?f=127
FAQ https://forum.supla.org/viewtopic.php?t=17277
Top
User avatar
uchnast.michal
Posts: 1334
Joined: Tue Jun 04, 2019 11:37 am
Has thanked: 7 times

Post

Z 0x10000 było to samo:(
Sprawdzę raz jeszcze :D
Edit
Powtórzyłem procedurę, nadal offline. Jak wgrałem czysty to ładnie się zgłasza :?
Moduł dawcy ma wersję Z2S-1.4.52-25/02/26
eksportuję tak: esptool.exe --chip esp32c6 --port COM8 read_flash 0x290000 0x160000 littlefs_zigbee.bin
importuję : esptool.exe --chip esp32c6 --port COM5 write_flash 0x100000 littlefs_zigbee.bin
oczywiście w kolejności: erase_flash, bin aktualizacji Z2S_Gateway.4MB.no_OTA.no_logs.update_only.WARNING_NEW_SIZE.bin, write_flash
Top
User avatar
vajera
Posts: 7293
Joined: Wed Oct 31, 2018 7:58 am
Location: Biedrusko
Has thanked: 291 times
Been thanked: 161 times

Post

uchnast.michal wrote: Thu Apr 16, 2026 5:53 pm Z 0x10000 było to samo:(
Sprawdzę raz jeszcze :D
Edit
Powtórzyłem procedurę, nadal offline. Jak wgrałem czysty to ładnie się zgłasza :?
Moduł dawcy ma wersję Z2S-1.4.52-25/02/26
eksportuję tak: esptool.exe --chip esp32c6 --port COM8 read_flash 0x290000 0x160000 littlefs_zigbee.bin
importuję : esptool.exe --chip esp32c6 --port COM5 write_flash 0x100000 littlefs_zigbee.bin
oczywiście w kolejności: erase_flash, bin aktualizacji Z2S_Gateway.4MB.no_OTA.no_logs.update_only.WARNING_NEW_SIZE.bin, write_flash
Przeczytałeś ten wątek, który Ci podesłałem? Nie zrobisz aktualizacji wersji < 1.5.0 plikiem >= 1.5.0, ponieważ z braku miejsca musiałem zmienić rozmiar partycji - konieczna jest jednorazowa ręczna procedura opisana przeze mnie krok po kroku w tamtym temacie.
Bramka Zigbee <=> SUPLA
Więcej informacji tutaj:
https://forum.supla.org/viewforum.php?f=127
FAQ https://forum.supla.org/viewtopic.php?t=17277
Top
User avatar
uchnast.michal
Posts: 1334
Joined: Tue Jun 04, 2019 11:37 am
Has thanked: 7 times

Post

Wybacz, moja wina :(
Masz absolutną rację a ja przez moje roztargnienie zawracam Ci głowę. Przepraszam
Top
zzrr
Posts: 1864
Joined: Wed Oct 26, 2022 7:35 pm
Has thanked: 76 times
Been thanked: 119 times

Post

@uchnast.michal w tematach Z2S to strach nie czytać na bieżąco :P Tu tempo zmian jest szokujące :) ;)
Top
User avatar
vajera
Posts: 7293
Joined: Wed Oct 31, 2018 7:58 am
Location: Biedrusko
Has thanked: 291 times
Been thanked: 161 times

Post

uchnast.michal wrote: Thu Apr 16, 2026 7:20 pm Wybacz, moja wina :(
Masz absolutną rację a ja przez moje roztargnienie zawracam Ci głowę. Przepraszam
Nic się nie stało, nie ma potrzeby szukania winnych ;)
Powodzenia z aktualizacją!
Bramka Zigbee <=> SUPLA
Więcej informacji tutaj:
https://forum.supla.org/viewforum.php?f=127
FAQ https://forum.supla.org/viewtopic.php?t=17277
Top
User avatar
uchnast.michal
Posts: 1334
Joined: Tue Jun 04, 2019 11:37 am
Has thanked: 7 times

Post

zzrr wrote: Thu Apr 16, 2026 7:39 pm @uchnast.michal w tematach Z2S to strach nie czytać na bieżąco :P Tu tempo zmian jest szokujące :) ;)
To wszystko wina @vajera :D Generuje zmiany i posty jak AI. Dopiero zamówiłem Xiao bo liczyłem, że zewnętrzna antena pozowli mi sie pozbyc 2 urządzeń a tu masz... bez 8MB flash nie podchodź. Jak żyć?!
Top

Return to “Bramka ZigBee”