Author Topic: Vera Concierge Setup Issue  (Read 1881 times)

Offline CheckedOut

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +1/-0
Vera Concierge Setup Issue
« on: December 26, 2017, 11:43:14 pm »
I am trying to get my Google Home working with Vera and i have started an install of the Vera Concierge server. It looks like a very cool solution and I'm looking forward to getting it working.

Unfortunately, I have not been able to get it up and running successfully. I have a problem with Vera Concierge not finding my google home device as well as the Vera system itself. Basically nothing shows up on the admin site after i have entered the vera creds and restarted. I am suspecting some sort of dependency or configuration problem. Any suggestions?

I am running Ubuntu in a VM:

Linux version 4.13.0-21-generic (buildd@lgw01-amd64-037) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)) #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017

On the server page from a remote machine i see the following:

Concierge Server IP: 127.0.1.1
Java VM: 9-Ubuntu

On the log page i see the following:
Dec 26, 2017, 8:27:04 PM V:CSWebContainer:Config Cmd:/Query
Dec 26, 2017, 8:27:11 PM V:CSWebContainer:Cmd:/Log
Dec 26, 2017, 8:27:16 PM V:CSWebContainer:Cmd:/Log
Dec 26, 2017, 8:27:21 PM V:CSWebContainer:Cmd:/Log
Dec 26, 2017, 8:27:26 PM V:CSWebContainer:Cmd:/Log

There are not obvious log records /var/log/syslog .

At a glance it looks like the server is running on the wrong network/ local interface. Should the concierge server be the localhost ip and not the public ip? Can i configure this?

Also, One other thing that i noticed after install was that the default port 8989 was only listening in IP v6 and not IP v4. I was able to quickly identify this problem by using netstat -t. I am not sure why this happened, but it was fixed by disabling ipv6 on the host.

Off topic but I have a quick list of suggestions for the tool to make it better and more secure:

1) Allow limit or selection of server ip address and ipv6 vs ipv4 as a command line arg
2) Change form combo box to hash so that passwords are not exposed
3) Enable a default password for the admin https site that can be changed by the user
4) Provide additional documentation on where the logging lives etc

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10091
  • Karma: +764/-142
