Vera - Smarter Home Control Forum

General => Remote Control => Google Home/Google Assistant - Vera Concierge => Topic started by: zednine on September 18, 2017, 07:25:28 am

Title: few questions/issues
Post by: zednine on September 18, 2017, 07:25:28 am
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
Title: Re: few questions/issues
Post by: RichardTSchaefer on September 18, 2017, 02:39:59 pm
Its already on my list.

Sent from my SAMSUNG-SM-G935A using Tapatalk

Title: Re: few questions/issues
Post by: MadMax1412 on October 11, 2017, 06:03:45 pm
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 (http://www.smarthome.com.au/aeotec-z-wave-plug-in-smart-switch-6.html) 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:

Quote
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?
Title: Re: few questions/issues
Post by: GaryOkie on October 12, 2017, 02:33:56 pm
@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:  http://forum.micasaverde.com/index.php/topic,50558.0.html (http://forum.micasaverde.com/index.php/topic,50558.0.html)

Title: Re: few questions/issues
Post by: MadMax1412 on October 12, 2017, 04:00:53 pm
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:

Quote
cd /etc/
sudo nano hosts

The last line of the file was

Quote
127.0.1.1    raspberrypi

I changed it to

Quote
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:

Quote
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
Title: Re: few questions/issues
Post by: GaryOkie on October 13, 2017, 10:08:51 am
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).



 
Title: Re: few questions/issues
Post by: MadMax1412 on October 13, 2017, 07:25:20 pm
I think I might delete all information from the VC Cloud, reboot everything and try from scratch.
Title: Re: few questions/issues
Post by: RichardTSchaefer on October 16, 2017, 11:42:38 am
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.
Title: Re: few questions/issues
Post by: GaryOkie on October 16, 2017, 11:51:53 am
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.
Title: Re: few questions/issues
Post by: RichardTSchaefer on October 16, 2017, 11:56:41 am
I need to detect the change ... and fix things for the users.
Title: Re: few questions/issues
Post by: GaryOkie on October 16, 2017, 12:03:49 pm
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?
Title: Re: few questions/issues
Post by: GaryOkie on October 16, 2017, 01:25:43 pm
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.
 

Title: Re: few questions/issues
Post by: RichardTSchaefer on October 18, 2017, 10:00:03 am
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).

 
Title: Re: few questions/issues
Post by: GaryOkie on October 18, 2017, 01:09:11 pm
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)...
Code: [Select]

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?
Title: Re: few questions/issues
Post by: MadMax1412 on October 18, 2017, 08:04:04 pm
What are we supposed to see in the new update?

I get this result (https://drive.google.com/open?id=0B7qhDetEFHRoZjZPOGw5SGl2TkE) 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.
Title: Re: few questions/issues
Post by: RichardTSchaefer on October 18, 2017, 08:44:52 pm
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.
Title: Re: few questions/issues
Post by: GaryOkie on October 19, 2017, 12:06:39 am
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.
Title: Re: few questions/issues
Post by: MadMax1412 on October 19, 2017, 12:55:17 am
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.
Title: Re: few questions/issues
Post by: RichardTSchaefer on October 19, 2017, 09:19:47 am
@MadMax
What country are you in ?
Title: Re: few questions/issues
Post by: GaryOkie on October 19, 2017, 12:44:34 pm
@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?

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


Title: Re: few questions/issues
Post by: MadMax1412 on October 19, 2017, 04:24:18 pm
@MadMax
What country are you in ?

Australia
Title: Re: few questions/issues
Post by: RichardTSchaefer on October 19, 2017, 04:45:35 pm
Try setting your Language to "English US".
Title: Re: few questions/issues
Post by: MadMax1412 on October 19, 2017, 08:43:20 pm
Try setting your Language to "English US".

Google Home says that it appears my account is not linked and I can do that by the Google Home app.

I can't for the life of me see any reference to Vera Concierge in the app or work out how to link.  What are the steps for this?  I'm using Google Home version 1.25.81.17 which updated on Oct 4th, 2017.
Title: Re: few questions/issues
Post by: RichardTSchaefer on October 19, 2017, 08:52:21 pm
@GaryOkie
Sorry I missed your response. This looks like it is having problems talking to the Vera Remote access servers.
Did you change your password after configuring the Concierge Server ?
If you are still having problems I suggest the following:
1) In the "Local Concierge Server" installation area.
    There should be an uninstall script. Execute it!
    This should shut down the "Local Concierge Server"
    Delete all the files except ConciergeServer.jar.
    If you have not already upgraded to Version 1.031 then delete it and download the latest Version.
