So we (hopefully you) are going to ultimately update the ZW DB with we find works best. Also what I’m doing is not that advanced and is outlined on the link above. For these devices (since they already exist you can download the XML from the ZW github site. I use VSC to edit the XMLs. Anyway here are the files.
alrezwew1pm_0_0.xml (17.9 KB)
wavei4dc_0_0.xml (17.7 KB)
waveshutter_0_0.xml (28.5 KB)
In the first I added the controller to group 1 and the other 2 I took it out and increased the group 1 count to 2 or 3. This should correct the message from the OH core BaseThingHandler
Try setting on the code tab before the XML overlay, just to check.
I see why, the COMMAND_CLASS_FIRMWARE_UPDATE_MD_V1 is only on EP0.
Stepping back a bit. ZWave-JS-UI has paid developers from the HA pile of money and they have added all sorts workarounds for non-compliant ZW devices. IMO these Shelly devices are the problem, not anything with OH ZW. OTH-The OH ZW developer has a full-time job and does lots of work related international travel, is a volunteer and is several time zones away from OH Central. For me this is one of my retirement hobbies. I started OH many years ago because of the ZW binding, have contributed a PR or two and feel this is a way to give back. Personally I use ZUI with OH on two ZW networks and a small OH ZW network, so I can run tests or take pictures to answer forum questions. My advice, since you are after the OTA upgrades would be consider my write-up on using ZUI with OH. I consider it the best of both worlds for moderate to advanced users.