Re: Vera Concierge Setup Issue
« Reply #1 on: December 27, 2017, 06:59:23 am »
The Local Vera Concierge Server, your Google Home Devices, and your Vera need to be on the same Local area network (i.e. the first 3 numbers of your IP need to be the same. Something like  192.168.10.xxx  and the xxx is different for each device.

There are tricks to do this with a VM ...   

Offline CheckedOut

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +1/-0
Re: Vera Concierge Setup Issue
« Reply #2 on: December 27, 2017, 01:23:30 pm »
Ok. Please let me know what the tricks are....I have a statically assigned address on eth0.

How are you determining which interface to use? I would assume that you grab any interface that isn't the loopback?

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.5  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 00:15:5d:0c:6c:05  txqueuelen 1000  (Ethernet)
        RX packets 129726  bytes 22422632 (22.4 MB)
        RX errors 0  dropped 36  overruns 0  frame 0
        TX packets 5211  bytes 1028550 (1.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 85  bytes 6233 (6.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 85  bytes 6233 (6.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10091
  • Karma: +764/-142
Re: Vera Concierge Setup Issue
« Reply #3 on: December 27, 2017, 01:28:37 pm »
If you are running linux ... you need to set a line in the /etc/hosts file for static/reserved ip address that is associated with your hostname.

You get that name by typing hostname

Also you need to run Java 8 ... There are reported problems on Java 9.


Offline CheckedOut

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +1/-0
Re: Vera Concierge Setup Issue
« Reply #4 on: December 27, 2017, 01:31:24 pm »
The Local Vera Concierge Server, your Google Home Devices, and your Vera need to be on the same Local area network (i.e. the first 3 numbers of your IP need to be the same. Something like  192.168.10.xxx  and the xxx is different for each device.

There are tricks to do this with a VM ...   

BTW, All my devices are on the same subnet so if i can get this server on that subnet i will be good to go it sounds like.

Offline CheckedOut

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +1/-0
Re: Vera Concierge Setup Issue
« Reply #5 on: December 27, 2017, 01:32:21 pm »
If you are running linux ... you need to set a line in the /etc/hosts file for static/reserved ip address that is associated with your hostname.

You get that name by typing hostname

Also you need to run Java 8 ... There are reported problems on Java 9.

Ok. I will give that a try. Thank you.

Offline CheckedOut

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +1/-0
Re: Vera Concierge Setup Issue
« Reply #6 on: December 27, 2017, 01:34:33 pm »
It looks like the hostname was assigned to 127.0.1.1 in the hosts file by Ubuntu setup or perhaps systemd so that likely was the problem. I am normally a redhat/centos guy so sorry for the churn on this! :)

Offline CheckedOut

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +1/-0
Re: Vera Concierge Setup Issue
« Reply #7 on: December 27, 2017, 02:27:27 pm »
Next issue: I have the server ip fixed. It now shows as a routable lan IP. I also installed and and reconfigured the concierge service to use java 1.8. The concierge server can now see the google home device on the admin page. However I am unable to see the Vera device that I configured.

My vera is a vera plus and is running the latest firmware. Its staticaly assigned on the lan (no wifi) and doesnt have high security enabled.

Logs are showing an SSL error:

Dec 27, 2017 11:25:18 AM V:CSWebContainer:Cmd:/Log
Dec 27, 2017 11:25:22 AM V:CSWebContainer:Cmd:/Log
Dec 27, 2017 11:25:26 AM V:CSWebContainer:Config Cmd:/Query
Dec 27, 2017 11:25:27 AM V:CSWebContainer:Cmd:/Log
Dec 27, 2017 11:25:35 AM V:CSWebContainer:Cmd:/Log
Dec 27, 2017 11:25:40 AM V:CSWebContainer:Cmd:/Log
Dec 27, 2017 11:25:45 AM V:CSWebContainer:Cmd:/Log
Dec 27, 2017 11:25:50 AM V:CSWebContainer:Cmd:/Log
Dec 27, 2017 11:25:51 AM V:VeraService:Wacthdog:Restart
Dec 27, 2017 11:25:51 AM I:VeraService:Start
Dec 27, 2017 11:25:51 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha11.mios.com/autha/auth/username/[SECRET]?SHA1Password=[SECRET]&PK_Oem=1
Dec 27, 2017 11:25:51 AM E:VeraConnect.VeraGateway:URLConnection
Exception:javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
   at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
   at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959)
   at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1916)
   at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1899)
   at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1420)
   at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
   at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
   at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
   at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
   at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:347)
   at com.rtsservices.veraconnect.access.VeraGateway.URLConnection(VeraGateway.java:114)
   at com.rtsservices.veraconnect.access.VeraGateway.URLRequest(VeraGateway.java:70)
   at com.rtsservices.veraconnect.access.UI6Gateway.GetAuthToken(UI6Gateway.java:99)
   at com.rtsservices.veraconnect.access.UI6Gateway.GetVeraIDs(UI6Gateway.java:53)
   at com.rtsservices.conciergeserver.VeraService.Start(VeraService.java:73)
   at com.rtsservices.conciergeserver.VeraService$1.run(VeraService.java:60)
   at java.util.TimerThread.mainLoop(Timer.java:555)
   at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
   at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:91)
   at sun.security.validator.Validator.getInstance(Validator.java:179)
   at sun.security.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:312)
   at sun.security.ssl.X509TrustManagerImpl.checkTrustedInit(X509TrustManagerImpl.java:171)
   at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:184)
   at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
   at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1496)
   at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
   at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
   at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
   at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072)
   at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
   at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
   ... 15 more
Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
   at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
   at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
   at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
   at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:89)
   ... 27 more

Dec 27, 2017 11:25:51 AM I:VeraConnect.VeraGateway:URLConnection:https://vera-us-oem-autha12.mios.com/autha/auth/username/[SECRET]?SHA1Password=[SECRET]&PK_Oem=1
Dec 27, 2017 11:25:51 AM E:VeraConnect.VeraGateway:URLConnection
Exception:javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
   at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
   at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1959)
   at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1916)
   at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1899)
   at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1420)
   at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
   at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
   at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564)
   at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492)
   at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480)
   at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:347)
   at com.rtsservices.veraconnect.access.VeraGateway.URLConnection(VeraGateway.java:114)
   at com.rtsservices.veraconnect.access.VeraGateway.URLRequest(VeraGateway.java:70)
   at com.rtsservices.veraconnect.access.UI6Gateway.GetAuthToken(UI6Gateway.java:99)
   at com.rtsservices.veraconnect.access.UI6Gateway.GetVeraIDs(UI6Gateway.java:53)
   at com.rtsservices.conciergeserver.VeraService.Start(VeraService.java:73)
   at com.rtsservices.conciergeserver.VeraService$1.run(VeraService.java:60)
   at java.util.TimerThread.mainLoop(Timer.java:555)
   at java.util.TimerThread.run(Timer.java:505)
Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
   at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:91)
   at sun.security.validator.Validator.getInstance(Validator.java:179)
   at sun.security.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:312)
   at sun.security.ssl.X509TrustManagerImpl.checkTrustedInit(X509TrustManagerImpl.java:171)
   at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:184)
   at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
   at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1496)
   at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
   at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1026)
   at sun.security.ssl.Handshaker.process_record(Handshaker.java:961)
   at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072)
   at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
   at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
   ... 15 more
