Solved: Rough OOBE (Out Of Box Experience)

wkearney99 · February 21, 2016, 4:08pm

OOBE is less than stellar, thus far.

First off, the hardware doesn’t light up any LEDs on plugging power into it. Oooookay… But Ethernet port on the switch showed a connection. Hmmm… Pulled power from the veraplus, waited a 3-count and plugged it back in… Power LED… for a minute or so. Curiously, the Ethernet connection light that had been lit, went out.

Unplugged, came back in a half-hour plugged it back in again. Got Power LED and it started marching through the others. Flipped it over meanwhile and made note of the Ethernet MAC listed on the back. Brought up a web page to my router’s DHCP list and looked for it… nothing. Meanwhile, various LEDs are still lit on the veraplus. Took a careful look through the router’s DHCP list and noticed there was an IP lease for a MAC address one higher. Erm, ok… set up a static lease for it and power cycled the veraplus. Checked the DHCP tables and now the listed MAC has asked for a lease. WTH? Um, ok, set up a static lease for THAT one too and power cycled the router.

Tried bringing up ‘getvera.com’ and got an error. Dug out the sole piece of paper that came with the Veraplus and noticed it’s ‘home.getvera.com’ which loads. Would it kill them to put up an HTTP redirect, or at least a LINK to home?

Proceeded through the setup pages. Lots of personal questions, with required answers. Not sure about this. Do not like an OOBE asking all this, but whatever. Bumped an SMS to the phone number, presumably that’s for notifications later.

Unit says don’t power it off as it needs an upgrade. Sort of expected that as manufacturing and shipping from Asia undoubtedly leaves hardware behind the latest software. Let it do it’s thing.

Meanwhile, the /cmh web page reports:

Luup engine is taking longer to reload

Along with a ‘Try again’ link. Which, several times now, has done nothing, bringing me right back to that same error. I don’t know if it’s safe to power cycle the router or not. But it’s been 15 minutes, so here goes…

wkearney99 · February 21, 2016, 4:52pm

Power cycling didn’t help. Going to the veraplus IP address redirects to /cmh (on itself). This brings up a web page with the Vera logo on the left and a spinning progress circle animation on the right. Which, after several minutes, times out and goes to the “Luup engine is taking longer to reload” message.

Logging out and logging back in again did not help. Same result.

I’ve e-mailed support.

Two hours wasted on an out of the box new piece of hardware.

Z-Waver · February 21, 2016, 6:08pm

[quote=“wkearney99, post:1, topic:191168”]First off, the hardware doesn’t light up any LEDs on plugging power into it. Oooookay… But Ethernet port on the switch showed a connection. Hmmm… Pulled power from the veraplus, waited a 3-count and plugged it back in… Power LED… for a minute or so. Curiously, the Ethernet connection light that had been lit, went out.[/quote]This sounds like a bad/weak power supply, not putting out enough amps for Vera. If that’s the case, flaky (in)operation can be expected.

Tried bringing up 'getvera.com' and got an error.

Works for everyone else. Perhaps a broswer problem. I strongly recommned that you use Firefox or Chrome with Vera and watch out for plugins getting in the way. NoScript will be a problem and Ad blockers might be too.

Dug out the sole piece of paper that came with the Veraplus and noticed it's 'home.getvera.com' which loads. Would it kill them to put up an HTTP redirect, or at least a LINK to home?

The link is under Control -> Remote access on the home page(getvera.com).

wkearney99 · February 21, 2016, 9:27pm

Already using Chrome, but it does seem to be adblock related. Whitelisting in both adblockplus and ghostery allows the page to redirect. Given the likely high percentage of users with a blocker running it’d be good to at least take it into account with regard to putting useful links on the page. A screen grab of which is attached.

The Control link does bring up the Choose your controller screen. Which then does a Direct Connection. Which times out with the LUUP error.

But, for the sake of exhausting options, I tried using my Nexus 7, Samsung S6 and iPad 4 to connect. Both on the local WiFi network and via cellular data (turned off WiFi on them to force use of cell data). No change, same hang up at LUUP error. To really exhaust options I tried using IE9 on a different local machine. No dice, same error.

Weak power supply, well, I’m using the one they shipped with it. Which is listed as a WB-18D12FU 12v 1.5A. Nothing particularly special, it’s just your garden variety cheapie power supply. I suppose I could dig up another 12vdc suppy, but I’d prefer to let support chime in first. No sense blowing out the unit before they’ve had a chance to connect to it remotely. That and since the error is repeatable, and the unit stays connected, I’m less inclined to think it’s the power supply. PS problems tend to lead to things erroring out in different ways or locking up. It’s not often a power problem would be as cleanly repeatable.

