Controller Offline

Anyone having an issue connecting to their controller through home.getvera.com

It isn’t working for me either. Of course, so far my Secure hasn’t worked consistently or right, since I received it. Still trying to get a refund.

Contacted tech support, they was no wait time and they fixed the issue immediately.

Mine’s doing the same thing since I asked them to take off the annoying Firmware Upgrade screen every time I log in. Connecting from my LAN works fine by over the server, not so much and I even rebooted the VeraPlus from afar using an Insigna WiFi Plug for which this is its sole purpose. About to put in yet another request for them to get it right.

Down here also

Mine went down in the middle of doing some PLEG programming earlier. Probably about the time everyone else went offline. I was so pissed though. It took over an hour before it was reachable again.

Seems we are not being told the truth. This has been an issue all day. I can remote into my PC and connect just fine. home.getvera.com will not let me in.

My controller went down today.
It is in remote location so I can’t check what’s going on, but other devices at that location are working fine.
I’ve tried to re-boot it remotely (It is plugged to WiFi remote switch) but no success.

Edit: It’s up again, with no trackable reason (no alerts from time it went down). Maybe in logs, but I don’t know how to get them remotely.

One of my Vera Plus controllers went “Offline” this week. I could access it within the network, but not remotely. Alexa could not communicate with the controller. All lights on the box were green. Rebooting everything did not work.

I called Vera Controls tech support. They established a remote session to my desktop, added a few lines of code to Vera and got the controller online. Then, the technician was able to gain remote access to my controller. After a few minutes, everything was working again.

He said my controller was running out of memory and he deleted temp files to clear up space. The controller has been in service about two years and this was the first trouble I’ve encountered.

My VeraPlus went “offline” (according to GetVera.com) last night. This morning I checked and GetVera.com was still showing it as “offline”, but I was able to HTTP directly into the LAN IP with no problems and everything looked fine. I went to Settings → Net & WiFi and re-saved my network settings (which were set to configure automatically). The VeraPlus said it was restarting the network and appeared to boot at least 2 or 3 times, but when all was done everything looks OK and I can now login via GetVera.com.

I’d love to know what “temporary files” Tech Support is cleaning up for you and get rid of them on mine as well (or better yet, have the VeraPlus clean itself up automatically regularly!), I constantly see stuff like this in my log:

01 02/08/18 7:21:17.217 UserData::WriteUserData saved–before move File Size: 49133 save size 49133 <0x77216520>
02 02/08/18 7:21:17.217 UserData::TempLogFileSystemFailure start 0 <0x77216520>
02 02/08/18 7:21:17.237 UserData::TempLogFileSystemFailure 4726 res:1

It looks like the VeraPlus does a soft restart, a list of system files is displayed and then it seems to run normally for 5 or 10 minutes before this repeats, over and over again. Among the files shown are a bunch of dumps a json backups, not sure that it needs to have so many if it is running out of space all the time:

