Error in admin when searching and username does not exist

Hi,
if your User model doesn't have "username" field, then search performed in Admin interface throw error.
Exception Type:	FieldError
Exception Value:   Related Field got invalid lookup: username

I made an assumption that the recipient will be django's user model or an extension of it. It is clearly a bad idea.
I'll remove the recipient field as a fix as soon as possible.
Thanks for reporting.

@truhlik i've update the pypi package to reflect this change. You should update your installed package to apply this fix.

Thx, it fine now.


Handle codeblocks (gfm?)

For one more time I got to conclusion that I <3 this. But it would be more awesome if it can handle code blocks in the leftside panel. Or is there some option to do this?

It should do that already, but just the button is not in the demo. MediumEditor has a button for that. I guess it's pre.

Hey! Unfortunately, formatting with pre does not work when converting to Markdown.
Can you look into that?
Thanks


[BUG] Can't start a new session before chip-all-clusters-app stop resending CASE_Sigma2

Reproduction steps

start chip-all-clusters-app and use chip-tool to pair
./chip-tool onoff toggle 1 1 and kill chip-tool after it send CASE_Sigma1.(Now chip-all-clusters-app is resending CASE_Sigma2)
./chip-tool onoff toggle 1 1 can't start a session before chip-all-clusters-app stop resending CASE_Sigma2

Bug prevalence
always
GitHub hash of the SDK that was being used
SDK 1.0
Platform
core
Platform Version(s)
20.04.1-Ubuntu
Anything else?

chip-tool
$ ./chip-tool-v<IP_ADDRESS> onoff toggle 1 1
[1671507864.915959][20017:20017] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1671507864.916235][20017:20017] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1671507864.916265][20017:20017] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1671507864.916282][20017:20017] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1671507864.916383][20017:20017] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-gBiXoP)
[1671507864.916569][20017:20017] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1671507864.916587][20017:20017] CHIP:DL: NVS set: chip-counters/reboot-count = 11 (0xB)
[1671507864.916809][20017:20017] CHIP:DL: Got Ethernet interface: enp0s3
[1671507864.916902][20017:20017] CHIP:DL: Found the primary Ethernet interface:enp0s3
[1671507864.917085][20017:20017] CHIP:DL: Failed to get WiFi interface
[1671507864.917093][20017:20017] CHIP:DL: Failed to reset WiFi statistic counts
[1671507864.917112][20017:20017] CHIP:IN: UDP::Init bind&listen port=0
[1671507864.917128][20017:20017] CHIP:IN: UDP::Init bound to port=42335
[1671507864.917131][20017:20017] CHIP:IN: UDP::Init bind&listen port=0
[1671507864.917141][20017:20017] CHIP:IN: UDP::Init bound to port=42712
[1671507864.917146][20017:20017] CHIP:IN: BLEBase::Init - setting/overriding transport
[1671507864.917148][20017:20017] CHIP:IN: TransportMgr initialized
[1671507864.917155][20017:20017] CHIP:FP: Initializing FabricTable from persistent storage
[1671507864.917186][20017:20017] CHIP:TS: Last Known Good Time: 2022-12-20T11:21:34
[1671507864.917309][20017:20017] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xFFA5FB03F2528B88, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1671507864.917778][20017:20017] CHIP:ZCL: Using ZAP configuration...
[1671507864.918118][20017:20017] CHIP:DL: MDNS failed to join multicast group on enp0s8 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
[1671507864.918287][20017:20017] CHIP:DL: MDNS failed to join multicast group on enp0s9 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
[1671507864.918594][20017:20017] CHIP:CTL: System State Initialized...
[1671507864.918613][20017:20017] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507864.918624][20017:20017] CHIP:CTL: Setting attestation nonce to random value
[1671507864.918630][20017:20017] CHIP:CTL: Setting CSR nonce to random value
[1671507864.918641][20017:20017] CHIP:IN: UDP::Init bind&listen port=5550
[1671507864.918650][20017:20017] CHIP:IN: UDP::Init bound to port=5550
[1671507864.918653][20017:20017] CHIP:IN: UDP::Init bind&listen port=5550
[1671507864.918680][20017:20017] CHIP:IN: UDP::Init bound to port=5550
[1671507864.918682][20017:20017] CHIP:IN: TransportMgr initialized
[1671507864.918861][20017:20019] CHIP:DL: CHIP task running
[1671507864.918984][20017:20019] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507864.919005][20017:20019] CHIP:CTL: Setting attestation nonce to random value
[1671507864.919021][20017:20019] CHIP:CTL: Setting CSR nonce to random value
[1671507864.919798][20017:20019] CHIP:CTL: Generating NOC
[1671507864.919995][20017:20019] CHIP:FP: Validating NOC chain
[1671507864.920411][20017:20019] CHIP:FP: NOC chain validation successful
[1671507864.920492][20017:20019] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1671507864.920534][20017:20019] CHIP:TS: Last Known Good Time: 2022-12-20T11:21:34
[1671507864.920540][20017:20019] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1671507864.920546][20017:20019] CHIP:TS: Retaining current Last Known Good Time
[1671507864.921053][20017:20019] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1671507864.921592][20017:20019] CHIP:TS: Committing Last Known Good Time to storage: 2022-12-20T11:21:34
[1671507864.921992][20017:20019] CHIP:CTL: Joined the fabric at index 1. Fabric ID is 0x0000000000000001 (Compressed Fabric ID: FFA5FB03F2528B88)
[1671507864.922032][20017:20019] CHIP:IN: UDP::Init bind&listen port=5550
[1671507864.922048][20017:20019] CHIP:IN: UDP::Init bound to port=5550
[1671507864.922051][20017:20019] CHIP:IN: UDP::Init bind&listen port=5550
[1671507864.922060][20017:20019] CHIP:IN: UDP::Init bound to port=5550
[1671507864.922062][20017:20019] CHIP:IN: TransportMgr initialized
[1671507864.925147][20017:20019] CHIP:TOO: Sending command to node 0x1
[1671507864.925528][20017:20019] CHIP:CSM: FindOrEstablishSession: PeerId = [1:0000000000000001]
[1671507864.925561][20017:20019] CHIP:CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found
[1671507864.925718][20017:20019] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 1 --> 2
[1671507864.926092][20017:20019] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp0s8:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507864.926138][20017:20019] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp0s9:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507864.926206][20017:20019] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507864.926230][20017:20019] CHIP:DIS: mDNS broadcast had only partial success: 5 successes and 3 failures.
[1671507864.926937][20017:20019] CHIP:DIS: Lookup clearing interface for non LL address
[1671507864.927011][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: new best score: 6
[1671507864.927184][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507864.927470][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507864.927650][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507864.927765][20017:20019] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507864.927779][20017:20019] CHIP:DIS: Checking node lookup status after 2 ms
[1671507864.927787][20017:20019] CHIP:DIS: Keeping DNSSD lookup active
[1671507864.928049][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507864.928225][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507864.928558][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507864.928973][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507864.939902][20017:20019] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507864.939951][20017:20019] CHIP:DIS: Checking node lookup status after 14 ms
[1671507864.939959][20017:20019] CHIP:DIS: Keeping DNSSD lookup active
[1671507864.940240][20017:20019] CHIP:DIS: UDP:<IP_ADDRESS>%docker0:5540: score has not improved: 2
[1671507864.940260][20017:20019] CHIP:DIS: Checking node lookup status after 14 ms
[1671507864.940264][20017:20019] CHIP:DIS: Keeping DNSSD lookup active
[1671507864.940568][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507864.940776][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507864.941059][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507864.941382][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507864.941624][20017:20019] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507864.941637][20017:20019] CHIP:DIS: Checking node lookup status after 16 ms
[1671507864.941640][20017:20019] CHIP:DIS: Keeping DNSSD lookup active
[1671507864.941772][20017:20019] CHIP:DIS: UDP:<IP_ADDRESS>%docker0:5540: score has not improved: 2
[1671507864.941786][20017:20019] CHIP:DIS: Checking node lookup status after 16 ms
[1671507864.941789][20017:20019] CHIP:DIS: Keeping DNSSD lookup active
[1671507864.942124][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507864.942356][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507864.942552][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507864.942726][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507864.942797][20017:20019] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507864.942810][20017:20019] CHIP:DIS: Checking node lookup status after 17 ms
[1671507864.942817][20017:20019] CHIP:DIS: Keeping DNSSD lookup active
[1671507864.943043][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507864.943190][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507864.943381][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507864.943523][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507864.943602][20017:20019] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507864.943612][20017:20019] CHIP:DIS: Checking node lookup status after 18 ms
[1671507864.943619][20017:20019] CHIP:DIS: Keeping DNSSD lookup active
[1671507864.943787][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507864.943962][20017:20019] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507864.944079][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507864.944236][20017:20019] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507864.944307][20017:20019] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507864.944319][20017:20019] CHIP:DIS: Checking node lookup status after 18 ms
[1671507864.944325][20017:20019] CHIP:DIS: Keeping DNSSD lookup active
[1671507865.139768][20017:20019] CHIP:DIS: Checking node lookup status after 214 ms
[1671507865.139863][20017:20019] CHIP:DIS: OperationalSessionSetup[1:0000000000000001]: Updating device address to UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5]:5540 while in state 2
[1671507865.139896][20017:20019] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 2 --> 3
[1671507865.139992][20017:20019] CHIP:IN: SecureSession[0x7fde700219e0]: Allocated Type:2 LSID:1475
[1671507865.140030][20017:20019] CHIP:SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000001
[1671507865.140511][20017:20019] CHIP:EM: <<< [E:15715i M:136957517] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
[1671507865.140599][20017:20019] CHIP:IN: (U) Sending msg 136957517 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5]:5540'
[1671507865.140702][20017:20019] CHIP:SC: Sent Sigma1 msg
[1671507865.140724][20017:20019] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 3 --> 4
^C