Caused by: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
   at java.security.cert.PKIXParameters.setTrustAnchors(PKIXParameters.java:200)
   at java.security.cert.PKIXParameters.<init>(PKIXParameters.java:120)
   at java.security.cert.PKIXBuilderParameters.<init>(PKIXBuilderParameters.java:104)
   at sun.security.validator.PKIXValidator.<init>(PKIXValidator.java:89)
   ... 27 more

Dec 27, 2017 11:25:51 AM I:VeraConnect.VeraGateway:URLRequest: No Response!
Dec 27, 2017 11:25:55 AM V:CSWebContainer:Cmd:/Log
Dec 27, 2017 11:25:56 AM V:CSWebContainer:Config Cmd:/Query
Dec 27, 2017 11:26:00 AM V:CSWebContainer:Cmd:/Log

Any suggestions?

Offline RichardTSchaefer

  • Moderator
  • Master Member
  • *****
  • Posts: 10091
  • Karma: +764/-142
Re: Vera Concierge Setup Issue
« Reply #8 on: December 27, 2017, 02:46:25 pm »
It looks like you are running with a version of Java with limited encryption for export.
There are usually add on's for bringing up to civilized world standards.

Offline CheckedOut

  • Sr. Newbie
  • *
  • Posts: 32
  • Karma: +1/-0
Re: Vera Concierge Setup Issue
« Reply #9 on: December 28, 2017, 12:38:43 pm »
It looks like you are running with a version of Java with limited encryption for export.
There are usually add on's for bringing up to civilized world standards.

Indeed it was. I removed all java packages as well as the certificates package and reinstalled only java 8 and it resolved the issue. Thanks!

Offline Srki

  • Newbie
  • *
  • Posts: 13
  • Karma: +1/-0
Re: Vera Concierge Setup Issue
« Reply #10 on: April 15, 2018, 07:58:55 am »
Hi!
Is there any step-by-step instructions on how to install vera concierge on Linux (Ubuntu)? I cannot get it to run at all. I miss the basic instruction for beginning with a fresh install of Ubuntu. Installing Java but which version of java, configuring the ubuntu for runnin .jar files etc. I want to run vera concierge on ubuntu because I have my server running on that same machine. 
I was able to get the vera concierge up and running on windows machine and I could control my vera with GH. Very simple installation and configuration but with Linux it's another story. Is there anyone that can help out here with some instruction? 
Thank you in advance.

Offline Srki

  • Newbie
  • *
  • Posts: 13
  • Karma: +1/-0
Re: Vera Concierge Setup Issue
« Reply #11 on: April 16, 2018, 04:16:56 am »
Hi!
Is there any step-by-step instructions on how to install vera concierge on Linux (Ubuntu)? I cannot get it to run at all. I miss the basic instruction for beginning with a fresh install of Ubuntu. Installing Java but which version of java, configuring the ubuntu for runnin .jar files etc. I want to run vera concierge on ubuntu because I have my server running on that same machine.
I was able to get the vera concierge up and running on windows machine and I could control my vera with GH. Very simple installation and configuration but with Linux it's another story. Is there anyone that can help out here with some instruction?
Thank you in advance.

I have fixed it. I needed to run the .jar file with sudo command, so in the folder where the file VeraConcierge.jar was placed I needed to run with command: sudo java -jar VeraConcierge.jar
I also needed to fix the  /etc/hosts file with the machine's ip adress.

cd /etc/
Sudo nano hosts


There, I needed to change the reference to my machine which is called HOME-SERVER.

192.168.1.110  HOME-SERVER