text:
Got the USB stick from Amazon with US frequency and would like to update firmware to have EU frequency instead.

          > Got the USB stick from Amazon with US frequency and would like to update firmware to have EU frequency instead.

AFAIK you can just switch the region in the settings on that firmware.
Originally posted by @AlCalzone in https://github.com/zwave-js/node-zwave-js/issues/5910#issuecomment-1636262505

???

Thank you very much for the recent update of the Z-Wave JS UI module - it looks much better now:

After the recent update of the Z-Wave JS UI module it is not possible to update the frequency by using the switch in the module.
Whatever I select in the menu it always turns back to US frequency again.
Just read the change log from Silicon Labs  [https://www.silabs.com/documents/public/release-notes/SRN14889-7.18.3.0.pdf] - does the Z-Wave JS UI module take care of this remark?

The log file looks like this:

Anything that I could do different?

What you're referencing applies to the initial programming, not changing the region on the fly.
Please disable application logs, and set your driver logs to loglevel debug, then make another log of that attempt.
Please no screenshots, just copy/paste the log output here, then format it as code with this:

2023-07-19 13:27:52.749 INFO APP: GET /health/zwave 200 2.915 ms - 2140 2023-07-19 13:28:20.724 INFO Z-WAVE: Calling api setRFRegion with args: [ 0, [length]: 1 ] 2023-07-19T11:28:20.751Z CNTRLR   Performing soft reset... 2023-07-19T11:28:20.978Z DRIVER     no handlers registered! 2023-07-19T11:28:21.764Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i                                   n 100 ms. 2023-07-19T11:28:22.089Z DRIVER     no handlers registered! 2023-07-19T11:28:22.873Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i                                   n 1100 ms. 2023-07-19 13:28:22.925 INFO APP: GET /health/zwave 200 6.586 ms - 2140 2023-07-19T11:28:24.197Z DRIVER     no handlers registered! 2023-07-19T11:28:24.983Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020                                   0) 2023-07-19T11:28:24.985Z CNTRLR   Waiting for the controller to reconnect... 2023-07-19T11:28:26.488Z CNTRLR   Waiting for the Serial API to start... 2023-07-19T11:28:31.491Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo                                   nds... 2023-07-19T11:28:31.520Z CNTRLR   Serial API responded 2023-07-19 13:28:31.538 INFO Z-WAVE: Success zwave api call setRFRegion true

2023-07-19 13:27:52.749 INFO APP: GET /health/zwave 200 2.915 ms - 2140
2023-07-19 13:28:20.724 INFO Z-WAVE: Calling api setRFRegion with args: [ 0, [length]: 1 ]
2023-07-19T11:28:20.751Z CNTRLR   Performing soft reset...
2023-07-19T11:28:20.978Z DRIVER     no handlers registered!
2023-07-19T11:28:21.764Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-07-19T11:28:22.089Z DRIVER     no handlers registered!
2023-07-19T11:28:22.873Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-07-19 13:28:22.925 INFO APP: GET /health/zwave 200 6.586 ms - 2140
2023-07-19T11:28:24.197Z DRIVER     no handlers registered!
2023-07-19T11:28:24.983Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
0)
2023-07-19T11:28:24.985Z CNTRLR   Waiting for the controller to reconnect...
2023-07-19T11:28:26.488Z CNTRLR   Waiting for the Serial API to start...
2023-07-19T11:28:31.491Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
nds...
2023-07-19T11:28:31.520Z CNTRLR   Serial API responded
2023-07-19 13:28:31.538 INFO Z-WAVE: Success zwave api call setRFRegion true

Was this done correct?

Ehh...
I still see application logs in there, so you did not disable them.
Also the driver logs are not on loglevel debug.
And as far as formatting goes it looks like you first pressed the code button, then inserted it. Need to do it the other way round.