2) ReInstall the Local Concierge Server
3) Start the Log right away before entering ANY data.
4) Do your configuration, connectivity tests, and updating Cloud info.
5) Email me the log when you are done if you still have problems.


Title: Re: few questions/issues
Post by: RichardTSchaefer on October 19, 2017, 08:59:44 pm
@MadMax1412
This is something that has continuously changes since Google Assistant was introduced.
It was a flat list when it started. As the number of APPS increased ... it became quite unusable.

NOW in the menu there is an "Explore" option.
Search for "Vera Concierge"
Title: Re: few questions/issues
Post by: GaryOkie on October 20, 2017, 07:38:03 pm
@Richard - thanks for the advice. 

 I had already done the delete everything/reinstall process yesterday, but gave it another go.   The result was identical - it is failing to connect to the Vera servers.    The log info I previously provided in reply#13 has the same errors, but I will email you the full log.

I mentioned this before, but the install process is prompting me for the admin password several times before it completes.   It did not do this on the very first install.   It also doesn't show any Java console output in the terminal window as it did on the first install.

I think I may need to just rebuild the Raspberry with a different OS than Raspbian.
Title: Re: few questions/issues
Post by: MadMax1412 on October 20, 2017, 08:43:55 pm
NOW in the menu there is an "Explore" option.
Search for "Vera Concierge"

Did that, found it and clicked on "Try It".

