I have my first Matter device, an Elko One thermostat. It shows that there’s a new firmware version available, but when I try to install it, it fails with a timeout, and then starts the install again, and again.
2026-07-10 22:05:16.858 INFO OtaSoftwar~derServer OTA Update to version 285240832 for Requestor @1:1 (5592dfad18ab009c84c6c619a5e8bfa62d3c26e8d8509cb86507253373682f22) is now Downloading (formerly Querying)
2026-07-10 22:05:16.860 INFO SoftwareUp~teManager OTA update status for node @1:1 changed to Downloading for version 285240832
2026-07-10 22:05:16.861 INFO BdxSession Starting BDX session exId: 61538 isSender: true isInitiator: false blobName: ota/105e.44a9.prod.285240832
2026-07-10 22:05:16.888 WARN MessageChannel Matter message to send to @1:1•78d8@udp://172.16.1.98:5540 is 4134bytes long, which is larger than the maximum allowed size of 1232. This only works if both nodes support it.
2026-07-10 22:05:17.232 WARN MessageChannel Matter message to send to @1:1•78d8@udp://172.16.1.98:5540 is 4134bytes long, which is larger than the maximum allowed size of 1232. This only works if both nodes support it.
2026-07-10 22:05:17.594 WARN MessageChannel Matter message to send to @1:1•78d8@udp://172.16.1.98:5540 is 4134bytes long, which is larger than the maximum allowed size of 1232. This only works if both nodes support it.
2026-07-10 22:05:17.821 INFO ClientEventEmitter Received event otaSoftwareUpdateRequestor.stateTransition on server-2-134b.@1:1 previousState: 2 newState: 4 reason: 1 targetSoftwareVersion: 285240832
2026-07-10 22:05:18.222 WARN MessageChannel Matter message to send to @1:1•78d8@udp://172.16.1.98:5540 is 4134bytes long, which is larger than the maximum allowed size of 1232. This only works if both nodes support it.
2026-07-10 22:05:19.080 WARN MessageChannel Matter message to send to @1:1•78d8@udp://172.16.1.98:5540 is 4134bytes long, which is larger than the maximum allowed size of 1232. This only works if both nodes support it.
2026-07-10 22:10:28.316 INFO OtaSoftwar~derServer OTA Update to version 285240832 for Requestor @1:1 (5592dfad18ab009c84c6c619a5e8bfa62d3c26e8d8509cb86507253373682f22) is now Cancelled (formerly Downloading)
2026-07-10 22:10:28.317 INFO SoftwareUp~teManager OTA update BDX cancelled for node @1:1, resetting for retry
2026-07-10 22:10:28.318 INFO SoftwareUp~teManager BDX transfer still active for node @1:1, skipping announcement
2026-07-10 22:10:28.320 WARN BdxProtocol Error processing BDX transfer: [peer-unresponsive] Peer is no longer responding to active session (timed out after 5m 11s)
at MessageExchange.#sentMessageAckFailure (/app/node_modules/@matter/protocol/src/protocol/MessageExchange.ts:622:29)
at MessageExchange.#retransmitMessage (/app/node_modules/@matter/protocol/src/protocol/MessageExchange.ts:768:22)
at StandardTimer.callback (/app/node_modules/@matter/protocol/src/protocol/MessageExchange.ts:759:36)
at Timeout.<anonymous> (/app/node_modules/@matter/general/src/time/StandardTime.ts:122:18)
at listOnTimeout (node:internal/timers:605:17)
at process.processTimers (node:internal/timers:541:7)
Why are we sending large packages? And is that even the problem here, or just a warning that has nothing to do with the problem?
I tried to add this to Google home too, but since there’s no way to force firmware update there, nothing has at least happened automatically within few days.
- Installation method Home Assistant OS
- Core 2026.7.1
- Supervisor 2026.06.2
- Operating System 18.1
- Frontend 20260624.4
- Matter Server version: 9.0.4