VeraEdge Help Install

[quote=“shadytaco, post:20, topic:185144”]If I plug it into my laptop the edge does not get an IP address… Obviously because my laptop is not a DHCP server. I did set the laptop up on the same LAN but seems like the vera edge does not store the IP address (rightly so because it is DHCP).

Hence, my question to fact default it and try and connect via 192.168.81.1 assuming that’s the default IP address…[/quote]

Vera is a router and AP. If you already have a router you could have conflicts (like I did) until I direct connected it and changed the IP settings.

The thing is direct connect doesn’t work. Like I said I can ping and SSH into it as root but the webserver is not running assuming it is listening on http or https at ://10.10.1.69

MANY other folks are having the same issue…

[quote=“shadytaco, post:22, topic:185144”]The thing is direct connect doesn’t work. Like I said I can ping and SSH into it as root but the webserver is not running assuming it is listening on http or https at ://10.10.1.69

MANY other folks are having the same issue…[/quote]

Keep trying your 10.10.1.69 if you would like. When you give up on that then go back to the basics.

http://wiki.micasaverde.com/index.php/Networking_Setup

Vera has always anwsered my phone call, but they won’t email back for a week or more. You can also call them and see if they tell you something different. You need to remove vera from your network reboot it and then use the default IP.

Yeah ok right.
I can ping it and SSH to it and login as root but I can not point my browser at it as the http service seems to not me working.

I’ll go back to basics.

Unplug>box up>send back to Amazon>contribute to the already poor reviews.

[quote=“shadytaco, post:24, topic:185144”]Yeah ok right.
I can ping it and SSH to it and login as root but I can not point my browser at it as the http service seems to not me working.

I’ll go back to basics.

Unplug>box up>send back to Amazon>contribute to the already poor reviews.[/quote]

You can do that to. You asked for help and I tried to help.

I think there was atleast 3 options to try one you said you tried. But who knows.
Have you called Vera?
Have you read and followed the directions I sent?

Shadytaco, could you look at the file /tmp/log.mios_firmware and check if there is any errors mounting /dev/mtdblock9? Please look at my first message, it had to wait for approval so is in the 1st page.

Integlikewhoa, i’ll try connecting the Edge directly to a computer when i get home and follow the instructions you pointed, but for now i can’t figure out how a conflict with the router could be the cause of this problem:

  1. The Edge got an (static) IP from the router.
  2. The Edge got an Internet connection. Vera detected it automatically, serial number included.

Also, there is a suspectful error in the log.mios_firmware, i guess trying to actually boot MIOS, so, if i could, i would bet a beer that it’s a problem with a bundle of Edges.

Best regards.

[quote=“shadytaco, post:18, topic:185144”]I am picking up a DHCP address from my router on the LAN. I set this address in my router as static.

I can ping the address of the vera edge and I can SSH to the address and login with root. However, the vera edge http service is not running. I point my browser to http://10.10.1.69 or https://10.10.1.69 and it times out.

now what???[/quote]

just verifying your not connected to the vera by the vera wifi trying to hit the local ip, cause that wont work, the vera has it’s own nat for wifi enabled by default, if logged in that way would need to use the 192.168.81.1 ip address to reach vera

[quote=“JS007, post:27, topic:185144”][quote=“shadytaco, post:18, topic:185144”]I am picking up a DHCP address from my router on the LAN. I set this address in my router as static.

I can ping the address of the vera edge and I can SSH to the address and login with root. However, the vera edge http service is not running. I point my browser to http://10.10.1.69 or https://10.10.1.69 and it times out.

now what???[/quote]

just verifying your not connected to the vera by the vera wifi trying to hit the local ip, cause that wont work, the vera has it’s own nat for wifi enabled by default, if logged in that way would need to use the 192.168.81.1 ip address to reach vera[/quote]

I’m suffering exactly the same problem as shadytaco and i can confirm that i’m not connected to the vera wifi. I guess neither is shadytaco.

last night I was looking at the logs and sure as sh!t I RECALL seeing an error enable to mount abc/xyz…
I’m in the biz so this stood out to my like a sore home directory :wink:

I will execute your action plan when I get home and update the thread with the data.

Assuming your theory is correct which I think your pretty spot on… What is the resolution?

