Raspberry PI - Google Home SDK Security Handshake Error - google-assistant-sdk

Thanks very much for reading my post
Have raspberry pi 3B
Running RASPBIAN JESSIE WITH DESKTOP.
Followed these instructions to get Google Assistance working
https://www.hackster.io/Salmanfarisvp/g ... -pi-9f3677
Then these to get hotword setup
https://stackoverflow.com/questions/436 ... spberry-pi
Upon running command 'googlesamples-assistant-hotword' I often get the below errors, other times google home will work for awhile only to give these errors then fail
E0723 00:23:58.518779664 2744 handshake.c:128] Security handshake failed: {"created":"#1500726238.518626644","description":"Handshake read failed","file":"../../third_party/grpc/src/core/lib/security/transport/handshake.c","file_line":237,"referenced_errors":[{"created":"#1500726238.518608103","description":"FD shutdown","file":"../../third_party/grpc/src/core/lib/iomgr/ev_epoll_linux.c","file_line":1045}]}
[2727:2744:ERROR:speech_recognition_activity.cc(550)] S3 connection has timed out: No data from S3
ON_ASSISTANT_ERROR:
{u'is_fatal': False}
[2727:2744:ERROR:assistant_output_handler.cc(618)] Failed with a general speech recognition error
Segmentation fault
pi#raspberrypi:~ $
Any assistance would be greatly appreciated

Related

Getting telemetry data from dji matrice 210 RTK to Raspberry pi with Rasbian

I'm trying to get the telemetry data from the DJI matrice 210 RTK with a Raspberry pi3 through the OSDK.
I've followed the guide https://jamesthesken.github.io/dji-sdk-setup/
and manage to start serial communication but unable to receive data.
I've double-checked the possible reasons but none of them are the source of the problem.
This is the log I get:
STATUS/1 # init, L65: ...Serial started successfully.
STATUS/1 # sendData, L405: Port did not send
ERRORLOG/1 #sendData, L411:Open Protocol cmd send failed, send_len:0 packet_1en :19
ERRORLOG/1 # getDroneVersion, L1418: Drone version not obtained! Please do not proceed.
I expected to run the telemetry sample and obtain the results.
Thank you in advance for your help
With the Raspberry Pi 3b you need to disable Bluetooth in order to make serial communication possible.
$ sudo nano /boot/config.txt
dtoverlay=pi3-disable-bt
sudo reboot
Agreed with #escardill above. I would suggest also just verifying that the tx pins are connected to rx pins, and vice versa, if you are using a USB to ttl adapter cable (the one DJI sells for $5).

How to resolve this docker error when running wolkenkit start on Windows 10

When I run wolkenkit start on a Windows machine, the command fails and I get the following output:
Starting the application...
Validating the application code...
Verifying health on environment default...
Verifying application status...
Verifying that ports are available...
Setting up network...
Building Docker images...
Starting Docker containers...
✗ Failed to start the application.
docker: Error response from daemon: driver failed programming external connectivity on endpoint boards-postgres (7cf3e33d876e8d22fced3926fdc9ddf2372b499803dc92a4b7bb403fd2552064): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:3030:tcp:172.21.0.4:5432: input/output error.
ExecutableFailed: docker: Error response from daemon: driver failed programming external connectivity on endpoint boards-postgres (7cf3e33d876e8d22fced3926fdc9ddf2372b499803dc92a4b7bb403fd2552064): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:3030:tcp:172.21.0.4:5432: input/output error.
at childProcess.exec (C:\Users\wagle\Dev\tnw\wolkenkit\src\shell\exec.js:21:20)
at ChildProcess.exithandler (child_process.js:301:5)
at ChildProcess.emit (events.js:189:13)
at maybeClose (internal/child_process.js:970:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
I'm running on Windows 10 using Docker Desktop for Windows 2.0.0.3. Any ideas where this problem might originate from?
Actually, we (at the native web, the company behind wolkenkit), ran into this problem as well.
It's actually a problem caused by one of the latest updates for Windows 10. This updated introduced a new feature called "Fast startup" which causes problems for Docker.
See this issue for more details: https://github.com/docker/compose/issues/3277
As a quick fix, you can restart Docker. As a more long term solution, you can disable the "Fast Startup" feature, see https://github.com/docker/for-win/issues/953#issuecomment-342498223
Hope this helps 😊
PS: Please note that I am one of the core developers of wolkenkit.

Travis CI - Unable to remove port forward Error executing adbExec

I am trying to setup automated tests for an android app using Appium (npm version) but I keep getting the error
[UiAutomator2] Did not get confirmation UiAutomator2 deleteSession worked; Error was: UnknownError: An unknown server-side error occurred while processing the command. Original error: Trying to proxy a session command without session id
[UiAutomator2] Unable to remove port forward 'Error executing adbExec. Original error: 'Command '/usr/local/android-sdk/platform-tools/adb -P 5037 -s emulator-5554 forward --remove tcp\:8200' exited with code 1'; Stderr: 'error: listener 'tcp:8200' not found'; Code: '1''
I have looked around google for ages but havnt been able to find any solution that has actually worked for me, so far totalling 50 failed builds.
If i run the commands on my local machine it works fine but within travis I have no such luck unfortunately. I am new to setting up appium so it could be something minor im not understanding.
A gist of my travis.yml file is here
Distribution:
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
Thanks in advance.
tcp:8200 is not forwarded and there should be no forwards.
try with adb forward --remove-all, when not knowing which port it is
... if it's even required to remove any forward.
After looking at the logs, I understand that the emulator is not ready to allow UiAutomator to get deployed properly.
So to make sure that emulator is ready, you can use avdLaunchTimeout and avdReadyTimeout by passing 60000 ms to both in your desired capabilities.
Once the emulator is ready, you won't get this error.

No acces to jenkins on raspberry Pi 2 (503 no service available)

Good evening.
I hope the question does not exist yet. I searched everything and found nothing suitable for me.
I have a problem with my jenkins that I want to run on my Raspberry Pi 2. I have the setup done as described here:
And it looks like he's running. But I do not get access to it via browser.
If I want to connect with http://192.168.2.XXX:8080, I get the message "Error 503 Service not availabele". But the Jenkins is running when I look at jenkins status. What am I doing wrong? :-(
Hope Someone can help

Issue with telefonica/orchestrator

I am dealing with an issue while trying to use telefonica/orchestrator and I hope anyone can help me with it.
My server is CentOS 7.3 and I am trying to build an IoT platform using docker version 1.10.3 and FIWARE. I have successfuly installed all necessary containers (mongodb, orion, mysql, keystone, keypass, pep and orchestrator). Everything works fine except orchestrator. When I am trying to
curl localhost:8084/v1.0/version
the response is:
curl: (56) Recv failure: Connection reset by peer
Any ideas why this is happening?
It seems that you are trying to ask API orchestrator before orchestrator is completed started. Just wait some seconds before do that.
BTW telefonica/orchestrator is not part of FIWARE.

Resources