few questions/issues

Apps & Remote Access Vera Concierge
#1

Hi Richard

great work on vera concierge.
i’m trying to get it to work with my system and i have a few questions.

When i execute command like : “hey google ask vera concierge to turn off living room light”

it says a “sure lets get vera concierge” “connected to your vera named: vera executing: turn off living room dimmer. what else?”
then it waits for further command.

My question is, can i turn off the verbose reply? I just want it to say “executing” or “unable to execute” for example
and also, can it exit back to google home without waiting for further command??

Also the system seems quite unstable
sometimes works, sometimes doesnt… like it says its executing and everything, but the living room dimmer doesnt change.
in this instance seems i have click the update and restart the server, unlike and relink in google home, etc. i’m not sure which one makes it work again.

Thank you

  • Zed
#2

Its already on my list.

Sent from my SAMSUNG-SM-G935A using Tapatalk

#3

Rather than start a new thread, I’ll use this one as I have a few questions.

I seem to have everything configured properly as when I go to https://veraconcierge.appspot.com/web/Account, it shows my Gmail account and my associated Vera controller. If I click the button “Vera Connectivty” it shows the following just below the explanations of the buttons - {“VeraConnectivity”:“null”}. If I click the button “Local Concierge Server Connectivity”, I don’t get any message.

I currently only have one device connected to my Vera Edge hub and that is a Aeotec Z Wave Switch which in Vera I’ve called “Popcorn” and associated it to the “Kitchen”.

I ask Google Home to let me talk to Vera Concierge and it says OK. I then get the Vera Concierge so I ask “Turn on Popcorn” and it keeps replying “Which Switch?”

What am I doing wrong?

EDIT: I found this page - http://forum.micasaverde.com/index.php?topic=48913.0 - and part of it reads:

Verify that the detected Concierge Server address is the static IP address of the machine running the software and not the loopback address 127.0.01

When I look at my page - 192.168.1.74:8989 - I see the following under Discovered Devices

Last Discovery Update: 12:09:12 PM
Concierge Server IP: 127.0.1.1
Java VM: 1.8.0_141

Does that help in trying to debug why Vera Concierge can’t see devices?

#4

@MadMax1412 - I had the exact same problem, and yes, having the loopback address shown is a show-stopper. You will likely need to update your local hosts file to contain 192.168.1.74 <hostname>