2023-07-19T14:04:01.283Z DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
2023-07-19T14:04:01.283Z DRIVER   version 11.5.0
2023-07-19T14:04:01.283Z DRIVER
2023-07-19T14:04:01.284Z DRIVER   starting driver...
2023-07-19T14:04:01.284Z DRIVER   opening serial port /dev/ttyUSB0
2023-07-19T14:04:01.294Z DRIVER   serial port opened
2023-07-19T14:04:01.295Z SERIAL » 0x15                                                                 (1 bytes)
2023-07-19T14:04:02.313Z DRIVER   loading configuration...
2023-07-19T14:04:02.322Z CONFIG   Using external configuration dir /data/db
2023-07-19T14:04:02.323Z CONFIG   version 11.5.0
2023-07-19T14:04:03.807Z DRIVER   beginning interview...
2023-07-19T14:04:03.808Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
1 registered
2023-07-19T14:04:03.809Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
1 registered
2023-07-19T14:04:03.809Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
1 registered
2023-07-19T14:04:03.809Z CNTRLR   querying controller IDs...
2023-07-19T14:04:03.816Z SERIAL » 0x01030020dc                                                         (5 bytes)
2023-07-19T14:04:03.817Z DRIVER » [REQ] [GetControllerId]
2023-07-19T14:04:03.823Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:03.824Z SERIAL « 0x01080120f11f556e0102                                              (10 bytes)
2023-07-19T14:04:03.825Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:03.827Z DRIVER « [RES] [GetControllerId]
home ID:     0xf11f556e
own node ID: 1
2023-07-19T14:04:03.830Z CNTRLR   received controller IDs:
home ID:     0xf11f556e
own node ID: 1
2023-07-19T14:04:03.830Z CNTRLR   querying API capabilities...
2023-07-19T14:04:03.834Z SERIAL » 0x01030007fb                                                         (5 bytes)
2023-07-19T14:04:03.835Z DRIVER » [REQ] [GetSerialApiCapabilities]
2023-07-19T14:04:03.843Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:03.844Z SERIAL « 0x012b01070713027a0001000df6873e88cf2bc04ffbd7fde01700008000808680b (45 bytes)
a0500700000ee7fc0000000a0
2023-07-19T14:04:03.846Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:03.847Z DRIVER « [RES] [GetSerialApiCapabilities]
payload: 0x0713027a0001000df6873e88cf2bc04ffbd7fde01700008000808680ba0500700
000ee7fc0000000
2023-07-19T14:04:03.850Z CNTRLR   received API capabilities:
firmware version:    7.19
manufacturer ID:     0x027a
product type:        0x01
product ID:          0x0d
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SerialAPIStarted (0x0a)
· SerialAPISetup (0x0b)
· SetRFReceiveMode (0x10)
· FUNC_ID_ZW_SEND_NODE_INFORMATION (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· FUNC_ID_ZW_GET_RANDOM (0x1c)
· GetControllerId (0x20)
· UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
· UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
· UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
· UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
· EnterBootloader (0x27)
· UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
· GetNVMId (0x29)
· ExtNVMReadLongBuffer (0x2a)
· ExtNVMReadLongByte (0x2c)
· NVMOperations (0x2e)
· undefined (0x37)
· undefined (0x38)
· UNKNOWN_FUNC_ClearNetworkStats (0x39)
· UNKNOWN_FUNC_GetNetworkStats (0x3a)
· GetBackgroundRSSI (0x3b)
· undefined (0x3c)
· UNKNOWN_FUNC_RemoveNodeIdFromNetwork (0x3f)
· GetNodeProtocolInfo (0x41)
· HardReset (0x42)
· FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
· FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
· AssignReturnRoute (0x46)
· DeleteReturnRoute (0x47)
· RequestNodeNeighborUpdate (0x48)
· ApplicationUpdateRequest (0x49)
· AddNodeToNetwork (0x4a)
· RemoveNodeFromNetwork (0x4b)
· FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
· AssignPriorityReturnRoute (0x4f)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· AssignSUCReturnRoute (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· AssignPrioritySUCReturnRoute (0x58)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· undefined (0x5f)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· undefined (0x65)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· GetPriorityRoute (0x92)
· SetPriorityRoute (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· FUNC_ID_SERIAL_API_SLAVE_NODE_INFO (0xa0)
· FUNC_ID_ZW_SEND_SLAVE_NODE_INFO (0xa2)
· FUNC_ID_ZW_SET_SLAVE_LEARN_MODE (0xa4)
· FUNC_ID_ZW_GET_VIRTUAL_NODES (0xa5)
· FUNC_ID_ZW_IS_VIRTUAL_NODE (0xa6)
· BridgeApplicationCommand (0xa8)
· SendDataBridge (0xa9)
· SendDataMulticastBridge (0xab)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xd6)
· undefined (0xd7)
· undefined (0xd8)
· Shutdown (0xd9)
· undefined (0xda)
· undefined (0xdb)
· undefined (0xdc)
· undefined (0xdd)
· undefined (0xde)
· undefined (0xdf)
· undefined (0xe7)
· undefined (0xe8)
2023-07-19T14:04:03.859Z CNTRLR   Performing soft reset...
2023-07-19T14:04:03.863Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:04:03.864Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:04:03.869Z SERIAL « [DISCARDED] invalid data 0xc6                                        (1 bytes)
2023-07-19T14:04:04.090Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:04:04.093Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:04.095Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:04:04.097Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:04:04.098Z DRIVER     no handlers registered!
2023-07-19T14:04:04.868Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-07-19T14:04:04.970Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:04:04.971Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:04:04.977Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:04:05.187Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:04:05.188Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:05.190Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:04:05.191Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:04:05.192Z DRIVER     no handlers registered!
2023-07-19T14:04:05.976Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-07-19T14:04:07.077Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:04:07.079Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:04:07.084Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:04:07.295Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:04:07.296Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:07.297Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:04:07.298Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:04:07.299Z DRIVER     no handlers registered!
2023-07-19T14:04:08.085Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
0)
2023-07-19T14:04:08.086Z CNTRLR   Waiting for the controller to reconnect...
2023-07-19T14:04:09.587Z CNTRLR   Waiting for the Serial API to start...
2023-07-19T14:04:14.588Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
nds...
2023-07-19T14:04:14.600Z SERIAL » 0x01030015e9                                                         (5 bytes)
2023-07-19T14:04:14.601Z DRIVER » [REQ] [GetControllerVersion]
2023-07-19T14:04:14.607Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.609Z SERIAL « 0x011001155a2d5761766520372e313900079f                              (18 bytes)
2023-07-19T14:04:14.611Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.617Z DRIVER « [RES] [GetControllerVersion]
payload: 0x5a2d5761766520372e31390007
2023-07-19T14:04:14.620Z CNTRLR   Serial API responded
2023-07-19T14:04:14.632Z CNTRLR   querying version info...
2023-07-19T14:04:14.636Z SERIAL » 0x01030015e9                                                         (5 bytes)
2023-07-19T14:04:14.637Z DRIVER » [REQ] [GetControllerVersion]
2023-07-19T14:04:14.643Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.644Z SERIAL « 0x011001155a2d5761766520372e313900079f                              (18 bytes)
2023-07-19T14:04:14.645Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.646Z DRIVER « [RES] [GetControllerVersion]
payload: 0x5a2d5761766520372e31390007
2023-07-19T14:04:14.654Z CNTRLR   received version info:
controller type: Bridge Controller
library version: Z-Wave 7.19
2023-07-19T14:04:14.655Z CNTRLR   querying protocol version info...
2023-07-19T14:04:14.659Z SERIAL » 0x01030009f5                                                         (5 bytes)
2023-07-19T14:04:14.660Z DRIVER » [REQ] [GetProtocolVersion]
2023-07-19T14:04:14.667Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.669Z SERIAL « 0x011901090007130200be3030303030303030303030303030303046            (27 bytes)
2023-07-19T14:04:14.670Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.672Z DRIVER « [RES] [GetProtocolVersion]
payload: 0x0007130200be30303030303030303030303030303030
2023-07-19T14:04:14.675Z CNTRLR   received protocol version info:
protocol type:             Z-Wave
protocol version:          7.19.2
appl. framework build no.: 190
git commit hash:           30303030303030303030303030303030
2023-07-19T14:04:14.676Z CNTRLR   supported Z-Wave features:
· SmartStart
2023-07-19T14:04:14.677Z CNTRLR   querying controller capabilities...
2023-07-19T14:04:14.682Z SERIAL » 0x01030005f9                                                         (5 bytes)
2023-07-19T14:04:14.683Z DRIVER » [REQ] [GetControllerCapabilities]
2023-07-19T14:04:14.688Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.689Z SERIAL « 0x010401053cc3                                                       (6 bytes)
2023-07-19T14:04:14.690Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.692Z DRIVER « [RES] [GetControllerCapabilities]
payload: 0x3c
2023-07-19T14:04:14.697Z CNTRLR   received controller capabilities:
controller role:      primary
is the SUC:           true
started this network: true
SIS is present:       true
was real primary:     true
2023-07-19T14:04:14.697Z CNTRLR   querying serial API setup capabilities...
2023-07-19T14:04:14.702Z SERIAL » 0x0104000b01f1                                                       (6 bytes)
2023-07-19T14:04:14.703Z DRIVER » [REQ] [SerialAPISetup]
command: GetSupportedCommands
payload: 0x01
2023-07-19T14:04:14.709Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.711Z SERIAL « 0x0116010b01ff9f8007800000008000000000000000800085                  (24 bytes)
2023-07-19T14:04:14.712Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.714Z DRIVER « [RES] [SerialAPISetup]
command: GetSupportedCommands
payload: 0xff9f80078000000080000000000000008000
2023-07-19T14:04:14.716Z CNTRLR   supported serial API setup commands:
· GetSupportedCommands
· SetTxStatusReport
· SetLRMaximumTxPower
· SetPowerlevel
· GetLRMaximumTxPower
· GetPowerlevel
· GetMaximumPayloadSize
· GetLRMaximumPayloadSize
· SetPowerlevel16Bit
· GetPowerlevel16Bit
· GetRFRegion
· SetRFRegion
· SetNodeIDType
2023-07-19T14:04:14.717Z CNTRLR   Enabling TX status report...
2023-07-19T14:04:14.722Z SERIAL » 0x0105000b02ff0c                                                     (7 bytes)
2023-07-19T14:04:14.723Z DRIVER » [REQ] [SerialAPISetup]
command: SetTxStatusReport
enabled: true
2023-07-19T14:04:14.731Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.733Z SERIAL « 0x0105010b0201f3                                                     (7 bytes)
2023-07-19T14:04:14.734Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.735Z DRIVER « [RES] [SerialAPISetup]
command: SetTxStatusReport
success: true
2023-07-19T14:04:14.738Z CNTRLR   Enabling TX status report successful...
2023-07-19T14:04:14.738Z CNTRLR   Querying configured RF region...
2023-07-19T14:04:14.743Z SERIAL » 0x0104000b20d0                                                       (6 bytes)
2023-07-19T14:04:14.744Z DRIVER » [REQ] [SerialAPISetup]
command: GetRFRegion
payload: 0x20
2023-07-19T14:04:14.749Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.751Z SERIAL « 0x0105010b2001d1                                                     (7 bytes)
2023-07-19T14:04:14.752Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.753Z DRIVER « [RES] [SerialAPISetup]
command: GetRFRegion
region:  USA
2023-07-19T14:04:14.756Z CNTRLR   The controller is using RF region USA
2023-07-19T14:04:14.756Z CNTRLR   finding SUC...
2023-07-19T14:04:14.764Z SERIAL » 0x01030056aa                                                         (5 bytes)
2023-07-19T14:04:14.765Z DRIVER » [REQ] [GetSUCNodeId]
2023-07-19T14:04:14.770Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.771Z SERIAL « 0x0104015601ad                                                       (6 bytes)
2023-07-19T14:04:14.772Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.773Z DRIVER « [RES] [GetSUCNodeId]
payload: 0x01
2023-07-19T14:04:14.776Z CNTRLR   This is the SUC
2023-07-19T14:04:14.776Z CNTRLR   querying additional controller information...
2023-07-19T14:04:14.781Z SERIAL » 0x01030002fe                                                         (5 bytes)
2023-07-19T14:04:14.782Z DRIVER » [REQ] [GetSerialApiInitData]
2023-07-19T14:04:14.790Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:14.792Z SERIAL « 0x012501020a081d010000000000000000000000000000000000000000000000000 (39 bytes)
00000000700c0
2023-07-19T14:04:14.793Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:14.795Z DRIVER « [RES] [GetSerialApiInitData]
payload: 0x0a081d01000000000000000000000000000000000000000000000000000000000
700
2023-07-19T14:04:14.798Z CNTRLR   received additional controller information:
Z-Wave API version:         1 (official)
Z-Wave chip type:           EFR32ZG14 / ZGM130S
node type                   Controller
controller role:            primary
controller is the SIS:      true
controller supports timers: false
nodes in the network:       1
2023-07-19T14:04:14.809Z DRIVER   Cache file for homeId 0xf11f556e found, attempting to restore the network from
cache...
2023-07-19T14:04:14.818Z CNTRLR   [Node 001] Embedded device config loaded
2023-07-19T14:04:14.820Z DRIVER   Restoring the network from cache was successful!
2023-07-19T14:04:14.822Z CNTRLR   [Node 001] [Manufacturer Specific] manufacturerId: metadata updated
2023-07-19T14:04:14.823Z CNTRLR   [Node 001] [Manufacturer Specific] productType: metadata updated
2023-07-19T14:04:14.824Z CNTRLR   [Node 001] [Manufacturer Specific] productId: metadata updated
2023-07-19T14:04:14.825Z CNTRLR   [Node 001] [~] [Manufacturer Specific] manufacturerId: 634 => 634
2023-07-19T14:04:14.827Z CNTRLR   [Node 001] [~] [Manufacturer Specific] productType: 1 => 1
2023-07-19T14:04:14.828Z CNTRLR   [Node 001] [~] [Manufacturer Specific] productId: 13 => 13
2023-07-19T14:04:14.829Z CNTRLR   [Node 001] [Version] firmwareVersions: metadata updated
2023-07-19T14:04:14.829Z CNTRLR   [Node 001] [~] [Version] firmwareVersions: 7.19 => 7.19
2023-07-19T14:04:14.830Z CNTRLR   [Node 001] [Version] zWaveProtocolVersion: metadata updated
2023-07-19T14:04:14.831Z CNTRLR   [Node 001] [~] [Version] zWaveProtocolVersion: "7.19.2" => "7.19.2"
2023-07-19T14:04:14.832Z CNTRLR   [Node 001] [Version] sdkVersion: metadata updated
2023-07-19T14:04:14.833Z CNTRLR   [Node 001] [~] [Version] sdkVersion: "7.19.2" => "7.19.2"
2023-07-19T14:04:14.833Z CNTRLR   Interview completed
2023-07-19T14:04:14.834Z DRIVER   Network key for S0 configured, enabling S0 security manager...
2023-07-19T14:04:14.835Z DRIVER   At least one network key for S2 configured, enabling S2 security manager...
2023-07-19T14:04:14.841Z DRIVER   driver ready
2023-07-19T14:04:14.844Z DRIVER   Checking for configuration updates...
2023-07-19T14:04:14.876Z CNTRLR   [Node 001] The node is alive.
2023-07-19T14:04:14.903Z CNTRLR   [Node 001] The node is ready to be used
2023-07-19T14:04:14.904Z CNTRLR   All nodes are ready to be used
2023-07-19T14:04:14.993Z SERIAL » 0x0104000b13e3                                                       (6 bytes)
2023-07-19T14:04:14.995Z DRIVER » [REQ] [SerialAPISetup]
command: GetPowerlevel16Bit
payload: 0x13
2023-07-19T14:04:15.009Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:15.011Z SERIAL « 0x0108010b1300000000ee                                              (10 bytes)
2023-07-19T14:04:15.012Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:15.013Z DRIVER « [RES] [SerialAPISetup]
command:               GetPowerlevel16Bit
normal powerlevel:     0.0 dBm
output power at 0 dBm: 0.0 dBm
2023-07-19T14:04:15.024Z SERIAL » 0x0104000b20d0                                                       (6 bytes)
2023-07-19T14:04:15.025Z DRIVER » [REQ] [SerialAPISetup]
command: GetRFRegion
payload: 0x20
2023-07-19T14:04:15.036Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:15.037Z SERIAL « 0x0105010b2001d1                                                     (7 bytes)
2023-07-19T14:04:15.038Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:15.039Z DRIVER « [RES] [SerialAPISetup]
command: GetRFRegion
region:  USA
2023-07-19T14:04:15.249Z DRIVER   No configuration update available...
2023-07-19T14:04:15.268Z DRIVER   Usage statistics sent - next transmission scheduled in 23 hours.
2023-07-19T14:04:20.053Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:04:20.055Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:04:20.064Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:20.066Z SERIAL « 0x0107013b9192927f2c                                                 (9 bytes)
2023-07-19T14:04:20.068Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:20.078Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -110 dBm
channel 2: -110 dBm
2023-07-19T14:04:31.430Z DRIVER   destroying driver instance...
2023-07-19T14:04:31.503Z DRIVER   driver instance destroyed
2023-07-19T14:04:31.558Z DRIVER   ███████╗ ██╗    ██╗  █████╗  ██╗   ██╗ ███████╗             ██╗ ███████╗
╚══███╔╝ ██║    ██║ ██╔══██╗ ██║   ██║ ██╔════╝             ██║ ██╔════╝
███╔╝  ██║ █╗ ██║ ███████║ ██║   ██║ █████╗   █████╗      ██║ ███████╗
███╔╝   ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝   ╚════╝ ██   ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║  ██║  ╚████╔╝  ███████╗        ╚█████╔╝ ███████║
╚══════╝  ╚══╝╚══╝  ╚═╝  ╚═╝   ╚═══╝   ╚══════╝         ╚════╝  ╚══════╝
2023-07-19T14:04:31.559Z DRIVER   version 11.5.0
2023-07-19T14:04:31.559Z DRIVER
2023-07-19T14:04:31.559Z DRIVER   starting driver...
2023-07-19T14:04:31.559Z DRIVER   opening serial port /dev/ttyUSB0
2023-07-19T14:04:31.573Z DRIVER   serial port opened
2023-07-19T14:04:31.574Z SERIAL » 0x15                                                                 (1 bytes)
2023-07-19T14:04:32.585Z DRIVER   loading configuration...
2023-07-19T14:04:32.598Z CONFIG   Using external configuration dir /data/db
2023-07-19T14:04:32.598Z CONFIG   version 11.5.0
2023-07-19T14:04:34.181Z DRIVER   beginning interview...
2023-07-19T14:04:34.183Z DRIVER   added request handler for AddNodeToNetwork (0x4a)...
1 registered
2023-07-19T14:04:34.183Z DRIVER   added request handler for RemoveNodeFromNetwork (0x4b)...
1 registered
2023-07-19T14:04:34.184Z DRIVER   added request handler for ReplaceFailedNode (0x63)...
1 registered
2023-07-19T14:04:34.184Z CNTRLR   querying controller IDs...
2023-07-19T14:04:34.192Z SERIAL » 0x01030020dc                                                         (5 bytes)
2023-07-19T14:04:34.193Z DRIVER » [REQ] [GetControllerId]
2023-07-19T14:04:34.199Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:34.200Z SERIAL « 0x01080120f11f556e0102                                              (10 bytes)
2023-07-19T14:04:34.202Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:34.204Z DRIVER « [RES] [GetControllerId]
home ID:     0xf11f556e
own node ID: 1
2023-07-19T14:04:34.207Z CNTRLR   received controller IDs:
home ID:     0xf11f556e
own node ID: 1
2023-07-19T14:04:34.207Z CNTRLR   querying API capabilities...
2023-07-19T14:04:34.211Z SERIAL » 0x01030007fb                                                         (5 bytes)
2023-07-19T14:04:34.212Z DRIVER » [REQ] [GetSerialApiCapabilities]
2023-07-19T14:04:34.222Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:34.225Z SERIAL « 0x012b01070713027a0001000df6873e88cf2bc04ffbd7fde01700008000808680b (45 bytes)
a0500700000ee7fc0000000a0
2023-07-19T14:04:34.232Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:34.233Z DRIVER « [RES] [GetSerialApiCapabilities]
payload: 0x0713027a0001000df6873e88cf2bc04ffbd7fde01700008000808680ba0500700
000ee7fc0000000
2023-07-19T14:04:34.236Z CNTRLR   received API capabilities:
firmware version:    7.19
manufacturer ID:     0x027a
product type:        0x01
product ID:          0x0d
supported functions:
· GetSerialApiInitData (0x02)
· SetApplicationNodeInformation (0x03)
· GetControllerCapabilities (0x05)
· SetSerialApiTimeouts (0x06)
· GetSerialApiCapabilities (0x07)
· SoftReset (0x08)
· GetProtocolVersion (0x09)
· SerialAPIStarted (0x0a)
· SerialAPISetup (0x0b)
· SetRFReceiveMode (0x10)
· FUNC_ID_ZW_SEND_NODE_INFORMATION (0x12)
· SendData (0x13)
· SendDataMulticast (0x14)
· GetControllerVersion (0x15)
· SendDataAbort (0x16)
· FUNC_ID_ZW_GET_RANDOM (0x1c)
· GetControllerId (0x20)
· UNKNOWN_FUNC_MEMORY_GET_BYTE (0x21)
· UNKNOWN_FUNC_MEMORY_PUT_BYTE (0x22)
· UNKNOWN_FUNC_MEMORY_GET_BUFFER (0x23)
· UNKNOWN_FUNC_MEMORY_PUT_BUFFER (0x24)
· EnterBootloader (0x27)
· UNKNOWN_FUNC_UNKNOWN_0x28 (0x28)
· GetNVMId (0x29)
· ExtNVMReadLongBuffer (0x2a)
· ExtNVMReadLongByte (0x2c)
· NVMOperations (0x2e)
· undefined (0x37)
· undefined (0x38)
· UNKNOWN_FUNC_ClearNetworkStats (0x39)
· UNKNOWN_FUNC_GetNetworkStats (0x3a)
· GetBackgroundRSSI (0x3b)
· undefined (0x3c)
· UNKNOWN_FUNC_RemoveNodeIdFromNetwork (0x3f)
· GetNodeProtocolInfo (0x41)
· HardReset (0x42)
· FUNC_ID_ZW_REPLICATION_COMMAND_COMPLETE (0x44)
· FUNC_ID_ZW_REPLICATION_SEND_DATA (0x45)
· AssignReturnRoute (0x46)
· DeleteReturnRoute (0x47)
· RequestNodeNeighborUpdate (0x48)
· ApplicationUpdateRequest (0x49)
· AddNodeToNetwork (0x4a)
· RemoveNodeFromNetwork (0x4b)
· FUNC_ID_ZW_CONTROLLER_CHANGE (0x4d)
· AssignPriorityReturnRoute (0x4f)
· FUNC_ID_ZW_SET_LEARN_MODE (0x50)
· AssignSUCReturnRoute (0x51)
· FUNC_ID_ZW_REQUEST_NETWORK_UPDATE (0x53)
· SetSUCNodeId (0x54)
· DeleteSUCReturnRoute (0x55)
· GetSUCNodeId (0x56)
· UNKNOWN_FUNC_SEND_SUC_ID (0x57)
· AssignPrioritySUCReturnRoute (0x58)
· FUNC_ID_ZW_EXPLORE_REQUEST_INCLUSION (0x5e)
· undefined (0x5f)
· RequestNodeInfo (0x60)
· RemoveFailedNode (0x61)
· IsFailedNode (0x62)
· ReplaceFailedNode (0x63)
· undefined (0x65)
· GetRoutingInfo (0x80)
· UNKNOWN_FUNC_LOCK_ROUTE_RESPONSE (0x90)
· GetPriorityRoute (0x92)
· SetPriorityRoute (0x93)
· UNKNOWN_FUNC_UNKNOWN_0x98 (0x98)
· FUNC_ID_SERIAL_API_SLAVE_NODE_INFO (0xa0)
· FUNC_ID_ZW_SEND_SLAVE_NODE_INFO (0xa2)
· FUNC_ID_ZW_SET_SLAVE_LEARN_MODE (0xa4)
· FUNC_ID_ZW_GET_VIRTUAL_NODES (0xa5)
· FUNC_ID_ZW_IS_VIRTUAL_NODE (0xa6)
· BridgeApplicationCommand (0xa8)
· SendDataBridge (0xa9)
· SendDataMulticastBridge (0xab)
· UNKNOWN_FUNC_GET_LIBRARY_TYPE (0xbd)
· UNKNOWN_FUNC_SEND_TEST_FRAME (0xbe)
· UNKNOWN_FUNC_GET_PROTOCOL_STATUS (0xbf)
· UNKNOWN_FUNC_UNKNOWN_0xD2 (0xd2)
· UNKNOWN_FUNC_UNKNOWN_0xD3 (0xd3)
· UNKNOWN_FUNC_UNKNOWN_0xD4 (0xd4)
· undefined (0xd6)
· undefined (0xd7)
· undefined (0xd8)
· Shutdown (0xd9)
· undefined (0xda)
· undefined (0xdb)
· undefined (0xdc)
· undefined (0xdd)
· undefined (0xde)
· undefined (0xdf)
· undefined (0xe7)
· undefined (0xe8)
2023-07-19T14:04:34.253Z CNTRLR   Performing soft reset...
2023-07-19T14:04:34.258Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:04:34.259Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:04:34.263Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:04:34.474Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:04:34.475Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:34.477Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:04:34.478Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:04:34.479Z DRIVER     no handlers registered!
2023-07-19T14:04:35.262Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-07-19T14:04:35.364Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:04:35.365Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:04:35.371Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:04:35.581Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:04:35.583Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:35.585Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:04:35.586Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:04:35.587Z DRIVER     no handlers registered!
2023-07-19T14:04:36.369Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-07-19T14:04:37.471Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:04:37.472Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:04:37.478Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:04:37.688Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:04:37.689Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:37.690Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:04:37.691Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:04:37.691Z DRIVER     no handlers registered!
2023-07-19T14:04:38.481Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
0)
2023-07-19T14:04:38.481Z CNTRLR   Waiting for the controller to reconnect...
2023-07-19T14:04:39.983Z CNTRLR   Waiting for the Serial API to start...
2023-07-19T14:04:44.984Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
nds...
2023-07-19T14:04:44.992Z SERIAL » 0x01030015e9                                                         (5 bytes)
2023-07-19T14:04:44.993Z DRIVER » [REQ] [GetControllerVersion]
2023-07-19T14:04:44.999Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.001Z SERIAL « 0x011001155a2d5761766520372e313900079f                              (18 bytes)
2023-07-19T14:04:45.002Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.003Z DRIVER « [RES] [GetControllerVersion]
payload: 0x5a2d5761766520372e31390007
2023-07-19T14:04:45.012Z CNTRLR   Serial API responded
2023-07-19T14:04:45.028Z CNTRLR   querying version info...
2023-07-19T14:04:45.032Z SERIAL » 0x01030015e9                                                         (5 bytes)
2023-07-19T14:04:45.033Z DRIVER » [REQ] [GetControllerVersion]
2023-07-19T14:04:45.039Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.041Z SERIAL « 0x011001155a2d5761766520372e313900079f                              (18 bytes)
2023-07-19T14:04:45.042Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.043Z DRIVER « [RES] [GetControllerVersion]
payload: 0x5a2d5761766520372e31390007
2023-07-19T14:04:45.046Z CNTRLR   received version info:
controller type: Bridge Controller
library version: Z-Wave 7.19
2023-07-19T14:04:45.046Z CNTRLR   querying protocol version info...
2023-07-19T14:04:45.051Z SERIAL » 0x01030009f5                                                         (5 bytes)
2023-07-19T14:04:45.052Z DRIVER » [REQ] [GetProtocolVersion]
2023-07-19T14:04:45.059Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.065Z SERIAL « 0x011901090007130200be3030303030303030303030303030303046            (27 bytes)
2023-07-19T14:04:45.066Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.068Z DRIVER « [RES] [GetProtocolVersion]
payload: 0x0007130200be30303030303030303030303030303030
2023-07-19T14:04:45.071Z CNTRLR   received protocol version info:
protocol type:             Z-Wave
protocol version:          7.19.2
appl. framework build no.: 190
git commit hash:           30303030303030303030303030303030
2023-07-19T14:04:45.074Z CNTRLR   supported Z-Wave features:
· SmartStart
2023-07-19T14:04:45.074Z CNTRLR   querying controller capabilities...
2023-07-19T14:04:45.079Z SERIAL » 0x01030005f9                                                         (5 bytes)
2023-07-19T14:04:45.079Z DRIVER » [REQ] [GetControllerCapabilities]
2023-07-19T14:04:45.084Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.086Z SERIAL « 0x010401053cc3                                                       (6 bytes)
2023-07-19T14:04:45.087Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.089Z DRIVER « [RES] [GetControllerCapabilities]
payload: 0x3c
2023-07-19T14:04:45.091Z CNTRLR   received controller capabilities:
controller role:      primary
is the SUC:           true
started this network: true
SIS is present:       true
was real primary:     true
2023-07-19T14:04:45.092Z CNTRLR   querying serial API setup capabilities...
2023-07-19T14:04:45.100Z SERIAL » 0x0104000b01f1                                                       (6 bytes)
2023-07-19T14:04:45.101Z DRIVER » [REQ] [SerialAPISetup]
command: GetSupportedCommands
payload: 0x01
2023-07-19T14:04:45.108Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.110Z SERIAL « 0x0116010b01ff9f8007800000008000000000000000800085                  (24 bytes)
2023-07-19T14:04:45.112Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.114Z DRIVER « [RES] [SerialAPISetup]
command: GetSupportedCommands
payload: 0xff9f80078000000080000000000000008000
2023-07-19T14:04:45.117Z CNTRLR   supported serial API setup commands:
· GetSupportedCommands
· SetTxStatusReport
· SetLRMaximumTxPower
· SetPowerlevel
· GetLRMaximumTxPower
· GetPowerlevel
· GetMaximumPayloadSize
· GetLRMaximumPayloadSize
· SetPowerlevel16Bit
· GetPowerlevel16Bit
· GetRFRegion
· SetRFRegion
· SetNodeIDType
2023-07-19T14:04:45.118Z CNTRLR   Enabling TX status report...
2023-07-19T14:04:45.124Z SERIAL » 0x0105000b02ff0c                                                     (7 bytes)
2023-07-19T14:04:45.125Z DRIVER » [REQ] [SerialAPISetup]
command: SetTxStatusReport
enabled: true
2023-07-19T14:04:45.129Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.131Z SERIAL « 0x0105010b0201f3                                                     (7 bytes)
2023-07-19T14:04:45.132Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.134Z DRIVER « [RES] [SerialAPISetup]
command: SetTxStatusReport
success: true
2023-07-19T14:04:45.137Z CNTRLR   Enabling TX status report successful...
2023-07-19T14:04:45.138Z CNTRLR   Querying configured RF region...
2023-07-19T14:04:45.147Z SERIAL » 0x0104000b20d0                                                       (6 bytes)
2023-07-19T14:04:45.148Z DRIVER » [REQ] [SerialAPISetup]
command: GetRFRegion
payload: 0x20
2023-07-19T14:04:45.153Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.155Z SERIAL « 0x0105010b2001d1                                                     (7 bytes)
2023-07-19T14:04:45.156Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.157Z DRIVER « [RES] [SerialAPISetup]
command: GetRFRegion
region:  USA
2023-07-19T14:04:45.161Z CNTRLR   The controller is using RF region USA
2023-07-19T14:04:45.161Z CNTRLR   finding SUC...
2023-07-19T14:04:45.166Z SERIAL » 0x01030056aa                                                         (5 bytes)
2023-07-19T14:04:45.167Z DRIVER » [REQ] [GetSUCNodeId]
2023-07-19T14:04:45.172Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.174Z SERIAL « 0x0104015601ad                                                       (6 bytes)
2023-07-19T14:04:45.175Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.177Z DRIVER « [RES] [GetSUCNodeId]
payload: 0x01
2023-07-19T14:04:45.184Z CNTRLR   This is the SUC
2023-07-19T14:04:45.185Z CNTRLR   querying additional controller information...
2023-07-19T14:04:45.192Z SERIAL » 0x01030002fe                                                         (5 bytes)
2023-07-19T14:04:45.193Z DRIVER » [REQ] [GetSerialApiInitData]
2023-07-19T14:04:45.201Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.203Z SERIAL « 0x012501020a081d010000000000000000000000000000000000000000000000000 (39 bytes)
00000000700c0
2023-07-19T14:04:45.206Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.208Z DRIVER « [RES] [GetSerialApiInitData]
payload: 0x0a081d01000000000000000000000000000000000000000000000000000000000
700
2023-07-19T14:04:45.212Z CNTRLR   received additional controller information:
Z-Wave API version:         1 (official)
Z-Wave chip type:           EFR32ZG14 / ZGM130S
node type                   Controller
controller role:            primary
controller is the SIS:      true
controller supports timers: false
nodes in the network:       1
2023-07-19T14:04:45.248Z DRIVER   Cache file for homeId 0xf11f556e found, attempting to restore the network from
cache...
2023-07-19T14:04:45.283Z CNTRLR   [Node 001] Embedded device config loaded
2023-07-19T14:04:45.293Z DRIVER   Restoring the network from cache was successful!
2023-07-19T14:04:45.297Z CNTRLR   [Node 001] [Manufacturer Specific] manufacturerId: metadata updated
2023-07-19T14:04:45.300Z CNTRLR   [Node 001] [Manufacturer Specific] productType: metadata updated
2023-07-19T14:04:45.301Z CNTRLR   [Node 001] [Manufacturer Specific] productId: metadata updated
2023-07-19T14:04:45.302Z CNTRLR   [Node 001] [~] [Manufacturer Specific] manufacturerId: 634 => 634
2023-07-19T14:04:45.305Z CNTRLR   [Node 001] [~] [Manufacturer Specific] productType: 1 => 1
2023-07-19T14:04:45.306Z CNTRLR   [Node 001] [~] [Manufacturer Specific] productId: 13 => 13
2023-07-19T14:04:45.307Z CNTRLR   [Node 001] [Version] firmwareVersions: metadata updated
2023-07-19T14:04:45.309Z CNTRLR   [Node 001] [~] [Version] firmwareVersions: 7.19 => 7.19
2023-07-19T14:04:45.310Z CNTRLR   [Node 001] [Version] zWaveProtocolVersion: metadata updated
2023-07-19T14:04:45.311Z CNTRLR   [Node 001] [~] [Version] zWaveProtocolVersion: "7.19.2" => "7.19.2"
2023-07-19T14:04:45.312Z CNTRLR   [Node 001] [Version] sdkVersion: metadata updated
2023-07-19T14:04:45.313Z CNTRLR   [Node 001] [~] [Version] sdkVersion: "7.19.2" => "7.19.2"
2023-07-19T14:04:45.313Z CNTRLR   Interview completed
2023-07-19T14:04:45.315Z DRIVER   Network key for S0 configured, enabling S0 security manager...
2023-07-19T14:04:45.318Z DRIVER   At least one network key for S2 configured, enabling S2 security manager...
2023-07-19T14:04:45.326Z DRIVER   driver ready
2023-07-19T14:04:45.327Z DRIVER   Checking for configuration updates...
2023-07-19T14:04:45.380Z CNTRLR   [Node 001] The node is alive.
2023-07-19T14:04:45.400Z CNTRLR   [Node 001] The node is ready to be used
2023-07-19T14:04:45.401Z CNTRLR   All nodes are ready to be used
2023-07-19T14:04:45.491Z SERIAL » 0x0104000b13e3                                                       (6 bytes)
2023-07-19T14:04:45.492Z DRIVER » [REQ] [SerialAPISetup]
command: GetPowerlevel16Bit
payload: 0x13
2023-07-19T14:04:45.511Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.517Z SERIAL « 0x0108010b1300000000ee                                              (10 bytes)
2023-07-19T14:04:45.519Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.522Z DRIVER « [RES] [SerialAPISetup]
command:               GetPowerlevel16Bit
normal powerlevel:     0.0 dBm
output power at 0 dBm: 0.0 dBm
2023-07-19T14:04:45.531Z SERIAL » 0x0104000b20d0                                                       (6 bytes)
2023-07-19T14:04:45.532Z DRIVER » [REQ] [SerialAPISetup]
command: GetRFRegion
payload: 0x20
2023-07-19T14:04:45.537Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:45.539Z SERIAL « 0x0105010b2001d1                                                     (7 bytes)
2023-07-19T14:04:45.540Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:45.541Z DRIVER « [RES] [SerialAPISetup]
command: GetRFRegion
region:  USA
2023-07-19T14:04:45.654Z DRIVER   Usage statistics sent - next transmission scheduled in 23 hours.
2023-07-19T14:04:45.816Z DRIVER   No configuration update available...
2023-07-19T14:04:50.553Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:04:50.555Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:04:50.560Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:04:50.562Z SERIAL « 0x0107013b9094947f2d                                                 (9 bytes)
2023-07-19T14:04:50.563Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:04:50.565Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -112 dBm
channel 1: -108 dBm
channel 2: -108 dBm
2023-07-19T14:05:20.554Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:05:20.557Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:05:20.562Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:05:20.564Z SERIAL « 0x0107013b9193937f2c                                                 (9 bytes)
2023-07-19T14:05:20.566Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:05:20.569Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -109 dBm
channel 2: -109 dBm
2023-07-19T14:05:45.515Z SERIAL » 0x0105000b4000b1                                                     (7 bytes)
2023-07-19T14:05:45.518Z DRIVER » [REQ] [SerialAPISetup]
command: SetRFRegion
region:  Europe
2023-07-19T14:05:45.522Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:05:45.524Z SERIAL « 0x0105010b4001b1                                                     (7 bytes)
2023-07-19T14:05:45.526Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:05:45.531Z DRIVER « [RES] [SerialAPISetup]
command: SetRFRegion
success: true
2023-07-19T14:05:45.540Z CNTRLR   Performing soft reset...
2023-07-19T14:05:45.546Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:05:45.547Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:05:45.552Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:05:45.763Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:05:45.765Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:05:45.767Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:05:45.769Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:05:45.769Z DRIVER     no handlers registered!
2023-07-19T14:05:46.552Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-07-19T14:05:46.655Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:05:46.655Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:05:46.666Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:05:46.871Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:05:46.872Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:05:46.875Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:05:46.877Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:05:46.877Z DRIVER     no handlers registered!
2023-07-19T14:05:47.659Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-07-19T14:05:48.760Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:05:48.761Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:05:48.767Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:05:48.977Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:05:48.979Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:05:48.984Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:05:48.986Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:05:48.987Z DRIVER     no handlers registered!
2023-07-19T14:05:49.768Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
0)
2023-07-19T14:05:49.768Z CNTRLR   Waiting for the controller to reconnect...
2023-07-19T14:05:51.270Z CNTRLR   Waiting for the Serial API to start...
2023-07-19T14:05:54.774Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:05:54.775Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:05:54.780Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:05:54.784Z SERIAL « 0x0107013b9094947f2d                                                 (9 bytes)
2023-07-19T14:05:54.785Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:05:54.788Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -112 dBm
channel 1: -108 dBm
channel 2: -108 dBm
2023-07-19T14:05:56.271Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
nds...
2023-07-19T14:05:56.281Z SERIAL » 0x01030015e9                                                         (5 bytes)
2023-07-19T14:05:56.283Z DRIVER » [REQ] [GetControllerVersion]
2023-07-19T14:05:56.289Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:05:56.291Z SERIAL « 0x011001155a2d5761766520372e313900079f                              (18 bytes)
2023-07-19T14:05:56.291Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:05:56.295Z DRIVER « [RES] [GetControllerVersion]
payload: 0x5a2d5761766520372e31390007
2023-07-19T14:05:56.298Z CNTRLR   Serial API responded
2023-07-19T14:05:56.304Z SERIAL » 0x0104000b20d0                                                       (6 bytes)
2023-07-19T14:05:56.305Z DRIVER » [REQ] [SerialAPISetup]
command: GetRFRegion
payload: 0x20
2023-07-19T14:05:56.311Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:05:56.312Z SERIAL « 0x0105010b2001d1                                                     (7 bytes)
2023-07-19T14:05:56.313Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:05:56.314Z DRIVER « [RES] [SerialAPISetup]
command: GetRFRegion
region:  USA
2023-07-19T14:06:24.776Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:06:24.778Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:06:24.783Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:06:24.785Z SERIAL « 0x0107013b9090907f2d                                                 (9 bytes)
2023-07-19T14:06:24.786Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:06:24.789Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -112 dBm
channel 1: -112 dBm
channel 2: -112 dBm
2023-07-19T14:06:54.778Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:06:54.780Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:06:54.785Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:06:54.787Z SERIAL « 0x0107013b9192927f2c                                                 (9 bytes)
2023-07-19T14:06:54.788Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:06:54.791Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -110 dBm
channel 2: -110 dBm
2023-07-19T14:07:24.775Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:07:24.776Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:07:24.782Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:07:24.783Z SERIAL « 0x0107013b9092927f2d                                                 (9 bytes)
2023-07-19T14:07:24.784Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:07:24.787Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -112 dBm
channel 1: -110 dBm
channel 2: -110 dBm
2023-07-19T14:07:54.777Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:07:54.779Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:07:54.784Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:07:54.785Z SERIAL « 0x0107013b9095957f2d                                                 (9 bytes)
2023-07-19T14:07:54.786Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:07:54.790Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -112 dBm
channel 1: -107 dBm
channel 2: -107 dBm
2023-07-19T14:08:24.775Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:08:24.778Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:08:24.784Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:08:24.787Z SERIAL « 0x0107013b9294947f2f                                                 (9 bytes)
2023-07-19T14:08:24.790Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:08:24.796Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -110 dBm
channel 1: -108 dBm
channel 2: -108 dBm
2023-07-19T14:08:51.722Z SERIAL » 0x0105000b4000b1                                                     (7 bytes)
2023-07-19T14:08:51.724Z DRIVER » [REQ] [SerialAPISetup]
command: SetRFRegion
region:  Europe
2023-07-19T14:08:51.729Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:08:51.730Z SERIAL « 0x0105010b4001b1                                                     (7 bytes)
2023-07-19T14:08:51.731Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:08:51.735Z DRIVER « [RES] [SerialAPISetup]
command: SetRFRegion
success: true
2023-07-19T14:08:51.738Z CNTRLR   Performing soft reset...
2023-07-19T14:08:51.746Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:08:51.747Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:08:51.751Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:08:51.962Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:08:51.963Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:08:51.965Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:08:51.966Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:08:51.966Z DRIVER     no handlers registered!
2023-07-19T14:08:52.752Z CNTRLR   Failed to execute controller command after 1/3 attempts. Scheduling next try i
n 100 ms.
2023-07-19T14:08:52.855Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:08:52.856Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:08:52.862Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:08:53.073Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:08:53.074Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:08:53.078Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:08:53.081Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:08:53.081Z DRIVER     no handlers registered!
2023-07-19T14:08:53.861Z CNTRLR   Failed to execute controller command after 2/3 attempts. Scheduling next try i
n 1100 ms.
2023-07-19T14:08:54.964Z DRIVER » [REQ] [SoftReset]
2023-07-19T14:08:54.965Z SERIAL » 0x01030008f4                                                         (5 bytes)
2023-07-19T14:08:54.971Z SERIAL « [DISCARDED] invalid data 0xe6                                        (1 bytes)
2023-07-19T14:08:55.181Z SERIAL « 0x0113000a0700010207095e748a568f989f6c5500ab                        (21 bytes)
2023-07-19T14:08:55.183Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:08:55.186Z DRIVER « [REQ] [SerialAPIStarted]
wake up reason:        SoftwareReset
watchdog enabled:      false
generic device class:  0x02
specific device class: 0x07
always listening:      false
supports Long Range:   false
2023-07-19T14:08:55.188Z DRIVER   handling request SerialAPIStarted (10)
2023-07-19T14:08:55.189Z DRIVER     no handlers registered!
2023-07-19T14:08:55.973Z CNTRLR   Soft reset failed: Timeout while waiting for an ACK from the controller (ZW020
0)
2023-07-19T14:08:55.974Z CNTRLR   Waiting for the controller to reconnect...
2023-07-19T14:08:57.475Z CNTRLR   Waiting for the Serial API to start...
2023-07-19T14:09:00.979Z SERIAL » 0x0103003bc7                                                         (5 bytes)
2023-07-19T14:09:00.980Z DRIVER » [REQ] [GetBackgroundRSSI]
2023-07-19T14:09:00.986Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:09:00.988Z SERIAL « 0x0107013b9191917f2c                                                 (9 bytes)
2023-07-19T14:09:00.989Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:09:00.991Z DRIVER « [RES] [GetBackgroundRSSI]
channel 0: -111 dBm
channel 1: -111 dBm
channel 2: -111 dBm
2023-07-19T14:09:02.477Z CNTRLR   Did not receive notification that Serial API has started, checking if it respo
nds...
2023-07-19T14:09:02.488Z SERIAL » 0x01030015e9                                                         (5 bytes)
2023-07-19T14:09:02.489Z DRIVER » [REQ] [GetControllerVersion]
2023-07-19T14:09:02.495Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:09:02.497Z SERIAL « 0x011001155a2d5761766520372e313900079f                              (18 bytes)
2023-07-19T14:09:02.498Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:09:02.500Z DRIVER « [RES] [GetControllerVersion]
payload: 0x5a2d5761766520372e31390007
2023-07-19T14:09:02.507Z CNTRLR   Serial API responded
2023-07-19T14:09:02.512Z SERIAL » 0x0104000b20d0                                                       (6 bytes)
2023-07-19T14:09:02.513Z DRIVER » [REQ] [SerialAPISetup]
command: GetRFRegion
payload: 0x20
2023-07-19T14:09:02.517Z SERIAL « [ACK]                                                                   (0x06)
2023-07-19T14:09:02.519Z SERIAL « 0x0105010b2001d1                                                     (7 bytes)
2023-07-19T14:09:02.520Z SERIAL » [ACK]                                                                   (0x06)
2023-07-19T14:09:02.521Z DRIVER « [RES] [SerialAPISetup]
command: GetRFRegion
region:  USA
``