# frey @ frey-ubuntu1 in ~/workspace/chip-apps [11:44:25] C:130
$ ./chip-tool-v<IP_ADDRESS> onoff toggle 1 1
[1671507867.251613][20025:20025] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1671507867.251761][20025:20025] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1671507867.251794][20025:20025] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1671507867.251846][20025:20025] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1671507867.251942][20025:20025] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-so6HFo)
[1671507867.252134][20025:20025] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1671507867.252151][20025:20025] CHIP:DL: NVS set: chip-counters/reboot-count = 12 (0xC)
[1671507867.252409][20025:20025] CHIP:DL: Got Ethernet interface: enp0s3
[1671507867.252535][20025:20025] CHIP:DL: Found the primary Ethernet interface:enp0s3
[1671507867.252769][20025:20025] CHIP:DL: Failed to get WiFi interface
[1671507867.252782][20025:20025] CHIP:DL: Failed to reset WiFi statistic counts
[1671507867.252829][20025:20025] CHIP:IN: UDP::Init bind&listen port=0
[1671507867.252858][20025:20025] CHIP:IN: UDP::Init bound to port=57450
[1671507867.252868][20025:20025] CHIP:IN: UDP::Init bind&listen port=0
[1671507867.252886][20025:20025] CHIP:IN: UDP::Init bound to port=44811
[1671507867.252895][20025:20025] CHIP:IN: BLEBase::Init - setting/overriding transport
[1671507867.252904][20025:20025] CHIP:IN: TransportMgr initialized
[1671507867.252919][20025:20025] CHIP:FP: Initializing FabricTable from persistent storage
[1671507867.252967][20025:20025] CHIP:TS: Last Known Good Time: 2022-12-20T11:21:34
[1671507867.253130][20025:20025] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xFFA5FB03F2528B88, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1671507867.253818][20025:20025] CHIP:ZCL: Using ZAP configuration...
[1671507867.254300][20025:20025] CHIP:DL: MDNS failed to join multicast group on enp0s8 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
[1671507867.254505][20025:20025] CHIP:DL: MDNS failed to join multicast group on enp0s9 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
[1671507867.254705][20025:20025] CHIP:CTL: System State Initialized...
[1671507867.254737][20025:20025] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507867.254759][20025:20025] CHIP:CTL: Setting attestation nonce to random value
[1671507867.254771][20025:20025] CHIP:CTL: Setting CSR nonce to random value
[1671507867.254790][20025:20025] CHIP:IN: UDP::Init bind&listen port=5550
[1671507867.254806][20025:20025] CHIP:IN: UDP::Init bound to port=5550
[1671507867.254814][20025:20025] CHIP:IN: UDP::Init bind&listen port=5550
[1671507867.254834][20025:20025] CHIP:IN: UDP::Init bound to port=5550
[1671507867.254841][20025:20025] CHIP:IN: TransportMgr initialized
[1671507867.255034][20025:20027] CHIP:DL: CHIP task running
[1671507867.255307][20025:20027] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507867.255337][20025:20027] CHIP:CTL: Setting attestation nonce to random value
[1671507867.255361][20025:20027] CHIP:CTL: Setting CSR nonce to random value
[1671507867.256185][20025:20027] CHIP:CTL: Generating NOC
[1671507867.256460][20025:20027] CHIP:FP: Validating NOC chain
[1671507867.257147][20025:20027] CHIP:FP: NOC chain validation successful
[1671507867.257223][20025:20027] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1671507867.257270][20025:20027] CHIP:TS: Last Known Good Time: 2022-12-20T11:21:34
[1671507867.257280][20025:20027] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1671507867.257283][20025:20027] CHIP:TS: Retaining current Last Known Good Time
[1671507867.258153][20025:20027] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1671507867.258823][20025:20027] CHIP:TS: Committing Last Known Good Time to storage: 2022-12-20T11:21:34
[1671507867.260045][20025:20027] CHIP:CTL: Joined the fabric at index 1. Fabric ID is 0x0000000000000001 (Compressed Fabric ID: FFA5FB03F2528B88)
[1671507867.260138][20025:20027] CHIP:IN: UDP::Init bind&listen port=5550
[1671507867.260191][20025:20027] CHIP:IN: UDP::Init bound to port=5550
[1671507867.260195][20025:20027] CHIP:IN: UDP::Init bind&listen port=5550
[1671507867.260216][20025:20027] CHIP:IN: UDP::Init bound to port=5550
[1671507867.260221][20025:20027] CHIP:IN: TransportMgr initialized
[1671507867.262854][20025:20027] CHIP:TOO: Sending command to node 0x1
[1671507867.263000][20025:20027] CHIP:CSM: FindOrEstablishSession: PeerId = [1:0000000000000001]
[1671507867.263009][20025:20027] CHIP:CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found
[1671507867.263023][20025:20027] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 1 --> 2
[1671507867.263270][20025:20027] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp0s8:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507867.263298][20025:20027] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp0s9:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507867.263329][20025:20027] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507867.263335][20025:20027] CHIP:DIS: mDNS broadcast had only partial success: 5 successes and 3 failures.
[1671507867.264152][20025:20027] CHIP:DIS: Lookup clearing interface for non LL address
[1671507867.264180][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: new best score: 6
[1671507867.264349][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507867.264485][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507867.264705][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507867.264831][20025:20027] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507867.264840][20025:20027] CHIP:DIS: Checking node lookup status after 2 ms
[1671507867.264843][20025:20027] CHIP:DIS: Keeping DNSSD lookup active
[1671507867.265065][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507867.265226][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507867.265373][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507867.265537][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507867.265610][20025:20027] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507867.265618][20025:20027] CHIP:DIS: Checking node lookup status after 3 ms
[1671507867.265620][20025:20027] CHIP:DIS: Keeping DNSSD lookup active
[1671507867.265797][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507867.265978][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507867.266133][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507867.266271][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507867.266351][20025:20027] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507867.266360][20025:20027] CHIP:DIS: Checking node lookup status after 4 ms
[1671507867.266363][20025:20027] CHIP:DIS: Keeping DNSSD lookup active
[1671507867.266605][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507867.266796][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507867.266973][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507867.267168][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507867.267239][20025:20027] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507867.267306][20025:20027] CHIP:DIS: Checking node lookup status after 4 ms
[1671507867.267309][20025:20027] CHIP:DIS: Keeping DNSSD lookup active
[1671507867.267476][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507867.267606][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507867.267732][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507867.267859][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507867.267930][20025:20027] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507867.267936][20025:20027] CHIP:DIS: Checking node lookup status after 5 ms
[1671507867.267938][20025:20027] CHIP:DIS: Keeping DNSSD lookup active
[1671507867.268098][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507867.268226][20025:20027] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507867.268362][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507867.268519][20025:20027] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507867.268595][20025:20027] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507867.268598][20025:20027] CHIP:DIS: Checking node lookup status after 6 ms
[1671507867.268600][20025:20027] CHIP:DIS: Keeping DNSSD lookup active
[1671507867.268689][20025:20027] CHIP:DIS: UDP:<IP_ADDRESS>%docker0:5540: score has not improved: 2
[1671507867.268697][20025:20027] CHIP:DIS: Checking node lookup status after 6 ms
[1671507867.268699][20025:20027] CHIP:DIS: Keeping DNSSD lookup active
[1671507867.268801][20025:20027] CHIP:DIS: UDP:<IP_ADDRESS>%docker0:5540: score has not improved: 2
[1671507867.268809][20025:20027] CHIP:DIS: Checking node lookup status after 6 ms
[1671507867.268811][20025:20027] CHIP:DIS: Keeping DNSSD lookup active
[1671507867.467705][20025:20027] CHIP:DIS: Checking node lookup status after 205 ms
[1671507867.467767][20025:20027] CHIP:DIS: OperationalSessionSetup[1:0000000000000001]: Updating device address to UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5]:5540 while in state 2
[1671507867.467775][20025:20027] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 2 --> 3
[1671507867.467833][20025:20027] CHIP:IN: SecureSession[0x7f7a740219e0]: Allocated Type:2 LSID:27243
[1671507867.467849][20025:20027] CHIP:SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000001
[1671507867.468251][20025:20027] CHIP:EM: <<< [E:43419i M:253386776] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
[1671507867.468298][20025:20027] CHIP:IN: (U) Sending msg 253386776 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5]:5540'
[1671507867.468381][20025:20027] CHIP:SC: Sent Sigma1 msg
[1671507867.468394][20025:20027] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 3 --> 4
[1671507867.469094][20025:20027] CHIP:EM: >>> [E:43419i M:180559539 (Ack:253386776)] (U) Msg RX from 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1671507867.469129][20025:20027] CHIP:EM: Found matching exchange: 43419i, Delegate: 0x7f7a740241b8
[1671507867.469143][20025:20027] CHIP:EM: Rxd Ack; Removing MessageCounter:253386776 from Retrans Table on exchange 43419i
[1671507873.699159][20025:20027] CHIP:SC: CASESession timed out while waiting for a response from the peer. Current state was 1
[1671507873.699211][20025:20027] CHIP:IN: SecureSession[0x7f7a740219e0]: Released - Type:2 LSID:27243
[1671507873.699251][20025:20027] CHIP:-: ../examples/chip-tool/third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout at ../examples/chip-tool/commands/clusters/ModelCommand.cpp:62
[1671507873.699747][20025:20025] CHIP:CTL: Shutting down the commissioner
[1671507873.699798][20025:20025] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507873.699853][20025:20025] CHIP:CTL: Shutting down the controller
[1671507873.699865][20025:20025] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1671507873.699874][20025:20025] CHIP:FP: Forgetting fabric 0x1
[1671507873.699889][20025:20025] CHIP:TS: Pending Last Known Good Time: 2022-12-20T11:21:34
[1671507873.699975][20025:20025] CHIP:TS: Previous Last Known Good Time: 2022-12-20T11:21:34
[1671507873.699995][20025:20025] CHIP:TS: Reverted Last Known Good Time to previous value
[1671507873.700020][20025:20025] CHIP:CTL: Shutting down the commissioner
[1671507873.700028][20025:20025] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507873.700055][20025:20025] CHIP:CTL: Shutting down the controller
[1671507873.700071][20025:20025] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1671507873.700191][20025:20025] CHIP:DMG: IM WH moving to [Uninitialized]
[1671507873.700212][20025:20025] CHIP:DMG: IM WH moving to [Uninitialized]
[1671507873.700217][20025:20025] CHIP:DMG: IM WH moving to [Uninitialized]
[1671507873.700221][20025:20025] CHIP:DMG: IM WH moving to [Uninitialized]
[1671507873.700228][20025:20025] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1671507873.700254][20025:20025] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1671507873.700270][20025:20025] CHIP:FP: Shutting down FabricTable
[1671507873.700278][20025:20025] CHIP:TS: Pending Last Known Good Time: 2022-12-20T11:21:34
[1671507873.700320][20025:20025] CHIP:TS: Previous Last Known Good Time: 2022-12-20T11:21:34
[1671507873.700325][20025:20025] CHIP:TS: Reverted Last Known Good Time to previous value
[1671507873.700463][20025:20025] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-JSeMKm)
[1671507873.700771][20025:20025] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1671507873.700794][20025:20025] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1671507873.700851][20025:20025] CHIP:DL: Inet Layer shutdown
[1671507873.700859][20025:20025] CHIP:DL: BLE shutdown
[1671507873.700866][20025:20025] CHIP:DL: System Layer shutdown
[1671507873.701122][20025:20025] CHIP:TOO: Run command failure: ../examples/chip-tool/third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout

# frey @ frey-ubuntu1 in ~/workspace/chip-apps [11:44:33] C:1
$ ./chip-tool-v<IP_ADDRESS> onoff toggle 1 1
[1671507882.953771][20033:20033] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
[1671507882.954020][20033:20033] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
[1671507882.954057][20033:20033] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
[1671507882.954075][20033:20033] CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
[1671507882.954196][20033:20033] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-H5nXh2)
[1671507882.954481][20033:20033] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1671507882.954505][20033:20033] CHIP:DL: NVS set: chip-counters/reboot-count = 13 (0xD)
[1671507882.954821][20033:20033] CHIP:DL: Got Ethernet interface: enp0s3
[1671507882.954976][20033:20033] CHIP:DL: Found the primary Ethernet interface:enp0s3
[1671507882.955225][20033:20033] CHIP:DL: Failed to get WiFi interface
[1671507882.955236][20033:20033] CHIP:DL: Failed to reset WiFi statistic counts
[1671507882.955335][20033:20033] CHIP:IN: UDP::Init bind&listen port=0
[1671507882.955366][20033:20033] CHIP:IN: UDP::Init bound to port=42752
[1671507882.955373][20033:20033] CHIP:IN: UDP::Init bind&listen port=0
[1671507882.955414][20033:20033] CHIP:IN: UDP::Init bound to port=52405
[1671507882.955419][20033:20033] CHIP:IN: BLEBase::Init - setting/overriding transport
[1671507882.955422][20033:20033] CHIP:IN: TransportMgr initialized
[1671507882.955436][20033:20033] CHIP:FP: Initializing FabricTable from persistent storage
[1671507882.955482][20033:20033] CHIP:TS: Last Known Good Time: 2022-12-20T11:21:34
[1671507882.955616][20033:20033] CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xFFA5FB03F2528B88, FabricId 0x0000000000000001, NodeId 0x000000000001B669, VendorId 0xFFF1
[1671507882.956220][20033:20033] CHIP:ZCL: Using ZAP configuration...
[1671507882.956708][20033:20033] CHIP:DL: MDNS failed to join multicast group on enp0s8 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
[1671507882.956851][20033:20033] CHIP:DL: MDNS failed to join multicast group on enp0s9 for address type IPv4: ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
[1671507882.957001][20033:20033] CHIP:CTL: System State Initialized...
[1671507882.957020][20033:20033] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507882.957037][20033:20033] CHIP:CTL: Setting attestation nonce to random value
[1671507882.957133][20033:20033] CHIP:CTL: Setting CSR nonce to random value
[1671507882.957148][20033:20033] CHIP:IN: UDP::Init bind&listen port=5550
[1671507882.957162][20033:20033] CHIP:IN: UDP::Init bound to port=5550
[1671507882.957165][20033:20033] CHIP:IN: UDP::Init bind&listen port=5550
[1671507882.957176][20033:20033] CHIP:IN: UDP::Init bound to port=5550
[1671507882.957182][20033:20033] CHIP:IN: TransportMgr initialized
[1671507882.957334][20033:20035] CHIP:DL: CHIP task running
[1671507882.957578][20033:20035] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507882.957596][20033:20035] CHIP:CTL: Setting attestation nonce to random value
[1671507882.957612][20033:20035] CHIP:CTL: Setting CSR nonce to random value
[1671507882.958484][20033:20035] CHIP:CTL: Generating NOC
[1671507882.958809][20033:20035] CHIP:FP: Validating NOC chain
[1671507882.964589][20033:20035] CHIP:FP: NOC chain validation successful
[1671507882.964654][20033:20035] CHIP:FP: Updated fabric at index: 0x1, Node ID: 0x000000000001B669
[1671507882.964660][20033:20035] CHIP:TS: Last Known Good Time: 2022-12-20T11:21:34
[1671507882.964663][20033:20035] CHIP:TS: New proposed Last Known Good Time: 2021-01-01T00:00:00
[1671507882.964665][20033:20035] CHIP:TS: Retaining current Last Known Good Time
[1671507882.966159][20033:20035] CHIP:FP: Metadata for Fabric 0x1 persisted to storage.
[1671507882.966959][20033:20035] CHIP:TS: Committing Last Known Good Time to storage: 2022-12-20T11:21:34
[1671507882.967472][20033:20035] CHIP:CTL: Joined the fabric at index 1. Fabric ID is 0x0000000000000001 (Compressed Fabric ID: FFA5FB03F2528B88)
[1671507882.967581][20033:20035] CHIP:IN: UDP::Init bind&listen port=5550
[1671507882.967636][20033:20035] CHIP:IN: UDP::Init bound to port=5550
[1671507882.967670][20033:20035] CHIP:IN: UDP::Init bind&listen port=5550
[1671507882.967712][20033:20035] CHIP:IN: UDP::Init bound to port=5550
[1671507882.967745][20033:20035] CHIP:IN: TransportMgr initialized
[1671507882.970498][20033:20035] CHIP:TOO: Sending command to node 0x1
[1671507882.970726][20033:20035] CHIP:CSM: FindOrEstablishSession: PeerId = [1:0000000000000001]
[1671507882.970782][20033:20035] CHIP:CSM: FindOrEstablishSession: No existing OperationalSessionSetup instance found
[1671507882.970830][20033:20035] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 1 --> 2
[1671507882.971177][20033:20035] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp0s8:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507882.971451][20033:20035] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp0s9:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507882.971625][20033:20035] CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../examples/chip-tool/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
[1671507882.971693][20033:20035] CHIP:DIS: mDNS broadcast had only partial success: 5 successes and 3 failures.
[1671507882.972177][20033:20035] CHIP:DIS: Lookup clearing interface for non LL address
[1671507882.972252][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: new best score: 6
[1671507882.972410][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507882.972597][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507882.972794][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507882.972994][20033:20035] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507882.973032][20033:20035] CHIP:DIS: Checking node lookup status after 2 ms
[1671507882.973067][20033:20035] CHIP:DIS: Keeping DNSSD lookup active
[1671507882.973314][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507882.973478][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507882.973697][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507882.973854][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507882.973990][20033:20035] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507882.974023][20033:20035] CHIP:DIS: Checking node lookup status after 3 ms
[1671507882.974051][20033:20035] CHIP:DIS: Keeping DNSSD lookup active
[1671507882.974273][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507882.974461][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507882.974605][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507882.974751][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507882.974841][20033:20035] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507882.974894][20033:20035] CHIP:DIS: Checking node lookup status after 4 ms
[1671507882.974919][20033:20035] CHIP:DIS: Keeping DNSSD lookup active
[1671507882.975014][20033:20035] CHIP:DIS: UDP:<IP_ADDRESS>%docker0:5540: score has not improved: 2
[1671507882.975046][20033:20035] CHIP:DIS: Checking node lookup status after 4 ms
[1671507882.975071][20033:20035] CHIP:DIS: Keeping DNSSD lookup active
[1671507882.975226][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507882.975449][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507882.975678][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507882.975833][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507882.975931][20033:20035] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507882.975965][20033:20035] CHIP:DIS: Checking node lookup status after 5 ms
[1671507882.975996][20033:20035] CHIP:DIS: Keeping DNSSD lookup active
[1671507882.976140][20033:20035] CHIP:DIS: UDP:<IP_ADDRESS>%docker0:5540: score has not improved: 2
[1671507882.976173][20033:20035] CHIP:DIS: Checking node lookup status after 5 ms
[1671507882.976201][20033:20035] CHIP:DIS: Keeping DNSSD lookup active
[1671507882.976385][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507882.976524][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507882.976679][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507882.976811][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507882.976894][20033:20035] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507882.976923][20033:20035] CHIP:DIS: Checking node lookup status after 6 ms
[1671507882.976948][20033:20035] CHIP:DIS: Keeping DNSSD lookup active
[1671507882.977100][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:5540: score has not improved: 6
[1671507882.977236][20033:20035] CHIP:DIS: UDP:[fdd5:582c:1c95:40e7:9315:592f:3a88:84e0%enp0s3]:5540: score has not improved: 6
[1671507882.977368][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:db28:72f9:bc26:879f%enp0s3]:5540: score has not improved: 6
[1671507882.977500][20033:20035] CHIP:DIS: UDP:[fd64:e880:2053:8254:f378:f51f:5230:197f%enp0s3]:5540: score has not improved: 6
[1671507882.977583][20033:20035] CHIP:DIS: UDP:[fe80::cc14:a2a7:ca7c:b4c8%enp0s3]:5540: score has not improved: 3
[1671507882.977612][20033:20035] CHIP:DIS: Checking node lookup status after 7 ms
[1671507882.977637][20033:20035] CHIP:DIS: Keeping DNSSD lookup active
[1671507883.171766][20033:20035] CHIP:DIS: Checking node lookup status after 201 ms
[1671507883.171853][20033:20035] CHIP:DIS: OperationalSessionSetup[1:0000000000000001]: Updating device address to UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5]:5540 while in state 2
[1671507883.171880][20033:20035] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 2 --> 3
[1671507883.171994][20033:20035] CHIP:IN: SecureSession[0x7ff7440219e0]: Allocated Type:2 LSID:47190
[1671507883.172020][20033:20035] CHIP:SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x0000000000000001
[1671507883.172455][20033:20035] CHIP:EM: <<< [E:12506i M:115948483] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
[1671507883.172503][20033:20035] CHIP:IN: (U) Sending msg 115948483 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5]:5540'
[1671507883.172601][20033:20035] CHIP:SC: Sent Sigma1 msg
[1671507883.172616][20033:20035] CHIP:CTL: OperationalSessionSetup[1:0000000000000001]: State change 3 --> 4
[1671507883.173108][20033:20035] CHIP:EM: >>> [E:12506i M:180559540 (Ack:115948483)] (U) Msg RX from 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
[1671507883.173161][20033:20035] CHIP:EM: Found matching exchange: 12506i, Delegate: 0x7ff7440241b8
[1671507883.173171][20033:20035] CHIP:EM: Rxd Ack; Removing MessageCounter:115948483 from Retrans Table on exchange 12506i
[1671507889.464332][20033:20035] CHIP:SC: CASESession timed out while waiting for a response from the peer. Current state was 1
[1671507889.464373][20033:20035] CHIP:IN: SecureSession[0x7ff7440219e0]: Released - Type:2 LSID:47190
[1671507889.464477][20033:20035] CHIP:-: ../examples/chip-tool/third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout at ../examples/chip-tool/commands/clusters/ModelCommand.cpp:62
[1671507889.464710][20033:20033] CHIP:CTL: Shutting down the commissioner
[1671507889.464753][20033:20033] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507889.464811][20033:20033] CHIP:CTL: Shutting down the controller
[1671507889.464825][20033:20033] CHIP:IN: Expiring all sessions for fabric 0x1!!
[1671507889.464835][20033:20033] CHIP:FP: Forgetting fabric 0x1
[1671507889.464851][20033:20033] CHIP:TS: Pending Last Known Good Time: 2022-12-20T11:21:34
[1671507889.464962][20033:20033] CHIP:TS: Previous Last Known Good Time: 2022-12-20T11:21:34
[1671507889.464989][20033:20033] CHIP:TS: Reverted Last Known Good Time to previous value
[1671507889.465017][20033:20033] CHIP:CTL: Shutting down the commissioner
[1671507889.465033][20033:20033] CHIP:CTL: Stopping commissioning discovery over DNS-SD
[1671507889.465064][20033:20033] CHIP:CTL: Shutting down the controller
[1671507889.465079][20033:20033] CHIP:CTL: Shutting down the System State, this will teardown the CHIP Stack
[1671507889.465188][20033:20033] CHIP:DMG: IM WH moving to [Uninitialized]
[1671507889.465206][20033:20033] CHIP:DMG: IM WH moving to [Uninitialized]
[1671507889.465211][20033:20033] CHIP:DMG: IM WH moving to [Uninitialized]
[1671507889.465215][20033:20033] CHIP:DMG: IM WH moving to [Uninitialized]
[1671507889.465221][20033:20033] CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
[1671507889.465244][20033:20033] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1671507889.465260][20033:20033] CHIP:FP: Shutting down FabricTable
[1671507889.465268][20033:20033] CHIP:TS: Pending Last Known Good Time: 2022-12-20T11:21:34
[1671507889.465309][20033:20033] CHIP:TS: Previous Last Known Good Time: 2022-12-20T11:21:34
[1671507889.465328][20033:20033] CHIP:TS: Reverted Last Known Good Time to previous value
[1671507889.465456][20033:20033] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-5hJUl1)
[1671507889.465785][20033:20033] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1671507889.465828][20033:20033] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1671507889.465842][20033:20033] CHIP:DL: Inet Layer shutdown
[1671507889.465849][20033:20033] CHIP:DL: BLE shutdown
[1671507889.465856][20033:20033] CHIP:DL: System Layer shutdown
[1671507889.466080][20033:20033] CHIP:TOO: Run command failure: ../examples/chip-tool/third_party/connectedhomeip/src/protocols/secure_channel/CASESession.cpp:295: CHIP Error 0x00000032: Timeout

