Device "not supported" in Home App following upgrade to Z-Wave v3.2.2

[~nightcrawler~]

We are preparing a fix for this issue. We can check it on your specific case if you can dedicate your time to our support.
@CaylinBr, if you are ready, please write to @aivs to make sure our fix covers your issue

Polto thank you for working on a fix! Will this resolve any of the issues I saw in the HomeKit Gate config with the previously removed devices?

Also are you able to explain the ID mapping and AID difference?

[PoltoS]

idMapping is the old one, legacy, replaced by the new hkDevices.

Will it solve all your issues? can not be sure - this is why we suggest to contact us via support and let us provide you a fix and test it before the next release

[PoltoS]

You can already try this: https://github.com/Z-Wave-Me/home-autom ... 4cc1b7e6e1

[~nightcrawler~]

You can already try this: https://github.com/Z-Wave-Me/home-autom ... 4cc1b7e6e1

I added the new lines to both files, restarted and I see the new hkDevicesArray, but for some reason it looks like it filled the array twice:

hkDevicesArray: [
"__RaZberry_Controller",
"ZWayVDev_zway_3-0-38",
"ZWayVDev_zway_4-0-38",
"ZWayVDev_zway_5-0-37",
"ZWayVDev_zway_6-0-38",
"ZWayVDev_zway_13-0-37",
"ZWayVDev_zway_14-0-37",
"ZWayVDev_zway_17-0-38",
"ZWayVDev_zway_3-0-38",
"ZWayVDev_zway_4-0-38",
"ZWayVDev_zway_5-0-37",
"ZWayVDev_zway_6-0-38",
"ZWayVDev_zway_13-0-37",
"ZWayVDev_zway_14-0-37",
"ZWayVDev_zway_17-0-38"

*UPDATE* Looks like each time HomeKit Gate is restarted it adds to this array. I just restarted the app again and now have three instances of the devices in the array.

hkDevicesArray: [
"__RaZberry_Controller",
"ZWayVDev_zway_3-0-38",
"ZWayVDev_zway_4-0-38",
"ZWayVDev_zway_5-0-37",
"ZWayVDev_zway_6-0-38",
"ZWayVDev_zway_13-0-37",
"ZWayVDev_zway_14-0-37",
"ZWayVDev_zway_17-0-38",
"ZWayVDev_zway_3-0-38",
"ZWayVDev_zway_4-0-38",
"ZWayVDev_zway_5-0-37",
"ZWayVDev_zway_6-0-38",
"ZWayVDev_zway_13-0-37",
"ZWayVDev_zway_14-0-37",
"ZWayVDev_zway_17-0-38",
"ZWayVDev_zway_3-0-38",
"ZWayVDev_zway_4-0-38",
"ZWayVDev_zway_5-0-37",
"ZWayVDev_zway_6-0-38",
"ZWayVDev_zway_13-0-37",
"ZWayVDev_zway_14-0-37",
"ZWayVDev_zway_17-0-38"
],

[~nightcrawler~]

Had a possibly unrelated issue where a zwave device (17-0-38) disappeared from the Home app, but was still in the the config as visible. I set it to tag as skipped in HomeKit Gate then set it back to not skip and it showed back up in the Home app. But even more interesting is the "Not supported" device disappeared after I did that. Is there a check that happens when the skip flag is changed but not with a restart of HomeKit Gate?

[aivs]

*UPDATE* Looks like each time HomeKit Gate is restarted it adds to this array. I just restarted the app again and now have three instances of the devices in the array.

Fixed, please test.
https://github.com/Z-Wave-Me/home-autom ... 52888e0ce2

[~nightcrawler~]

*UPDATE* Looks like each time HomeKit Gate is restarted it adds to this array. I just restarted the app again and now have three instances of the devices in the array.

Fixed, please test.
https://github.com/Z-Wave-Me/home-autom ... 52888e0ce2

Looks like the fix worked -- at least for the array problem. Now what is the best way to remove the duplicate devices from the array without causing issues?

[putrzop]

looks like the same issue with needing to rename the HomeKit Gate instance from previous connections to the Home app still exists.