forum

Again, there is no bootloader file for you - no need. Just place the UPD_FIRMWARE_Razberry_from_05_10_to_05_04_.bin at address 0x7800 and also put byte 0x01 (one byte) at 0x77ff (you can prepend this byte manually and write single file at 0x77ff). After you put this back to your RaZ, it should go in...

See above. One for UZB, one for RaZ. You need the one for RaZ I've sent you. There is no bootloader inside as you don't need it now. You need to restore the f/w first

no

UPD.
No, first is for UZB, second is for RaZberry

Please read the mark on the crystal. If it is E, you have European boards. Where have you bought them? For US you need boards with U.

Some small part of log - no idea what happens. New node found, nothing special

well, you can write a v8 C++ module to export your stuff in JS and then just use Z-Wave API in JS: zway.devices[xx]....

the difference is in first 0x1800 bytes. Just compare them. The bootloader is in the chip

No ;( we dont' have them. We program Z-Wave chips and not EEPROMS. EEPROM is a temporarily place for firmwares, then they are uploaded in the Z-Wave chip. In your case since Z-Wave chip still runs the old bootloader you can write old f/w in the EEPROM and force bootloader to upgrade. But this is a c...

I've show the full instructions to follow. There is nothing to send more. You need to write the file I've sent at 0x7800 and then write 0x01 at 0x77ff. This should heal it. SHOULD - means we have never tired. For us it is clearly easier to fix it inhouse with our tools than to explain remotelly how ...

hm.. looks you have no lights in Hue. Can you add

console.logJS(deviceLights);
if (!deviceLights) return;

And show the log after restart, please