chip-all-clusters-app
$ ./chip-all-clusters-app-v<IP_ADDRESS>
CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_kvs
CHIP:DL: ChipLinuxStorage::Init: Attempt to re-initialize with KVS config file: /tmp/chip_kvs
CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_factory.ini
CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_config.ini
CHIP:DL: ChipLinuxStorage::Init: Using KVS config file: /tmp/chip_counters.ini
CHIP:DL: writing settings to file (/tmp/chip_counters.ini-ylyuBz)
CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
CHIP:DL: NVS set: chip-counters/reboot-count = 10 (0xA)
CHIP:DL: Got Ethernet interface: enp0s3
CHIP:DL: Found the primary Ethernet interface:enp0s3
CHIP:DL: Failed to get WiFi interface
CHIP:DL: Failed to reset WiFi statistic counts
CHIP:SPT: *** WARNING: Using temporary passcode 20202021 due to no neither --passcode or --spake2p-verifier-base64 given on command line. This is temporary and will disappear. Please update your scripts to explicitly configure onboarding credentials. ***
CHIP:SPT: *** WARNING: Using temporary test discriminator 3840 due to --discriminator not given on command line. This is temporary and will disappear. Please update your scripts to explicitly configure discriminator. ***
CHIP:SPT: PASE PBKDF iterations set to 1000
CHIP:SPT: LinuxCommissionableDataProvider didn't get a PASE salt, generating one.
CHIP:DL: Device Configuration:
CHIP:DL:   Serial Number: TEST_SN
CHIP:DL:   Vendor Id: 65521 (0xFFF1)
CHIP:DL:   Product Id: 32769 (0x8001)
CHIP:DL:   Hardware Version: 0
CHIP:DL:   Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
CHIP:DL:   Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
CHIP:DL:   Manufacturing Date: (not set)
CHIP:DL:   Device Type: 65535 (0xFFFF)
CHIP:-: ==== Onboarding payload for Standard Commissioning Flow ====
CHIP:SVR: SetupQRCode: [MT:-24J0AFN00KA0648G00]
CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code:
CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0AFN00KA0648G00
CHIP:SVR: Manual pairing code: [34970112332]
CHIP:SVR: Server initializing...
CHIP:FP: Initializing FabricTable from persistent storage
CHIP:TS: Last Known Good Time: 2022-12-20T11:12:58
CHIP:FP: Fabric index 0x1 was retrieved from storage. Compressed FabricId 0xFFA5FB03F2528B88, FabricId 0x0000000000000001, NodeId 0x0000000000000001, VendorId 0xFFF1
CHIP:DMG: AccessControl: initializing
CHIP:DMG: Examples::AccessControlDelegate::Init
CHIP:DMG: AccessControl: setting
CHIP:DMG: DefaultAclStorage: initializing
CHIP:DMG: AccessControl: validating f=1 p=a a=c s=1 t=0
CHIP:DMG:   validating subject 0x000000000001B669
CHIP:DMG: DefaultAclStorage: 1 entries loaded
CHIP:IN: UDP::Init bind&listen port=5540
CHIP:IN: UDP::Init bound to port=5540
CHIP:IN: UDP::Init bind&listen port=5540
CHIP:IN: UDP::Init bound to port=5540
CHIP:IN: TransportMgr initialized
CHIP:DL: writing settings to file (/tmp/chip_kvs-vVyibA)
CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
CHIP:DL: writing settings to file (/tmp/chip_kvs-MP5iUz)
CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
CHIP:DL: MDNS failed to join multicast group on enp0s8 for address type IPv4: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
CHIP:DL: MDNS failed to join multicast group on enp0s9 for address type IPv4: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
CHIP:DL: writing settings to file (/tmp/chip_kvs-tcTvxA)
CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
CHIP:ZCL: Using ZAP configuration...
CHIP:DMG: Failed to read stored attribute (0, 0x0000_0028, 0x0000_0005: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (0, 0x0000_0028, 0x0000_0010: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (0, 0x0000_002C, 0x0000_0000: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (0, 0x0000_002C, 0x0000_0001: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (0, 0x0000_002D, 0x0000_0000: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0006, 0x0000_4003: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0008, 0x0000_4000: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0050, 0x0000_0003: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0050, 0x0000_0004: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0050, 0x0000_0005: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0003: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0004: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0005: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0006: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0008: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0009: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_000E: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_000F: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0010: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0011: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0012: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0013: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: Failed to read stored attribute (1, 0x0000_0102, 0x0000_0017: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:DMG: AccessControlCluster: initializing
CHIP:ZCL: Initiating Admin Commissioning cluster.
CHIP:ZCL: Door Lock server initialized
CHIP:DMG: Endpoint 0, Cluster 0x0000_0030 update version to 3c98cd9e
CHIP:ZCL: GeneralDiagnostics: OnDeviceReboot
CHIP:DMG: Endpoint 0, Cluster 0x0000_0033 update version to ffbc1287
CHIP:EVL: LogEvent event number: 0x0000000000050000 priority: 2, endpoint id:  0x0 cluster id: 0x0000_0033 event id: 0x3 Sys timestamp: 0x000000000081B56D
CHIP:ZCL: Initialize PCC Plugin Server Cluster.
CHIP:DMG: Endpoint 0, Cluster 0x0000_0003 update version to 959a7da9
CHIP:DMG: Endpoint 0, Cluster 0x0000_0004 update version to 541fa06
CHIP:DMG: Endpoint 0, Cluster 0x0000_0004 update version to 541fa07
CHIP:DL: writing settings to file (/tmp/chip_kvs-AoyknB)
CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
CHIP:DMG: Endpoint 0, Cluster 0x0000_002B update version to b5c85a63
CHIP:DMG: Endpoint 1, Cluster 0x0000_0003 update version to 8411962f
CHIP:DMG: Endpoint 1, Cluster 0x0000_0004 update version to 7190ba70
CHIP:DMG: Endpoint 1, Cluster 0x0000_0004 update version to 7190ba71
CHIP:DMG: Endpoint 1, Cluster 0x0000_0005 update version to 6a682522
CHIP:ZCL: On/Off set value: 1 1
CHIP:ZCL: On/off already set to new value
CHIP:DL: writing settings to file (/tmp/chip_kvs-PKOnHA)
CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
CHIP:DMG: Endpoint 1, Cluster 0x0000_0008 update version to d68173fa
CHIP:ZCL: Door Lock cluster initialized at endpoint #1
CHIP:DMG: Endpoint 1, Cluster 0x0000_0101 update version to e9c387f8
CHIP:DMG: Endpoint 1, Cluster 0x0000_0101 update version to e9c387f9
CHIP:DMG: Endpoint 1, Cluster 0x0000_0101 update version to e9c387fa
CHIP:EVL: LogEvent event number: 0x0000000000050001 priority: 2, endpoint id:  0x1 cluster id: 0x0000_0101 event id: 0x1 Sys timestamp: 0x000000000081B56E
CHIP:DMG: Endpoint 1, Cluster 0x0000_0101 update version to e9c387fb
CHIP:ZCL: Initialized new lock door endpoint [id=1,users=10,credentials=10,weekDaySchedulesPerUser=10,yearDaySchedulesPerUser=10,numberOfCredentialsSupportedPerUser=5,holidaySchedules=0]
CHIP:DL: writing settings to file (/tmp/chip_kvs-XQDh0z)
CHIP:DL: renamed tmp file to file (/tmp/chip_kvs)
CHIP:DMG: Endpoint 1, Cluster 0x0000_0102 update version to 8c57d766
CHIP:ZCL: WC POST ATTRIBUTE=7
CHIP:ZCL: ConfigStatus 0x1B Operational=1 OnlineReserved=1
CHIP:ZCL: Lift(PA=1 Encoder=0 Reversed=0) Tilt(PA=1 Encoder=0)
CHIP:ZCL: Initialize PCC Server Cluster [EP:1]
CHIP:ZCL: Constant Pressure Supported
CHIP:ZCL: PCC Server: Constant Proportional Pressure Supported
CHIP:ZCL: PCC Server: Constant Flow Supported
CHIP:ZCL: PCC Server: Constant Temperature Supported
CHIP:ZCL: PCC Server: Constant Speed Supported
CHIP:DMG: Endpoint 1, Cluster 0x0000_0300 update version to 34bd9d66
CHIP:DMG: Endpoint 1, Cluster 0x0000_0300 update version to 34bd9d67
CHIP:DMG: Endpoint 1, Cluster 0x0000_0300 update version to 34bd9d68
CHIP:DMG: Endpoint 1, Cluster 0x0000_0406 update version to abfbce4c
CHIP:DMG: Endpoint 1, Cluster 0x0000_0406 update version to abfbce4d
CHIP:-: Setting LowPower default delegate to global manager
CHIP:DMG: Endpoint 2, Cluster 0x0000_0004 update version to 395f7aa0
CHIP:DMG: Endpoint 2, Cluster 0x0000_0004 update version to 395f7aa1
CHIP:DMG: Endpoint 2, Cluster 0x0000_0406 update version to 4e4366c0
CHIP:DMG: Endpoint 2, Cluster 0x0000_0406 update version to 4e4366c1
CHIP:SVR: Fabric already commissioned. Disabling BLE advertisement
CHIP:DIS: Updating services using commissioning mode 0
CHIP:DL: MDNS failed to join multicast group on enp0s8 for address type IPv4: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
CHIP:DL: MDNS failed to join multicast group on enp0s9 for address type IPv4: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:764: Inet Error 0x00000110: Address not found
CHIP:DIS: CHIP minimal mDNS started advertising.
CHIP:DL: Using wifi MAC for hostname
CHIP:DIS: Advertise operational node FFA5FB03F2528B88-0000000000000001
CHIP:DIS: Responding with _matter._tcp.local
CHIP:DIS: Responding with FFA5FB03F2528B88-0000000000000001._matter._tcp.local
CHIP:DIS: Responding with FFA5FB03F2528B88-0000000000000001._matter._tcp.local
CHIP:DIS: Responding with 080027D3DC1A0000.local
CHIP:DIS: Responding with 080027D3DC1A0000.local
CHIP:DIS: Responding with _IFFA5FB03F2528B88._sub._matter._tcp.local
CHIP:DIS: CHIP minimal mDNS configured as 'Operational device'; instance name: FFA5FB03F2528B88-0000000000000001.
CHIP:DIS: mDNS service published: _matter._tcp
CHIP:IN: CASE Server enabling CASE session setups
CHIP:IN: SecureSession[0x611000000f40]: Allocated Type:2 LSID:35451
CHIP:SC: Allocated SecureSession (0x611000000f40) - waiting for Sigma1 msg
CHIP:SVR: Joining Multicast groups
CHIP:ZCL: Emitting StartUp event
CHIP:EVL: LogEvent event number: 0x0000000000050002 priority: 2, endpoint id:  0x0 cluster id: 0x0000_0028 event id: 0x0 Sys timestamp: 0x000000000081B57E
CHIP:SVR: Server Listening...
CHIP:DL: Device Configuration:
CHIP:DL:   Serial Number: TEST_SN
CHIP:DL:   Vendor Id: 65521 (0xFFF1)
CHIP:DL:   Product Id: 32769 (0x8001)
CHIP:DL:   Hardware Version: 0
CHIP:DL:   Setup Pin Code (0 for UNKNOWN/ERROR): 20202021
CHIP:DL:   Setup Discriminator (0xFFFF for UNKNOWN/ERROR): 3840 (0xF00)
CHIP:DL:   Manufacturing Date: (not set)
CHIP:DL:   Device Type: 65535 (0xFFFF)
CHIP:SVR: SetupQRCode: [MT:-24J0AFN00KA0648G00]
CHIP:SVR: Copy/paste the below URL in a browser to see the QR Code:
CHIP:SVR: https://project-chip.github.io/connectedhomeip/qrcode.html?data=MT%3A-24J0AFN00KA0648G00
CHIP:SVR: Manual pairing code: [34970112332]
CHIP:DMG: Endpoint 0, Cluster 0x0000_001D update version to 25b1820b
CHIP:SVR: Cannot load binding table: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/platform/Linux/KeyValueStoreManagerImpl.cpp:53: CHIP Error 0x000000A0: Value not found in the persisted storage
CHIP:EM: >>> [E:15715r M:136957517] (U) Msg RX from 0:54578965ECBB7E1B [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
CHIP:EM: Handling via exchange: 15715r, Delegate: 0x55dc44841008
CHIP:IN: CASE Server received Sigma1 message. Starting handshake. EC 0x60c000001fc0
CHIP:IN: CASE Server disabling CASE session setups
CHIP:SC: Received Sigma1 msg
CHIP:SC: Peer assigned session key ID 1475
CHIP:SC: CASE matched destination ID: fabricIndex 1, NodeID 0x0000000000000001
CHIP:EM: <<< [E:15715r M:180559538 (Ack:136957517)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:31 (SecureChannel:CASE_Sigma2)
CHIP:IN: (U) Sending msg 180559538 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:42335'
CHIP:SC: Sent Sigma2 msg
CHIP:EM: Retransmitting MessageCounter:180559538 on exchange 15715r Send Cnt 1
CHIP:IN: (U) Sending msg 180559538 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:42335'
CHIP:EM: Retransmitting MessageCounter:180559538 on exchange 15715r Send Cnt 2
CHIP:IN: (U) Sending msg 180559538 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:42335'
CHIP:EM: Retransmitting MessageCounter:180559538 on exchange 15715r Send Cnt 3
CHIP:IN: (U) Sending msg 180559538 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:42335'
CHIP:EM: Retransmitting MessageCounter:180559538 on exchange 15715r Send Cnt 4
CHIP:IN: (U) Sending msg 180559538 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:42335'
CHIP:EM: >>> [E:43419r M:253386776] (U) Msg RX from 0:84051CBD0781A1BD [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
CHIP:EM: Generating StandaloneAck via exchange: 43419r
CHIP:EM: <<< [E:43419r M:180559539 (Ack:253386776)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
CHIP:IN: (U) Sending msg 180559539 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:57450'
CHIP:EM: Flushed pending ack for MessageCounter:253386776 on exchange 43419r
CHIP:EM: Failed to Send CHIP MessageCounter:180559538 on exchange 15715r sendCount: 4 max retries: 4
CHIP:EM: >>> [E:12506r M:115948483] (U) Msg RX from 0:C646F6C5E2EED4ED [0000] --- Type 0000:30 (SecureChannel:CASE_Sigma1)
CHIP:EM: Generating StandaloneAck via exchange: 12506r
CHIP:EM: <<< [E:12506r M:180559540 (Ack:115948483)] (U) Msg TX to 0:0000000000000000 [0000] --- Type 0000:10 (SecureChannel:StandaloneAck)
CHIP:IN: (U) Sending msg 180559540 to IP address 'UDP:[fdd5:582c:1c95:40e7:7166:c0f2:62e9:be5%enp0s3]:42752'
CHIP:EM: Flushed pending ack for MessageCounter:115948483 on exchange 12506r
CHIP:DIS: SRV record already actively processed.
CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp0s8:  ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
CHIP:DIS: Warning: Attempt to mDNS broadcast failed on enp0s9:  ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
CHIP:DIS: Warning: Attempt to mDNS broadcast failed on docker0:  ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/inet/UDPEndPointImplSockets.cpp:411: OS Error 0x02000065: Network is unreachable
CHIP:DIS: mDNS broadcast had only partial success: 5 successes and 3 failures.
CHIP:DIS: SRV record already actively processed.
^CCHIP:DL: Caught signal 2
CHIP:DL: Select failed: ../../examples/all-clusters-app/linux/third_party/connectedhomeip/src/system/SystemLayerImplSelect.cpp:493: OS Error 0x02000004: Interrupted system call
CHIP:ZCL: Emitting ShutDown event
CHIP:EVL: LogEvent event number: 0x0000000000050003 priority: 2, endpoint id:  0x0 cluster id: 0x0000_0028 event id: 0x1 Sys timestamp: 0x0000000000825E73
CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
CHIP:IN: SecureSession[0x611000000f40]: Released - Type:2 LSID:35451
CHIP:DMG: IM WH moving to [Uninitialized]
CHIP:DMG: IM WH moving to [Uninitialized]
CHIP:DMG: IM WH moving to [Uninitialized]
CHIP:DMG: IM WH moving to [Uninitialized]
CHIP:DMG: All ReadHandler-s are clean, clear GlobalDirtySet
CHIP:DMG: AccessControl: finishing
CHIP:DMG: Examples::AccessControlDelegate::Finish
CHIP:DL: writing settings to file (/tmp/chip_counters.ini-2Ga8Py)
CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
CHIP:DL: Inet Layer shutdown
CHIP:DL: System Layer shutdown

@FreyZhang007 In the future, please attach logs as files instead of just pasting them in?
In any case, the SDK currently supports one incoming CASE handshake at a time (and constraint devices likely can't handle more than that in practice).  Given that, what behavior did you expect here?

@bzbarsky-apple Thanks, I see. This is not a bug.
But, It waits 30 seconds(1671597307-1671597257) from Sent Sigma2 msg to CASE Server enabling CASE session setups. No new CASE can be established during this time. This time is a bit too long.
Can I reduce this waiting time?
[1671597257.514878][142643:142643] CHIP:SC: Sent Sigma2 msg
[1671597257.865415][142643:142643] CHIP:EM: Retransmitting MessageCounter:133262898 on exchange 51440r Send Cnt 1
[1671597257.865579][142643:142643] CHIP:IN: (U) Sending msg 133262898 to IP address 'UDP:[fdd5:582c:1c95:40e7:6949:dba:31f6:1fb8%enp0s3]:48712'
[1671597258.245189][142643:142643] CHIP:EM: Retransmitting MessageCounter:133262898 on exchange 51440r Send Cnt 2
...
[1671597307.536927][142643:142643] CHIP:IN: CASE Server enabling CASE session setups

all-cluster.log

The wait time is controlled by https://github.com/project-chip/connectedhomeip/blob/e1017305e3b0f51048ab7362c52dc6b851789f38/src/protocols/secure_channel/CASESession.cpp#L127
You could reduce it, but of course that can cause problems if the device processing Sigma2 is a bit slow and the crypto takes a while...

Thanks, It is useful for me.


Add filtering for identifiers on items

We need this for the requesting API:

items will filter by the canonical ID
items.identifiers will filter by the source identifiers

This is consistent with our existing approach to identifiers. See this conversation in Slack for more discussion: https://wellcome.slack.com/archives/C016NQB58N4/p1649406089573399

I need to document this before I close the ticket.

Done, and new documentation published.


add markitup definition file

markitup/markitup.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/markitup
http://bower.io/search/?q=markitup
others?

[X] has a test file? (markitup/markitup-tests.ts or others)
[ ] pass the Travis-CI test?

thanks mate!


Device Request - Human Presence detector Device Model: TS0225

Device Name: Human Presence detector
Device Model: TS0225
Device Description: Human Presence detector
Link to device image: https://nl.aliexpress.com/item/1005006038128151.html?spm=a2g0o.order_list.order_list_main.10.6bbf79d2LwX1s5&gatewayAdapt=glo2nld
Device Interview:
"ids": {
"modelId": "TS0225",
"manufacturerName": "_TZE200_2aaelwxk"
},
"endpoints": {
"endpointDescriptors": [
{
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 1026,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
3,
1280,
57346,
61184,
60928,
57344,
1024
],
"outputClusters": []
},
{
"endpointId": 242,
"applicationProfileId": 41440,
"applicationDeviceId": 97,
"applicationDeviceVersion": 0,
"_reserved1": 0,
"inputClusters": [],
"outputClusters": [
33
]
}
],
"endpoints": {
"1": {
"clusters": {
"basic": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "zclVersion"
},
{
"acl": [
"readable"
],
"id": 1,
"name": "appVersion"
},
{
"acl": [
"readable"
],
"id": 2,
"name": "stackVersion"
},
{
"acl": [
"readable"
],
"id": 3,
"name": "hwVersion"
},
{
"acl": [
"readable"
],
"id": 4,
"name": "manufacturerName"
},
{
"acl": [
"readable"
],
"id": 5,
"name": "modelId"
},
{
"acl": [
"readable"
],
"id": 7,
"name": "powerSource"
},
{
"acl": [
"readable",
"writable"
],
"id": 18,
"name": "deviceEnabled"
},
{
"acl": [
"readable"
],
"id": 16384,
"name": "swBuildId"
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision"
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"identify": {
"attributes": [
{
"acl": [
"readable",
"writable"
],
"id": 0
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"iasZone": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "zoneState",
"value": "notEnrolled"
},
{
"acl": [
"readable"
],
"id": 1,
"name": "zoneType",
"value": "motionSensor"
},
{
"acl": [
"readable"
],
"id": 2,
"name": "zoneStatus",
"value": {
"type": "Buffer",
"data": [
0,
0
]
}
},
{
"acl": [
"readable",
"writable"
],
"id": 16,
"name": "iasCIEAddress",
"value": "00:00:00:00:00:00:00:00"
},
{
"acl": [
"readable"
],
"id": 17,
"name": "zoneId",
"value": 6
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"illuminanceMeasurement": {
"attributes": [
{
"acl": [
"readable"
],
"id": 0,
"name": "measuredValue",
"value": 1000
},
{
"acl": [
"readable"
],
"id": 1,
"name": "minMeasuredValue",
"value": 0
},
{
"acl": [
"readable"
],
"id": 2,
"name": "maxMeasuredValue",
"value": 4000
},
{
"acl": [
"readable"
],
"id": 65533,
"name": "clusterRevision",
"value": 1
}
],
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
},
"bindings": {}
},
"242": {
"clusters": {},
"bindings": {}
}
}
}

I am also interested in this device to be added to the Tuya Zigbee app.
Hopefully this will be soon.
Best regards,
Henk de Boom

I'm also trying to make this sensor ( _TZE200_2aaelwxk ) compatible. I have the Lux sensor working, but the presence sensor has different datapoints. I also cannot write new settings to the device. (so it doesn't use the default tuya cluster for writing settings it seems...
I'm using the datapoints described in this post: https://github.com/Koenkk/zigbee2mqtt/issues/18612
and using these datapoint values:
//[1, 'presence_state', tuya.valueConverterBasic.lookup({'none': tuya.enum(0), 'presence': tuya.enum(1)})],
[1, 'presence', tuya.valueConverter.trueFalse1],
[2, 'motion_detection_sensitivity', tuya.valueConverter.raw],
[3, 'mov_minimum_distance', tuya.valueConverter.raw],
[4, 'motion_detection_distance', tuya.valueConverter.divideBy100],
[101, 'human_motion_state', tuya.valueConverterBasic.lookup({'none': tuya.enum(0), 'large': tuya.enum(1), 'small': tuya.enum(2), 'breathe': tuya.enum(3)})],
[102, 'fading_time', tuya.valueConverter.raw],
[103, 'motion_false_detection', tuya.valueConverter.raw],
[104, 'small_motion_detection_distance', tuya.valueConverter.divideBy100],
[105, 'small_motion_detection_sensitivity', tuya.valueConverter.raw],
[106, 'illuminance_value', tuya.valueConverter.raw],
[107, 'indicator', tuya.valueConverter.onOff],
[108, 'static_detection_distance', tuya.valueConverter.divideBy100],
[109, 'static_detection_sensitivity', tuya.valueConverter.raw],
[110, 'micro_minimum_distance', tuya.valueConverter.raw],
[111, 'motionless_minimum_distance', tuya.valueConverter.raw],
[112, 'reset_setting', tuya.valueConverter.raw],
[113, 'breathe_false_detection', tuya.valueConverter.raw],
[114, 'time', tuya.valueConverter.raw],
[115, 'alarm_time', tuya.valueConverter.raw],
[116, 'alarm_volume', tuya.valueConverterBasic.lookup({'low': tuya.enum(0), 'medium': tuya.enum(1), 'high': tuya.enum(2), 'mute': tuya.enum(3)})],
[117, 'working_mode', tuya.valueConverterBasic.lookup({'arm': tuya.enum(0), 'off': tuya.enum(1), 'alarm': tuya.enum(2),  'doorbell': tuya.enum(3)})],
[118, 'auto1', tuya.valueConverter.raw],
[119, 'auto2', tuya.valueConverter.raw],
[120, 'auto3', tuya.valueConverter.raw],

It looks like it cannot identify some of the inputClusters:  57346, 60928, 57344 and outputCluster: 33
also from the 1024 (IlluminanceMeasurementCluster) the attribute measuredValue is a weird value, way to high unless the hex calculations below are correct....
zigbee-clusters:cluster ep: 1, cl: illuminanceMeasurement (1024) received frame reportAttributes illuminanceMeasurement.reportAttributes {
  attributes: <Buffer 00 00 21 6f 7f>

not sure it could be like this:
00 00 in hexadecimal is 0 in decimal.
21 in hexadecimal is 33 in decimal.
6f in hexadecimal is 111 in decimal.
7f in hexadecimal is 127 in decimal.

then:

0 + 0 + 33 + 111 + 127 = 271 Lux

and not:

216f7f in hexadecimal is equal to 2207327 in decimal.

i'm also receiving these errors:
  zigbee-clusters:cluster ep: 1, cl: iasZone (1280) unknown command received: ZCLStandardHeader {
  frameControl: Bitmap [ clusterSpecific, directionToClient ],
  trxSequenceNumber: 220,
  cmdId: 0,
  data: <Buffer 01 00 00 ff 00 00>
} {} +1ms
  zigbee-clusters:endpoint ep: 1, cl: iasZone (1280), error while handling frame unknown_command_received {
  meta: {},
  frame: ZCLStandardHeader {
    frameControl: Bitmap [ clusterSpecific, directionToClient ],
    trxSequenceNumber: 220,
    cmdId: 0,
    data: <Buffer 01 00 00 ff 00 00>
  }
}

and the only "working data" i'm getting is:
 zigbee-clusters:cluster ep: 1, cl: tuya (61184) received frame response tuya.response {
  status: 0,
  transid: 218,
  dp: 1,
  datatype: 4,
  length: 1,
  data: <Buffer 01>
} +2m
2023-11-18T21:00:37.048Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] presence state: 1
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) received frame response tuya.response {
  status: 0,
  transid: 219,
  dp: 101,
  datatype: 4,
  length: 1,
  data: <Buffer 02>
} +72ms
2023-11-18T21:00:37.119Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] AIS Zone: 2
2023-11-18T21:00:37.119Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] IASZoneStatusChangeNotification received: true 0 255 0

2023-11-18T21:06:11.425Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] lux value: 1806
2023-11-18T21:06:11.425Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] measure_luminance | Luminance - measuredValue (lux): 1806
  zigbee-clusters:cluster ep: 1, cl: illuminanceMeasurement (1024) received frame reportAttributes illuminanceMeasurement.reportAttributes {
  attributes: <Buffer 00 00 21 38 7f>
}
  zigbee-clusters:cluster ep: 1, cl: iasZone (1280) received frame zoneStatusChangeNotification iasZone.zoneStatusChangeNotification {
  zoneStatus: Bitmap [ alarm1 ],
  extendedStatus: 0,
  zoneId: 255,
  delay: 0
}

write settings errors:
 zigbee-clusters:cluster ep: 1, cl: iasZone (1280) unknown command received: ZCLStandardHeader {
  frameControl: Bitmap [ clusterSpecific, directionToClient ],
  trxSequenceNumber: 7,
  cmdId: 0,
  data: <Buffer 01 00 00 ff 00 00>
} {} +0ms
  zigbee-clusters:endpoint ep: 1, cl: iasZone (1280), error while handling frame unknown_command_received {
  meta: {},
  frame: ZCLStandardHeader {
    frameControl: Bitmap [ clusterSpecific, directionToClient ],
    trxSequenceNumber: 7,
    cmdId: 0,
    data: <Buffer 01 00 00 ff 00 00>
  }
} +11s
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) send frame ZCLStandardHeader {
  frameControl: [ 'clusterSpecific' ],
  data: tuya.datapoint {
    status: 0,
    transid: 0,
    dp: 109,
    datatype: 2,
    length: 4,
    data: <Buffer 00 00 00 01>
  },
  cmdId: 0,
  trxSequenceNumber: 1
} +39s
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) received frame reporting tuya.reporting {
  status: 0,
  transid: 0,
  dp: 109,
  datatype: 2,
  length: 4,
  data: <Buffer 00 00 00 01>
} +335ms
2023-11-18T21:10:34.191Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] DEBUG DATA!!!!!!
2023-11-18T21:10:34.191Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] tuya.reporting {
  status: 0,
  transid: 0,
  dp: 109,
  datatype: 2,
  length: 4,
  data: <Buffer 00 00 00 01>
}
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) received frame defaultResponse tuya.defaultResponse { cmdId: 0, status: 'FAILURE' } +1ms
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) received frame reporting tuya.reporting {
  status: 0,
  transid: 0,
  dp: 109,
  datatype: 2,
  length: 4,
  data: <Buffer 00 00 00 01>
} +1ms
2023-11-18T21:10:34.192Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] DEBUG DATA!!!!!!
2023-11-18T21:10:34.194Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:ad704e4c-bfe5-476f-92de-e81d60ee0b65] tuya.reporting {
  status: 0,
  transid: 0,
  dp: 109,
  datatype: 2,
  length: 4,
  data: <Buffer 00 00 00 01>
}
/app/node_modules/zigbee-clusters/lib/Cluster.js:1062
                throw new Error(response.status);
                      ^

Error: FAILURE
    at TuyaSpecificCluster.datapoint (/app/node_modules/zigbee-clusters/lib/Cluster.js:1062:23)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Hopefully another person finds this info useful...

After some testing i managed to retrieve all the sensor data. but saving/setting settings still doesn't work.
does not matter which function i use to save:

this.dataPoinst = {
  presence: 1, // [0/1]
  motion_detection_sensitivity: 2, // [0-10, 1, x]
  mov_minimum_distance: 3, //
  motion_detection_distance: 4, // [0-10, 0.01, m]
  human_motion_state: 101, // [enum(0,1,2,3) none, large, small, breathe]
  fading_time: 102, // [0-28800, 1, s]
  motion_false_detection: 103, // [0-10, 1, x]
  small_motion_detection_distance: 104, // [0-6, 0.01, m]
  small_motion_detection_sensitivity: 105, // [0-10, 1, x]
  illuminance_value: 106, // (lux)
  indicator: 107, // LED Indicator
  static_detection_distance: 108, // [0-6, 0.01, m]
  static_detection_sensitivity: 109, // [0-10, 1, x]
  micro_minimum_distance: 110,
  motionless_minimum_distance: 111,
  reset_setting: 112,
  breathe_false_detection: 113, // [0/1]
  time: 114,
  alarm_time: 115, // [1-60, 1, m]
  alarm_volume: 116, // [enum(0: low, 1: medium, 2: high, 3: mute)]
  working_mode: 117, // [enum(0: arm, 1: off, 2: alarm, 3: doorbell)]
  auto1: 118,
  auto2: 119,
  auto3: 120,
};

async onSettings({ oldSettings, newSettings, changedKeys }) {

    if (changedKeys.includes("motion_detection_sensitivity")) {
      this.writeData32(
        this.dataPoints.motion_detection_sensitivity,
        newSettings["motion_detection_sensitivity"]
      );
    }

    if (changedKeys.includes("indicator")) {
      this.writeBool(this.dataPoints.indicator, newSettings["indicator"]);
    }

    if (changedKeys.includes("alarm_volume")) {
      this.writeEnum(this.dataPoints.alarm_volume, newSettings["alarm_volume"]);
    }
}

There are the errors when saving settings from homey... So the cluster 61184 (tuya) is not capable to write data to ...
 zigbee-clusters:cluster ep: 1, cl: tuya (61184) send frame ZCLStandardHeader {
  frameControl: [ 'clusterSpecific' ],
  data: tuya.datapoint {
    status: 0,
    transid: 0,
    dp: 2,
    datatype: 2,
    length: 4,
    data: <Buffer 00 00 00 0a>
  },
  cmdId: 0,
  trxSequenceNumber: 1
} +53s
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) received frame reporting tuya.reporting {
  status: 0,
  transid: 0,
  dp: 2,
  datatype: 2,
  length: 4,
  data: <Buffer 00 00 00 0a>
} +339ms
2023-11-20T18:57:56.275Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:4eea8eda-61f7-4584-a01a-f3b6df5426d6] ########### Reporting:  tuya.reporting {
  status: 0,
  transid: 0,
  dp: 2,
  datatype: 2,
  length: 4,
  data: <Buffer 00 00 00 0a>
}
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) received frame defaultResponse tuya.defaultResponse { cmdId: 0, status: 'FAILURE' } +101ms
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) received frame reporting tuya.reporting {
  status: 0,
  transid: 0,
  dp: 2,
  datatype: 2,
  length: 4,
  data: <Buffer 00 00 00 0a>
} +1ms
2023-11-20T18:57:56.377Z [log] [ManagerDrivers] [Driver:radar_sensor] [Device:4eea8eda-61f7-4584-a01a-f3b6df5426d6] ########### Reporting:  tuya.reporting {
  status: 0,
  transid: 0,
  dp: 2,
  datatype: 2,
  length: 4,
  data: <Buffer 00 00 00 0a>
}
/app/node_modules/zigbee-clusters/lib/Cluster.js:1062
                throw new Error(response.status);
                      ^