Thanks for your support.

authors: AlCalzone MarcusSteen

repo: zwave-js/node-zwave-js


text:
feat: Zniffer polishing

This PR adds:

a special frame type to distinguish Broadcast frames (= non-routed singlecast with broadcast Node ID)
an optional parameter for znifferProtocolDataRateToString to omit the protocol name
an option to limit the number of captured frames kept in memory

@zwave-js-bot automerge

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
chore(docker): docker labels opencontainers

Fixes #257

@chrisns I would like to set some env vars in stage 1 and then use them on last stage. How could I do this?

@chrisns I would like to set some env vars in stage 1 and then use them on last stage. How could I do this?

Pull Request Test Coverage Report for Build 493843381

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 23.579%

Totals

Change from base Build 493742410:
0.0%

Covered Lines:
1958

Relevant Lines:
8483

💛  - Coveralls

Pull Request Test Coverage Report for Build 493843381

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 23.579%

Totals

Change from base Build 493742410:
0.0%

Covered Lines:
1958

Relevant Lines:
8483

💛  - Coveralls

Closed in favor of #266

Closed in favor of #266

authors: coveralls robertsLando


text:
Join forces with zxing-cpp?

Hi there. Apologies in advance if someone thinks the following proposal is inappropriate.
I'm the maintainer of zxing-cpp. Since this PR we have a wrapper for iOS. The project has been ported to c++ from the Java version about 4 years ago but has been improved/rewritten substantially over the years. Depending on the use case it is now 2x to 10x faster than the original and has improved detection capabilities as well. Glancing over the open issues an PR list here, I estimate that the following issues would go away by switching to zxing-cpp: #470, #483,  #485, #498, #501, #567, #517, #524, #570.
It seems that this project here is partly abandoned (based on the date of the last commit) but quite a few people are using/working on this port. I'd therefore like to invite anyone who is interested to give zxing-cpp a try and if you find something is lacking with the new wrapper, please let me know. I'd love to help consolidate the rather fragmented landscape of zxing ports and bring the community closer together working on one solution instead of fixing issues multiple times in different code bases.

