I do open source stuff myself so I’m upset kind of easily by projects that claim to be open source when I cannot find the actual source code anywhere. There should be the schematics, PCB files if any, CAD files, BOM ideally and the of course arduino or micropython code. I explicitly searched for open source air quality monitor. Things looked good and I was about to buy. Then I realize the source code is not actually anywhere to be found. It should be right here, under documetation or support. Even the firmware page only appears to have binaries.
The links to the source code are on various places on our website, eg here at the bottom: AirGradient ONE (I-9PSL) and Open Air (O-1PST) Firmware Versions
Or in the overview page with all schematics etc.
https://www.airgradient.com/documentation/overview/
Also just googling “airgradient firmware” should lead you to the GitHub.
Ok, that’s not just hard to find, that’s buried. Also it’s not at all clear that the ONE is the same as the I-9PSL. I don’t see that anywhere else. If they are the same, the name should be exactly the same. One device, one firmware, unless there are multiple versions that have reasons to exist, like different feature sets.
I’m not just saying this from my armchair. You go to my website, openerv.ca, and there is a section right there that says source code, and it’s right there.
Ok, I know you can’t be fussed about selling to one person, but I’m sure I’m not the only one who is going to notice this. I wont’ be buying until the source code is published properly, probably. To be able to honestly say this is open source you need to :
A)Make it clear exactly which code is part of which design
B)make the code much easier to find
C)recognize that for a physical device, the code is not just the firmware. The schematics and so on also need to be published. An abbreviated BOM. I need to be able to maintain, repair and modify. I don’t need to be able to make a new one from scratch, but the PCB files would be useful for some repairs/mods so they should be included. Let’s face it, pirate cloning is not a major concern here. You might as well spruce up and publish the stuff. I know it takes some work to publish things and keep the published stuff up to date, but you have to do that. I have to go update my stuff too, for sure, and people rarely seem to use it so I understand the hesitancy, but this is about laying a foundation for something better instead of staying where we are.
I do agree that a more cohesive single page with all related links would be an improvement, but all of the data is available.
This page has all of the KiCad, STL, and instructions