Error: FAILURE
    at TuyaSpecificCluster.datapoint (/app/node_modules/zigbee-clusters/lib/Cluster.js:1062:23)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
───────────────────────────────────────────────────────

I made a fork with the working readings of the device. but writing settings still fails...
https://github.com/eelco2k/com.tuya.zigbee/

I made a fork with the working readings of the device. but writing settings still fails...
https://github.com/eelco2k/com.tuya.zigbee/tree/SDK3/drivers/radar_sensor_2

I tried your fork and it works OK. Just sensors like breath and small motion are not available in flows. Any idea?

@gooooba  yes I noticed after installing it as well si it crashes only in debug mode (cli run cmd)
Perhaps because the send functions expect a response but there is none… haven’t really found out why…
I did not have the time to check all the flows, will try to do next week.

@eelco2k  thank you for your great effort on this device! 👍  it works superb for me, hoping it also could be part of the official app :)
and now i discovered that theres a pull request for a ceiling device that has the same id tags
"ids": {
"modelId": "TS0225",
"manufacturerName": "_TZE200_2aaelwxk"
},
here: https://github.com/JohanBendz/com.tuya.zigbee/pull/653
difference is this is lacking small, large and breathe presence.
though.. maybe this contains some ideas for you to make your own pull request on this? :)