@axxel yeah, I wanted to rewrite the ObjC port with Swift some while ago but didn't find the time to do so. I fixed some bugs and as the original zxing is kind of dead, I tried to port all the outstanding changes from zxing to this objc port. I succeeded in doing so but keeping up with issues and bugs did not work out for me. With @Liftric we started playing around with the cpp port and actually it is super fast and convenient for us to use. I don't really see any point in either rewriting the ObjC port to Swift or cleaning this repo up. You made awesome progress and I believe it is more meaningful to support your port instead of this. I will add a remark to this repos README and archive it in a couple of months.

@axxel I will put a small hint on the top of the README to redirect people to your project, which makes sense the most IMHO.

@axxel with https://github.com/zxing-cpp/zxing-cpp/pull/630 the zxing-cpp project should be fully working and could replace this one. There is still room for a bit more work on the iOS wrapper in terms of documentation and feature richness but it is already a noteworthy replacement.
After this PR is merged and released, I would invest a bit of time in some README enhancements in zxing-cpp and add a remark to this repository (and probably in the near future archive it). It can still be taken over if somebody is interested in maintaining that.

@benjohnde and the others:
I may have another reason why you would want to switch from this ObjC variant to the C++ variant:
Long story:
We have many UseCases where we have to deal with 2D barcodes (especially DataMatrix) that contain binary data. (Especially for the purpose of VDS - Visible Digital Seals)
I have noticed that the zxing-objc has problems reading these codes with binary payloads correctly. The dangerous thing is that scanning works, but unfortunately there is simply a complete block of data missing in between the decoded payload.
We noticed this problem with one of our older apps in which we have still used zxing-objc. But since we were already in the process of switching to zxing-cpp anyway, we "solved" the problem by throwing out zxing-objc completely instead of looking for the error here for a long time.
But the bottom line is that there are still problems somewhere in zxing-objc when processing binary barcodes.
You can try it out for yourself:

This VDS contains the binary raw data:
1a)
E75F9D58C54785D6ADC087AA322CBBF3EC7C9AB447E7B855F482149143BE6E0C90267614E9A432CE15DE8E1FC0497A10EFEA606709E4332153EF73B3ADEC0F9AC4A3CE46028366F27568B3F5D7B6FE21514639E7ED4016A0A92A7262AB2DDDBA94F237F1AE6CE2EE874406F14E6F782DDB5065E5FDB6D9895E7381FBE0336381FCEE4B4D328E5A305DB3D73E7785D651137A6E1E1009C3819D34CA61F78F26BC53E98018AE45DB720AA037CD64FA
1b) --> after correct datamatrix decoding this will have the payload bytes:
DC01D9C56D296AE819A699FDF799FDF77F04010C474E58504D34513650594748020A4A6F686E20536D69746803034DB293041139383220526567656E742053747265657405105065746572626F726F75676820504538FF4034A79345A053405AA1E6AE5E82A9D2B2292C5480D59D289CBBD3B3321D9FC3506AAA29A286D5932DB69BF8BF2B7B4178B84F109E70138C472C592A89A3FF6387
But zxing-objc gives as result in _result.rawBytes:
2a)
E75F9D58C54785D6ADC087AA322CBBF3EC7C9AB447E7B855F482149143BE6EC90267614E9A432CE15DE8E1FC0497A10EFEA60679E4332153EF73B3ADECF9AC4A3CE4628366F27568B3F5D7B6FE21514639E7ED4016A0A92A7262AB2DDDBA94F237F1AE6CE2EE87446F14E6F782DDB5065E5FDB6D9895E7381FBE0336381FCEE4B4D328E5A305DB3D73E7785D651137A6E1E109C3819D34CA61F78F26BC53E98018AE45DB72AA037CD64FA
2b) --> and after datamatrix decoding this will have the payload bytes:
DC01D9C56D296AE819A699FDF799FDF77F04010C474E58504D34513650594748020A4A6F686E20536D69746803034DB2930411FF4034A79345A053405AA1E6AE5E82A9D2B2292C5480D59D289CBBD3B3321D9FC3506AAA29A286D5932DB69BF8BF2B7B4178B84F109E70138C472C592A89A3FF6387
The strange thing about this is that both the start range and the end range are the same, only one data block is missing in between, which of course makes the result from zxing-objc useless.
You could dive really deep into it now and it would certainly be an interesting journey, but the effort is too high for me right now, given that our decision in favor of zxing-cpp had already been made beforehand anyway.

