For the mom who gives us everything - Mother's Day gifts that connects us.
J

New Member

 • 

5 Messages

Tuesday, August 17th, 2021 11:49 PM

My Enabled Devices Error

My enabled devices application on ch. 9301 is not working. I keep getting the following “my enabled devices error, STB did not peovide a client certificate. Please try again later. 006

Community Support

 • 

231.9K Messages

3 years ago

We'll gladly help you clear the error and connect your U-Verse receiver and app, @jib22.

 

First, reboot your gateway following these steps:

  • Unplug the power cord from the back of your gateway and wait 20 seconds.
  • Plug the power cord back in.
  • Wait up to 10 minutes for the gateway to restart and the Broadband light to turn solid green.

Afterward, make sure you’re connected to your home Wi-Fi and signed into the app with the correct home account credentials.

 

Then you should be able to enable communication between U-verse TV and the app.

 

Be sure to follow the steps in the online guide to make sure you don't miss anything.

 

If you need further assistance, let us know.

 

Aminah, AT&T Community Specialist

New Member

 • 

5 Messages

3 years ago

Sadly this did not work. After the reboot of my AT&T RG, I then went into the U-verse app to setup my receivers, BUT my network’s wifi isn’t recognized. Ugh…

Community Support

 • 

231.9K Messages

3 years ago

We are here to help get your equipment back up and running, @jib22.

 

We recommend that you reboot your equipment, because this will refresh everything. You can reboot the main receiver, which is the DVR receiver because this will reboot all of them. This will help with the receiver not being able to recognize the network.

 

Let us know if this helps.

 

Marc, AT&T Community Specialist

New Member

 • 

3 Messages

3 years ago

Struggling with the same problem as well. They’ve tried four new receivers to fix this error for me and still no joy. I really appreciate AT&Ts efforts but there has to be someone within the entire company who knows how to fix this error. Reboots, resets, replacement receivers clearly are not working.

(edited)

New Member

 • 

5 Messages

3 years ago

In all honesty, I finally just had to throw my hands up in the air and give up. I find it very frustrating but, like you, after a new DVR, router and more resets, uninstalls/reinstalls than I care to remember, I had to let it go. 
I couldn’t agree with you more, one would think some upper level tech has heard of this issue. I have searched the net and noticed other AT&T Uverse customers have had this problem too but I have yet to find a resolution.

Was wondering if by any chance you have an Amazon TV Fire-stick or use a wifi extender? Our TV is a Samsung. No clue as to why any of those devices would make a difference but I’m desperate to find a “common denominator” as to why this issue persists. Thanks for taking the time to respond to my post. Sincerely appreciate it. Please do let me know if you ever discover a solution. Friendly Regards.

(edited)

ACE - Professor

 • 

5.5K Messages

3 years ago

Well, not all of us have issues with this certificate problem.  I did test myself and it works as it always has, which is to say poorly.  What I mean by that is the default behavior is to allow all devices to control the settop boxes, which is fine in and of itself, but the app just can’t see the boxes reliably and in fact fails more than it works.  

New Member

 • 

3 Messages

3 years ago

@jib22 I do have a Fire Tv and wi-fi extender, great thoughts! Although wired receivers should be communicating directly with the gateway and wi-fi receivers should be talking directly to the access point provided by AT&T.  

@gr8sho That is not the default behavior on a new receiver out of the box in my experience, otherwise the app would work to control the receiver out of the box.

ACE - Professor

 • 

5.5K Messages

3 years ago

@Aaronneunz 

The default behavior is to allow access.  Why the app can’t see the settop boxes has to do with a bug in their system.  

New Member

 • 

5 Messages

3 years ago

A bug in AT&T’s system?! That would be a first. ;-)

New Member

 • 

3 Messages

3 years ago

@gr8sho I checked 9301 and you are correct, my error.

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.