I have been having this issue on two separate SS6 fw 1.0.3 for quite a while now. When I try to do a secure join the LED glows red for more than 2 seconds supposedly indicating it failed however ST app at some point says it found something. It recognizes the SS6 as the Aeon Light Bulb so I save it, configure it and then go to the IDE to change the device handler to the one you wrote. The device works normally however I am unable to change the settings as I keep getting "Error Refreshing Page". I set the missing settings through the IDE for ledBehavior, ledBrightness and monitorInterval however I am still unable to access the settings.
I have gone through this several times as these 2 SS6 devices seem to occasionally crash (especially if controlling inductive loads - white noise machine) and when they do they wreck havoc in my zwave network. Everything starts failing and the network repair pretty much lists 100% of my 90 or so devices.
I explored options with Aeotec (they had me update firmware to 1.03) but the issues remain. Could it be the device handler?
I have been having this issue on two separate SS6 fw 1.0.3 for quite a while now. When I try to do a secure join the LED glows red for more than 2 seconds supposedly indicating it failed however ST app at some point says it found something. It recognizes the SS6 as the Aeon Light Bulb so I save it, configure it and then go to the IDE to change the device handler to the one you wrote. The device works normally however I am unable to change the settings as I keep getting "Error Refreshing Page". I set the missing settings through the IDE for ledBehavior, ledBrightness and monitorInterval however I am still unable to access the settings.
I have gone through this several times as these 2 SS6 devices seem to occasionally crash (especially if controlling inductive loads - white noise machine) and when they do they wreck havoc in my zwave network. Everything starts failing and the network repair pretty much lists 100% of my 90 or so devices.
I explored options with Aeotec (they had me update firmware to 1.03) but the issues remain. Could it be the device handler?