Skip to content

Firmware version confusion #284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AlexanderLeporiday opened this issue Feb 6, 2025 · 3 comments
Open

Firmware version confusion #284

AlexanderLeporiday opened this issue Feb 6, 2025 · 3 comments

Comments

@AlexanderLeporiday
Copy link

Releases show 3.1.13, website shows 3.1.13.
Dashboard shows 3.1.21 and just updated brand new (previously locally connected) I-9PSL.

I had it connected to home assistant and showed it shipped with 3.1.11, manually updated to 3.1.13 from the website.
Connected it to home assistant and shows 3.1.21 was ready.
Connected to cloud, restarted, automatically updated to 3.1.21.
Reset to local mode and home assistant says it's working as expected.

So why have none of the versions since 3.1.13 been marked as releases?

@samuelbles07
Copy link
Collaborator

samuelbles07 commented Feb 7, 2025

There's a problem on our versioning now that needs to be more managed properly. We try to improve it little by little until release pipeline better in the future.

@MallocArray
Copy link
Contributor

To make matters worse, now on the Dashboard, it appears that 3.1.21 was pulled, as the most recent shown in 3.1.13

Image

But the Releases here in Github now shows 3.2.0

@AlexanderLeporiday
Copy link
Author

3.2.0 was pushed to release 3 days ago but so far hasn't shown up anywhere.
The API (which I can't find right now) where you put in your device serial number and it returns the latest version seems so still return 3.1.21.
Image

Website still shows Version 3.1.13 Release which was the latest version pushed to GitHub prior to 3.2.0.
https://www.airgradient.com/documentation/firmwares/

Release pipelines seems to be fairly fundamental and you probably shouldn't be maintaining and supporting multiple pathways to release firmware anyway. Make a CI/CD pipeline and then hook in a release system, however you want to do it but pick a lane and stick to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants