v24.05 - żaluzje fasadowe

User avatar
fracz
Posts: 2262
Joined: Fri Oct 28, 2016 10:56 pm
Location: Kraków

Post

Ruszyły aktualizacje Clouda do wersji v24.05.

Głównymi nowościami w wersji v24.05 jest wsparcie dla żaluzji fasadowych oraz możliwość otwierania i zamykania rolet i żaluzji o podaną wartość (np. odsłoń roletę o 20%). Dotychczas było możliwe jedynie określenie wartości docelowej - teraz można to robić także względem obecnego stanu. Funkcjonalność działa w akcjach wykonywanych ze strony internetowej, a także w linkach bezpośrednich, scenach i harmonogramach.

Wkrótce pojawi się także aktualizacja aplikacji mobilnych ze wsparciem dla fasadówek oraz nowy firmware dla urządzeń SRW.

Pełny changelog znajdziecie na Githubie: SUPLA Cloud oraz SUPLA Core.

Wydanie dockerów: już jest.
User avatar
fracz
Posts: 2262
Joined: Fri Oct 28, 2016 10:56 pm
Location: Kraków

Post

Najmocniej przepraszam za opóźnienie w wydaniu obrazów dockerowych wersji majowej. Już są.
User avatar
lukfud
Posts: 2117
Joined: Thu Nov 23, 2017 11:33 pm
Location: Warszawa

Post

Zaktualizowane, dzięki ;)
https://www.facebook.com/groups/supladiy/
User avatar
kris.sg
Posts: 413
Joined: Mon Aug 07, 2017 8:08 pm
Location: Przezchlebie

Post

Też u siebie zaktualizowałem ale jest problem aplikacja się restartuje, urządzenia wszystkie offline.
Log z contenera supla-server:

Code: Select all

024-06-18 08:51:28,512 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-06-18 08:51:28,512 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-18 08:51:29,516 INFO spawned: 'supla-server' with pid 1418
INFO[08:51:29.557097] Server version 24.05 [Protocol v24]
INFO[08:51:29.557245] Started at Tue Jun 18 08:51:29 2024
INFO[08:51:29.564721] SSL version: LibreSSL 3.5.4
ERR[08:51:29.689007] Could not get any token for any remote gateway from AD server.
INFO[08:51:29.774096] Connection accepted: 192.168.1.1:60790 ClientSD: 12 Secure: 1
INFO[08:51:29.948528] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 12
INFO[08:51:30.258721] Client registered. ClientSD: 12 Protocol Version: 24
INFO[08:51:30.269447] Connection accepted: 192.168.1.1:39131 ClientSD: 27 Secure: 1
2024-06-18 08:51:30,533 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-06-18 08:51:30,534 INFO exited: supla-server (terminated by SIGBUS; not expected)
■Rpi4(m.2) Supla Cloud, Scripts ■Rpi3(sd) SD: 6x MI ATC, 1x W.S.
ROLETY_V3 x12 ■SWITCH_DUAL x4 ■GATE_MODULE_V3 x1 ■SOCKET_SSR x1 ■SMOKE_MODULE x1
SONOFF_TOUCH x4 ■YUNSCHAN x1 ■STAITCASE_DIMMER x1 ■MEW-01 x2 ■mROW-02 x1 ■LEW-01 x1
POW_R2 x2 ■SP111 x3
User avatar
kris.sg
Posts: 413
Joined: Mon Aug 07, 2017 8:08 pm
Location: Przezchlebie

Post

Wszystko usunąłem, postawiłem na nowo i odtworzyłem bazę.
Wszystko działa, moduły na zielono, jak tylko dodam aplikację to moduły przestają się łączyć, a apka się zapętla na łączenie po chwili migną kanały i tak w kółko. Aplikację też zainstalowałem na nowo, ale to samo (android).

