Decipher Vera Plus Logs

Vera Controllers, Services & Devices General Vera Discussions
1

Like a few others I have seen some erratic behavior with my Vera Plus system recently. Odd logs in scenes and delays with motion sensor triggered scenes. These have been stable for years now so it just seems a bit odd.

I looked in the logs to see if I could decipher anything but pretty cryptic stuff there.

I did see one pattern repeated a dozen times or so that really surprised me (below). The same group of lines are present for several IP addresses on my LAN 192.168.2.106, …92, …108, …59, …102, …61, …70, …62, …86, …

What is odd is that none of these addresses have anything to do with Vera. Some are WiFi thermostats, one is an iPhone, and a couple are empty IP addresses.

I am wondering how and why Vera would be doing anything with these IP addresses? A few years ago I had the Honeywell TSTAT plug in installed but I dumped that in favor of the native iPhone app to control my thermostats. So I unloaded the plug in and it no longer shows in teh My Apps tab in Vera.

So I am wondering if I have left over bits from old plug ins that didn’t uninstall fully meaning there are tasks running for apps that no longer exist?? Other reasons for this log activity?

01 01/02/24 16:45:55.194 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.199 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/CgiTagMenu?page=Top&Language=0 response: <0x764c8520>
01 01/02/24 16:45:55.202 FileUtils::ReadURL 7/resp:0 user:admin pass: size 1 http://192.168.2.61/CgiTagMenu?page=Top&Language=0 response: <0x764c8520>
01 01/02/24 16:45:55.206 FileUtils::ReadURL 7/resp:0 user:dceadmin pass:dcepass size 1 http://192.168.2.61/CgiTagMenu?page=Top&Language=0 response: <0x764c8520>
01 01/02/24 16:45:55.210 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/top.htm response: <0x764c8520>
01 01/02/24 16:45:55.213 FileUtils::ReadURL 7/resp:0 user:admin pass: size 1 http://192.168.2.61/top.htm response: <0x764c8520>
01 01/02/24 16:45:55.217 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/index.html response: <0x764c8520>
01 01/02/24 16:45:55.220 FileUtils::ReadURL 7/resp:0 user:admin pass: size 1 http://192.168.2.61/index.html response: <0x764c8520>
01 01/02/24 16:45:55.224 FileUtils::ReadURL 7/resp:0 user:dceadmin pass:dcepass size 1 http://192.168.2.61/index.html response: <0x764c8520>
01 01/02/24 16:45:55.229 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.232 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/cgi-bin/CGIProxy.fcgi response: <0x764c8520>
01 01/02/24 16:45:55.237 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/get_status.cgi response: <0x764c8520>
01 01/02/24 16:45:55.241 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/cgi-bin/get_status.cgi response: <0x764c8520>
01 01/02/24 16:45:55.245 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/get_status.cgi response: <0x764c8520>
01 01/02/24 16:45:55.248 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.251 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/pages/camera_login.php?login=true response: <0x764c8520>
01 01/02/24 16:45:55.255 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/check_user.cgi?user=test&pwd=test response: <0x764c8520>
01 01/02/24 16:45:55.258 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.262 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/common/info.cgi response: <0x764c8520>
01 01/02/24 16:45:55.265 FileUtils::ReadURL 7/resp:0 user:admin pass:admin size 1 http://192.168.2.61/common/info.cgi response: <0x764c8520>
01 01/02/24 16:45:55.269 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/common/info.cgi response: <0x764c8520>
01 01/02/24 16:45:55.272 FileUtils::ReadURL 7/resp:0 user:admin pass:admin size 1 http://192.168.2.61/common/info.cgi response: <0x764c8520>
01 01/02/24 16:45:55.276 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/SDK/activateStatus response: <0x764c8520>
01 01/02/24 16:45:55.279 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/SDK/activateStatus response: <0x764c8520>
01 01/02/24 16:45:55.283 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.294 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.297 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.301 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.304 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61:3580/ISAPI/System/deviceInfo response: <0x764c8520>
01 01/02/24 16:45:55.307 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61:3580/ISAPI/System/deviceInfo response: <0x764c8520>
01 01/02/24 16:45:55.311 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61:3580/ISAPI/System/deviceInfo response: <0x764c8520>
01 01/02/24 16:45:55.314 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61:3580/ISAPI/System/deviceInfo response: <0x764c8520>
01 01/02/24 16:45:55.318 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/util/query.cgi response: <0x764c8520>
01 01/02/24 16:45:55.321 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/SDK/activateStatus response: <0x764c8520>
01 01/02/24 16:45:55.325 FileUtils::ReadURL 7/resp:0 user: pass: size 1 http://192.168.2.61/SDK/activateStatus response: <0x764c8520>
2

There is a setting somewhere to do with Vera detecting other devices on the LAN I have it turned off I think. I will find the setting location soon.

I am also having issues with my motion sensors and MSR rules for them being slow, like turning on or off lights…

What is IP 192.168.2.61 ?

3

Screenshot_20240103-142038_Chrome
Screenshot_20240103-142038_Chrome720×1600 180 KB

Net & Wifi - Automatic Device Detection make sure that is turned off.

4

Uninstalling plugins should stop any activity that was previously associated with that plugin. However I do know that when you uninstall a plugin its files are not actually removed off the system. I had to manually go into this folder using WinSCP and delete any files I thought were related to a plugin I had uninstalled etc.

/etc/cmh-ludl

For example looking in my folder now I see there are files still present for Dark Sky Weather plugin, yet I no longer have that plugin on my Vera controller, so I will need to delete those files.

Obviously be very careful deleting files and don’t delete any you are not 100% sure about.

image
image679×623 82.5 KB

5

It looks like an IP Camera.

I did see some entries like these in my log which appeared to be related to IP cams.