[font=courier]/etc/cmh/wan_failover:
-rw-r–r-- 1 root root 44 Aug 18 12:17 check_internet.hosts
<0x77216520>
02 02/08/18 7:51:17.302 UserData::TempLogFileSystemFailure start 0 <0x77216520>
02 02/08/18 7:51:17.323 UserData::TempLogFileSystemFailure 4637 res:1
-rw-r–r-- 1 root root 33 Oct 16 14:09 /etc/cmh/HW_Key
-rw-r–r-- 1 root root 33 Oct 16 14:09 /etc/cmh/HW_Key2
-rw-r–r-- 1 root root 9 Oct 16 14:09 /etc/cmh/PK_AccessPoint
-rw-r–r-- 1 root root 7 Nov 24 11:48 /etc/cmh/PK_Account
-rw-r–r-- 1 root root 423 Oct 18 14:08 /etc/cmh/cmh.conf
-rw-r–r-- 1 root root 0 Oct 6 06:43 /etc/cmh/devices
-rw-r–r-- 1 root root 16383 Dec 21 13:37 /etc/cmh/dongle.4.5.dump.0
-rw-r–r-- 1 root root 16383 Nov 25 11:21 /etc/cmh/dongle.4.5.dump.1
-rw-r–r-- 1 root root 16383 Nov 25 10:28 /etc/cmh/dongle.4.5.dump.2
-rw-r–r-- 1 root root 16383 Nov 24 19:43 /etc/cmh/dongle.4.5.dump.3
-rw-r–r-- 1 root root 16383 Nov 24 16:34 /etc/cmh/dongle.4.5.dump.4
-rw-r–r-- 1 root root 16383 Nov 10 03:00 /etc/cmh/dongle.4.5.dump.5
-rw-r–r-- 1 root root 41 Oct 16 14:12 /etc/cmh/ergy_key
-rw-r–r-- 1 root root 0 Oct 6 06:43 /etc/cmh/first_boot
-rw-r–r-- 1 root root 0 Feb 8 06:57 /etc/cmh/fresh_install
-rw-r–r-- 1 root root 1 Feb 8 06:59 /etc/cmh/ip_mode
-rw-r–r-- 1 root root 48 Oct 16 14:10 /etc/cmh/keys
-rw-r–r-- 1 root root 3 Oct 6 06:43 /etc/cmh/language
-rw-r–r-- 1 root root 2 Oct 6 06:43 /etc/cmh/language_id
-rw-r–r-- 1 root root 10 Feb 7 11:52 /etc/cmh/last_backup
-rw-r–r-- 1 root root 11 Feb 8 07:00 /etc/cmh/last_report
-rw-r–r-- 1 root root 70 Dec 12 21:27 /etc/cmh/lighttpd_failures
-rw-r–r-- 1 root root 36316 Aug 18 12:17 /etc/cmh/network_pnp.lua
-rw-r–r-- 1 root root 12 Oct 6 06:43 /etc/cmh/platform
-rw-r–r-- 1 root root 458 Aug 18 12:17 /etc/cmh/ra_key
-rw-r–r-- 1 root root 0 Oct 6 06:43 /etc/cmh/scenarios
-rw-r–r-- 1 root root 2032 Jan 11 13:27 /etc/cmh/servers.conf
-rw-r–r-- 1 root root 1520 Oct 6 06:40 /etc/cmh/servers.conf.default
-rw-r–r-- 1 root root 20 Jan 15 21:27 /etc/cmh/servers.conf.timestamp
-rw-r–r-- 1 root root 154 Aug 18 12:17 /etc/cmh/servers_whitelist
-rw-r–r-- 1 root root 1598 Feb 8 07:00 /etc/cmh/services.conf
-rw-r–r-- 1 root root 20 Oct 16 14:11 /etc/cmh/sync_kit
-rw-r–r-- 1 root root 20 Oct 16 14:11 /etc/cmh/sync_rediscover
-rw-r–r-- 1 root root 2 Oct 6 06:43 /etc/cmh/ui
-rw-r–r-- 1 root root 2 Oct 6 06:43 /etc/cmh/ui_man
-rw-r–r-- 1 root root 5 Oct 6 06:43 /etc/cmh/ui_skin
-rw-r–r-- 1 root root 504 Aug 18 12:17 /etc/cmh/user_data.json.luup.lzo
-rw-r–r-- 1 root root 49095 Feb 8 07:51 /etc/cmh/user_data.json.lzo
-rw-r–r-- 1 root root 49113 Feb 8 07:45 /etc/cmh/user_data.json.lzo.1
-rw-r–r-- 1 root root 49131 Feb 8 07:39 /etc/cmh/user_data.json.lzo.2
-rw-r–r-- 1 root root 49115 Feb 8 07:33 /etc/cmh/user_data.json.lzo.3
-rw-r–r-- 1 root root 49123 Feb 8 07:27 /etc/cmh/user_data.json.lzo.4
-rw-r–r-- 1 root root 49133 Feb 8 07:21 /etc/cmh/user_data.json.lzo.5
-rw-r–r-- 1 root root 37 Nov 24 11:48 /etc/cmh/users.conf
-rw-r–r-- 1 root root 20 Nov 24 11:48 /etc/cmh/users.conf.timestamp
-rw-r–r-- 1 root root 3 Oct 6 06:43 /etc/cmh/vera_model
-rw-r–r-- 1 root root 9 Oct 6 06:43 /etc/cmh/version
-rw-r–r-- 1 root root 9 Feb 8 06:59 /etc/cmh/version_latest
-rw-r–r-- 1 root root 5 Oct 16 14:09 /etc/cmh/zigbee_version
-rw-r–r-- 1 root root 8 Feb 8 07:48 /etc/cmh/zwave_house_id
-rw-r–r-- 1 root root 3 Oct 16 14:09 /etc/cmh/zwave_locale
-rw-r–r-- 1 root root 48 Feb 8 07:00 /etc/cmh/zwave_version

/etc/cmh/orig:
-rw-r–r-- 1 root root 0 Oct 6 06:43 devices
-rw-r–r-- 1 root root 0 Oct 6 06:43 first_boot
-rw-r–r-- 1 root root 0 Oct 6 06:43 fresh_install
-rw-r–r-- 1 root root 0 Oct 6 06:43 scenarios
-rw-r–r-- 1 root root 523 Oct 6 06:43 user_data.json.lzo
[/font]

What you are seeing, as silly as it looks, is Vera saving user data every 6 minutes. There’s nothing wrong and it isn’t restarting.

01 02/08/18 7:21:17.217 UserData::WriteUserData saved–before move File Size: 49133 save size 49133 <0x77216520> This is the indication that the user data save was successful. The rest of the listing is debug info. This question has been asked for years on this forum, and so far Vera shows no inclination to change the behavior.

Thanks HSD99, that’s good to know - why in the world they consider this acceptable is beyond me. If this is a “normal” scheduled event, DON’T report it as a TempLogFileSystemFailure - that sure doesn’t sound “normal”! And at least give us the option to “hide” all this chatty stuff, the log is busy enough to read without a screen full of useless data every 6 minutes. :frowning:

Yup. Sadly, the logs aren’t designed to be user-friendly—they are for Vera’s developers. And you may have noticed on the Settings—> Logs page, that there is an option for Verbose logging!! :frowning:

Yup, I turned on Verbose once just to see what else would be logged - it was a LOT. :slight_smile:

I’d settle for a checkbox that said "Comphensible Logging!!