Hi @GoodOmens

GoodOmens wrote

  @Clive_A Updated

 

Seems there is an issue with selecting the ER7212PC in the auto upgrade section in global settings

 

It created an auto update entry for the model (first screenshot) but when I go to edit it, I can't (get an error (last screen shot)) as the router is not a item I can select (second screen shot)

 

 

 

 

 

Not sure what you are doing and why. Downgrade it and I don't think the pre-release would display that.

You are using a pre-release and it may not be displayed in the cloud because the upgrade requires the controller and cloud authentication.

Hi @GoodOmens 

Thanks for posting in our business forum.

GoodOmens wrote

  @Clive_A The ER7212PC entry was put in by your update script when I went from 1.2->1.3. I didn't do anything. So either the bug is in your update or on this page to allow the ER7212PC to be selected for automatic upgrades.

Downgrade the firmware and verify if it was there in the official release.

This is pre-release and has not been synced to the cloud.

And you mean that we proactively add an entry? You did not add any entries regarding the router before?

Hi @GoodOmens 

Thanks for posting in our business forum.

GoodOmens wrote

  @Clive_A Ok I rolled back /restored from backup and I see it in 1.2.0 as an option shown but similar to 1.3 when I click in I can no longer select it as a device to auto-upgrade. No idea how it got included as I am done rolling back versions.

 

Will this come to the cloud or should I delete the ER7212PC entry? It seems your upgrade script should clear out bogus entries.

 

The update option in 1.2.0 showing ER7212PC:

 

 

 

 

 

The device list shown in 1.2.0 when I click edit, no ER7212PC shown

 

 

 

Something I never seen before. I need to confirm with the team.

Hi @GoodOmens 

Thanks for posting in our business forum.

GoodOmens wrote

  @Clive_A Yea I just reupdated and its back

 

Before:

 

After:

 

We reviewed your case based on the description. From the code, we did not find anything regarding this.

And we tested locally but we failed to reproduce the issue.

Please contact us by email and provide a backup of your config.

Since the beginning of 2025, we no longer create the email ticket for the user. To assist and figure it out efficiently, we recommend submitting a support ticket via email.
Please include:
1. Your Forum ID and link;
2. Your community nickname;
3. A detailed description of the issue and result if I have suggested anything on the thread, and the troubleshooting steps you've taken in the subject line or body of your email.

Email template