I can confirm that I have errors in /var/log.mios_firmware >
2015-01-06_15:50:19| 1962|MF|Try 4 : mount -t squashfs /dev/mtdblock9 /mios
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-06_15:50:19| 1962|MF|ERROR: Failed to mount: /dev/mtdblock9 .

2015-01-06_15:50:34| 1962|MF|Stop background check_busybox_mount process with pid=2122
2015-01-06_15:50:39| 1962|MF|Process (busybox mount) check suspended
2015-01-06_15:50:49| 1962|MF|ERROR: Failed permanently to mount MiOS mtd.
It seems like we need to reflash a whole system or an error in memory. I connect via wired connection I don’t use wifi.

I have the mount errors too. WTF. I called Vera goes right to a message system. Idiots.

login as: root
root@10.10.1.69’s password:
Access denied
root@10.10.1.69’s password:

BusyBox v1.19.4 (2014-03-20 10:39:37 PDT) built-in shell (ash)
Enter ‘help’ for a list of built-in commands.


| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|
_____|| |
||||___||| |____|
|
| W I R E L E S S F R E E D O M


  BARRIER BREAKER (Bleeding Edge, r39638)

*** MiOS LTD. ( www.mios.com ) ***


*** WARNING : ***
*** Any changes made to the system without ***
*** guidance from MiOS support will VOID ***
*** your future Support requests ***

