After upgrade to 3.0: An unexpected error occurred while initialising the Z-Wave controller data.

[quadrumanous]

I've upgraded the software to 3.0 in my Pi. Than i got the message "An unexpected error occurred while initialising the Z-Wave controller data." In the logs it writes:
[2019-09-13 18:54:03.246] [core] Error: Invalid config
[2019-09-13 18:54:03.249] [core] Tried 5 times without success. Stopping tries.
[2019-09-13 18:54:03.259] [core] Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Invalid config

But the configuration is correct, as I can get some info from the controller using the ZMESerialUpdater with the same port info:
./ZMESerialUpdater serialapi_uzbupdate -d /dev/ttyAMA0


Z-WAVE Serial API Tool
Version:LWE0.9
by Z-WAVE>ME


-->
-->
-->
Device ready in:5.0815410614 seconds
FULL INFO
Openning port .............................. OK


SERIAL INFO
VERSION: 05 20 VENDOR: 01 47

ZME_CAPABILITIES
UID: BD 45 24 76 7B 6D 73 7E B0 80 62 09 41 93 16 98
VENDOR: 00 00 NODES: FF
FLAGS: 05 00 00 00 00 00 00 00 00 00 00 00 00

FIRMWARE CRC
BOOT: 8A AA FW: C2 31
MISC
FREQ: EU

NVR Content
--------------------------------------------------------------------------------------------
Prog/erase lock : FF FF FF FF FF FF FF FF, Read back lock: FF
Rev 01, Cal FC, TXCal 19 14, SAW 0D 3C DE 05, Pin 01, CRC 9C 63
NMV: CS 04, TYPE 02, SIZE 01 00, PSIZE 01 00 (EEPROM M25PE20)
USB: VID 00 01, PID 00 02, UUID 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
--------------------------------------------------------------------------------------------
FACTORY ID: WEEK 30, YEAR 16, CHIP 00 07, SER 0E E6, WS 5, HWREV: 00 01, CRC8 1A

elapsed 7.4163620472 seconds

Any body an idea what is going on? And how I can fix it?

[quadrumanous]

Tried a firmware upgrade now.. goes througt to +/- 60% and then:
./ZMESerialUpdater serialapi_uzbupdate -d /dev/ttyAMA0 -f UPD_FIRMWARE_Razberry_STATIC_2ch_ZME_05_20_04000002_ZME_05_1b_04000002.bin


Z-WAVE Serial API Tool
Version:LWE0.9
by Z-WAVE>ME


-->
Device ready in:3.06108903885 seconds
FIRMWARE
Openning port .............................. OK
Writing NVM data .............................. FAILED

Error 0 returned 1 for ACK


Error 1 Unknown exception:Can't write NVM data! at=4e000

[quadrumanous]

Another try, some command, got futher:
./ZMESerialUpdater serialapi_uzbupdate -d /dev/ttyAMA0 -f UPD_FIRMWARE_Razberry_STATIC_2ch_ZME_05_20_04000002_ZME_05_1b_04000002.bin


Z-WAVE Serial API Tool
Version:LWE0.9
by Z-WAVE>ME


-->
Device ready in:3.06408905983 seconds
FIRMWARE
Openning port .............................. OK
Writing NVM data .............................. OK
Setting update flag .............................. OK
Reseting chip .............................. OK
Waiting for FW reflashing .............................. OK
-->
-->
-->
-->
Device ready in:11.8130400181 seconds
FULL INFO
Openning port .............................. OK
Openning port .............................. FAILED

Error 0 returned 1 for ACK


Error 1 returned a for ACK


Error 2 returned 0 for ACK


Error 3 Unknown exception:list index out of range

[quadrumanous]

./ZMESerialUpdater serialapi_uzbupdate -d /dev/ttyAMA0 -f UPD_FIRMWARE_Razberry_STATIC_2ch_ZME_05_1b_04000002_ZME_05_24_04000002.bin


Z-WAVE Serial API Tool
Version:LWE0.9
by Z-WAVE>ME


-->
Device ready in:3.03405714035 seconds
FIRMWARE
Openning port .............................. OK
Writing NVM data .............................. OK
Setting update flag .............................. OK
Reseting chip .............................. OK
Waiting for FW reflashing .............................. OK
-->
-->
-->
-->
Device ready in:12.1210620403 seconds
FULL INFO
Openning port .............................. OK


SERIAL INFO
VERSION: 05 24 VENDOR: 01 47

ZME_CAPABILITIES
UID: BD 45 24 76 7B 6D 73 7E B0 80 62 09 41 93 16 98
VENDOR: 00 00 NODES: FF
FLAGS: 05 00 00 00 00 00 00 00 00 00 00 00 00

FIRMWARE CRC
BOOT: 8A AA FW: 8B C3
MISC
FREQ: EU

NVR Content
--------------------------------------------------------------------------------------------
Prog/erase lock : FF FF FF FF FF FF FF FF, Read back lock: FF
Rev 01, Cal FC, TXCal 19 14, SAW 0D 3C DE 05, Pin 01, CRC 9C 63
NMV: CS 04, TYPE 02, SIZE 01 00, PSIZE 01 00 (EEPROM M25PE20)
USB: VID 00 01, PID 00 02, UUID 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
--------------------------------------------------------------------------------------------
FACTORY ID: WEEK 30, YEAR 16, CHIP 00 07, SER 0E E6, WS 5, HWREV: 00 01, CRC8 1A

elapsed 93.0816600323 seconds
another succesfull firmware upgrade. But still:
[2019-09-13 19:17:53.995] [core] Error: Invalid config
[2019-09-13 19:17:53.996] [core] Trying to restart Z-Wave binding (zway) in 10 seconds
[2019-09-13 19:18:04.000] [core] Restarting Z-Wave binding (zway)

[PoltoS]

More logs from Z-Way would be helpful. Looks like two controllers are running simultaneously. At least your problems with firmware upgrade was caused by Z-Way also speaking in the port

[equathza]

I've been able to "finally" clean my device with:

Code: Select all

./ZMESerialUpdater serialapi_uzbupdate -d /dev/ttyAMA0 -c

after that i was able to re-flash the device successfully. (the same bootloader and firmware file, though firmware still took a second attempt)
It really seems I previously messed up my z-wave controller config, probably had some remaining stuff from the controller transfer I have done in the past. However I think you need to be careful with this ZMESerialUpdater nad loading specific firmware, and better have Z-way taking care of upgrades.I

My Z-way however installation behaves exactly quadrumanous. After the upgrade from v2 to v3 and a reboot of the raspberry, Z-way is unable to bind.
Before that one reboot it seemed fine.
I've only managed to fix this by re-imaging my SD card with the 3.01 image, and upgrade from there (not bad as it's my 2nd controller for lab testing)