We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
These updates could be MUCH quicker:
2024-04-10T12:24:17.438Z DRIVER « [Node 256] [REQ] [BridgeApplicationCommand] │ RSSI: -75 dBm └─[Security2CCMessageEncapsulation] │ sequence number: 173 │ security class: S2_Authenticated └─[FirmwareUpdateMetaDataCCMetaDataReport] manufacturer id: 634 firmware id: 3 checksum: 0 firmware upgradable: true max fragment size: 128 hardware version: 1 2024-04-10T12:24:17.439Z CNTRLR [Node 256] Updating firmware (part 1 / 1)... 2024-04-10T12:24:17.439Z CNTRLR » [Node 256] Starting firmware update... 2024-04-10T12:24:17.455Z SERIAL » 0x012600a900010100189f035600f8f135affa69e002760978db21ecd51cf8f8b23 (40 bytes) 42500000000506b 2024-04-10T12:24:17.456Z DRIVER » [Node 256] [REQ] [SendDataBridge] │ source node id: 1 │ transmit options: 0x25 │ callback id: 80 └─[Security2CCMessageEncapsulation] │ sequence number: 86 │ security class: S2_Authenticated └─[FirmwareUpdateMetaDataCCRequestGet] manufacturer id: 0x027a firmware id: 0x03 checksum: 0x6796 firmware target: 0 fragment size: 28 activation: false
The text was updated successfully, but these errors were encountered:
Already fixed
Sorry, something went wrong.
No branches or pull requests
These updates could be MUCH quicker:
The text was updated successfully, but these errors were encountered: