"Secure inclusion failed" after update z-uno2b firmware (problem not solved - sometimes it occurs)
Posted: 01 Sep 2024 20:43
I updated the z-uno beta firmware in the IDE to 3.0.13. I uploaded the bootloader to board X and then the compiled sketch. After that I was unable to include the board to the network. Instead of information "Wait for Key verification".
I get a request for a PIN
or "Secure inclusion failed".
On the interview page you can see that the include is incorrect.
I rolled back the IDE to 3.0.12 and uploaded the compiled sketch to another board Y. The same problem appeared again. I reinstalled z-way and this time tried to include another board Z but without uploading anything to it. It worked, which means something was wrong when uploading the compiled sketch. I found files that had changed and restored the old versions. I manually overwrote the files from z-uno2_core_03_00_12_beta28 to the files from z-uno2_core_03_00_12_beta21, then compiled the sketch and uploaded it to board Y. It worked again. As a test, I uploaded a blank sketch to board X, where I have 3.0.13 firmware, and the error appears again. If there was a possibility to downgrade the firmware, I could find where the problem is without testing other boards, and I would be able to restore the board's functionality. Now I have to wait with a non-working board until you solve this problem. That is why I am asking for the possibility of downgrading the firmware to be restored.
I get a request for a PIN
or "Secure inclusion failed".
On the interview page you can see that the include is incorrect.
I rolled back the IDE to 3.0.12 and uploaded the compiled sketch to another board Y. The same problem appeared again. I reinstalled z-way and this time tried to include another board Z but without uploading anything to it. It worked, which means something was wrong when uploading the compiled sketch. I found files that had changed and restored the old versions. I manually overwrote the files from z-uno2_core_03_00_12_beta28 to the files from z-uno2_core_03_00_12_beta21, then compiled the sketch and uploaded it to board Y. It worked again. As a test, I uploaded a blank sketch to board X, where I have 3.0.13 firmware, and the error appears again. If there was a possibility to downgrade the firmware, I could find where the problem is without testing other boards, and I would be able to restore the board's functionality. Now I have to wait with a non-working board until you solve this problem. That is why I am asking for the possibility of downgrading the firmware to be restored.