source: gharchive/issue

authors: alexmanzer axxel benjohnde

repo: zxingify/zxingify-objc


text:
Create learning.md

[ ] geemap & duckdb course
[ ] SQL Language basic & PostGIS
[ ] R language learning w/ census data and spatial analysis
[ ] ESRI conference
[ ] Climate AI revisit
[ ] ESRI product learning (revisit)
[ ] Graphic design basic

In progress


text:
【Feature request】- outline of code (at least common used types like markdown, c/c++, python, etc)

[Feature request description]
A sideabar showing the headlines/structure of current code/text file.
[Why]
When browsing through a long text file (e.g., markdown type), it's painful to locate and navigate. An outline of contents at sidebar would greatly improve the efficiency.
[Reference]
https://github.com/hedyhli/outline.nvim?tab=readme-ov-file
[Appearing like this]

Thank you very much for the great work.

Glad to know that. Thanks a lot.

repo: zyedidia/micro


text:
handle all rune-keys.

if the key is a rune-key and its not handled by a commandbinding,
process the key even if the modifiers differ from shift.
this fixes issue #310

Is this the same as #312?

Looks the same. Only with differences I can spot:

bool variable is called "handled" instead of "isBinding"
my PR is based on a newer version of the code which includes macros.

#312 has been merged so I'll close this.

