Prevent OTA from updating pre-release firmware

Golioth Device Help
1

Description

I have a cohort that I’m using for development to test out new firmware builds. The cohort currently has an active deployment of v1.1.1 firmware package and a single Thingy:91 X device.

I’m working on an in-development v2.0.0 firmware that I’d like to test out on the device in my cohort. When I program the v2.0.0 firmware via JTAG onto the device, the Golioth OTA service automatically reprograms the device with the “Active” v1.1.1 firmware as soon as the device connects to Golioth. This makes it hard to test out a new firmware build before officially publishing it in the console.

Is there a way to temporarily disable OTA firmware updates for individual devices or cohorts?

(This may also be an overall workflow issue on my end, so let me know if there is a recommended workflow for testing new builds like this.)

Environment

SDK v0.19.1

1 Like
2

@cdwilson as long as you are no longer using releases, just moving the device in question out of the cohort, or if you do still have releases moving it to a “quarantine” cohort with no deployments, should result in it not receiving a manifest with the old version when connecting to Golioth. Does that work for your scenario?

1 Like
3

This works. I was using the original cohort to test out OTA to new releases, but I also wanted to use the same device for testing out pre-release builds (programmed via JTAG). I’m realizing those two things are kind of at odds with each other, so it makes sense to have separate cohorts for each (although slightly inconvenient to have to move the device back and forth each time).

1 Like