I'm having real problems with getting my Secure SCS317 (aka Horstmann SCSC7) thermostat into the z-wave network properly.
It's a real pain to include, works about one time in five and has to be done with the z-stick off the PC, has never succeeded via domoticz or ozwcp. Once it is included, the SCS317 shows a network connection and I can associate it (using its UI) with the boiler control relay. However, it shows up in the OZW device list as an unnamed device - image below - and whatever I try, I just can't get ozw to pull any info from it. Mfr & Dev IDs remain stubbornly 0x0000.
The two devices are about 6ft apart. To get the SCS317 included, I held the z-stick between my fingertips, about 20cm from the device - and even then it was fourth time lucky!
It seems to include more easily on a z-stick S2 than on the newer Gen5 stick - and ozwcp does recognise it when it's using the S2. I wonder whether there's a problem with this device and the Gen5. Has anyone got this combination working and can help?
Secure's support are pointing to the z-stick, not unreasonably (the SCS worked with Vera ok too); Aeotec have yet to reply to my email

I've also removed the SCS317 from the ozwcfg xml file and let the system find it again, but that makes no difference; that suggests to me that the problem is more likely between the z-stick and the SCS317. I've tried asking ozw / domo to heal the device while having it in 'listen' mode (stay-awake), removing and re-including, sending NIFs, everything I can think of. Nothing shows up in domoticz.log for the device ID when I have the SCS317 send a NIF, which is strange, yet the thing is clearly in the z-wave network as it can associate with other nodes on the network (the boiler relay, which you can see in the screenshot is already part of the z-stick's network). After a while, OZW will decide to deem it a dead device.
Does anyone have any suggestions / ideas what the problem might be or what I can try to diagnose it?
Thanks!
Jeff