root@MiOS_45001020:~#
root@MiOS_45001020:~#
root@MiOS_45001020:~# ls
root@MiOS_45001020:~# pwd
/root
root@MiOS_45001020:~# cd /tmp
root@MiOS_45001020:/tmp# ls
RT2860.dat etc log.mios_firmware run
TZ hosts opkg-lists state
alerts lock overlay sysinfo
dhcp.leases log resolv.conf usr
dnsmasq.d log.lighttpd_error resolv.conf.auto
root@MiOS_45001020:/tmp# more log.mios_firmware
2015-01-07_23:31:56| 1078|CF|Checking package : mios-firmware-mtd files existance
2015-01-07_23:31:57| 1078|CF|File : /etc/functions_leds.sh FOUND
2015-01-07_23:31:57| 1078|CF|File : /etc/rc.d/S11mios_mount_firmware.sh FOUND
2015-01-07_23:31:57| 1078|CF|File : /etc/functions_usbdrive.sh FOUND
2015-01-07_23:31:57| 1078|CF|File : /etc/banner FOUND
2015-01-07_23:31:57| 1078|CF|File : /etc/init.d/mios_get_firmware.sh FOUND
2015-01-07_23:31:57| 1078|CF|File : /usr/bin/groups FOUND
2015-01-07_23:31:57| 1078|CF|File : /etc/init.d/mios_mount_firmware.sh FOUND
2015-01-07_23:31:57| 1078|CF|File : /etc/rc.d/S96mios_get_firmware.sh FOUND
2015-01-07_23:31:57| 1078|CF|File : /etc/functions_firmware.sh FOUND
2015-01-07_23:31:57| 1078|CF|Package : mios-firmware-mtd OK
2015-01-07_23:31:57| 1078|CF|DONE
2015-01-07_23:31:57| 1098|MF|Details of mios mtd : BLOCKDEV=/dev/mtdblock9 , CHARDEV=/dev/mtd9 , FLASH_TYPE=nand
2015-01-07_23:31:57| 1098|MF|UsbStick is NOT INSTALLED
2015-01-07_23:31:57| 1098|MF|Got MAGIC=hsqs for MTD=mios
2015-01-07_23:31:57| 1098|MF|Match Found: hsqs == hsqs
2015-01-07_23:31:57| 1098|MF|MiOS MTD Magic found OK.
2015-01-07_23:31:57| 1098|MF|Check md5sum of /etc/cmh-firmware/mios-hooks.sh
2015-01-07_23:31:57| 1098|MF|md5sum ok
2015-01-07_23:31:57| 1098|MF|Load firmware script: /etc/cmh-firmware/mios-hooks.sh
2015-01-07_23:31:57| 1098|MF|Loaded mios-firmware script for version: 1.7.778
2015-01-07_23:31:57| 1098|MF|[MH]mount_mios function not loaded. Creating default one
2015-01-07_23:31:57| 1098|MF|Running PRE SQUASHFS MOUNT function
2015-01-07_23:31:57| 1098|MF|Running: mios_pre_squashfs_mount
2015-01-07_23:31:57| 1098|MF|Trying to mount mtd block: /dev/mtdblock9 on: /mios
2015-01-07_23:31:57| 1098|MF|READY: rootfs_data (/dev/mtdblock6) mounted as overlayfs in /overlay
2015-01-07_23:31:57| 1098|MF|overlayfs_in_Jffs2 Ready. Proceeding…
2015-01-07_23:31:57| 1098|MF|Check if process busybox mount is still running after 20 seconds
2015-01-07_23:31:57| 1098|MF|Started background check_busybox_mount process with pid=1214
2015-01-07_23:31:57| 1098|MF|Try 1 : mount -t squashfs /dev/mtdblock9 /mios
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:31:57| 1098|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:31:57| 1098|MF|Stop background check_busybox_mount process with pid=1214
2015-01-07_23:32:02| 1098|MF|Process (busybox mount) check suspended
2015-01-07_23:32:12| 1098|MF|Check if process busybox mount is still running after 20 seconds
2015-01-07_23:32:12| 1098|MF|Started background check_busybox_mount process with2015-01-07_23:32:12| 1098|MF|Try 2 : mount -t squashfs /dev/mtdblock9 /mios
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:32:13| 1098|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:32:13| 1098|MF|Stop background check_busybox_mount process with pid=1225
2015-01-07_23:32:18| 1098|MF|Process (busybox mount) check suspended
2015-01-07_23:32:28| 1098|MF|Check if process busybox mount is still running after 20 seconds
2015-01-07_23:32:28| 1098|MF|Started background check_busybox_mount process with pid=1236
2015-01-07_23:32:28| 1098|MF|Try 3 : mount -t squashfs /dev/mtdblock9 /mios
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:32:28| 1098|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:32:28| 1098|MF|Stop background check_busybox_mount process with pid=1236
2015-01-07_23:32:33| 1098|MF|Process (busybox mount) check suspended
2015-01-07_23:32:43| 1098|MF|Started background check_busybox_mount process with pid=1247
2015-01-07_23:32:43| 1098|MF|Try 4 : mount -t squashfs /dev/mtdblock9 /mios
2015-01-07_23:32:43| 1098|MF|Check if process busybox mount is still running after 20 seconds
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:32:43| 1098|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:32:43| 1098|MF|Stop background check_busybox_mount process with pid=1247
2015-01-07_23:32:48| 1098|MF|Process (busybox mount) check suspended
2015-01-07_23:32:58| 1098|MF|Check if process busybox mount is still running after 20 seconds
2015-01-07_23:32:58| 1098|MF|Started background check_busybox_mount process with pid=1258
2015-01-07_23:32:58| 1098|MF|Try 5 : mount -t squashfs /dev/mtdblock9 /mios
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:32:58| 1098|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:32:58| 1098|MF|Stop background check_busybox_mount process with pid=1258
2015-01-07_23:33:03| 1098|MF|Process (busybox mount) check suspended
2015-01-07_23:33:13| 1098|MF|ERROR: Failed permanently to mount MiOS mtd.
–More-- (48% of 9797 bytes)
2015-01-07_23:33:17| 1410|GF|Details of mios mtd : BLOCKDEV=/dev/mtdblock9 , CHARDEV=/dev/mtd9 , FLASH_TYPE=nand
2015-01-07_23:33:17| 1410|GF|MiOS MTD MD5 Test requested
2015-01-07_23:33:29| 1410|GF|Got CMP_MD5=498dda6282d785242a509746a5adef61 for SQUASHFS=/etc/cmh-firmware/mios.squashfs having SIZE=5455872
2015-01-07_23:33:29| 1410|GF|Got MD5=9e2b72f65353f51c2cb652da2ac9fb07 for MTD=mios
2015-01-07_23:33:29| 1410|GF|ERROR: Mismatch: 9e2b72f65353f51c2cb652da2ac9fb07 != 498dda6282d785242a509746a5adef61
2015-01-07_23:33:29| 1410|GF|ERROR: Mismatched md5sum of Mtd: mios
2015-01-07_23:33:29| 1410|GF|Erasing it and request reflash…
2015-01-07_23:33:31| 1410|GF|MiOS MTD Reflash requested
2015-01-07_23:33:31| 1410|GF|Writting /etc/cmh-firmware/mios.squashfs on mios
2015-01-07_23:33:31| 1410|GF|Erasing mios : /dev/mtd9 …
2015-01-07_23:33:31| 1410|GF|Writting mios : /dev/mtd9 …
2015-01-07_23:33:35| 1410|GF|Successfully flashed mios
2015-01-07_23:33:37| 1410|GF|Request Mounting of MiOS squashfs
2015-01-07_23:33:37| 1957|MF|Details of mios mtd : BLOCKDEV=/dev/mtdblock9 , CHARDEV=/dev/mtd9 , FLASH_TYPE=nand
2015-01-07_23:33:37| 1957|MF|UsbStick is NOT INSTALLED
2015-01-07_23:33:37| 1957|MF|Got MAGIC=hsqs for MTD=mios
2015-01-07_23:33:37| 1957|MF|Match Found: hsqs == hsqs
2015-01-07_23:33:37| 1957|MF|MiOS MTD Magic found OK.
2015-01-07_23:33:37| 1957|MF|Check md5sum of /etc/cmh-firmware/mios-hooks.sh
2015-01-07_23:33:37| 1957|MF|md5sum ok
2015-01-07_23:33:37| 1957|MF|Load firmware script: /etc/cmh-firmware/mios-hooks.sh
2015-01-07_23:33:37| 1957|MF|Loaded mios-firmware script for version: 1.7.778
2015-01-07_23:33:37| 1957|MF|[MH]mount_mios function not loaded. Creating defaul–More-- (66% of 9797 bytes)
2015-01-07_23:33:37| 1957|MF|Running PRE SQUASHFS MOUNT function
2015-01-07_23:33:37| 1957|MF|Running: mios_pre_squashfs_mount
2015-01-07_23:33:37| 1957|MF|Trying to mount mtd block: /dev/mtdblock9 on: /mios
2015-01-07_23:33:37| 1957|MF|READY: rootfs_data (/dev/mtdblock6) mounted as overlayfs in /overlay
2015-01-07_23:33:37| 1957|MF|overlayfs_in_Jffs2 Ready. Proceeding…
2015-01-07_23:33:38| 1957|MF|Check if process busybox mount is still running after 20 seconds
2015-01-07_23:33:38| 1957|MF|Started background check_busybox_mount process with pid=2073
2015-01-07_23:33:38| 1957|MF|Try 1 : mount -t squashfs /dev/mtdblock9 /mios
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:33:38| 1957|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:33:38| 1957|MF|Stop background check_busybox_mount process with pid=2073
2015-01-07_23:33:43| 1957|MF|Process (busybox mount) check suspended
2015-01-07_23:33:53| 1957|MF|Started background check_busybox_mount process with pid=2084
2015-01-07_23:33:53| 1957|MF|Try 2 : mount -t squashfs /dev/mtdblock9 /mios
2015-01-07_23:33:53| 1957|MF|Check if process busybox mount is still running after 20 seconds
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:33:53| 1957|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:33:53| 1957|MF|Stop background check_busybox_mount process with pid=2084
2015-01-07_23:33:58| 1957|MF|Process (busybox mount) check suspended
2015-01-07_23:34:08| 1957|MF|Check if process busybox mount is still running after 20 seconds
2015-01-07_23:34:08| 1957|MF|Started background check_busybox_mount process with–More-- (83% of 9797 bytes)
2015-01-07_23:34:08| 1957|MF|Try 3 : mount -t squashfs /dev/mtdblock9 /mios
–More-- (84% of 9797 bytes)
2015-01-07_23:34:08| 1957|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:34:08| 1957|MF|Stop background check_busybox_mount process with pid=2095
2015-01-07_23:34:13| 1957|MF|Process (busybox mount) check suspended
2015-01-07_23:34:23| 1957|MF|Check if process busybox mount is still running after 20 seconds
2015-01-07_23:34:23| 1957|MF|Started background check_busybox_mount process with pid=2106
2015-01-07_23:34:23| 1957|MF|Try 4 : mount -t squashfs /dev/mtdblock9 /mios
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:34:23| 1957|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:34:23| 1957|MF|Stop background check_busybox_mount process with pid=2106
2015-01-07_23:34:28| 1957|MF|Process (busybox mount) check suspended
2015-01-07_23:34:38| 1957|MF|Started background check_busybox_mount process with pid=2117
2015-01-07_23:34:38| 1957|MF|Try 5 : mount -t squashfs /dev/mtdblock9 /mios
2015-01-07_23:34:38| 1957|MF|Check if process busybox mount is still running after 20 seconds
mount: mounting /dev/mtdblock9 on /mios failed: Invalid argument
2015-01-07_23:34:38| 1957|MF|ERROR: Failed to mount: /dev/mtdblock9 .
2015-01-07_23:34:38| 1957|MF|Stop background check_busybox_mount process with pid=2117
2015-01-07_23:34:43| 1957|MF|Process (busybox mount) check suspended
–More-- (98% of 9797 bytes)
2015-01-07_23:34:53| 1957|MF|Request MiOS MTD MD5 Test to mount MiOS mtd.
2015-01-07_23:34:53| 1410|GF|ERROR: Failed again to mount the MiOS mtd
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#
root@MiOS_45001020:/tmp#

