A common use of the adapter pattern is to support functionality that isn't actually supported in an underlying class. For example, if I use an API to interact with a Samsung Smart TV, I might want to add functionality not available through the API. To do this necessitates the use of a wrapper object that interacts with the API, rather than just interact with the API itself.
This indirect use of the Samsung API suggests to me that we are now in proxy pattern territory. Am I wrong?