Your statement about Matter OTA is not entirely correct. It is true that you cannot perform a firmware update using the resources on the board. However, if you have paired a Matter device, you can connect it to the iOS Home app via “Advanced Settings > Share Matter Device,” for example. Firmware updates will now be downloaded automatically during operation.
(Tested with my Eve motion sensor during the FW update from v3.2.0 to 3.2.1)
BDW: I pointed this workaround out to Athom some time ago, but unfortunately did not receive any feedback. However, since you have better contact with Enschede than I do, you could point out this possibility to them again.
The question was: “does Homey Pro 2023 support OTA firmware update for Zigbee, Zwave, Matter”. The answer that @Dijker gave, “No”, is still 100% correct.
But like I said: it is. Homey cannot perform Matter OTA updates. You need other hardware for that, just like you need other hardware if you want to perform Zigbee or Z-Wave OTA updates.
Sure, and that’s great to mention, but it doesn’t invalidate @Dijker’s answer.
I think the way Chris has written it is correct and especially the hint that it is possible with additional hardware is very helpful. Especially for those like me who have not been dealing with smarthome for years and are very happy about simple “possibilities”.
Now that we’ve clarified the situation with Matter devices, I’d like to say a few words about firmware updates for Z-Wave devices.
With a workaround, it is also possible to update the firmware of Z-Wave devices without having to exclude them:
In addition, @Emile said in the Homey YouTube podcast #3 that it’s generally possible to update the firmware of Z-Wave devices via Homey, but this feature would have to be integrated by the app developers into their apps:
However, I have already been informed by two app developers that this is not true…
Athom has stated the same for Zigbee for many years, yet not even their own apps have implemented OTA-updates and there are no guidelines, examples or tips anywhere in the developer documentation on how to implement this. So I see this simply as “more marketing BS”.