Pomożecie ?
■Rpi4(m.2) Supla Cloud, Scripts ■Rpi3(sd) SD: 6x MI ATC, 1x W.S.
ROLETY_V3 x12 ■SWITCH_DUAL x4 ■GATE_MODULE_V3 x1 ■SOCKET_SSR x1 ■SMOKE_MODULE x1
SONOFF_TOUCH x4 ■YUNSCHAN x1 ■STAITCASE_DIMMER x1 ■MEW-01 x2 ■mROW-02 x1 ■LEW-01 x1
POW_R2 x2 ■SP111 x3
User avatar
kris.sg
Posts: 413
Joined: Mon Aug 07, 2017 8:08 pm
Location: Przezchlebie

Post

log z kontenera supla-server po dodaniu smartfona:

Code: Select all

INFO[09:55:11.852848] Device registration started. ClientSD: 11 Protocol Version: 12 ThreadID: 265 GUID: 17FD8496
INFO[09:55:11.908234] Device registered. ID: 14, ClientSD: 11 Protocol Version: 12 ThreadID: 265 GUID: 17FD8496 ResultCode: 3
INFO[09:55:12.020843] Connection accepted: 192.168.1.1:19960 ClientSD: 34 Secure: 1
INFO[09:55:12.030614] Client registered. ClientSD: 25 Protocol Version: 24
INFO[09:55:12.185691] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 30
INFO[09:55:12.240273] Connection accepted: 192.168.1.1:43579 ClientSD: 38 Secure: 1
INFO[09:55:12.306973] Device registration started. ClientSD: 30 Protocol Version: 16 ThreadID: 267 GUID: E72E773B
2024-06-19 09:55:13,334 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-19 09:55:14,340 INFO spawned: 'supla-server' with pid 272
INFO[09:55:14.407574] Server version 24.05 [Protocol v24]
INFO[09:55:14.407796] Started at Wed Jun 19 09:55:14 2024
INFO[09:55:14.417272] SSL version: LibreSSL 3.5.4
INFO[09:55:14.435012] Connection accepted: 192.168.1.1:18176 ClientSD: 11 Secure: 1
ERR[09:55:14.544349] Could not get any token for any remote gateway from AD server.
INFO[09:55:14.602128] Connection accepted: 192.168.1.1:60648 ClientSD: 19 Secure: 1
INFO[09:55:14.882583] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 11
INFO[09:55:14.995404] Device registration started. ClientSD: 11 Protocol Version: 16 ThreadID: 283 GUID: 3216F9BF
INFO[09:55:15.126825] Device registered. ID: 39, ClientSD: 11 Protocol Version: 16 ThreadID: 283 GUID: 3216F9BF ResultCode: 3
INFO[09:55:15.265358] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 19
INFO[09:55:15.501259] Connection accepted: 192.168.1.1:37994 ClientSD: 30 Secure: 1
2024-06-19 09:55:15,501 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO[09:55:15.691031] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 30
INFO[09:55:15.931742] Connection accepted: 192.168.1.1:18971 ClientSD: 36 Secure: 1
INFO[09:55:15.994034] Client registered. ClientSD: 30 Protocol Version: 24
INFOINFO[09:55:16.227364] [09:55:16.227361] Connection accepted: 192.168.1.1:57896 ClientSD: 12 Secure: 0
Connection accepted: 192.168.1.1:64031 ClientSD: 41 Secure: 1
INFO[09:55:16.228166] Connection accepted: 192.168.1.1:49180 ClientSD: 45 Secure: 0
INFO[09:55:16.231802] Connection accepted: 192.168.1.1:59558 ClientSD: 48 Secure: 0
INFO[09:55:16.232469] Device registration started. ClientSD: 12 Protocol Version: 16 ThreadID: 291 GUID: 08C8A3CE
INFO[09:55:16.238655] Connection accepted: 192.168.1.1:63134 ClientSD: 51 Secure: 0
2024-06-19 09:55:16,276 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-19 09:55:17,281 INFO spawned: 'supla-server' with pid 295
INFO[09:55:17.327728] Server version 24.05 [Protocol v24]
INFO[09:55:17.327936] Started at Wed Jun 19 09:55:17 2024
INFO[09:55:17.335273] SSL version: LibreSSL 3.5.4
ERR[09:55:17.446195] Could not get any token for any remote gateway from AD server.
INFO[09:55:17.559860] Connection accepted: 192.168.1.1:44786 ClientSD: 11 Secure: 1
INFO[09:55:17.610089] Connection accepted: 192.168.1.1:50742 ClientSD: 27 Secure: 1
INFO[09:55:17.731856] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 11
INFO[09:55:18.065764] Client registered. ClientSD: 11 Protocol Version: 24
INFO[09:55:18.069883] Connection accepted: 192.168.1.1:44372 ClientSD: 30 Secure: 1
INFO[09:55:18.173954] Connection accepted: 192.168.1.1:7531 ClientSD: 33 Secure: 1
INFO[09:55:18.194624] Connection accepted: 192.168.1.1:6624 ClientSD: 36 Secure: 1
2024-06-19 09:55:18,219 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-19 09:55:19,223 INFO spawned: 'supla-server' with pid 311
INFO[09:55:19.269081] Server version 24.05 [Protocol v24]
INFO[09:55:19.269253] Started at Wed Jun 19 09:55:19 2024
INFO[09:55:19.279708] SSL version: LibreSSL 3.5.4
ERR[09:55:19.410525] Could not get any token for any remote gateway from AD server.
INFO[09:55:19.487975] Connection accepted: 192.168.1.1:44790 ClientSD: 11 Secure: 1
INFO[09:55:19.699443] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 11
INFO[09:55:20.039782] Client registered. ClientSD: 11 Protocol Version: 24
2024-06-19 09:55:21,205 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-06-19 09:55:21,205 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-19 09:55:22,210 INFO spawned: 'supla-server' with pid 323
INFO[09:55:22.255012] Server version 24.05 [Protocol v24]
INFO[09:55:22.255179] Started at Wed Jun 19 09:55:22 2024
INFO[09:55:22.262863] SSL version: LibreSSL 3.5.4
ERR[09:55:22.371998] Could not get any token for any remote gateway from AD server.
2024-06-19 09:55:23,373 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
INFO[09:55:23.492370] Connection accepted: 192.168.1.1:44822 ClientSD: 12 Secure: 1
INFO[09:55:23.672005] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 12
INFO[09:55:23.995567] Client registered. ClientSD: 12 Protocol Version: 24
INFO[09:55:24.128114] Connection accepted: 192.168.1.1:56872 ClientSD: 27 Secure: 1
2024-06-19 09:55:24,146 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-19 09:55:25,150 INFO spawned: 'supla-server' with pid 336
INFO[09:55:25.191081] Server version 24.05 [Protocol v24]
INFO[09:55:25.191228] Started at Wed Jun 19 09:55:25 2024
INFO[09:55:25.197304] SSL version: LibreSSL 3.5.4
ERR[09:55:25.310869] Could not get any token for any remote gateway from AD server.
INFO[09:55:25.480560] Connection accepted: 192.168.1.1:44834 ClientSD: 12 Secure: 1
INFO[09:55:25.649222] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 12
INFO[09:55:25.964955] Client registered. ClientSD: 12 Protocol Version: 24
INFO[09:55:26.103811] Connection accepted: 192.168.1.1:40931 ClientSD: 27 Secure: 1
2024-06-19 09:55:26,147 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-19 09:55:27,152 INFO spawned: 'supla-server' with pid 349
INFO[09:55:27.197304] Server version 24.05 [Protocol v24]
INFO[09:55:27.197478] Started at Wed Jun 19 09:55:27 2024
INFO[09:55:27.204633] SSL version: LibreSSL 3.5.4
ERR[09:55:27.318600] Could not get any token for any remote gateway from AD server.
INFO[09:55:27.493581] Connection accepted: 192.168.1.1:44128 ClientSD: 11 Secure: 1
INFO[09:55:27.714406] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 11
INFO[09:55:28.122103] Client registered. ClientSD: 11 Protocol Version: 24
2024-06-19 09:55:28,289 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-06-19 09:55:28,289 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-19 09:55:29,294 INFO spawned: 'supla-server' with pid 361
INFO[09:55:29.338725] Server version 24.05 [Protocol v24]
INFO[09:55:29.338897] Started at Wed Jun 19 09:55:29 2024
INFO[09:55:29.346850] SSL version: LibreSSL 3.5.4
ERR[09:55:29.474821] Could not get any token for any remote gateway from AD server.
INFO[09:55:29.496432] Connection accepted: 192.168.1.1:44144 ClientSD: 15 Secure: 1
INFO[09:55:29.667011] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 15
INFO[09:55:30.001616] Client registered. ClientSD: 15 Protocol Version: 24
2024-06-19 09:55:31,250 INFO success: supla-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-06-19 09:55:31,251 INFO exited: supla-server (terminated by SIGBUS; not expected)
2024-06-19 09:55:32,254 INFO spawned: 'supla-server' with pid 382
INFO[09:55:32.299915] Server version 24.05 [Protocol v24]
INFO[09:55:32.300075] Started at Wed Jun 19 09:55:32 2024
INFO[09:55:32.307833] SSL version: LibreSSL 3.5.4
ERR[09:55:32.431402] Could not get any token for any remote gateway from AD server.
log ja usunę smartfona:

Code: Select all

  
INFO[09:57:38.325632] Connection accepted: 192.168.1.1:50475 ClientSD: 81 Secure: 1
INFO[09:57:38.345045] Connection accepted: 192.168.1.1:52913 ClientSD: 63 Secure: 0
INFO[09:57:38.367744] Connection accepted: 192.168.1.1:53294 ClientSD: 89 Secure: 0
INFO[09:57:38.412099] Connection accepted: 192.168.1.1:60503 ClientSD: 92 Secure: 0
INFO[09:57:38.430407] Device registered. ID: 40, ClientSD: 79 Protocol Version: 16 ThreadID: 1107 GUID: C3C7BFB2 ResultCode: 3
INFO[09:57:38.486773] Device registration started. ClientSD: 63 Protocol Version: 16 ThreadID: 1109 GUID: 10CE9149
INFO[09:57:38.508767] Device registration started. ClientSD: 89 Protocol Version: 16 ThreadID: 1110 GUID: 499275B5
INFO[09:57:38.538107] Device registered. ID: 1, ClientSD: 63 Protocol Version: 16 ThreadID: 1109 GUID: 10CE9149 ResultCode: 3
INFO[09:57:38.555937] Device registration started. ClientSD: 92 Protocol Version: 16 ThreadID: 1111 GUID: 12CDB7E7
INFO[09:57:38.565620] Device registered. ID: 7, ClientSD: 89 Protocol Version: 16 ThreadID: 1110 GUID: 499275B5 ResultCode: 3
INFO[09:57:38.612105] Device registered. ID: 11, ClientSD: 92 Protocol Version: 16 ThreadID: 1111 GUID: 12CDB7E7 ResultCode: 3
INFO[09:57:38.981617] Cipher: AES128-SHA256, SSL Version: TLSv1.2, ClientSD: 81
INFO[09:57:39.006522] Device registration started. ClientSD: 81 Protocol Version: 16 ThreadID: 1108 GUID: 4F22559C
INFO[09:57:39.043586] Device registered. ID: 10, ClientSD: 81 Protocol Version: 16 ThreadID: 1108 GUID: 4F22559C ResultCode: 3
INFO[09:57:44.890043] Connection accepted: 192.168.1.1:11490 ClientSD: 86 Secure: 1
INFO[09:57:45.312656] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 86
INFO[09:57:45.423937] Device registration started. ClientSD: 86 Protocol Version: 16 ThreadID: 1112 GUID: 2119F89C
INFO[09:57:45.517189] Device registered. ID: 13, ClientSD: 86 Protocol Version: 16 ThreadID: 1112 GUID: 2119F89C ResultCode: 3
INFO[09:57:56.925980] Connection accepted: 192.168.1.1:22291 ClientSD: 96 Secure: 1
INFO[09:57:57.362391] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 96
INFO[09:57:57.478859] Device registration started. ClientSD: 96 Protocol Version: 16 ThreadID: 1113 GUID: 3216F9BF
INFO[09:57:57.552313] Device registered. ID: 39, ClientSD: 96 Protocol Version: 16 ThreadID: 1113 GUID: 3216F9BF ResultCode: 3
INFO[09:57:58.548135] Connection accepted: 192.168.1.1:30085 ClientSD: 99 Secure: 1
INFO[09:57:58.974124] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 99
INFO[09:57:59.084046] Device registration started. ClientSD: 99 Protocol Version: 16 ThreadID: 1114 GUID: E72E773B
INFO[09:57:59.126549] Device registered. ID: 24, ClientSD: 99 Protocol Version: 16 ThreadID: 1114 GUID: E72E773B ResultCode: 3
INFO[09:57:59.655194] Connection accepted: 192.168.1.1:22557 ClientSD: 102 Secure: 1
INFO[09:58:00.081203] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 102
INFO[09:58:00.192565] Device registration started. ClientSD: 102 Protocol Version: 16 ThreadID: 1115 GUID: D5774719
INFO[09:58:00.276010] Device registered. ID: 28, ClientSD: 102 Protocol Version: 16 ThreadID: 1115 GUID: D5774719 ResultCode: 3
INFO[09:58:01.295810] Connection accepted: 192.168.1.1:37374 ClientSD: 105 Secure: 1
INFO[09:58:01.748951] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 105
INFO[09:58:01.781642] Connection accepted: 192.168.1.1:34845 ClientSD: 108 Secure: 1
INFO[09:58:01.858278] Device registration started. ClientSD: 105 Protocol Version: 16 ThreadID: 1116 GUID: 3BF07ABC
INFO[09:58:01.933010] Device registered. ID: 22, ClientSD: 105 Protocol Version: 16 ThreadID: 1116 GUID: 3BF07ABC ResultCode: 3
INFO[09:58:02.261392] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 108
INFO[09:58:02.278228] Connection accepted: 192.168.1.1:44546 ClientSD: 111 Secure: 1
INFO[09:58:02.371804] Device registration started. ClientSD: 108 Protocol Version: 16 ThreadID: 1117 GUID: DD958257
INFO[09:58:02.418280] Device registered. ID: 36, ClientSD: 108 Protocol Version: 16 ThreadID: 1117 GUID: DD958257 ResultCode: 3
INFO[09:58:02.774387] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 111
INFO[09:58:02.885459] Device registration started. ClientSD: 111 Protocol Version: 16 ThreadID: 1118 GUID: DA0999CE
INFO[09:58:03.044942] Device registered. ID: 35, ClientSD: 111 Protocol Version: 16 ThreadID: 1118 GUID: DA0999CE ResultCode: 3
INFO[09:58:04.959536] Connection accepted: 192.168.1.1:37057 ClientSD: 114 Secure: 1
INFO[09:58:05.378241] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 114
INFO[09:58:05.488782] Device registration started. ClientSD: 114 Protocol Version: 16 ThreadID: 1119 GUID: 6ED45465
INFO[09:58:05.519552] Device registered. ID: 3, ClientSD: 114 Protocol Version: 16 ThreadID: 1119 GUID: 6ED45465 ResultCode: 3
INFO[09:58:06.636456] Connection accepted: 192.168.1.1:3013 ClientSD: 117 Secure: 1
INFO[09:58:07.063927] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 117
INFO[09:58:07.177573] Device registration started. ClientSD: 117 Protocol Version: 16 ThreadID: 1120 GUID: D5EB4FE2
INFO[09:58:07.266140] Device registered. ID: 31, ClientSD: 117 Protocol Version: 16 ThreadID: 1120 GUID: D5EB4FE2 ResultCode: 3
INFO[09:58:07.344005] Connection accepted: 192.168.1.1:38882 ClientSD: 120 Secure: 1
INFO[09:58:07.459474] Connection accepted: 192.168.1.1:2922 ClientSD: 123 Secure: 1
INFO[09:58:07.776138] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 120
INFO[09:58:07.889235] Device registration started. ClientSD: 120 Protocol Version: 16 ThreadID: 1121 GUID: 8D68D593
INFO[09:58:07.963395] Device registered. ID: 37, ClientSD: 120 Protocol Version: 16 ThreadID: 1121 GUID: 8D68D593 ResultCode: 3
INFO[09:58:08.022142] Connection accepted: 192.168.1.1:21975 ClientSD: 126 Secure: 1
INFO[09:58:08.470661] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 126
INFO[09:58:08.592181] Device registration started. ClientSD: 126 Protocol Version: 16 ThreadID: 1123 GUID: 9A75AB79
INFO[09:58:08.604079] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 123
INFO[09:58:08.712220] Device registered. ID: 20, ClientSD: 126 Protocol Version: 16 ThreadID: 1123 GUID: 9A75AB79 ResultCode: 3
INFO[09:58:08.733517] Device registration started. ClientSD: 123 Protocol Version: 16 ThreadID: 1122 GUID: 466D1E1D
INFO[09:58:08.824175] Device registered. ID: 26, ClientSD: 123 Protocol Version: 16 ThreadID: 1122 GUID: 466D1E1D ResultCode: 3
INFO[09:58:12.312503] Connection accepted: 192.168.1.1:1420 ClientSD: 129 Secure: 1
INFO[09:58:12.744998] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 129
INFO[09:58:12.856734] Device registration started. ClientSD: 129 Protocol Version: 16 ThreadID: 1125 GUID: 711ACCD1
INFO[09:58:12.951556] Device registered. ID: 25, ClientSD: 129 Protocol Version: 16 ThreadID: 1125 GUID: 711ACCD1 ResultCode: 3
INFO[09:58:17.704882] Connection accepted: 192.168.1.1:19818 ClientSD: 131 Secure: 1
INFO[09:58:18.127962] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 131
INFO[09:58:18.237540] Device registration started. ClientSD: 131 Protocol Version: 16 ThreadID: 1128 GUID: 46E99A18
INFO[09:58:18.311503] Device registered. ID: 12, ClientSD: 131 Protocol Version: 16 ThreadID: 1128 GUID: 46E99A18 ResultCode: 3
INFO[09:58:18.429337] Connection accepted: 192.168.1.1:20613 ClientSD: 135 Secure: 1
INFO[09:58:18.892745] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 135
INFO[09:58:19.014477] Device registration started. ClientSD: 135 Protocol Version: 12 ThreadID: 1129 GUID: 17FD8496
INFO[09:58:19.055603] Device registered. ID: 14, ClientSD: 135 Protocol Version: 12 ThreadID: 1129 GUID: 17FD8496 ResultCode: 3
INFO[09:58:21.344337] Connection accepted: 192.168.1.1:47356 ClientSD: 138 Secure: 1
INFO[09:58:21.517734] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 138
INFO[09:58:25.197614] Connection accepted: 192.168.1.1:15107 ClientSD: 140 Secure: 1
INFO[09:58:25.645988] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 140
INFO[09:58:25.751809] Device registration started. ClientSD: 140 Protocol Version: 16 ThreadID: 1132 GUID: 30ED4261
INFO[09:58:25.838954] Device registered. ID: 38, ClientSD: 140 Protocol Version: 16 ThreadID: 1132 GUID: 30ED4261 ResultCode: 3
INFO[09:58:26.977935] Connection accepted: 192.168.1.1:35004 ClientSD: 139 Secure: 1
INFO[09:58:27.416159] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 139
INFO[09:58:27.530731] Device registration started. ClientSD: 139 Protocol Version: 16 ThreadID: 1133 GUID: 889BBD4F
INFO[09:58:27.676527] Device registered. ID: 30, ClientSD: 139 Protocol Version: 16 ThreadID: 1133 GUID: 889BBD4F ResultCode: 3
INFO[09:58:28.794296] Connection accepted: 192.168.1.1:33656 ClientSD: 144 Secure: 1
INFO[09:58:29.214040] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 144
INFO[09:58:29.335198] Device registration started. ClientSD: 144 Protocol Version: 16 ThreadID: 1135 GUID: 418AF853
INFO[09:58:29.411759] Device registered. ID: 41, ClientSD: 144 Protocol Version: 16 ThreadID: 1135 GUID: 418AF853 ResultCode: 3
ERR[09:58:29.492677] Could not get any token for any remote gateway from AD server.
INFO[09:58:29.879519] Connection accepted: 192.168.1.1:15041 ClientSD: 146 Secure: 1
INFO[09:58:30.301495] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 146
INFO[09:58:30.410328] Device registration started. ClientSD: 146 Protocol Version: 16 ThreadID: 1137 GUID: CE4B51E7
INFO[09:58:30.490544] Device registered. ID: 21, ClientSD: 146 Protocol Version: 16 ThreadID: 1137 GUID: CE4B51E7 ResultCode: 3
INFO[09:58:32.682036] Connection accepted: 192.168.1.1:45278 ClientSD: 151 Secure: 1
INFO[09:58:32.796883] Cipher: TLS_AES_256_GCM_SHA384, SSL Version: TLSv1.3, ClientSD: 151
INFO[09:58:32.802555] Connection accepted: 192.168.1.1:40662 ClientSD: 95 Secure: 0
INFO[09:58:33.198851] Connection accepted: 192.168.1.1:25367 ClientSD: 153 Secure: 1
INFO[09:58:33.649936] Cipher: AES128-SHA, SSL Version: TLSv1.1, ClientSD: 153
INFO[09:58:34.269940] Device registration started. ClientSD: 153 Protocol Version: 16 ThreadID: 1148 GUID: ED15ADB1
INFO[09:58:34.382646] Device registered. ID: 23, ClientSD: 153 Protocol Version: 16 ThreadID: 1148 GUID: ED15ADB1 ResultCode: 3
■Rpi4(m.2) Supla Cloud, Scripts ■Rpi3(sd) SD: 6x MI ATC, 1x W.S.
ROLETY_V3 x12 ■SWITCH_DUAL x4 ■GATE_MODULE_V3 x1 ■SOCKET_SSR x1 ■SMOKE_MODULE x1
SONOFF_TOUCH x4 ■YUNSCHAN x1 ■STAITCASE_DIMMER x1 ■MEW-01 x2 ■mROW-02 x1 ■LEW-01 x1
POW_R2 x2 ■SP111 x3
User avatar
klew
Posts: 8763
Joined: Thu Jun 27, 2019 12:16 pm
Location: Wrocław