I’ve created a pull request. As my this driver has successfully been tested in my environment.
https://github.com/JohanBendz/com.tuya.zigbee/pull/774/files

I’ve created a pull request. As this driver has successfully been tested in my environment. #774

Great work.  Is it possible to get info on current distance to be added to device screen and also in flows? Then automation would be on another level.

This device does not offer distance unfortunately :-(

To bad...  know sensor that does?


Dev/inchi split

This is code to break the InChI into the layers.
The bits to do the merging based on particular layers is still to come. It's still worth taking a look at this though.

I took a quick look; do you want to pull this as-is, or add merging first?

Let's hold off a bit until I get at least some of the code to help with the merging in. Should have that later today.

Ok, I think this one is now ready to merge.


add mixin to support drf views

Problem
I just wanted to integrate this great library with django-rest-framework, so I could use export capability of library beside ListModelMixin in drf
Solution
I developed a mixin with one drf.action so if you inherit it in your view, you can export your queryset in your APIs
Acceptance Criteria
this is work with swagger, so its look like this image.

Hi Amir - thanks for creating this PR.  I would say that this is something we are not ready to include in the library at this time.
We have a thread here where we are talking about integrating with DRF, but we are not there yet.  You are welcome to follow the thread and make suggestions based on your experiences.

This is a cool idea, I think there's a lot of discussion to how any drf integration would work like Matthew said.
At a minimum would need some tests and I'd suggest adding options.extras_require for DRF, and figuring out how to cleanly test extras. I've never looked at how libraries with extras do testing; my guess is you'd need to update the tox settings to make sure it installs DRF.
That said, I don't know how much effort I'd put into it until we've got a design direction.


Black sky issue after setting weather.fog_density to close to zero values

Carla: 0.9.9
Problem:

Observe the sky becomes fully black with exact 0 pixel values from time to time.
This becomes more persistent after setting weather.fog_density=0 (or small to 0 value). The sky in the rendered frames becomes fully black (left image).
This black sky issue is also observed without running a), but much less often.

  weather = world.get_weather()

  weather.fog_density = 0

  world.set_weather(weather)