Interesting I haven’t seen this firmware version mentioned before. 1.7.906 is the current firmware for the Edge.

OK by btches and jackbags.

I left a message for Vera support and they called me back.

Turns out that everyone initializing a new controller over the last few days sucked down a corrupt image from the vera servers and f’d there systems.

The support guys have to load 1 image on and reboot and load another image on and reboot.

takes about 20 min.

CALL THEM AND GET YOU SH!T FIXED.

OvernOut.

[quote=“shadytaco, post:33, topic:185144”]OK by btches and jackbags.

I left a message for Vera support and they called me back.

Turns out that everyone initializing a new controller over the last few days sucked down a corrupt image from the vera servers and f’d there systems.

The support guys have to load 1 image on and reboot and load another image on and reboot.

takes about 20 min.

CALL THEM AND GET YOU SH!T FIXED.

OvernOut.[/quote]

Glad you got if fixed. This is gonna be good info for the others. Save alot of RMA’s and waiting when the fix is only a phone call away.

same problem here.

I am glad that this is a known problem and there is a fix for it, but i can not understand why they don’t just put that up on the wiki along with the firmware you need to flash.

shadytaco, do you happen to have these two images lying around still?

I sent an email to Vera yestarday but i got no answer, so i kept working myself.

The problem seems to be caused by the unit’s OpenWRT version, 87, that, probably by mistake, doesn’t include support for SQUASHFS ZLIB. The MIOS image uses ZLIB compression so it cannot be mounted.

