Yes, this is running Hubitat 2.2.3.118 on C7 hardware. The Z-Wave update was also successfully applied, prior to any of my reports from yesterday.
I used Android for SmartStart, I gave a walkthrough of my process here:
Today, after failing in my SmartStart trials, I have proceeded rebuilding my network, trying to add each of my devices using S2 in every case. I have the following results:
1 / 17 LZW31-SN (v1.47 beta) pair with S2
2 / 2 LVW30-SN (v1.19) pair with S2
4 / 4 LVW36 (v1.34) pair with S2
So I should modify my claim, I believe under 1.47 the LZW31-SN may have issues with S2 bootstrapping. Of the devices that do join with S2, most (6 / 7) publish an abbreviated list of capabilities. Three LZW36 and one LZW31-SN publish “0x5E, 0x55, 0x98, 0x9F, 0x22, 0x6C”, and one each LZW30-SN and LZW31-SN publish “0x5E, 0x6C, 0x55, 0x98, 0x9F, 0x22”.
(EDIT: The two command groups above are anagrams and therefore identical.)
I’m still testing the network and dealing with some non-responsiveness issues (including in switches that were working without security before I nuked my z-wave network for v2.2.3), so I can’t say for sure yet what might be related to this. So far I’ve not noticed a correlation between missing capabilities as reported by Hubitat and device failure to respond to commands from the hub, but I still have a couple LZW36 I can’t talk to right now.