Questions:

Why does black sky issue appear in general (even without modifying weather)?
For the black sky issue caused by setting fog parameter, what are the potential causes and solutions?

Still image:

Some video frames:

Seems related to #3494 and #3545. But no clear solution yet.

Seems related to #3494 and #3545. But no clear solution yet.

Figured out that this is related to the 'Low' mode I used in rendering. 'Epic' mode generates correct images.

Figured out that this is related to the 'Low' mode I used in rendering. 'Epic' mode generates correct images.


Improve file stager

For batch downloading, the connector used a class FileStager together with helper classes StagingParameters and StagingState and a helper function init_file_stager.
The PR simplifies this setup by slimming down FileStager to its essentials and removing the helper classes and function.
Also, the batch downloader did not heed the retry-after value suggested by the download controller, but used its own fixed value of 60s. However, it also did not always wait that long between retries, depending on how many files were staged in the first run. If no files were staged, staging requests for the same file were made two times consecutively without waiting.
The PR improves this behavior by waiting as long as specified by the download controller and keeping track of when files were staged last time individually. Since less code is involved, the code should also be easier to understand and maintain. Note that the batch downloader is not tested other than via the archive test bed.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

55 of 65 (84.62%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.5%) to 72.029%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/ghga_connector/core/downloading/batch_processing.py
52
62
83.87%

