Have had my VeraLite for a few years now - and it has done everything I needed it to. Was excited to see I could get it to work with my Echo. d/l'ed the latest beta - and now I have a brick with a blue blinking light and a solid red one.
Have tried all the tricks with trying to SSH into the device (I have it with the orange light blinking), set IP addressing to 192.168.0.2 /24 on my PC (and it does recognize Network 10 (any other class C addressing schemes as referenced in other posts on the forums do not elicit a "network found")) but I cannot ping nor SSH into 192.168.0.1.
...EDIT... - found another posting - and was able to get this to work as far as actually getting telnet into the device. Still working on getting it back to life ;-).
1. Connect your computer directly into the LAN port on the Vera lite unit (really not needed. As long as both units are hard wired to same switch you just need to change your pc IP, cannot do this wireless)
2. Put a static IP on your computer (192.168.1.2) and the gateway 192.168.1.1 . You Can find
more information about it at step 8.
3. Plug the power adapter in Vera and when the blue light starts blinking, press and release
the reset button - blue light should be blinking fast
4. Open a command prompt and telnet into the unit: telnet 192.168.1.1
Run these commands:
flash_eraseall -j /dev/mtd7
echo b > /proc/sysrq-trigger
Finally obtained solid blue light and solid red and blinking green. Could not get back in via previous IP - but noticed the LAN light would at least engage when I plugged and unplugged the patch cable.
Brought up Wireshark to see if I could see anything and noticed I was getting DHCP Discovery packets from an unknown MAC address - assumed it was VeraLite.
Downloaded TFTPD64 and set up an impromptu DHCP server - Vera grabbed an address right away (192.168.1.100 as this was the scope I setup) and now I can at least HTTP back into it. ;-)
Now I have a "Luup engine is taking longer to reload" screen
Will do some more digging and see what happens...
After a bit more fiddling - put it back on the home network - let it boot - and now I can HTTP into it - although most of my devices are missing (had to leave - so maybe it is syncing).
I do have a backup I created before attempting the update - - may try to update again and then restore backup. Keeping fingers crossed ;-)