Please refer to this thread for more info: [url=http://forum.micasaverde.com/index.php/topic,50558.0.html]http://forum.micasaverde.com/index.php/topic,50558.0.html[/url]

#5

Just to clarify, I update the localhost file on the computer that runs the Java (ie my Raspberry Pi which has an address of 192.168.1.74).

I remoted into my Raspberry Pi unit (using PuTTY) and entered:

cd /etc/ sudo nano hosts

The last line of the file was

127.0.1.1 raspberrypi

I changed it to

192.168.1.74 raspberrypi

I then went back to my PC, went to https://192.168.1.74:8989/ and deleted the account info.

I then rebooted the raspberrypi, whilst on the Windows PC, I closed the browser tab. Once the raspberryPi had rebooted, I went to https://192.168.1.74:8989/ and updated my info.

Now under Discovered Devices it has:

Concierge Server IP: 127.168.1.74 Java VM: 1.8.0_141

It then lists my Vera device and I validated my license and below that, it shows the name of my Google Home and one of my Chromecasts.

I clicked Update Vera Concierge Server Cloud Info and on the “My Account” page it shows my Gmail account.

Clicking on Vera Connectivity button returns {“VeraConnectivity”:“null”} and clicking on Local Concierge Server Connectivity doesn’t seem to do anything.

Now when I go to Google Home and say “Ok Google, Let me talk to my Vera Concierge” it tells me it doesn’t know how to help with that and it’s learning. Prior to these changes, it would pass me on and I would get a male voice.

Cheers

#6

Wish I could help you with the issue of the connectivity tests having no/null response. I (and others) have reported the exact same issue after ensuring the IP address is identified correctly. I am also using a Raspberry PI. I’ve had no luck at all figuring out what the problem is, but at least I do get the male concierge voice response to work.

(See the last few posts in the top stickied “Debug” thread).

#7

I think I might delete all information from the VC Cloud, reboot everything and try from scratch.

#8

You should be able to delete the “VeraDatabase*” files from the area where you installed the Vera Concierge Server software.
That should re-initialize the software, and update Vera with the address of the Concierge Server.

The problem is that your Vera still thinks the address of the Vera Concierge server is 127.0.0.1.
I did not do a good job of handling changing the Vera Concierge server address. You need to get it right the first time … or you will have problems.

#9

Thanks Richard - I was in the middle of replying to his post when I received your reply. I did not know that deleting the databases was the key to clearing the incorrect cached information. I will try that today, and report back.

Please update your documentation for Linux-based OS users to stress that the /etc/hosts file needs to be updated with the server’s static IP and hostname BEFORE launching the Java app the first time.

#10

I need to detect the change … and fix things for the users.

#11

Well, that’s even better - but wouldn’t you agree that unless your configuration app is modified to make the server IP address manually configurable (i.e., when it lists 127.0.0.1 incorrectly), that you still need to document the hosts file update requirement?

#12

OK, after deleting the 2 Vera database files, rebooting and relaunching java -jar ConciergeServer.jar, the system is now asking me for administrative (root) password to cp conciergeserver to /etc/init.d ; chmod 755…; starting the service, etc. It did not do that before, but otherwise seems to have reinstalled fine and detected the server IP, Vera’s and GoogleHome properly.

There was also no Java console information displayed in the terminal window as before. (Haven’t found a way to display the Java console on Raspbian in any other way).

Sadly, the Vera connectivity tests still are still showing null/nothing.

I’ll shelf this for now, pending any further app updates.

#13

Added “Connectivity” testing to the Local Concierge Server. (Version 1.031)
It will also provides hints on how to fix the problems.
Fixed the problem of not detecting IP changes immediately (a problem when you are trying to get the configuration working properly).

#14

Thanks Richard! Just installed the update and found the new connectivity test between local Vera and local Concierge server was successful - but I knew it had been all along. The problem continues to be the complete path connectivity tests are failing. The tests are not providing any useful information on the web page once clicked - they just do nothing or show “null”.

However, the logs now appear to be showing something is wrong with the handshake to the Vera authentication servers (I never saw these errors before)…


Oct 18, 2017 11:37:00 AM I:VeraService:Run:Stop
Oct 18, 2017 11:37:00 AM I:VeraDatabase:Save
Oct 18, 2017 11:37:00 AM I:VeraService:Start
Oct 18, 2017 11:37:00 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha11.mios.com/autha/auth/username/Gxxxxxx?SHA1Password=xxxxxxxxxxxxxxxxxxx&PK_Oem=1
Oct 18, 2017 11:37:01 AM I:VeraConnect.UI6Gateway:GetAuthToken:xxxxxxxxxxxxxxxxxxxxxxxxxx==
Oct 18, 2017 11:37:01 AM I:VeraConnect.UI6Gateway:GetAuthToken:PK_Account:xxxxxxxxxxxx
Oct 18, 2017 11:37:01 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-account12.mios.com/info/session/token
Oct 18, 2017 11:37:01 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-account12.mios.com:xxxxxxxxxxxxxxxx
Oct 18, 2017 11:37:01 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-account12.mios.com/account/account/account/xxxx1/devices
Oct 18, 2017 11:37:01 AM I:VeraConnect.VeraConnection:UpdateVeraIDs:UI6 - Gxxxxxxx:UI6-35025098;;;UI6-50010616
Oct 18, 2017 11:37:01 AM I:VeraDatabase:Restore:UI6-35025098
Oct 18, 2017 11:37:01 AM I:VeraDatabase:Restore:UI6-50010616
Oct 18, 2017 11:37:01 AM I:VeraService:Run:Start
Oct 18, 2017 11:37:01 AM V:VeraConnect.VeraConnection:GetVeraAccess:UI6-35025098
Oct 18, 2017 11:37:01 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha11.mios.com/autha/auth/username/Gxxxxxx?SHA1Password=xxxxxxxxxxxxxxxxxxxx&PK_Oem=1
Oct 18, 2017 11:37:01 AM I:VeraService:Run:Start
Oct 18, 2017 11:37:01 AM V:VeraConnect.VeraConnection:GetVeraAccess:UI6-50010616
Oct 18, 2017 11:37:01 AM V:CSWebContainer:Config Cmd:/Update
Oct 18, 2017 11:37:01 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha11.mios.com/autha/auth/username/Gxxxxxxxxxxxx?SHA1Password=xxxxxxxxxxxxx&PK_Oem=1
Oct 18, 2017 11:37:01 AM I:VeraConnect.UI6Gateway:GetAuthToken:xxxxxxxxxxxxxxxxxxxxxxxx==
Oct 18, 2017 11:37:01 AM I:VeraConnect.UI6Gateway:GetAuthToken:PK_Account:xxxx
Oct 18, 2017 11:37:01 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-account12.mios.com/info/session/token
Oct 18, 2017 11:37:01 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-account12.mios.com:xxxxxxxxxxxxxxxxxxx
Oct 18, 2017 11:37:01 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-account12.mios.com/account/account/account/xxxx/devices
Oct 18, 2017 11:37:01 AM I:VeraConnect.UI6Gateway:GetAuthToken:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==
Oct 18, 2017 11:37:02 AM I:VeraConnect.UI6Gateway:GetAuthToken:PK_Account:xxxxx
Oct 18, 2017 11:37:02 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-account12.mios.com/info/session/token
Oct 18, 2017 11:37:02 AM W:VeraConnect.UI6Gateway:UI6VeraAccess: Setting Connection Info:UI6-35025098
Oct 18, 2017 11:37:02 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-device11.mios.com/info/session/token
Oct 18, 2017 11:37:02 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-account12.mios.com:xxxxxxxxxxxx
Oct 18, 2017 11:37:02 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-account12.mios.com/account/account/account/xxxx/devices
Oct 18, 2017 11:37:02 AM W:VeraConnect.UI6Gateway:UI6VeraAccess: Setting Connection Info:UI6-50010616
Oct 18, 2017 11:37:02 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-device11.mios.com/info/session/token
Oct 18, 2017 11:37:02 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-device11.mios.com:xxxxxxxxxxx
Oct 18, 2017 11:37:02 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-device11.mios.com/device/device/device/35025098
Oct 18, 2017 11:37:02 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.0.118/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:02 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-device11.mios.com:xxxxxxxxxxxxxxx
Oct 18, 2017 11:37:02 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-device11.mios.com/device/device/device/50010616
Oct 18, 2017 11:37:02 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.2.10/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=297297381&LoadTime=1508297295
Oct 18, 2017 11:37:02 AM V:VeraService:ParseLuStatus:0
Oct 18, 2017 11:37:03 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:03 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.2.10/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=297297381&LoadTime=1508297295
Oct 18, 2017 11:37:03 AM V:VeraService:ParseLuStatus:0
Oct 18, 2017 11:37:05 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.2.10/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=297297381&LoadTime=1508297295
Oct 18, 2017 11:37:05 AM V:VeraService:ParseLuStatus:0
Oct 18, 2017 11:37:08 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:09 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.2.10/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=297297381&LoadTime=1508297295
Oct 18, 2017 11:37:09 AM V:VeraService:ParseLuStatus:0
Oct 18, 2017 11:37:13 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:17 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.2.10/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=297297381&LoadTime=1508297295
Oct 18, 2017 11:37:17 AM V:VeraService:ParseLuStatus:0
Oct 18, 2017 11:37:18 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:20 AM V:CSWebContainer:Config Cmd:/Query
Oct 18, 2017 11:37:22 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.SocketTimeoutException: connect timed out
Oct 18, 2017 11:37:22 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Oct 18, 2017 11:37:22 AM I:VeraConnect.LocalRemoteManager:URLRequest: Failed for Choice:-1
Oct 18, 2017 11:37:22 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay31.mios.com/info/session/token
Oct 18, 2017 11:37:22 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-relay31.mios.com:xxxxxxxxxxxxxxxxxxxxxxxxx
Oct 18, 2017 11:37:22 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay31.mios.com/relay/relay/relay/device/35025098/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:23 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.SocketException: Unexpected end of file from server
Oct 18, 2017 11:37:23 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay31.mios.com/relay/relay/relay/device/35025098/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:23 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:23 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.SocketException: Unexpected end of file from server
Oct 18, 2017 11:37:23 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Oct 18, 2017 11:37:23 AM I:VeraConnect.LocalRemoteManager:URLRequest: Failed for Choice:0
Oct 18, 2017 11:37:23 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay32.mios.com/info/session/token
Oct 18, 2017 11:37:23 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.ConnectException: Connection refused
Oct 18, 2017 11:37:23 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Oct 18, 2017 11:37:23 AM I:VeraConnect.UI6Gateway:GetSessionKey:  Failed for:https://vera-us-oem-relay32.mios.com
Oct 18, 2017 11:37:23 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay32.mios.com/relay/relay/relay/device/35025098/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:23 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.ConnectException: Connection refused
Oct 18, 2017 11:37:23 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay32.mios.com/relay/relay/relay/device/35025098/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:24 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.ConnectException: Connection refused
Oct 18, 2017 11:37:24 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Oct 18, 2017 11:37:24 AM I:VeraConnect.LocalRemoteManager:URLRequest: Failed for Choice:1
Oct 18, 2017 11:37:24 AM W:VeraConnect.LocalRemoteManager:URLRequest: Failed for all BaseURLs
Oct 18, 2017 11:37:24 AM W:VeraConnect.UI6Gateway:FetchURL: Get a new Auth and Try Again:UI6-35025098
Oct 18, 2017 11:37:24 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha11.mios.com/autha/auth/username/Gxxxxxx?SHA1Password=xxxxxxxxxxxxxxxxx&PK_Oem=1
Oct 18, 2017 11:37:24 AM I:VeraConnect.UI6Gateway:GetAuthToken:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==
Oct 18, 2017 11:37:24 AM I:VeraConnect.UI6Gateway:GetAuthToken:PK_Account:xxxxx
Oct 18, 2017 11:37:24 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.0.118/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:28 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:33 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:33 AM I:VeraConnect.VeraGateway:URLConnection:http://192.168.2.10/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=297297381&LoadTime=1508297295
Oct 18, 2017 11:37:33 AM V:VeraService:ParseLuStatus:0
Oct 18, 2017 11:37:38 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:43 AM V:CSWebContainer:Cmd:/Log
Oct 18, 2017 11:37:44 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.SocketTimeoutException: connect timed out
Oct 18, 2017 11:37:44 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Oct 18, 2017 11:37:44 AM I:VeraConnect.LocalRemoteManager:URLRequest: Failed for Choice:-1
Oct 18, 2017 11:37:44 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay31.mios.com/info/session/token
Oct 18, 2017 11:37:44 AM I:VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-relay31.mios.com:xxxxxxxxxxxxxxxxxxx
Oct 18, 2017 11:37:44 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay31.mios.com/relay/relay/relay/device/35025098/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:44 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.SocketException: Unexpected end of file from server
Oct 18, 2017 11:37:44 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay31.mios.com/relay/relay/relay/device/35025098/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:45 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.SocketException: Unexpected end of file from server
Oct 18, 2017 11:37:45 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Oct 18, 2017 11:37:45 AM I:VeraConnect.LocalRemoteManager:URLRequest: Failed for Choice:0
Oct 18, 2017 11:37:45 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay32.mios.com/info/session/token
Oct 18, 2017 11:37:45 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.ConnectException: Connection refused
Oct 18, 2017 11:37:45 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Oct 18, 2017 11:37:45 AM I:VeraConnect.UI6Gateway:GetSessionKey:  Failed for:https://vera-us-oem-relay32.mios.com
Oct 18, 2017 11:37:45 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay32.mios.com/relay/relay/relay/device/35025098/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:45 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.ConnectException: Connection refused
Oct 18, 2017 11:37:45 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-relay32.mios.com/relay/relay/relay/device/35025098/port_3480/data_request?output_format=json&id=lu_status2&DataVersion=838654035&LoadTime=1507838654
Oct 18, 2017 11:37:45 AM E:VeraConnect.VeraGateway:URLConnection
Exception:java.net.ConnectException: Connection refused
Oct 18, 2017 11:37:45 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Oct 18, 2017 11:37:45 AM I:VeraConnect.LocalRemoteManager:URLRequest: Failed for Choice:1
Oct 18, 2017 11:37:45 AM W:VeraConnect.LocalRemoteManager:URLRequest: Failed for all BaseURLs
Oct 18, 2017 11:37:45 AM W:VeraConnect.UI6Gateway:FetchURL: Resetting Connection Info:UI6-35025098

Does this show there is actually a problem with the Vera Control web servers, or is it a normal sequence of events trying to find a server that responds properly?

#15

What are we supposed to see in the new update?

I get this result where there’s an “Options” section with a tick that obscures part of the text, plus when I click on “Connectivity” I get a little box above it.

Prior to the upgrade, I was getting the {“Vera Connectivity”,“Null”} response.

I’ve tried deleting my account following the steps in the threads here, and deleting the VeraDatabase file (I seem to only have one whereas others talk of more than one). When I go to https://192.168.1.74:8989/ (Raspberry Pi where my java is), it seems to know my username and password already, plus my Vera devices and Google Cast devices before I even do anything - not sure why.

At the moment when I ask Google Home to let me talk to my Vera Concierge she said she can’t help with that at the moment. When I try again later (with no changes made), it says It doesn’t know how to help with that.

Thanks in advance.

#16

Sorry I am in the middle of making changes … new features are only partially working … existing features should keep working … with a possible delay while i am doing updates.

#17

MadMax… Just wanted to clarify that you will have 1 VeraDatabase for each Vera you may have. Deleting it for the purpose of recognizing IP changes should no longer be necessary.

#18

Yes. I only have one Vera Edge hub. When I read about others having more than 1 database file, I thought there might be an issue.

I didn’t realise (or know why) people would have more than one hub.

#19

@MadMax
What country are you in ?

#20

@Richard,

I have tried again after seeing that you have made further updates to the My Account page. I sure appreciate that you are trying to improve the connectivity diagnostics, but in my case - the results are still unhelpful. Now, when running the connectivity test, a popup appears which is nothing more than a tiny empty message box (formerly “null”).

Well, I’m not surprised the connectivity test isn’t working since the log file is still showing the same errors over and over again that I posted yesterday in this thread. Here is a small snip from the log. Have you had a chance to look at what could be causing these handshake errors or what else I might try to solve it?

[size=8pt]VeraGateway:URLConnection: > java io errors: connect timed out or Connection Refused
VeraGateway:URLRequest: No Response!
VeraConnect.LocalRemoteManager:URLRequest: Failed for Choice:-1
VeraConnect.UI6Gateway:GetSessionKey:https://vera-us-oem-relay31.mios.com
VeraConnect.VeraGateway:URLConnection:BadResponse:500

VeraConnect.LocalRemoteManager:URLRequest: Failed for all BaseURLs
VeraConnect.UI6Gateway:FetchURL: Get a new Auth and Try Again:UI6-35025098[/size]