Files with Coverage Reduction
New Missed Lines
%

src/ghga_connector/core/downloading/batch_processing.py
2
79.84%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.5%

Covered Lines:
994

Relevant Lines:
1380

💛  - Coveralls


Cards

Please identify which UI elements fit into cards, and whether this issue needs to be broken down into multiple!

Airbnb

I've uploaded the file for cards into github, if any of you are interested on taking a look. There are a lot of designs to look at


Redoing pull. Reverted to previous commit (before removing CompFlickable from Rail Switch)

Changes:

Added powered rails
Added AutoSwitch toggle to Rail Switch with custom texture
Allowed placement of rail utilities onto track blueprints
Fixed Dump Free Space mode not filling existing item stacks
Fixed Rail Dump radius increases with each item dropped
Fixed Rail Dump ignoring storage that shares space with other buildings (Like conduits)
Included unused textures for rail direction widget (to be implemented)

D*** forgot the bit about load mode ignoring conduits;

Not stable -- Rail dump in dump all mode causes freeze.

Now It's stable. I'll leave it as is for the time being and tinker in another branch so the pull request won't change.

After a bit of testing I've noticed only 1 thing wrong:
Both kinds of rails can coexist in the same space. I have no idea how to resolve this.
At first I was just like "eh I'll just make a placeworker." It turns out I have no idea how to do that.
I tried adding the placeworker into the xml def and making the class for it which looks almost identical to the minecart placeworker, but the game couldn't see it.
Could not find a type named Minecart.PlaceWorker_Rails
Small bug, it shouldn't have any major impact on gameplay but really there should only be one kind of rail on a space.
Please advise -_-

Wait... ok this might not be a problem after all. I was in dev mode.
I'm pretty sure that when a colonist would try to build one rail atop another, they would deconstruct the rail which was already there. Will test.

Nope. If a player builds one type of rail atop another one then both rails will exist in the same spot.
It doesn't throw errors or cause bad behavior, the state is just weird in itself.

Reworking the dump all code made it more efficient, I think, on top of fixing the radius increase that was bugging me.
Now instead of iterating over the items and trying to drop in each cell per item, it will iterate over the cells and try to drop each item into it.
That stops the code from re-iterating over cells that it already placed items into.

Adding this in 1.5

Updated now in 26f86da
I fixed separate textures for the powered rails


initrd-network RFC: use kernel DHCP

Description of changes
This is request for comments to add (or reinstate? it has been disabled at least since 2009 cc @edolstra) DHCP for initialization stage 1 use. I successfully booted remote squashfs image using a hack to init-1-sh. The use-case is related to booting rootfs systems over 2GB, which coincidentally has a bug currently. These changes are mutually exclusive -- you cannot use boot.initrd.network.enable with the kernel module and vice versa -- the configurations will be overwritten and the initrd won't have be able to resolve the network. I have successfully booted a rootfs over 2GB using my current changes.
I think this might be worth upstreaming, because compared to the current implementation, I see corollary benefits to the systemd in init1 phase effort (for networking: see #169116). This is because using the kernel implementation simplifies the network configuration a lot -- the phase 1 /init script is not executed before the network is up. This means there is less orchestration needed to wait for the interface to be configured -- which anecdotally is a burden with init1 stage systemd distros like Fedora CoreOS, in which a lot of the dracut generated systemd scripts have a dependency on network access. However, it's worth noting that the kernel DHCP implementation does not guarantee that the network will resolve -- DNS has to be configured separately, though this can integrate with already existing DNS configurations in Nix.
I'm suspect that currently the feature is overlooked, but I might be wrong -- quick Googling shows that in one occasion the functionality to other distros have not been well-received (e.g., ubuntu). Other threads say that network configuration belongs to the initrd, not the kernel, for which this feature should be disabled. However, I am not sure if I'm convinced that it's necessarily better to have a separate userspace DHCP client in the initrd. The kernel module abides to the /proc/cmdline ip declaration which seems much easier than making a pick on userland DHCP tool to use, which often do the same thing nonetheless, which is to parse the parameter.
Any thoughts or people to ping? Current changes have not been tested, but are a draft of what I imagine it would roughly look like.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Maybe a good way to go at it is:

keep the existing way to perform DHCP
offer the kernel DHCP way through an experimental flag boot.initrd.networking.useKernelDHCP
have a NixOS test to check this works ~fine
documentation in release notes on this

Let's merge after we hit those points and we can collect feedback on how it works and deprecated one or the other way if that makes sense at all.

Sounds good, I can get along with it. I'll update the changes once I have it working.


Word Add-in in NET CORE 8 with blazor

Will there be a example template for the office word add-in with .net 8 and blazor?

Yes, I will work on that the upcoming weeks. Keep an eye on my fork, you most likely will find a proto there soon!

I just created a new Pull Request #669 to upgrade the Office Blazor Sample project to .NET 8. Once approved you should be able to run that and close this issue.

Thank you


Element in dropdown menu not found

Hi,
appreciate your work and I would like to use YWinAppDriver in my project.
In my project I just replaced the WinAppDriver and gave it a go.
However when selecting an entry in a dropdown menu (which was opened in a previous click) this error occurs:
"Didn't found the element in cache" and the program fails.
While debugging the value of the variable is not null, as seen in this if statement where the error is thrown:
if (element != null)
{
element.Click();  // error occurs here
}
Is it also possible to implement the screenshot feature of Selenium ? Would be very helpful.
Best regards and thanks

Are you using the newest version? I didn't see below code.
if (element != null)
{
element.Click();
}

For the menu, if you open it and close it, although the name is the same, you need to locate the element again.
To reduce the cache size, the logic is like this:

You located a element, and YWinAppDrive cached it. YWinAppDriver hold an reference to the UIA element
The element changed(like you close the menu, then open again). The actual UIA element is changed too although it looks like the same
You use the old reference to click, then YWinAppDriver report Stale Element and remove the element from the cache
If you use the old reference to click again, then YWinAppDriver report 'Didn't found the element in cache'

I already added the screenshot feature

@Jteve-Sobs did you still see the problem in latest version?


Added support for smart throttle for human emu.

To make sure the map can complete all required scans within the hash
cycle period

I updated the PR

done

rebased


The torch version used in requirements.txt seems to be removed

Describe the bug
I am trying to reproduce the example under examples/BuddyLlama, but I found that the torch version used in requirements.txt seems to be removed.
To Reproduce

Create a new conda env named llama and activate it

$ conda create -n llama
$ conda activate llama

Intall the packages needed

$ cd buddy-mlir
$ pip install -r requirements.txt

Then we can see the error.
Expected behavior
torch is successfully installed.
Screenshots

Desktop (please complete the following information):

OS: Ubuntu
Version 22.04

Additional context
I am trying another "dev" version of torch. However, for the sake of generality, maybe we should use a stable version of torch to make the reproduction of this example more stable?

Besides, it seems that the pybind11 package needs to be installed extraly by running conda install pybind11 -c conda-forge before building llvm and buddy-mlir, which will not be installed by running pip install -r requirements.txt.

ping @Lester-1

Thank you for your suggestion. We have switched torch to a stable version. Please see the link https://github.com/buddy-compiler/buddy-mlir/pull/266 for details.

@BHbean Thanks for reporting this! We have fixed the issue. Please check😄

Thanks a lot! The torch2.1.2+cpu version did work!

Besides, it seems that the pybind11 package needs to be installed extraly by running conda install pybind11 -c conda-forge before building llvm and buddy-mlir, which will not be installed by running pip install -r requirements.txt.
Should this be added under pip install -r requirements.txt in examples/BuddyLlama? I could open a pr if you guys think it neccessary :)

@BHbean, feel free to add this! Thanks!