ZigBee and Z-Wave OTA updates are coming!

Off-Topic
145

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…

146

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).
"

147

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.

148

any news on shelly wave OTA updates?

149

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

150

Have completed zwave firmware update on Heatit devices successfully