Today I tested the device with an old z-wave controller (a razberry / pi running domoticz) and it works properly.
I re-added it to the qolsys panel and did some more troubleshooting and found some interesting facts:
After a reboot, the on/off functionality works correctly for about 30 seconds directly after the reboot. If I wait 60 seconds or more it does not work…
I tested this over multiple reboots and it’s very reproducible.
My suspicion guess would be that somehow it is hanging when trying to communicate the state change to ADC - considering that the device does not get automatically added to ADC as expected when I clear and re-add it, this was what I wanted to test next.
I was able verify that the device works until the “manual phone test” completes - other z-wave actions such as locking and unlocking the front door lock also don’t get communicated and logged to adc until the “manual phone test” is complete.
To test my suspicion a little more, I disabled wifi, powered off the panel, removed the sim card, and tested the switch after rebooting… After disabling wifi and cell connectivity, the z-wave switch worked perfectly for over 20 minutes.
After rebooting with only wifi enabled (no sim), everything seemed to work normally from the panel, including the z-wave switch, but none of the z-wave devices transmit their activity to adc, and none of the z-wave devices function from adc (such as the door lock), but overall panel status is communicated to the adc activity log.
After installing the sim, it’s back to the original state where the z-wave switch status only works for about 30 seconds after a reboot (other z-wave devices appear to work normall).
The dual path wifi test and cellular tests run successfully.
Hopefully this information helps troubleshoot from your side / adc!