I used the web page form to send an e-mail to support. I received what looks like a generic reply about two minutes later. It’s a Sunday so I wouldn’t expect a reply as the website lists M-F hours.

The box has gotten itself into some sort of state that leaves it unusable. This happening straight out of the box. Not a great way to get started.

I can, however, SSH into the box using ‘remote’ and the password generated for allowing remote connection. Any tips on what to “poke at” to get it past this LUUP issue?

Looking into the logs now. serproxy.log reports that it’s failing to download and find_self failed.

http://127.0.0.1:3480/data_request?id=lu_finddevice&devid=5000xxxx&devtype=urn:micasaverde-org:device:SerialPortRoot:1 to /tmp/serproxy.1-22816 with /usr/bin/curl -k -s -S --fail --connect-timeout 5 --max-time 5 -o "/tmp/serproxy.1-22816" "http://127.0.0.1:3480/data_request?id=lu_finddevice&devid=5000xxxx&devtype=urn:micasaverde-org:device:SerialPortRoot:1" Response 1792

I did a ‘tail -f LuaUPnP.log’ and it appear to be a continuous loop where it’s constantly running into this error:

2016-02-21 12:26:24 - LuaUPnP Terminated with Exit Code: 16

From one, to another, the log contains the same thing:

[code]---------------exited-------------
PID USER VSZ STAT COMMAND
1 root 1488 S /sbin/procd
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [kworker/0:0]
5 root 0 SW< [kworker/0:0H]
6 root 0 SW [kworker/u4:0]
7 root 0 SW [migration/0]
8 root 0 SW [rcu_bh]
9 root 0 SW [rcu_sched]
10 root 0 SW [migration/1]
11 root 0 SW [ksoftirqd/1]
13 root 0 SW< [kworker/1:0H]
14 root 0 SW< [khelper]
93 root 0 SW< [writeback]
95 root 0 SW< [bioset]
97 root 0 SW< [kblockd]
105 root 0 SW [khubd]
120 root 0 SW [kworker/1:1]
138 root 0 SW [kworker/0:1]
142 root 0 SW [kswapd0]
143 root 0 SW [fsnotify_mark]
144 root 0 SW< [crypto]
233 root 0 SW< [krfcommd]
237 root 0 SW< [deferwq]
243 root 0 SW [jfsIO]
244 root 0 SW [jfsCommit]
245 root 0 SW [jfsCommit]
246 root 0 SW [jfsSync]
258 root 0 SW< [kworker/1:1H]
298 root 0 SWN [jffs2_gcd_mtd6]
412 root 892 S /sbin/ubusd
413 root 768 S /sbin/askfirst ttyS1 /bin/ash --login
1146 root 0 SW [kworker/u4:2]
1158 root 0 SW< [kworker/0:1H]
1286 root 0 SWN [jffs2_gcd_mtd10]
1516 root 1048 S /sbin/logd -S 16
1523 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
1524 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
1525 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
2432 root 0 SW [kworker/1:2]
2552 root 1584 S /sbin/netifd
2658 root 0 SW [RtmpCmdQTask]
2659 root 0 SW [RtmpWscTask]
2660 root 0 SW [RtmpMlmeTask]
2668 root 1648 S udhcpc -p /var/run/udhcpc-br-wan.pid -s /lib/netifd/dhcp.script -f -t 0 -i br-wan -C
2869 root 0 SW [RtmpCmdQTask]
2870 root 0 SW [RtmpWscTask]
2872 root 0 SW [RtmpMlmeTask]
3146 root 1652 S /usr/sbin/crond -f -c /etc/crontabs -l 5
3227 root 4180 S /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
3232 root 1736 S /usr/sbin/dbus-daemon --system
3249 root 3360 S /usr/bin/bluetoothd -n -E
3289 root 0 SW< [kworker/u5:0]
3290 root 0 SW< [hci0]
3291 root 0 SW< [hci0]
3294 root 0 SW< [kworker/u5:2]
3446 root 1104 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
3457 root 1648 S /usr/sbin/ntpd -n -p 0.openwrt.pool.ntp.org 1.openwrt.pool.ntp.org 2.openwrt.pool.ntp.org 3.openwrt.pool.ntp.org
3499 nobody 960 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k
3905 root 1652 S {Start_NetworkMo} /bin/sh /usr/bin/Start_NetworkMonitor.sh
3922 root 1816 S {cmh-ra-daemon.s} /bin/sh /usr/bin/cmh-ra-daemon.sh 127.0.0.1 80 vera-us-oem-relay41.mios.com 31023 06290873CB11FD257074476
3988 root 1232 S ssh -p 232 -T -y -i /etc/cmh-ra/keys/cmh-ra-key.priv -R 31023:127.0.0.1:80 cmh-ra@vera-us-oem-relay41.mios.com
5030 root 1796 S {SetupRemoteAcce} /bin/sh /usr/bin/SetupRemoteAccess.sh
5125 root 1796 S {SetupRemoteAcce} /bin/sh /usr/bin/SetupRemoteAccess.sh
5126 root 1212 S ssh -y -T -p 232 -i /etc/cmh/ra_key -R 24738:127.0.0.1:22 -R 25661:127.0.0.1:80 -R 11845:127.0.0.1:23 remoteassistance@vera
5127 root 768 S /usr/bin/charperiod
6227 root 7428 S /usr/bin/NetworkMonitor
6697 root 1148 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300
9637 root 1216 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300
10068 root 1656 S -ash
13220 root 1648 S tail -f LuaUPnP.log
15503 root 1660 S {Start_LuaUPnP.s} /bin/sh /usr/bin/Start_LuaUPnP.sh
15530 root 1648 S {Start_serproxy.} /bin/sh /usr/bin/Start_serproxy.sh
16160 root 1640 S sleep 58
17248 root 0 Z [sh]
17316 root 1640 S sleep 10
17462 root 1640 S sleep 5
17531 root 1648 R ps axf
---------------after sleep-------------
PID USER VSZ STAT COMMAND
1 root 1488 S /sbin/procd
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [kworker/0:0]
5 root 0 SW< [kworker/0:0H]
6 root 0 SW [kworker/u4:0]
7 root 0 SW [migration/0]
8 root 0 SW [rcu_bh]
9 root 0 SW [rcu_sched]
10 root 0 SW [migration/1]
11 root 0 SW [ksoftirqd/1]
13 root 0 SW< [kworker/1:0H]
14 root 0 SW< [khelper]
93 root 0 SW< [writeback]
95 root 0 SW< [bioset]
97 root 0 SW< [kblockd]
105 root 0 SW [khubd]
120 root 0 SW [kworker/1:1]
138 root 0 SW [kworker/0:1]
142 root 0 SW [kswapd0]
143 root 0 SW [fsnotify_mark]
144 root 0 SW< [crypto]
233 root 0 SW< [krfcommd]
237 root 0 SW< [deferwq]
243 root 0 SW [jfsIO]
244 root 0 SW [jfsCommit]
245 root 0 SW [jfsCommit]
246 root 0 SW [jfsSync]
258 root 0 SW< [kworker/1:1H]
298 root 0 SWN [jffs2_gcd_mtd6]
412 root 892 S /sbin/ubusd
413 root 768 S /sbin/askfirst ttyS1 /bin/ash --login
1146 root 0 SW [kworker/u4:2]
1158 root 0 SW< [kworker/0:1H]
1286 root 0 SWN [jffs2_gcd_mtd10]
1516 root 1048 S /sbin/logd -S 16
1523 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
1524 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
1525 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
2432 root 0 SW [kworker/1:2]
2552 root 1584 S /sbin/netifd
2658 root 0 SW [RtmpCmdQTask]
2659 root 0 SW [RtmpWscTask]
2660 root 0 SW [RtmpMlmeTask]
2668 root 1648 S udhcpc -p /var/run/udhcpc-br-wan.pid -s /lib/netifd/dhcp.script -f -t 0 -i br-wan -C
2869 root 0 SW [RtmpCmdQTask]
2870 root 0 SW [RtmpWscTask]
2872 root 0 SW [RtmpMlmeTask]
3146 root 1652 S /usr/sbin/crond -f -c /etc/crontabs -l 5
3227 root 4180 S /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
3232 root 1736 S /usr/sbin/dbus-daemon --system
3249 root 3360 S /usr/bin/bluetoothd -n -E
3289 root 0 SW< [kworker/u5:0]
3290 root 0 SW< [hci0]
3291 root 0 SW< [hci0]
3294 root 0 SW< [kworker/u5:2]
3446 root 1104 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
3457 root 1648 S /usr/sbin/ntpd -n -p 0.openwrt.pool.ntp.org 1.openwrt.pool.ntp.org 2.openwrt.pool.ntp.org 3.openwrt.pool.ntp.org
3499 nobody 960 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k
3905 root 1652 S {Start_NetworkMo} /bin/sh /usr/bin/Start_NetworkMonitor.sh
3922 root 1816 S {cmh-ra-daemon.s} /bin/sh /usr/bin/cmh-ra-daemon.sh 127.0.0.1 80 vera-us-oem-relay41.mios.com 31023 06290873CB11FD257074476
3988 root 1232 S ssh -p 232 -T -y -i /etc/cmh-ra/keys/cmh-ra-key.priv -R 31023:127.0.0.1:80 cmh-ra@vera-us-oem-relay41.mios.com
5030 root 1796 S {SetupRemoteAcce} /bin/sh /usr/bin/SetupRemoteAccess.sh
5125 root 1796 S {SetupRemoteAcce} /bin/sh /usr/bin/SetupRemoteAccess.sh
5126 root 1212 S ssh -y -T -p 232 -i /etc/cmh/ra_key -R 24738:127.0.0.1:22 -R 25661:127.0.0.1:80 -R 11845:127.0.0.1:23 remoteassistance@vera
5127 root 768 S /usr/bin/charperiod
6227 root 7428 S /usr/bin/NetworkMonitor
6697 root 1148 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300
9637 root 1216 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300
10068 root 1656 S -ash
13220 root 1648 S tail -f LuaUPnP.log
15503 root 1660 S {Start_LuaUPnP.s} /bin/sh /usr/bin/Start_LuaUPnP.sh
15530 root 1648 S {Start_serproxy.} /bin/sh /usr/bin/Start_serproxy.sh
16160 root 1640 S sleep 58
17248 root 0 Z [sh]
17316 root 1640 S sleep 10
17462 root 1640 S sleep 5
17534 root 1648 R ps axf
---------------after kill -9-------------
PID USER VSZ STAT COMMAND
1 root 1488 S /sbin/procd
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [kworker/0:0]
5 root 0 SW< [kworker/0:0H]
6 root 0 SW [kworker/u4:0]
7 root 0 SW [migration/0]
8 root 0 SW [rcu_bh]
9 root 0 SW [rcu_sched]
10 root 0 SW [migration/1]
11 root 0 SW [ksoftirqd/1]
13 root 0 SW< [kworker/1:0H]
14 root 0 SW< [khelper]
93 root 0 SW< [writeback]
95 root 0 SW< [bioset]
97 root 0 SW< [kblockd]
105 root 0 SW [khubd]
120 root 0 SW [kworker/1:1]
138 root 0 SW [kworker/0:1]
142 root 0 SW [kswapd0]
143 root 0 SW [fsnotify_mark]
144 root 0 SW< [crypto]
233 root 0 SW< [krfcommd]
237 root 0 SW< [deferwq]
243 root 0 SW [jfsIO]
244 root 0 SW [jfsCommit]
245 root 0 SW [jfsCommit]
246 root 0 SW [jfsSync]
258 root 0 SW< [kworker/1:1H]
298 root 0 SWN [jffs2_gcd_mtd6]
412 root 892 S /sbin/ubusd
413 root 768 S /sbin/askfirst ttyS1 /bin/ash --login
1146 root 0 SW [kworker/u4:2]
1158 root 0 SW< [kworker/0:1H]
1286 root 0 SWN [jffs2_gcd_mtd10]
1516 root 1048 S /sbin/logd -S 16
1523 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
1524 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
1525 root 1132 S /usr/bin/btn -c /etc/config/button.ini -d
2432 root 0 SW [kworker/1:2]
2552 root 1584 S /sbin/netifd
2658 root 0 SW [RtmpCmdQTask]
2659 root 0 SW [RtmpWscTask]
2660 root 0 SW [RtmpMlmeTask]
2668 root 1648 S udhcpc -p /var/run/udhcpc-br-wan.pid -s /lib/netifd/dhcp.script -f -t 0 -i br-wan -C
2869 root 0 SW [RtmpCmdQTask]
2870 root 0 SW [RtmpWscTask]
2872 root 0 SW [RtmpMlmeTask]
3146 root 1652 S /usr/sbin/crond -f -c /etc/crontabs -l 5
3227 root 4180 S /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf
3232 root 1736 S /usr/sbin/dbus-daemon --system
3249 root 3360 S /usr/bin/bluetoothd -n -E
3289 root 0 SW< [kworker/u5:0]
3290 root 0 SW< [hci0]
3291 root 0 SW< [hci0]
3294 root 0 SW< [kworker/u5:2]
3446 root 1104 S /usr/sbin/ntpclient -i 600 -s -l -D -p 123 -h 0.openwrt.pool.ntp.org
3457 root 1648 S /usr/sbin/ntpd -n -p 0.openwrt.pool.ntp.org 1.openwrt.pool.ntp.org 2.openwrt.pool.ntp.org 3.openwrt.pool.ntp.org
3499 nobody 960 S /usr/sbin/dnsmasq -C /var/etc/dnsmasq.conf -k
3905 root 1652 S {Start_NetworkMo} /bin/sh /usr/bin/Start_NetworkMonitor.sh
3922 root 1816 S {cmh-ra-daemon.s} /bin/sh /usr/bin/cmh-ra-daemon.sh 127.0.0.1 80 vera-us-oem-relay41.mios.com 31023 06290873CB11FD257074476
3988 root 1232 S ssh -p 232 -T -y -i /etc/cmh-ra/keys/cmh-ra-key.priv -R 31023:127.0.0.1:80 cmh-ra@vera-us-oem-relay41.mios.com
5030 root 1796 S {SetupRemoteAcce} /bin/sh /usr/bin/SetupRemoteAccess.sh
5125 root 1796 S {SetupRemoteAcce} /bin/sh /usr/bin/SetupRemoteAccess.sh
5126 root 1212 S ssh -y -T -p 232 -i /etc/cmh/ra_key -R 24738:127.0.0.1:22 -R 25661:127.0.0.1:80 -R 11845:127.0.0.1:23 remoteassistance@vera
5127 root 768 S /usr/bin/charperiod
6227 root 7428 S /usr/bin/NetworkMonitor
6697 root 1148 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300
9637 root 1216 S /usr/sbin/dropbear -F -P /var/run/dropbear.1.pid -p 22 -K 300
10068 root 1656 S -ash
13220 root 1648 S tail -f LuaUPnP.log
15503 root 1660 S {Start_LuaUPnP.s} /bin/sh /usr/bin/Start_LuaUPnP.sh
15530 root 1648 S {Start_serproxy.} /bin/sh /usr/bin/Start_serproxy.sh
16160 root 1640 S sleep 58
17248 root 0 Z [sh]
17316 root 1640 S sleep 10
17462 root 1640 S sleep 5
17536 root 1648 R ps axf