authors: boombuler zyedidia


text:
🛑 UM300 at Home is down

In bcba979, UM300 at Home (home.$DOMAIN_CN) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UM300 at Home is back up in adf64db after 5 minutes.

repo: zzc-tongji/upptime


text:
Metro bundle does not start after installing react-native-readium

@salomon16 you're going to need to provide a reproduction. Things work for me so I suspect it's something to do with your project.


text:
Add Example for SSL.

Added in #6.


text:
ABIS updates and new NSL pattern

Deployed (with guidance from Richard!)

authors: gward-ardc nicholascar

repo: AGLDWG/pid-proxy


text:
Use guid for all primitives

Ready for merge.

repo: ALIGN-analoglayout/ALIGN-public


text:
Added sort asc by name to print commands

Codecov Report

Merging #6 (058474b) into main (2dc1d82) will decrease coverage by 0.21%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   91.92%   91.70%   -0.22%
==========================================
  Files          19       19
  Lines         421      422       +1
==========================================
  Hits          387      387
- Misses         34       35       +1

Impacted Files
Coverage Δ

src/Console/Command/AddScope.php
100.00% <ø> (ø)

src/Console/Command/DeactivateApiKey.php
100.00% <ø> (ø)

src/Console/Command/DeleteScope.php
100.00% <ø> (ø)

src/Console/Command/GenerateApiKey.php
100.00% <ø> (ø)

src/Console/Command/GenerateScope.php
100.00% <ø> (ø)

src/Console/Command/RemoveScope.php
100.00% <ø> (ø)

src/ServiceProvider.php
90.90% <75.00%> (-9.10%)
:arrow_down:

src/Console/Command/Command.php
100.00% <100.00%> (ø)

src/Console/Command/PrintApiKey.php
100.00% <100.00%> (ø)

src/Console/Command/PrintScope.php
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2dc1d82...058474b. Read the comment docs.

authors: TomHAnderson codecov-commenter

repo: API-Skeletons/laravel-doctrine-apikey


text:
add prefix for time and tag

Codecov Report

Merging #87 (9974cf4) into master (5532b91) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master      #87      +/-   ##
============================================
+ Coverage     70.79%   70.81%   +0.02%
  Complexity      401      401
============================================
  Files            72       72
  Lines          1260     1261       +1
  Branches        129      129
============================================
+ Hits            892      893       +1
  Misses          336      336
  Partials         32       32

Impacted Files
Coverage Δ

.../main/java/seedu/unify/logic/parser/CliSyntax.java
85.71% <100.00%> (+2.38%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5532b91...9974cf4. Read the comment docs.


text:
Add delete meeting feature in UG

Codecov Report

Merging #26 (60ab635) into master (cc8413f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #26   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cc8413f...60ab635. Read the comment docs.


text:
Fix Image & Add Links to UG

Codecov Report

Merging #191 (4658fb2) into master (0ad4c45) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #191   +/-   ##
=========================================
  Coverage     75.06%   75.06%
  Complexity      671      671
=========================================
  Files           100      100
  Lines          2049     2049
  Branches        243      243
=========================================
  Hits           1538     1538
  Misses          410      410
  Partials        101      101

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: anthonyhoth codecov-commenter


text:
Update view sequence diagram

Codecov Report
Base: 75.67% // Head: 75.67% // No change to project coverage :thumbsup:

Coverage data is based on head (7fb2b47) compared to base (84ca515).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #312   +/-   ##
=========================================
  Coverage     75.67%   75.67%
  Complexity      719      719
=========================================
  Files           108      108
  Lines          2064     2064
  Branches        255      255
=========================================
  Hits           1562     1562
  Misses          439      439
  Partials         63       63

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter fannyjian


text:
[TASK] get WBS for Bengaluru, India / Anil

wbs is B2PGQ003

repo: Accenture/sfmc-devtools-copado


text:
update packages

:white_check_mark: Build TheIdServer 3.0.1-fix-dependencies1-0006 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/a32fb0b12d by @)

authors: AppVeyorBot aguacongas

repo: Aguafrommars/TheIdServer


text:
OBS Scene

https://github.com/AlexHedley/poker-recording/blob/main/resources/OBS/README.md

repo: AlexHedley/poker-recording


text:
[Enhancement] make navbar responsive

@Aadarsh805 I would like to work on this issue. Can you assign this to me?

@Aadarsh805 I would like to work on this issue. Can you assign this to me?

Go ahead Ser !!

@Aman-Mandal bro how we gonna keep navbar on mobile, do we make another onclick sidebar or do we just push those links to the already made sidebar or we just make then small

I want to contribute please assign it to me

lets just make them small for now, we'll do it later

I'm on it.

I want to contribute please assign it to me

it's already assigned, you can try other issues or just wait 2-3 days if we don't get any response from the assignee, we'll assign it to you

@Aman-Mandal bro how we gonna keep navbar on mobile, do we make another onclick sidebar or do we just push those links to the already made sidebar or we just make then small

We can simply add the navbar links on our already present sidebar and hide the navbar on small screens

I'm on it.

I want to contribute please assign it to me

it's already assigned, you can try other issues or just wait 2-3 days if we don't get any response from the assignee, we'll assign it to you

alright Kunal, go ahead

I'm on it.

I want to contribute please assign it to me

it's already assigned, you can try other issues or just wait 2-3 days if we don't get any response from the assignee, we'll assign it to you

alright Kunal, go ahead

Is there a discord community or something where I can contact if I get some issues while developing?

@Aman-Mandal where should they contact us

We don't have a community yet, you can text us on twitter (given on readme) for now!! Will make a group/channel soon ✨

We don't have a community yet, you can text us on twitter (given on readme) for now!! Will make a group/channel soon ✨

Cool

repo: Aman-Mandal/groovy


text:
Create GUI .exe file for Mac and Linux

.exe files are a Windows-only format, and there is no direct equivalent for Linux or macOS.
With regards to macOS, I don't think it's realistic for us to be able to package it neatly without tripping up Apple's Gatekeeper system, which blocks unsigned executables from running, and setting up the proper developer tools for signing is beyond the scope of this project.
With regards to Linux: there are hundreds (if not thousands) of different Linux distros (short for distributions), with different ways of handling executable files. There are three options that I would consider workable:

AppImage:

Tries to be the direct equivalent to Windows .exe files for Linux, and work across distros
I personally avoid these whenever possible, because I prefer to be able to use a package manager tool to update software automatically, and these don't support that.
I have never dealt with these from a developer perspective, and only rarely dealt with them as a user.
I'd recommend against this, but it would still work.

Flatpak: packaging and distribution format for graphical programs on Linux systems.

Flatpak software is distributed through Flatpak repositories, and the Flatpak system takes care of installing updates.
I prefer this over AppImage.
I have far more experience with Flatpaks as a user, but have not dealt with them as a developer before.
I could theoretically set up a Flatpak repository to use for this project

DPKG (.deb): Unlike the other two I mentioned, .deb files are specific to the Debian distro, and its many forks, and their forks, and so on.

DPKGs can be distributed as standalone .deb files, or through online Advanced Package Tool (APT) repositories that take care of dependency management and the like.
I have an existing personal APT repository which we could use for distribution.
Unlike AppImages and Flatpaks, dependencies are separate packages, making the file size smaller
This would be my recommended way to package this for Linux, even though it limits it to the Debian family tree.

Thanks for the info, Eli. From what you mentioned, it sounds like we probably should write off making a macOS version, although I definitely want look into those options for Linux. I'm pretty unexperienced with Linux, just having done CSI 230 with it and not much else, but I'll do my best to figure everything out, and maybe we can go over it during our next meeting.

I already have the infrastructure to build and distribute DPKG files, so I can take care of that

Ok, sounds good. If you want, we can hold off from doing this until more features are added to the GUI. Otherwise you might have to update it a few times. Appreciate the help!


text:
Services: first build: abs added

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_d82itztxdz/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:128: missing_imports_or_run_test_py: output "_robotframework_tests": Python packages require imports or a python test file in tests.
clone/recipe/meta.yaml:38: wrong_output_script_key: It should be outputs/x/script, not outputs/x/build/script
===== Final Report: =====
2 Errors and 0 Warnings were found

authors: anaconda-pkg-build bkreider


text:
hvds

ssdgfbdgs

repo: AnastasiaSkoropad/homepage


text:
Update README.md

Pipelines as Code CI/test-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
17 seconds
noop-task


text:
refactor: add pyinstaller specs

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: AnotherStranger/rockbox-scrobbler


text:
Display the API data on the HTML browser page

I had to add a card from bootstrap to display the movie api response because I could not do it on the question mark div

authors: AntonScheving ChidoMunyanyi


text:
FE-73 Crear componente form CheckOut para pasarela de pagos

 FE-73 Crear componente form CheckOut para pasarela de pagos


text:
update docs

Codecov Report

Merging #2 (f2f3423) into main (7b8ec04) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main        #2   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            4         4
  Branches         1         1
=========================================
  Hits             4         4

Impacted Files
Coverage Δ

index.js
100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7b8ec04...f2f3423. Read the comment docs.

authors: Austionian codecov-commenter

