zzrr wrote: Sun Jun 21, 2026 10:32 pm
W wersji 1.5.97 jest tak samo jak 96. Czyli reset sterownika zeruje CCT.
reset_sterownika_taśmaWYŁ.rar
reset_sterownika_taśmaWŁ.rar
Tutaj mamy prawdopodobną przyczynę:
Code: Select all
[2026-06-22 00:29:20.364] [348576][D][ZigbeeCore.cpp:517] zb_apsde_data_indication_handler(): APSDE INDICATION - Received APSDE-DATA indication, status: 0
[2026-06-22 00:29:20.364] [348577][D][ZigbeeCore.cpp:521] zb_apsde_data_indication_handler(): APSDE INDICATION - dst_endpoint: 1, src_endpoint: 1, dst_addr_mode: 255
[2026-06-22 00:29:20.367] APSDE INDICATION - src_addr_mode: 0, cluster_id: 0x0300, asdu_length: 8
[2026-06-22 00:29:20.367] APSDE INDICATION - dst_short_addr: 0x0000, src_short_addr: 0xf3ee
[2026-06-22 00:29:20.367] APSDE INDICATION - profile_id: 0x0104, security_status: 0, lqi: 137, rx_time: 0
[2026-06-22 00:29:20.367] [348579][I][ZigbeeHandlers.cpp:246] zb_raw_cmd_handler(): cluster id: 0x300, command id: 10
[2026-06-22 00:29:20.367] [348579][I][ZigbeeHandlers.cpp:249] zb_raw_cmd_handler(): src endpoint (0x1, dst endpoint 0x1
[2026-06-22 00:29:20.367] [348580][I][ZigbeeHandlers.cpp:253] zb_raw_cmd_handler(): is common comand 1, disable_default_response 1, is_manuf_specific 0
[2026-06-22 00:29:20.371] [348581][I][ZigbeeHandlers.cpp:257] zb_raw_cmd_handler(): manuf_specific 0x0
[2026-06-22 00:29:20.371] [348581][I][ZigbeeHandlers.cpp:261] zb_raw_cmd_handler(): RAW bufid: 7 size: 5
[2026-06-22 00:29:20.371] [348582][I][ZigbeeHandlers.cpp:264] zb_raw_cmd_handler(): 0x07
[2026-06-22 00:29:20.371] [348582][I][ZigbeeHandlers.cpp:264] zb_raw_cmd_handler(): 0x00
[2026-06-22 00:29:20.371] [348582][I][ZigbeeHandlers.cpp:264] zb_raw_cmd_handler(): 0x21
[2026-06-22 00:29:20.371] [348583][I][ZigbeeHandlers.cpp:264] zb_raw_cmd_handler(): 0x00
[2026-06-22 00:29:20.371] [348583][I][ZigbeeHandlers.cpp:264] zb_raw_cmd_handler(): 0x00
[2026-06-22 00:29:20.376] [348584][I][ZigbeeHandlers.cpp:274] zb_raw_cmd_handler(): ZigbeeHandlers rawCMD 0xf3ee, 0xf3ee, 0x0, 0x0
[2026-06-22 00:29:20.376] [348584][I][z2s_devices_table.cpp:7356] Z2S_onUpdateDeviceLastRssi(): short addr 0xF3EE, rssi -53
[2026-06-22 00:29:20.376] [348585][I][z2s_devices_table.cpp:6667] Z2S_onCustomCmdReceive(): , endpoint 0x1, cluster 0x300, cmd id 0xa
[2026-06-22 00:29:20.376] [348585][I][z2s_devices_table.cpp:286] Z2S_findChannelNumberSlot(): sub id -1
[2026-06-22 00:29:20.376] [348586][I][z2s_devices_table.cpp:6681] Z2S_onCustomCmdReceive(): z2s_channels_table[channel_number_slot].Supla_channel 0x0
[2026-06-22 00:29:20.376] [348586][I][ZigbeeHandlers.cpp:301] zb_raw_cmd_handler(): -----------------raw command not processed------------------
[2026-06-22 00:29:20.376] [348587][I][ZigbeeHandlers.cpp:89] zb_action_handler(): Receive Zigbee action(0x2000) callback
[2026-06-22 00:29:20.376] [348588][V][ZigbeeHandlers.cpp:344] zb_attribute_reporting_handler(): Received report from address(0xf3ee) src endpoint(1) to dst endpoint(1) cluster(0x300)
[2026-06-22 00:29:20.380] [348589][I][ZigbeeGateway.cpp:1742] zbAttributeReporting(): short address 0xF3EE
[2026-06-22 00:29:20.380] [348589][I][ZigbeeGateway.cpp:1421] zbProcessAttributeReporting(): color control cluster color temperature 0x0
[2026-06-22 00:29:20.380] [348590][I][z2s_devices_table.cpp:6302] Z2S_onColorTemperatureReceive(): 0xF3EE, endpoint 0x01, cluster 0x0300, color temperature 0x0000
Twój sterownik po restarcie zwraca zerową wartość
color temperature, co jest zachowaniem nieprawidłowym, zważywszy m.in. na to, że prawidłowy zakres CT w jego przypadku to [153...500]. Mój
GLEDOPTO zwraca po restarcie zapamiętaną wartość
CT, niezależnie od tego, czy przed restartem był wyłączony czy włączony.
Wersja
1.5.98-22/06/26 próbuje temu zaradzić w następujący sposób - jeżeli otrzyma zerową wartość
CT ze sterownika to wysyła mu ostatnią zapamiętaną przez bramkę wartość .