I am trying to get my Amazon Echo device connected to my wifi so it will work.
At one point, the Echo device said it could not connect.
I want to find out if there is a connectivity issue. This may help me eliminate some things that are o.k. I can learn in the process.
At one point, the Echo device said it could not connect.
Thanks
Here is what I believe you need:
From what I've seen, you need to configure the Echo's WiFi via a smartphone app before it becomes sufficiently "network visible" for you to then be able to interract with it from a Wifi-capable Linux box.
---- additional info ----
Have you checked the details offered in the appropriate document for your device offered on this page for free ?
Also, have you seen this at Canonical SNAP for Alexa ?
And some other sources:
That last one is not specifically for networking between Echo and Linux, but may give some insights into the interractions. 
As for the security side, you may wish to review these:
I read the document for Generation 3 echos.
The Alexa app on my phone does not detect the Echo.
And I am again back here.
As for Ask Ubuntu, they are less than helpful as far as my post on this topic goes.
This does not apply to anyone on Ubuntu-Mate Community.
But whatever your intentions or the cause of your [bitterness](https://www.verywellmind.com/how-to-forgive-3144957), holding a grudge can end up hurting you as much as the person who inspired it. Clinging to anger can impact you, emotionally, physically, and socially, so it's important to learn to let go of your grudges and cope with anger in a healthier way.
I ask that consideration be given to creating a new Category for any discussion other than politics and religion.
Sorry, @fixit7. I don't know how to interpret
If this
is a sample of the type of posting you would like to see in that new Category, I think you will find the Moderators responding that this Community is not intended for such discussion, nor for discussion of religion.
I may be wrong on this point, but the category of politics is a bit less restrictive in that there may be discussions as relate to politics impacting Information Technology or the degree of acceptance of Open-Source Software and Applications within various national/international government-regulated standards/requirements.
You did not read my post thoroughly. I said that grudges do NOT apply to this site.
I would not post anything negative on any forum intentionally.
I like to stay positive and encourage others.
I live in the U.S.
My mother was born in Hannover, Germany.
She had to deal with WW2.
I have been to Germany twice.
I stay with relatives and volunteered at a German hospital.
I was impressed with the Europeans work ethic.
Take care.
I apologize for the misunderstanding, but I did read your post.
I seemed apparent that you were looking to open up a new discussion group/heading. I responded to that proposed idea. No intention on my part to raise conflict.
Also, for your own protection/security, I would offer my opinion that sharing such personal information, as you did in your latest response, while much appreciated for its demonstrating your willingness and courage at "making the human contact", is highly inadvisable, because it could be used inappropriately by corrupt elements.
Who are "corrupt elements" ?
Threat actors, also known as cyber threat actors or malicious actors.
I followed the instructions on Amazon and even reset the device.
I was thinking about taking it apart for parts.
Look like it might taking some drilling.
Following upon what @ericmarceau linked in the first answer I would also add this link:
It shows you can connect via Bluetooth as well so you might try that before you disassemble it - it may not be better solution than those already linked but might just work as last resort
Hope you manage to make it work!
EDIT: one older post but might be worth to read:
Bearing in mind that Ubuntu has some differences from Ubuntu_Mate.
## 3 Answers
1. Remove the Echo device from your bluetooth devices if you haven't already.
2. Go to the [Alexa web interface](https://alexa.amazon.com/). Go to settings, select the Echo you're trying to connect to, and click Bluetooth.
3. If you're computer is listed on this page, forget the device.
I can problem do step #2.
The poster assumed that a reader would understand #1 and #3.
I need help with #1 and #3.
(I used to be a technical writer. When I wrote S.O.P., manuals, etc. I always needed to keep in mind my audience.)
To demonstrate the new skill I learned from @ericmarceau from another topic I will try and help with the part 1:
On your desktop you should have this menu when you click the Bluetooth icon on the applet bar in the top panel assuming you've got that applets enabled and when you click on devices it will open up the window in which there will be all your previously connected devices - there is also a search button that will search for nearby devices so try and see if it will locate your device (also note that there might be a button on the device to turn Bluetooth pairing on - I don't know myself since I never used this kind of device before so I can't help with that - there might be some information in previous links posted by @ericmarceau earler today so that may be helpful to re-check)
About the third part - reading it in the context I really don't understand what list, maybe I'm just too tired to think but the sentence doesn't seem too logical given the fact that link mentioned above just forwards me to some link that required QR code from an app that I don't have - really am confused right now and sorry because I can't be of much more help 
EDIT: I think number 1 is about the presumption that somehow you managed to connect it once already and it somehow didn't work would be my guess after a second read
EDIT part 2: on this short tutorial video (even though its on Fedora) the process is explained the same for Bluetooth connection:
I do not have a Bluetooth icon.
Two questions:
Does your computer have the physical capability (hardware) to support "Bluetooth" ? (an interface card/emitter ?)
If you search for installed "bluetooth" packages, what does your package manager report to you? (below image is search in Synaptic)
... or at command line
apt -a list bluetooth
You may wish to consider using the following two packages in addition to "bluetooth":
That line says that IF your Echo was already recognized by your computer, and was showing as a recognized network peripheral, then you should remove the logical definition of that device (Echo) from the location where the computer shows that as a recognized device.
Regarding
I agree with you! That is very ambiguous. I believe it means that if, after doing step 2, you see your Echo showing as a device, then either
OR
I don't know enough to tell you which of those two interpretations should apply. 
Maybe check out this.
Regarding that snapshot of yours, I see in your Synaptic that you have "bluez" installed.
If you don't have "bluez-tools" installed, I recommend you do that. It states that it provides indicators, i.e. icons.
Fair disclosure: I don't have bluetooth ...
... but UbuntuMATE auto-installed all of these as part of the previous installation, or my most recent upgrade:
Also, if you open the "blueman" tool (check under internet category), what does it give you?
Looking at what "bluemon" gives as description, it may also have smarts to notify availability of a bluetooth device to the Linux OS's "plug-n-play" logic. But I'm only guessing on that.
apt -a list bluetooth
Listing... Done
bluetooth/noble,noble 5.72-0ubuntu5 all
"blueman" is a GUI package giving a front-end to Bluetooth.
It would not harm to install that, try to see what it could give you, and if not benefit, remove it completely.
Does entering the commands (revised commands)
hcitool dev
hcitool name $(hcitool dev | grep -v '^Devices:' | head -1 | awk '{ print $2 }' )
hcitool info $(hcitool dev | grep -v '^Devices:' | head -1 | awk '{ print $2 }' )
hcitool lp $(hcitool dev | grep -v '^Devices:' | head -1 | awk '{ print $2 }' )
give you anything ?