ER8411 V1_1.1.0 Build 20230705 Official Firmware (Released on July 11th, 2023)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

ER8411 V1_1.1.0 Build 20230705 Official Firmware (Released on July 11th, 2023)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
15 Reply
Re:ER8411 V1_1.1.0 Official Firmware (Released on July 11th, 2023)
2023-07-18 14:07:15

  @Clive_A 

 

Appreciate the acknoldgement and support. Look forward to hearing from engineering. 

0
0
#12
Re:ER8411 V1_1.1.0 Official Firmware (Released on July 11th, 2023)
2023-07-19 03:57:13

  @Clive_A 

 

Hi Clive quick question how would one get access to Omada Pro Cloud-Based Controller. It says to contact support. I imagine version is higher than current cloud controller.

0
0
#13
Re:ER8411 V1_1.1.0 Official Firmware (Released on July 11th, 2023)
2023-07-19 05:49:17

Hi @IamMurphy 

Sorry that I don't have any information about this product. Currently, it is not open to most customers.

If you want to learn more about this, please find our sales team in your country.

0
0
#14
Re:ER8411 V1_1.1.0 Official Firmware (Released on July 11th, 2023)
2023-08-29 19:36:30 - last edited 2023-08-29 19:37:31

  @Clive_A 

After my frimware upate my password does not work. is there a way to get logged in with out having to reset the whole router ?

 

Also, The WEB UI does not work on Firefox  116.0.3 (32-bit) getting this message

 

Unsupported browser!

Please update or use a different browser.

2
2
#18
Re:ER8411 V1_1.1.0 Official Firmware (Released on July 11th, 2023)
2023-08-30 00:53:54

Hi @Lozanosteve 

Thanks for posting in our business forum.

Clear the browser cache would be the solution or try it in Private/Incognito mode as a temp fix.

Reason behind this is that our dev team has modified some lines that affect browsers. We recommend Chrome/Firefox, not Safari. 

 

If you see the wrong password after the update and you are pretty sure you have it right, it's also a cache problem. Clear the cache would fix it as well.

0
0
#19