I moved all our posts on this matter to a new topic since it is getting quite lengthy.
Zwave nodes are for an entire device, not child endpoints.
Yes I have seen that happen before on ghost nodes, not sure why exactly. The false devices can be force removed again.
Also, you can roll back to the production build using the diagnostic tool if you want, you just lose any new features. Just click Download Latest which gets production builds only, then install from the Restore Previous version button.
Recommendations:
- Go back to production platform if possible.
- Use SS Manager app to disable/enable SS to prevent accidental inclusion [APP] SmartStart Manager for Z-Wave (Long Range support)
- Clean up all ghost nodes and devices (or as many as possible for now anyway) How To Remove Ghosts using hub tools or a UZB Stick
- Exclude ZEN16
- Factory reset ZEN16
- Include device
- Adjust only the Input Type settings [contact sensor recommended]
- Do not change input control setting yet
- Verify SS is disabled / removed
- Exclude device
- Power cycle device.
- Include device again
- Verify that the Input settings you set before came back through the same, it should sync from device and show the settings you selected before the exclude.