12	01/03/24 14:57:57.582	luvd_get_info_data_request starting /data_request?id=request_image&cam=474&res=low pMem 0x3594000/56180736 diff: 39297024 <0x6c1ab520>
12	01/03/24 14:57:57.585	luvd_get_info_data_request starting /data_request?id=request_image&cam=476&res=low pMem 0x3594000/56180736 diff: 39297024 <0x6af20520>
02	01/03/24 14:57:57.612	write_data_header failed with 0/401 0x48 0x54 0x54 0x50 0x2f 0x31 0x2e 0x31 0x20 0x34 0x30 0x31 0x20 0x55 0x6e 0x61 0x75 0x74 0x68 0x6f 0x72 0x69 0x7a 0x65 0x64 0xd 0xa (HTTP/1.1 401 Unauthorized\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.612	write_data_header wrote:0 bytes:27 <0x6c1ab520>
02	01/03/24 14:57:57.612	write_data_header failed with 0/401 0x44 0x61 0x74 0x65 0x3a 0x20 0x57 0x65 0x64 0x2c 0x20 0x30 0x33 0x20 0x4a 0x61 0x6e 0x20 0x32 0x30 0x32 0x34 0x20 0x31 0x34 0x3a 0x35 0x37 0x3a 0x35 0x35 0x20 0x47 0x4d 0x54 0xd 0xa (Date: Wed, 03 Jan 2024 14:57:55 GMT\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.613	write_data_header wrote:0 bytes:37 <0x6c1ab520>
02	01/03/24 14:57:57.614	write_data_header failed with 0/401 0x53 0x65 0x72 0x76 0x65 0x72 0x3a 0x20 0x77 0x65 0x62 0x73 0x65 0x72 0x76 0x65 0x72 0xd 0xa (Server: webserver\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.614	write_data_header wrote:0 bytes:19 <0x6c1ab520>
02	01/03/24 14:57:57.614	write_data_header failed with 0/401 0x58 0x2d 0x43 0x6f 0x6e 0x74 0x65 0x6e 0x74 0x2d 0x54 0x79 0x70 0x65 0x2d 0x4f 0x70 0x74 0x69 0x6f 0x6e 0x73 0x3a 0x20 0x6e 0x6f 0x73 0x6e 0x69 0x66 0x66 0xd 0xa (X-Content-Type-Options: nosniff\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.617	write_data_header wrote:0 bytes:33 <0x6c1ab520>
02	01/03/24 14:57:57.618	write_data_header failed with 0/401 0x58 0x2d 0x46 0x72 0x61 0x6d 0x65 0x2d 0x4f 0x70 0x74 0x69 0x6f 0x6e 0x73 0x3a 0x20 0x53 0x41 0x4d 0x45 0x4f 0x52 0x49 0x47 0x49 0x4e 0xd 0xa (X-Frame-Options: SAMEORIGIN\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.619	write_data_header wrote:0 bytes:29 <0x6c1ab520>
02	01/03/24 14:57:57.619	write_data_header failed with 0/401 0x58 0x2d 0x58 0x53 0x53 0x2d 0x50 0x72 0x6f 0x74 0x65 0x63 0x74 0x69 0x6f 0x6e 0x3a 0x20 0x31 0x3b 0x20 0x6d 0x6f 0x64 0x65 0x3d 0x62 0x6c 0x6f 0x63 0x6b 0xd 0xa (X-XSS-Protection: 1; mode=block\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.620	write_data_header wrote:0 bytes:33 <0x6c1ab520>
02	01/03/24 14:57:57.620	write_data_header failed with 0/401 0x43 0x6f 0x6e 0x74 0x65 0x6e 0x74 0x2d 0x4c 0x65 0x6e 0x67 0x74 0x68 0x3a 0x20 0x31 0x37 0x38 0xd 0xa (Content-Length: 178\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.620	write_data_header wrote:0 bytes:21 <0x6c1ab520>
02	01/03/24 14:57:57.621	write_data_header failed with 0/401 0x43 0x6f 0x6e 0x74 0x65 0x6e 0x74 0x2d 0x54 0x79 0x70 0x65 0x3a 0x20 0x74 0x65 0x78 0x74 0x2f 0x68 0x74 0x6d 0x6c 0xd 0xa (Content-Type: text/html\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.622	write_data_header wrote:0 bytes:25 <0x6c1ab520>
02	01/03/24 14:57:57.622	write_data_header failed with 0/401 0x43 0x6f 0x6e 0x6e 0x65 0x63 0x74 0x69 0x6f 0x6e 0x3a 0x20 0x63 0x6c 0x6f 0x73 0x65 0xd 0xa (Connection: close\r\n) <0x6c1ab520>
02	01/03/24 14:57:57.623	write_data_header wrote:0 bytes:19 <0x6c1ab520>```

My IP cams still work though in the Vera UI7 web interface.
6

Thanks cw-kid,

192.168.2.61 is a Honeywell WiFi Thermostat. I can ping it from a command prompt but it doesn’t launch a log in screen from a browser to that address.

I did have the auto detection of devices check mark turned on so have disabled it now. I just rebooted so we’ll see if those entries stop going into the logs.

I do have several IP cameras on my system but they are all static IP starting at 192.168.2.170 and higher. I might have had a camera at some of these addresses long ago when I first set them up and before I decided to make them all static IP but that would have been a 4+ years ago.

To me it looked like a periodic polling event from Vera to a device. Not clear what in Vera is triggering the polling.

Anyway not sure this is anything. I guess I’ll check back in a couple hours and see if the entries remain.

Update: after 2 hours those rogue entries seemed to have disappeared. So it must have been background polling when auto detect is on?

7

Likely something like that, that Auto Detection of Devices was always dubious, why I’ve never had it turned On.