CHOP3-800 error

Brian160
Investigator
Investigator

Various users have been getting the CHOP3-800 error. This seems to have been going on for over 18 months and still it's happening, now to me with a brand new hub. It looks like the hub's web server is the problem. Is EE ever going to fix it? Do EE monitor this forum? Should I cancel my shiny new contract and go somewhere else?

13 REPLIES 13
Brian160
Investigator
Investigator

It's a well known issue. It's happening to me on a brand new Smarthub+. It's infuriating and I want to go back to BT. Is this forum monitored by staff? When is it going to be fixed? Is it a hardware, firmware or software issue? Does anybody know?

 

Mustrum
EE Community Star
EE Community Star

@Brian160    did you not bother to read the last thread you posted on?

You router should get a firmware update overnight which should clear the problem - if it is a problem.

XRaySpeX
EE Community Star
EE Community Star

It's spasmodic but not too often. It usually goes away when you retry. It's just a minor irritation & does not prevent you accessing the router.

The latest f/ware, r3.8.11-R-1414606-PROD-83002, does not get rid of it.

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Home Broadband & Home Phone or Option 2 for Mobile Phone & Mobile Broadband

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP
Brian160
Investigator
Investigator

@Mustrum I read it all and I'm still frustrated. It is a problem and if there's really an update tonight that'll be great. Pity they don't tell us about things like that.

@XRaySpeX Yes, it's a relatively minor nuisance, but it shouldn't happen and EE should have fixed it long ago.

XRaySpeX
EE Community Star
EE Community Star

What update tonight? Is there to be 1?

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Home Broadband & Home Phone or Option 2 for Mobile Phone & Mobile Broadband

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP
JimM11
Brilliant Contributor
Brilliant Contributor

@Brian160 The update will happen when it happens nothing you can do about it, if you just don't like what you have now, then put all the old equipment back on, nothing else for it! If you want to get out the time to do it is before you get committed to it all!

Ali_A
EE Community Support Team

HI @Brian160 

Are you still seeing the CHOP3-800 error? This was resolved on firmware version 1.34 and above.  

Do you know which version shows on your hub? 

Ali 

XRaySpeX
EE Community Star
EE Community Star

Really, @Ali_A ? I'm still getting them occasionally with App version: 2.36.9 Firmware version: r3.8.11-R-1414606-PROD-83002

If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE CS: Dial Freephone +44 800 079 8586 - Option 1 for Home Broadband & Home Phone or Option 2 for Mobile Phone & Mobile Broadband

ISPs: 1999: Freeserve 48K Dial-Up > 2005: Wanadoo 1 Meg BB > 2007: Orange 2 Meg BB > 2008: Orange 8 Meg LLU > 2010: Orange 16 Meg LLU > 2011: Orange 20 Meg WBC > 2014: EE 20 Meg WBC > 2020: EE 40 Meg FTTC > 2022:EE 80 Meg FTTC SoGEA > 2025 EE 150 Meg FTTP
Brian160
Investigator
Investigator

@Ali_A Yes, I'm still getting the CHOP3 blockage. Firmware is r3.8.11-R-1414606-PROD-83002. A power cycle fixes the problem for an hour or two and then it happens again.

My app is 2.36.9.

I also have a problem with IPv6. The router says it's enabled but I can't access any IPv6-only websites.

They have just agreed to send me a new router. I have no idea whether that will fix the problem but it seems worth a try.