wire-pod
wire-pod copied to clipboard
kercre123
escapepod.local works fine, but vector still cannot connect
Like what it said! I was able to get the debian host put together pretty easy, I'm running on a VM in my homelab, everything seems to resolve fine! But.. no matter what I do, i cant seem to get vector to connect or see it.
My bot is running version v2.0.1.6076 0dd1b62e and I'm using the latest commit from the github, Is it ok if i post the logs downloaded from the bot? Let me know I'll attach them to this issue! And thank you!
Hey, that sure looks like a connection in the server journal?...
Oct 02 23:07:34 escapepod start.sh[408]: Token expires: 2023-10-03T23:07:34.860927094-04:00
Oct 02 23:07:34 escapepod start.sh[408]: ESN not found in store or this is an associate primary user request, act as if this is a new robot
Oct 02 23:07:34 escapepod start.sh[408]: Adding 10.85.5.211 to TokenHashStore
Oct 02 23:07:34 escapepod start.sh[408]: UUID for this token request: 0c877cdc-783a-4d3a-b137-178b3a70fd19
10.85.5.211 is the robot dhcp, checked with my router.
So.. whats it doing?
Dosn't seem like it registered properly with the escapepod server, since i cant select it from the dropdown
What do you have in
wire-pod/chipper/jdocs/botSdkInfo.json?
# cat wire-pod/chipper/jdocs/botSdkInfo.json
{"global_guid":"tni1TRsTRTaNSapjo0Y+Sw==","robots":[{"esn":"0dd1b62e","ip_address":"10.85.5.211","guid":"WCbjhAKnnm1gmr5TXr99PA==","activated":true}]}
OK so it's definitely activated, what about
jdocs.json?
Here you go!
# cat wire-pod/chipper/jdocs/jdocs.json
[{"thing":"vic:0dd1b62e","name":"vic.AppTokens","jdoc":{"doc_version":1,"fmt_version":1,"client_metadata":"wirepod-new-token","json_doc":"{\"client_tokens\":[{\"hash\":\"Boi3HrTPfUxS1dMAuXR7R92EN5Idh4NtKx6+PKuJKYwvz7j5kljfnJdD6meNaj6w\",\"client_name\":\"wirepod\",\"app_id\":\"SDK\",\"issued_at\":\"2023-10-04T13:34:58.128468087-04:00\"}]}"}},{"thing":"vic:0dd1b62e","name":"vic.UserEntitlements","jdoc":{"fmt_version":1,"json_doc":"{\n \"KICKSTARTER_EYES\" : false\n}\n"}},{"thing":"vic:0dd1b62e","name":"vic.RobotSettings","jdoc":{"fmt_version":2,"json_doc":"{\n \"button_wakeword\" : 0,\n \"clock_24_hour\" : false,\n \"custom_eye_color\" : {\n \"enabled\" : false,\n \"hue\" : 0,\n \"saturation\" : 0\n },\n \"default_location\" : \"San Francisco, California, United States\",\n \"dist_is_metric\" : false,\n \"eye_color\" : 0,\n \"locale\" : \"en-US\",\n \"master_volume\" : 4,\n \"temp_is_fahrenheit\" : true,\n \"time_zone\" : \"America/Los_Angeles\"\n}\n"}}]
What am i looking at?
This is the 2 config files wire-pod uses to communicate with Vector and stores its current config (eye colour etc, what you're supposed to access via the UI). 0dd1b62e appears in both so it's puzzling, it has everything it needs to communicate.
Can you confirm you're now on the ep firmware? Seems like you were not in the other thread.
Can you check service avahi-daemon statusand ps aux see if avahi-daemon is running and can you check netstat -ltnp and see if you see avahi-daemon running on port 5353 udp
I have a similar problem with the last step "Activate"
https://escapepod.local/ shows 404 page not found http://escapepod.local/ shows the Apache2 Debian Default Page http://escapepod.local:8080 redirects me correctly to the wire-pod interface.
I'm on the latest wire-pod build