It takes me to my Google Assistant screen like it does when I ask my phone a question.  The only problem is that Google's response doesn't come.  It just sits on the 3 pulsating dots as shown here (https://drive.google.com/open?id=0B7qhDetEFHRoWG9XdklReDZ4XzQ).

When it comes to trying to determine where the fault lies, I think my configuration must be ok.  When I go to https://192.168.1.74:8989/ (https://drive.google.com/open?id=0B7qhDetEFHRoRVJkSmNpemNOSjQ) and go down to Vera Devices and click on "Custom settings", it shows my Aoetec Smart Switch which I called "Popcorn" and assigned to the Kitchen as shown in this screenshot (https://drive.google.com/open?id=0B7qhDetEFHRoZVMwMVlWc1BFZ0k).

BTW, a few days ago I had installed the Vera Concierge app from the Play Store.  When I say "Turn on Popcorn", it responds "Which Switch?" - See screenshot (https://drive.google.com/open?id=0B7qhDetEFHRoa0xkV2pvNzRnV0U).

If I go to my Google Home and ask "Let me talk to Vera Concierge" it says "I don't know how to help with that" as shown in this screenshot (https://drive.google.com/open?id=0B7qhDetEFHRoWVMzV3hLdC1vNmc) of my activity.  A few days ago (I think prior to me deleting the Vera Database files from the Raspberry Pi and trying the setup again), when I asked it the same question, it put me through to Vera Concierge and I got a male voice telling me of the service etc, but when I asked him to turn on Popcorn, he said "Which Switch".

I've gone through the "Debug your configuration" thread and tried all the steps and I can't see what I'm doing wrong, if anything.  I've even changed my language settings to US rather than AUS as suggested but it hasn't helped.

When I bought the Google Home, I was very excited about starting my journey into home automation using voice controls.  Samsung's SmartThings hub isn't available in Australia, so I opted for the Vera Edge to control my Z-wave unit.  So until I can get this one Z-wave unit to work via voice, I'm holding off on buying anything else such as switches for my downlights etc.

There's nothing in the settings within the Vera Dashboard side of things that can affect this, is there? 

Is the fact my browser shows the connection as not secure, even though I installed the security certificate, causing any issues?

Just grasping at straws here as I can't see anything wrong in my setup.
Title: Re: few questions/issues
Post by: RichardTSchaefer on October 20, 2017, 11:26:30 pm
@MadMax1412
What happens when you do connectivity on the Local Concierge Server and the Cloud Server ?
By any chance have you configured your Vera as  "Secure"  (User and Account Info -> Unit Settings) ?
I have been told that connectivity fails if that is turned on.

Also let me know what your Vera Serial # is ... so I can look in the Server Logs.
Title: Re: few questions/issues
Post by: MadMax1412 on October 21, 2017, 03:26:10 am
By any chance have you configured your Vera as  "Secure"  (User and Account Info -> Unit Settings) ?
I have been told that connectivity fails if that is turned on.

It shows a greyed out box with a tick in it next to "Secure Your Vera", but when I click on the box it says "Confirmation required
By enabling this option you will not have local access to your Vera. You will only be able to access your Vera through relay. Are you sure you want to continue?
" at which point I cancel out.  So although the box has a tick in it, the fact that both the box and tick are grey I gather means it's not enabled.

What happens when you do connectivity on the Local Concierge Server and the Cloud Server ?

If you mean going to https://192.168.1.74:8989/ and going down to the section called "Vera Devices" and clicking on the button called "Connectivity", then I get a response that reads: Successfull bi-diretional connectivity  (that's the spelling it's got BTW).

Also let me know what your Vera Serial # is ... so I can look in the Server Logs.
The serial number is 45202318
Title: Re: few questions/issues
Post by: GaryOkie on October 21, 2017, 12:17:13 pm
just noticed a new update was released to support UI7 mixed case names.   That probably explains why my connectivity to Vera servers was failing.    Installing update now, and will report back.

EDIT:  Latest update did indeed fix my issue! 
Title: Re: few questions/issues
Post by: MadMax1412 on October 23, 2017, 06:34:17 pm
Just a heads up in case your servers are running hard....

My commands to Google Home are working (eg Vera is turning on or off the lights), but Google Home then responds with Vera Concierge isn't responding right now. Please try again later.
Title: Re: few questions/issues
Post by: MadMax1412 on April 02, 2018, 05:13:17 am
Just a quick question/clarification

My home network was recently changed from 192.168.1.x to 192.168.178.x due to a new router.  I've got the Raspberry Pi connected to my new Wi-Fi and it's been given the new address etc and now when I go to https://<IP Address of Pi>:8989, I can connect.

I thought that I hadn't touched this since I had only a Google Home but now have a number of Google Home Minis and "Groups" which now appear on this page under the heading "Google Cast Devices".  I thought I had better click on "Update Vera Concierge Server Cloud" just to make sure everything worked ok.

This takes me to https://veraconcierge.appspot.com/web/Account and under "Associated Vera Controllers" it shows my Vera unit name, my account name and a Connectivity button.  When I click on this button, I get the message:

Quote
Can't talk to your local concierge server. Check the connectivity on your local Concierge Server

Am I getting that message because of "Google has temporarily removed the Concierge Agent!" or is it something I still need to do since the Raspberry Pi has a new IP address?

Thanks in advance.
Title: Re: few questions/issues
Post by: Inzax on April 02, 2018, 08:37:17 am
@madmax.  The connectivity test button still works for me.  So, you are having another issue.  Unfortunately, I would only being throwing out wild guesses on how to fix but it sounds like the connectivity test is still looking for your old IP.  On mine, I had to tweak my firewall rules to point to my new internal IP address for VC.
Title: Re: few questions/issues
Post by: MadMax1412 on April 16, 2018, 06:40:21 am
Hi

Any answer to my question I posed in the last paragraph? I don't think it's my firewall as I didn't have to do anything when the IP address of the Raspberry pi was 192.168.1.x so not sure what else I need to do now it's IP address is 192.168.178.x

EDIT:

Hey guys,

I'm wondering if it has anything to do with the security certificate.

When I go to <IP Address of Pi>:8989, it shows (Not Secure) https://(IP Address of PI):8989/

I have clicked on the UnSecureWeb tab and downloaded the certificate and installed it as both "current user" and "Local" machine" in the following locations: Trusted Root Certification Authorities and also the sub-directory "Registry".

My web browser (chrome) still shows as unsecure.