Hi support team,
I want to bring a usability issue up with the new version of the goodcloud interface.
Previously a settings template was not tied to a specific Device + Firmware version. Meaning, we could apply a template to any firmware version that might be on a device. These things are now permanently linked. Even if we copy a template to use on a new firmware version, we can't change which firmware that template is valid for.
Here's the problem: If we update a router, or have an updated router that we want to apply a template to we can't. The only way to do it is to create a whole new template that is permanently locked to that version of firmware OR downgrade the router first, then log back in and upgrade.
This is causing a lot of extra work for my deployment team. Is it a bug/oversight or is there a reason we have to lock the templates?
Second issue is: Upgrading (bulk or single) firmware on devices from GoodCloud seems to be broken.
Request: Is there a way that we can integrate "update to latest" or "Update to " and apply a settings template at the same time? This would increase deployment efficiency so we didn't have to wait for a the reboot after the template application THEN do another reboot with firmware update.
Template Firmware Lock:
Currently, templates are locked to specific firmware versions due to differences in configurable items across versions. This prevents compatibility issues when pushing settings. That said, we’ve added this request to our backlog — we plan to support editable firmware bindings and partial compatibility in future updates.
Template + Firmware Upgrade Flow:
Since both config changes and firmware upgrades may trigger reboots, combining them could cause conflicts. We recommend scheduling OTA upgrades after config changes — upgrades preserve settings and will auto-apply at the set time.
Appreciate your input — it's noted and will help shape future improvements.
Firmware lock:
This really creates the possibility of introducing errors and versions of the templates that are not identical. business customers run the risk of simply skipping important security firmware updates because that means we have to start over with all new templates, keeping each firmware version in-sync.
Templates + Firmware Upgrade:
Can we apply a template that creates an OTA schedule? I'm not aware of this, and if we can't that means another reboot cycle that is really just a waste of time for my deployment team. I guess it goes back to the firmware lock issue as well. I can't apply a template to multiple devices if the firmware has been upgraded.
Please help us out here with priority! It's a usability issue which I know isn't as attractive as "new features", but goodcloud is primarily focused at business fleets. We need to be efficient and accurate when dealing with larger fleets of devices.
