As said in title, try to get Alexa to change channels on Hopper. It conforms it's doing it...but not. Joeys are still responding fine. Even changed out Dots to no avail. Anybody else?
Google is better"She who shall not be named" tends to do that and it's getting worse. Since they opened up the Eastern Hemisphere to "She who shall not be named" who became the #1 Christmas gift, early January when they were all up and running, the servers crashed. Since, things have never been the same and are getting really dumb and dumber by the minute.
Now instead of being amazed at what "She who shall not be named" could do, I'm amazed that anything happens at all anymore. I have had severely long conversations with her Developers, they can't explain anything. I'm getting the impression that the stupidity is genetic.
Sent from my SM-T290 using Tapatalk
It was a lot worse when the Google Voice search feature was first added. It would suggest YouTube links on both Wally and Hopper Duo receivers. (Need I remind everyone that neither the Wally nor Hopper Duo actually support the YouTube app. So, those links were absolutely worthless!) At least they got that issue fixed. So, if you want Google Voice search to work properly, without a bunch of YouTube suggestions, there is a way to do that. You just have to do the search on a Hopper Duo or Wally, instead of your fancy Hopper 3.Too bad the Google AI on D¡SH can only seem to be able to access programing on YouTube. Even though I specifically ask for "on D¡SH" I still get YouTube suggestions.
As said in title, try to get Alexa to change channels on Hopper. It conforms it's doing it...but not. Joeys are still responding fine. Even changed out Dots to no avail. Anybody else?
The one practical use I could see is if you don't know the exact channel number, but you do know the name of the channel, since Alexa can change channels on the Dish receiver based on either the name or the channel number. Using Alexa may be faster than scrolling through the guide looking for the specific channel you want. Unfortunately, for what are probably the two most common instances of this situation (where the SiriusXM channels and RSN's are each grouped on collapsible channels in the guide) I never could get Alexa to properly recognize these channels, by either method (name or five-digit channel number). Telling Alexa to go to a specific OTA subchannel also fails, for the same reason (five-digit channel numbers).I have Lexi all over the house but don't even try to use her for Hopper. It's already made things more than easy. How hard is it to grab the remote and change a channel? Just don't see much use for Lexi/Dish...
No.Did you recently change to a different Hopper? When I had to replace my Hopper3 receivers Alexa stopped working. I found out that Alexa was tied to the old Hopper3 receiver.
Yes, sir. I have unplugged, rebooted, reset and changed wifi networks on my dots, deleted kasa skill and reinstalled, deleted Alexa app and reinstalled on my phone. I've exhausted every thing I can think of. I even switched to a backup router just in case to no avail. I'm actually thinking of adding the Dish skill back to see if I will have issues like the OPThis may be an obvious question, but have any of you who are having problems with Alexa tried unplugging your Echo Dot (or whatever Alexa device you are using) for about a minute, and then plugging it back in? Earlier this week, I was having audio dropout issues with anything I tried to play on my Echo Dot. I unplugged it and plugged it back in, and that fixed the sound problems for me. I still have issues with the Live X Live skill, where it will either suddenly stop playing for no apparent reason, or the skill will stop working entirely, making me have to Disable and then Enable the skill again to get it to work again. These issues seem to be specific to just that one skill, though.
Having said that, I gave up on having my Echo Dot control any of my Dish receivers a long time ago. At first, it worked great. It was paired with one specific Wally, and I could control that Wally without having to specify a room name or even say "...on Dish" most of the time. Then, something got screwed up, and I would have to specify a room name, or it would suddenly switch to controlling the wrong receiver for no apparent reason. It finally got to the point where it would not work for controlling any of my Dish receivers anymore, no matter what version of the command I tried. I think part of the issue in my case was that I had too many receivers on my account, some of which had the same room name as each other. ("Living Room 1" for both the Wally and the Hopper Duo in the Living Room, for instance.) I have since sold all of my old Wally and Hopper Duo receivers. When I get the money and time to finally purchase and install a Hopper 3, I may try to pair Alexa to that receiver, and see if it will start working, with none of my other old receivers on the account to confuse it.