2016-02-21 12:27:10 - LuaUPnP Terminated with Exit Code: 16
[/code]

I tried using a pin held 10 seconds to factory reset. The unit did reboot after I held the pin for a 10 count and then released it. I don’t know how to tell if it succeeded or not. The end result, however, is unchanged as it’s still stuck in that loop.

wkearney99 · February 21, 2016, 10:03pm

Support has replied and is attempting to make a connection into it. fingers crossed 8)

wkearney99 · February 21, 2016, 10:49pm

Support managed to connect. I can now continue the setup process.

bertrand · February 22, 2016, 11:23pm

Hi,

how did you solved your LUUP error? I have the exact same problem with a fresh new veraplus

Thank you

PS : I sent an email to the support

LibraSun · February 23, 2016, 8:28pm

Thank goodness I’m not the only one!! The OOBE with my VeraPlus has been pretty poor overall. Can’t believe I’ve had to submit 3-4 support requests, plus the latest one to combat this damn spinning green wheel issue (still waiting for results, though I did follow their disable/enable links per their initial response).

While I’m venting, allow me to mention how bass-ackwards the “Unpair” procedure is, as if new users are going to understand they should first attempt to “Pair” – wait for it to fail – and then expect the screen to magically change to “Unpair” and try again.

No, no, no. Don’t want to even speculate how many Vera Plus units are going to get re-boxed and shipped right back to the factory!

[quote=“wkearney99, post:2, topic:191168”]Power cycling didn’t help. Going to the veraplus IP address redirects to /cmh (on itself). This brings up a web page with the Vera logo on the left and a spinning progress circle animation on the right. Which, after several minutes, times out and goes to the “Luup engine is taking longer to reload” message.

Logging out and logging back in again did not help. Same result.

I’ve e-mailed support.

Two hours wasted on an out of the box new piece of hardware.[/quote]

LibraSun · February 23, 2016, 9:04pm

Wow, just solved my own problem, and arguably in the least likely of ways.

BY UNPLUGGING MY INSTEON MODEM from the USB port on the back of my VeraPlus. I just remembered plugging it in on Day 2 in hopes of adding Insteon functionality (nope!), but never unplugged it.

The simply physical connection must have been driving Vera crazy, leading to that “Luup taking longer to load” message.

Now I’m 100% back to my Home screen. Thanks, me!!