Post

Sprawdzamy
Widzimy się na Supla Offline Party vol. 2 :!:
User avatar
pzygmunt
Posts: 18593
Joined: Tue Jan 19, 2016 9:26 am
Location: Paczków

Post

Bez dostępu do tych kontenerów nie jestem w stanie nic zweryfikować.
User avatar
kris.sg
Posts: 413
Joined: Mon Aug 07, 2017 8:08 pm
Location: Przezchlebie

Post

Nie ma problemu mogę dać dostęp anydesk wystarczy ?
■Rpi4(m.2) Supla Cloud, Scripts ■Rpi3(sd) SD: 6x MI ATC, 1x W.S.
ROLETY_V3 x12 ■SWITCH_DUAL x4 ■GATE_MODULE_V3 x1 ■SOCKET_SSR x1 ■SMOKE_MODULE x1
SONOFF_TOUCH x4 ■YUNSCHAN x1 ■STAITCASE_DIMMER x1 ■MEW-01 x2 ■mROW-02 x1 ■LEW-01 x1
POW_R2 x2 ■SP111 x3
User avatar
pzygmunt
Posts: 18593
Joined: Tue Jan 19, 2016 9:26 am
Location: Paczków

Post

teamviewer albo dostęp bezpośrednio przez ssh ?

Return to “Nowości”