Alexa on Matrix Voice - chown problem

Hello,

By following the indications within


I encounter the following errors at the end of Step 4:

chown: changing ownership of ‘/home/pi/Desktop/alexa-avs-sample-
app/samples/wakeWordAgent/ext/lib/libblas.so.3’: Operation not permitted
chown: cannot access ‘/home/pi/.asoundrc’: No such file or directory

Thanks in advance for your suggestions.

Hi,

the /home/pi/.asoundrc is an optional file, ignore it and keep on going. also ignore the wakeword test failure issue, if it still happens. see pull request

OK, thanks, but what about the first error?

chown: changing ownership of ‘/home/pi/Desktop/alexa-avs-sample-
app/samples/wakeWordAgent/ext/lib/libblas.so.3’: Operation not permitted

When going on, when in Terminal Window 2, I got an error (exception in thread):

[INFO] Building Alexa Voice Service Sample Java Client 20160207.7

[INFO] ------------------------------------------------------------------------

[INFO]

[INFO] — exec-maven-plugin:1.2.1:exec (default-cli) @ sample-java-client —

Exception in thread “Thread-24” java.lang.NoClassDefFoundError: sun/security/ssl/SupportedEllipticCurvesExtension

at sun.security.ssl.ClientHandshaker.getKickstartMessage(ClientHandshaker.java:1438)

at sun.security.ssl.Handshaker.kickstart(Handshaker.java:1087)

at sun.security.ssl.SSLSocketImpl.kickstartHandshake(SSLSocketImpl.java:1497)

at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1361)

at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)

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.amazon.alexa.avs.auth.companionservice.CompanionServiceClient.callService(CompanionServiceClient.java:224)

at com.amazon.alexa.avs.auth.companionservice.CompanionServiceClient.getRegistrationCode(CompanionServiceClient.java:157)

at com.amazon.alexa.avs.auth.companionservice.CompanionServiceAuthManager.requestRegistrationCode(CompanionServiceAuthManager.java:74)

at com.amazon.alexa.avs.auth.companionservice.CompanionServiceAuthManager.startNewProvisioningRequest(CompanionServiceAuthManager.java:66)

at com.amazon.alexa.avs.auth.companionservice.CompanionServiceAuthManager.startRemoteProvisioning(CompanionServiceAuthManager.java:61)

at com.amazon.alexa.avs.auth.AuthSetup.lambda$startProvisioningThread$1(AuthSetup.java:90)

at java.lang.Thread.run(Thread.java:748)

I got rid of that last problem by following the indication from https://github.com/alexa/alexa-avs-sample-app/issues/90.

But now, when I have to authenticate the device (from Terminal Window 2), I get this error:

This site can’t provide a secure connection
localhost doesn’t adhere to security standards.
ERR_SSL_SERVER_CERT_BAD_FORMAT

1 Like

I solved that by restarting the web browser on the Pi.
My Alexa is alive now :slight_smile:

1 Like

Alive :slight_smile:
With sensory or kitt_ai?

With sensory. Works OK so far.