repo: Austionian/last-method


text:
black

Hello @GaetanDu! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file autopycoin/asserts.py:

Line 38:80: E501 line too long (81 > 79 characters)
Line 39:80: E501 line too long (86 > 79 characters)
Line 43:80: E501 line too long (88 > 79 characters)
Line 69:80: E501 line too long (86 > 79 characters)

In the file autopycoin/dataset/generator.py:

Line 212:80: E501 line too long (109 > 79 characters)
Line 301:80: E501 line too long (87 > 79 characters)
Line 305:80: E501 line too long (83 > 79 characters)
Line 577:80: E501 line too long (83 > 79 characters)
Line 810:80: E501 line too long (96 > 79 characters)

In the file autopycoin/dataset/generator_test.py:

Line 205:80: E501 line too long (83 > 79 characters)
Line 574:50: E231 missing whitespace after ','
Line 1035:77: E231 missing whitespace after ','

In the file autopycoin/layers/__init__.py:

Line 5:80: E501 line too long (80 > 79 characters)

In the file autopycoin/layers/nbeats_layers.py:

Line 582:80: E501 line too long (88 > 79 characters)
Line 606:80: E501 line too long (88 > 79 characters)
Line 629:80: E501 line too long (82 > 79 characters)
Line 697:80: E501 line too long (82 > 79 characters)
Line 708:80: E501 line too long (86 > 79 characters)

In the file autopycoin/layers/nbeats_layers_test.py:

Line 218:47: E231 missing whitespace after ','
Line 477:80: E501 line too long (88 > 79 characters)

In the file autopycoin/losses/losses_test.py:

Line 18:80: E501 line too long (81 > 79 characters)
Line 27:80: E501 line too long (84 > 79 characters)
Line 153:80: E501 line too long (82 > 79 characters)
Line 160:80: E501 line too long (82 > 79 characters)
Line 170:80: E501 line too long (86 > 79 characters)
Line 179:80: E501 line too long (85 > 79 characters)
Line 188:80: E501 line too long (82 > 79 characters)
Line 197:80: E501 line too long (82 > 79 characters)
Line 207:80: E501 line too long (82 > 79 characters)

In the file autopycoin/models/nbeats.py:

Line 15:80: E501 line too long (86 > 79 characters)
Line 606:60: E203 whitespace before ':'
Line 642:80: E501 line too long (87 > 79 characters)
Line 916:80: E501 line too long (88 > 79 characters)
Line 918:80: E501 line too long (83 > 79 characters)

In the file autopycoin/models/nbeats_test.py:

Line 120:80: E501 line too long (81 > 79 characters)
Line 128:74: E231 missing whitespace after ','
Line 132:77: E231 missing whitespace after ','
Line 132:80: E501 line too long (81 > 79 characters)
Line 139:80: E501 line too long (88 > 79 characters)
Line 139:83: E231 missing whitespace after ','
Line 145:80: E501 line too long (88 > 79 characters)
Line 145:87: E231 missing whitespace after ','
Line 235:80: E231 missing whitespace after ','
Line 235:80: E501 line too long (82 > 79 characters)
Line 634:9: E731 do not assign a lambda expression, use a def

In the file autopycoin/utils/data_utils.py:

Line 182:80: E501 line too long (81 > 79 characters)
Line 213:80: E501 line too long (80 > 79 characters)

In the file autopycoin/utils/data_utils_test.py:

Line 100:80: E501 line too long (85 > 79 characters)
Line 103:80: E501 line too long (84 > 79 characters)
Line 103:82: E231 missing whitespace after ','
Line 109:80: E501 line too long (85 > 79 characters)
Line 112:80: E501 line too long (84 > 79 characters)
Line 112:82: E231 missing whitespace after ','
Line 118:80: E501 line too long (85 > 79 characters)
Line 121:80: E501 line too long (84 > 79 characters)
Line 121:82: E231 missing whitespace after ','
Line 127:80: E501 line too long (85 > 79 characters)
Line 130:80: E231 missing whitespace after ','
Line 130:80: E501 line too long (82 > 79 characters)
Line 138:80: E501 line too long (85 > 79 characters)
Line 153:80: E501 line too long (85 > 79 characters)
Line 162:80: E501 line too long (85 > 79 characters)
Line 171:80: E501 line too long (85 > 79 characters)
Line 180:80: E501 line too long (85 > 79 characters)
Line 198:80: E501 line too long (85 > 79 characters)
Line 245:80: E501 line too long (88 > 79 characters)

repo: AutocoinLab/autopycoin


text:
Push plugin to Gradle plugin portal

According to the instructions from https://docs.gradle.org/current/userguide/publishing_gradle_plugins.html

repo: AxenAPI/axenapi-gradle-plugin


text:
Make all friagetes have no limit

and all transport ships

repo: AzerothWarsLR/WarcraftLegacies


text:
feat(avm): keccack as blackbox

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5722  👈
#5707
#5706
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @fcarreiro and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

note_successful_decrypting_time_in_ms (8): 228 (+44%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
772
772
772

l1_rollup_calldata_gas
6,808
6,808 (+1%)
6,808

l1_rollup_execution_gas
587,289
587,289
587,289

l2_block_processing_time_in_ms
1,462 (+12%)
5,168 (+9%)
10,096 (+12%)

note_successful_decrypting_time_in_ms
:warning: 228 (+44%)
527 (+8%)
889 (-6%)

note_trial_decrypting_time_in_ms
27.2 (-56%)
33.6 (-66%)
109 (+58%)

l2_block_building_time_in_ms
10,972 (+4%)
39,021 (+3%)
77,345 (+4%)

l2_block_rollup_simulation_time_in_ms
10,774 (+3%)
38,331 (+3%)
75,990 (+4%)

l2_block_public_tx_process_time_in_ms
5,356 (+5%)
20,857 (+5%)
41,752 (+5%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
15,143 (+9%)
28,845 (+3%)

note_history_successful_decrypting_time_in_ms
1,169 (+3%)
2,234 (+4%)

note_history_trial_decrypting_time_in_ms
40.3 (+7%)
77.1 (+7%)

node_database_size_in_bytes
18,673,744
35,098,704

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
144 (-1%)
44,561
26,424

private-kernel-inner
155 (-1%)
72,188
26,424

private-kernel-ordering
108
51,090
39,297

base-parity
3,949 (+1%)
128
311

root-parity
1,062 (+1%)
1,244
311

base-rollup
13,371 (+1%)
110,820
957

root-rollup
49.6 (+1%)
4,551
821

public-kernel-app-logic
81.9 (-1%)
48,151
40,933

public-kernel-tail
121 (-1%)
53,644
7,385

merge-rollup
11.4 (+11%)
2,760
957

public-kernel-teardown
78.7 (+1%)
48,151
40,933

public-kernel-setup
77.9 (+1%)
48,151
40,933

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.9 (+9%)
17.6 (+10%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.635 (+9%)
0.545 (+10%)
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
51.6 (+12%)
80.0 (+10%)
260 (+13%)
498 (+11%)
972 (+11%)
1,941 (+12%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.529 (+13%)
0.494 (+10%)
0.474 (+13%)
0.466 (+11%)
0.463 (+12%)
0.465 (+12%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.7 (+10%)
119 (+11%)
374 (+10%)
731 (+10%)
1,452 (+11%)
2,896 (+11%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.530 (+11%)
0.535 (+11%)
0.509 (+10%)
0.505 (+11%)
0.504 (+11%)
0.505 (+11%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
66.8 (+9%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.585 (+9%)

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
41,005
528,889

Transaction size based on fee payment method

Metric
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
905
1,161
1,377

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
1,152 (+2%)
778 (+2%)
3,421 (+1%)

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
453 (+4%)
311 (+5%)
821 (+9%)
395 (+4%)
1,364 (+11%)
463 (+2%)

authors: AztecBot fcarreiro

repo: AztecProtocol/aztec-packages


text:
Terraform template for AzureSQLMIUse case

approved

authors: tiagobalabuch vitaled

repo: Azure/SQL-Migration-AzureSQL-PoC


text:
[bulk]Validation: metadata and absolute link changes

Docs Build status updates of commit 7918198:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/latest/core-management-readme.md
:warning:Warning
View (azure-java-stable)
Details

docs-ref-services/latest/core-http-okhttp-readme.md
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-services/latest/core-readme.md
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-services/latest/core-management-readme.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 10, Column 16: [Warning: ms-prod-technology-invalid - See documentation] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e710361:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/latest/core-http-okhttp-readme.md
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-services/latest/core-management-readme.md
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-services/latest/core-readme.md
:white_check_mark:Succeeded
View (azure-java-stable)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Global effort to fix build validation errors
@alzimmermsft
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!

Docs Build status updates of commit a175575:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/latest/core-http-okhttp-readme.md
:bulb:Suggestion
View (azure-java-stable)
Details

docs-ref-services/latest/core-management-readme.md
:bulb:Suggestion
View (azure-java-stable)
Details

docs-ref-services/latest/core-readme.md
:bulb:Suggestion
View (azure-java-stable)
Details

docs-ref-services/latest/core-http-okhttp-readme.md

Line 21, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 21, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.

docs-ref-services/latest/core-management-readme.md

Line 15, Column 72: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/azure/azure-resource-manager/management/' will be broken in isolated environments. Replace with a relative link.
Line 21, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 21, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.

docs-ref-services/latest/core-readme.md

Line 30, Column 5: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable' will be broken in isolated environments. Replace with a relative link.
Line 30, Column 5: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/java/azure/jdk/?view=azure-java-stable. Otherwise, remove the view parameter.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

repo: Azure/azure-docs-sdk-java