Upgraded to Luup Beta firmware for development (1.0.745)… found out all of the timers have been changed, it seems you can only do one daily timer per event. Not only that but all of the dropdown boxes for the timers would not work correctly for selecting even 1 individual daily timer. Then, I found I could not implement “ON” and “AFTER 15SEC” > “OFF” because the dropdown boxes were so small you couldnt tell which amount of time you were selecting…
Bottom line is, I really needed timers working correctly for some automatic feeders that are on zwave outlets despite my development curiosity… SO I attempted to revert to 602 firmware as stated in another thread by using the following command…
[your local Vera IP addres]/cgi-bin/cmh/upgrade_step2.sh?ver=1.0.602
I selected to upgrade the firmware and restore defaults… 15min passed… 30min passed… so I powercycled Vera as instructed.
Now all I get is a blinking power light… is my Vera an expensive paperweight?
Connect your PC’s network connection the LAN 1 port of Vera. It must be LAN 1, not any of the other LAN ports.
Give your PC a static IP: 192.168.1.2, with subnet mask 255.255.255.0. You can leave the gateway and dns server blank.
Run the program ‘rescue.exe’. Click ‘browse’ and find the firmware.
Unplug the power to Vera. Hold the black button in while you reconnect the power. Let go of the black button when the power light starts blinking.
Click ‘upload’ in the firmware utility. It takes up to 5 minutes to flash the firmware. Please note you may need to disable your Antivirus software to run the EXE. The anit-virus will think this is maliciuos code.
Note
* The rescue utility is know to work only on Windows XP and with only ONE network card (disable wireless and other cards if you have).
The program "rescue.exe" just gives me the message "Please wait for finding available IP address..." and never uploads the firmware to the router... anyone had to do this before?
Your PC, it’s not connected to any other wireless or wired network at the same time, is it? The idea is to make PC think that Vera is its sole router/gateway with IP address 192.168.1.1…
Nope, all other networks are disconnected. I even tried unchecking the IPv6 configuration from the network configuration page so that it would only connect with IPv4. The only thing my PC is doing is trying to connect the IPv4 with 192.168.1.2 IP and 255.255.255.0 Subnet.
When I connect the cable my PC sits there and tries to figure out the connection for a couple minutes and finally comes back with “No Network Access” with a little yellow exclamation point in the network icon.
I can even ping the router @ 192.168.1.1 with a 100% success rate… ugh. I don’t know… I guess I’ll have to bring my WindowsXP laptop home from work tommorrow and give that a shot.
I triple checked them, I even went to some OpenWRT and DD-WRT boards to check on how to recover these routers… sometimes they just cant be brought back to life without opening up the case. I will not be doing that since I’d most likely be voiding my warranty. I’ve got a call into MCV, hopefully they get back to me today…
The best Ive been able to do as far as communicating with the router is pinging 192.168.1.1 in recovery mode and getting a response.
Make sure that your PC doesn’t have a static IP assigned. That caused me hours of detective work trying to figure out why my PC couldn’t talk to vera, when the vera was reset to factory defaults.
[quote=“B0SST0N, post:12, topic:164563”]I triple checked them, I even went to some OpenWRT and DD-WRT boards to check on how to recover these routers… sometimes they just cant be brought back to life without opening up the case. I will not be doing that since I’d most likely be voiding my warranty. I’ve got a call into MCV, hopefully they get back to me today…
The best Ive been able to do as far as communicating with the router is pinging 192.168.1.1 in recovery mode and getting a response.[/quote]
Strange, just recently I “bricked” my second router while playing with different FW, but Asus’ tftp.exe utility done recovery job with no problems. It just worked… My laptop was setup with static IP though…
I was attempting recovery on a Win7 PC last night… brought my WindowsXP laptop home tonight from work. I am going to give that a shot now…
What concerns me is… I left a trouble ticket yesterday for MCV, I also called MCV this morning and was told “someone would call me back today”. Nobody ever called me. I have been impressed by their vision and support thus far… so this is kind of a let down.
When you power on Vera if the power light immediately starts blinking steady about once per second, that means the firmware image is messed up and it can’t boot. Usually this happens if Vera loses power while writing a firmware upgrade. The firmware restoration utility is the only way to recover. That utility is really picky about having only 1 single NIC going. But, if you do, I’ve never seen it not work.
Can you run ipconfig on your computer and paste the result here in this thread? If you have only 1 IP address, and it’s connected, and on the 192.168.1.xxx address, and connected to the LAN1 port on Vera, it should work. If you can’t get it to recover, we can send you an RMA # and exchange the Vera for you.
I was using a Win7 computer last night and everything seemed fine in the ipconifg, I only had one NIC active. However Vista’s network config can be more of a pain than XP… so I brought my Toughbook home from work with XP on it tonight. Unfortunately, my power adapter here at home for that laptop seems to have died so I will not be able to attempt this on an XP machine until tomorrow. I am hoping all goes well with the restore from that machine. At least I will know for a fact that everything is being done the way I want it and no settings are being hidden from me. I will try to get home on lunch tomorrow and do this so I can give you guys a call in the afternoon if it does not work.
I apologize for the persistence… I know you guys are busy and are a small company, I work for a small company myself and am constantly inundated by technical problems from customers. I know how hard it is to keep track of everyone and also stay on schedule with my own work. It seems you guys probably suffer from the same “too much to do and not enough people” that my company does. I do appreciate the quick response and how dedicated you are to your customers, especially with limited staff.
Well, the problem was Windows 7. I got my XP laptop power supply working for long enough to attempt the recovery and it succeeded with flying colors. For anyone else who attempts this in the future, I wouldnt use a Win7 or Vista machine… Trust me, I am saving you 2 days of headaches