To solve this i forced the download of the MIOS firmware (the unit download the 1.7.906 version) and updated the OpenWRT version to the build required by MIOS firmware for the Vera Edge (103). After the reboot due to the OpenWRT update the unit sucessfully mount the MIOS image in mtd9 and it’s working fine.

I’m not giving details of how to do that because it’s probably unsupported and i dont want to be responsible of bricking some units or voiding warranties, if someone try to do something similar it’s on his/her own. I hope Vera will give an official solution soon.

Best regards.

You’ll probley get a email back in a few or more. For anyone that needs to contact VERA you’ll have a faster response by calling 99% of the time.

It should be very nice if Vera can tell us how to reflash the system and where to download the image version 1.7.906 for Vera Edge. I have send about 5 emails w/o any response. I am in Europe and calling to USA will cost much money (perhaps the cost of another Vera Edge) ! I purchased Vera Edga 6 days ago and I have just small blackbox connected to my network w/o support for home automation and that’s make me sad :frowning:

I just fixed it by upgrading the openwrt version, this is easily possible by using the built-in update scripts
if someone needs assistance doing this, i am glad to share my findings, just send me a private message

You’ll probley get a email back in a few or more. For anyone that needs to contact VERA you’ll have a faster response by calling 99% of the time.[/quote]

As duchm1ak, I am also in Europe, and calling USA is quite expensive. Also, there is a big timezone jump.