# ZigBee and Z-Wave OTA updates are coming! **URL:** \ **Category:** Off-Topic\ **Created:** [March 15, 2026, 1:56am UTC](https://community.homey.app/t/zigbee-and-z-wave-ota-updates-are-coming/152498 "2026-03-15T01:56:05Z")\ **Posts on this page:** 6\ **Page:** 8
**Author:** ![Jocke\_Wallen](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jocke_wallen/32/76525_2.png) [@Jocke\_Wallen](https://community.homey.app/u/Jocke_Wallen)\ **Post date:** [September 4, 2026, 9:35am UTC](https://community.homey.app/t/zigbee-and-z-wave-ota-updates-are-coming/152498/145 "2026-09-04T09:35:59Z")
IKEA’s STYRBAR took some long time to start the update process. During that wait I pressed a random button like every 30 sec or so just to keep the button alive. When the process started (like 5-10%) I just put the device close to Homey and let the process continue over night. In the morning it was completed so how long the update took in the end I don’t know… ---
**Author:** ![Jorgen\_Westerberg](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jorgen_westerberg/32/74882_2.png) [@Jorgen\_Westerberg](https://community.homey.app/u/Jorgen_Westerberg)\ **Post date:** [September 7, 2026, 1:28pm UTC](https://community.homey.app/t/zigbee-and-z-wave-ota-updates-are-coming/152498/146 "2026-09-07T13:28:45Z")
I asked Schneider if they will support OTA (hope the will ), there replay din´t say mutch. " We are currently looking into whether we want to support OTA with our Homey app, but unfortunately a final decision has not been made as of now. As you can understand we have no insight as to when that decision might be made, but rest assured: when it becomes available you will automatically be presented with device updates (when available for your devices). " ---
**Author:** ![Pantera\_Ruber](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/pantera_ruber/32/7091_2.png) [@Pantera\_Ruber](https://community.homey.app/u/Pantera_Ruber)\ **Post date:** [September 8, 2026, 2:59pm UTC](https://community.homey.app/t/zigbee-and-z-wave-ota-updates-are-coming/152498/147 "2026-09-08T14:59:29Z")
After the latest update: Homey OS 13.5.0 and IKEA Home smart update: 2.10.4 things seems to have gotten a bit better. I am able to update both old switches and some air sensors. ---
**Author:** ![Kristof](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/kristof/32/79673_2.png) [@Kristof](https://community.homey.app/u/Kristof)\ **Post date:** [September 21, 2026, 8:40am UTC](https://community.homey.app/t/zigbee-and-z-wave-ota-updates-are-coming/152498/148 "2026-09-21T08:40:22Z")
any news on shelly wave OTA updates? ---
**Author:** ![c0d3x](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/c0d3x/32/84468_2.png) [@c0d3x](https://community.homey.app/u/c0d3x)\ **Post date:** [September 21, 2026, 2:18pm UTC](https://community.homey.app/t/zigbee-and-z-wave-ota-updates-are-coming/152498/149 "2026-09-21T14:18:10Z")
Hi @Doekse — a Z-Wave OTA question, with logs. Following up on your post #109: I bundled firmware files in my app (ID Lock Next, for ID Lock 150/202 Z-Wave modules), and the update is correctly offered — but it never starts. It fails instantly with “Failed to send initial FIRMWARE\_UPDATE\_MD\_REQUEST\_GET, cannot start firmware update”. It’s a send failure, not a timeout. Reproduced on three locks belonging to three users, at 4 metres through a wall and at 40 cm line-of-sight, so it isn’t the mesh. Lock/unlock, codes and settings all work normally on the same devices. What I can see from the app: - `node.firmwareId` is `null`, and the init summary shows `Firmware id: undefined`, while `COMMAND_CLASS_FIRMWARE_UPDATE_MD` is present. - These locks are S0, and `VERSION` / `FIRMWARE_UPDATE_MD` are secure-only, so I suspect the firmware id was never captured at inclusion. - When my app asks the lock itself with `FIRMWARE_MD_GET`, it answers immediately: manufacturer 883, firmware ID 769, checksum 30617. Afterwards `node.firmwareId` is still `null`. So the device has the data Homey needs and hands it over on request — it just doesn’t end up in the node record. Incidentally, 769 is 0x0301, which is the productType and productId already declared in my `driver.firmware.compose.json`. Two questions: 1. **Is a missing firmware id the reason the update can’t start** , and is there something I should do differently in the app or the manifest? 2. **Has anyone completed a Z-Wave OTA yet?** Every success I can find in this thread is Zigbee, so I may simply be first to hit this path. Filed with details and logs here: [Z-Wave OTA cannot start when the node record has no firmware id — "Failed to send initial FIRMWARE\_UPDATE\_MD\_REQUEST\_GET" · Issue #461 · athombv/homey-apps-sdk-issues · GitHub](https://github.com/athombv/homey-apps-sdk-issues/issues/461) ---
**Author:** ![cscheiene](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/cscheiene/32/58218_2.png) [@cscheiene](https://community.homey.app/u/cscheiene)\ **Post date:** [September 22, 2026, 10:49am UTC](https://community.homey.app/t/zigbee-and-z-wave-ota-updates-are-coming/152498/150 "2026-09-22T10:49:09Z")
Have completed zwave firmware update on Heatit devices successfully > **[GitHub - Heatit-Controls/no.thermofloor](https://github.com/Heatit-Controls/no.thermofloor)** > > Contribute to Heatit-Controls/no.thermofloor development by creating an account on GitHub. [Previous page](https://community.homey.app/t/zigbee-and-z-wave-ota-updates-are-coming/152498.md?page=7)