I appreciate you sharing your feedback, I would like to clarify a few points.
Regarding the temperature sensor, I’m not sure what you mean by saying it could easily have been isolated from the main electronics. We have already isolated it as much as we reasonably could within the device’s design. This is why the temperature and humidity sensor is positioned in the small protruding section on the underside of the enclosure. If it were located inside the main enclosure, it would likely be affected even more by internal heat.
I understand your frustration with the readings, but I don’t agree that this is simply a case of poor design. I’ve seen firsthand how much thought and effort our team has put into the design and the decisions behind it. We certainly welcome criticism and constructive feedback, but I also believe there are more productive ways to communicate it. If you’ve followed the blog posts by Achim and Ethan on the Go production processes, you’ve must have seen exactly how much effort goes into this.
Regarding the outdoor monitor, we’ve explained several times over the past few months that we originally did not report temperature and humidity readings from this device because we knew they could be affected by internal heat. These readings were primarily intended for PM sensor corrections. We later made them available following customer requests, with the understanding that they would be affected by internal heat, direct sunlight, and other environmental factors. The devices are primarily designed as air quality monitors. We are very transparent about the limitations of temperature and humidity measurements when this is the case.
My own experience testing the Go has generally been quite good with GPS, so I’d be interested to understand the conditions under which you’re seeing deviations of around 200 metres. I also wonder if anyone else in the community has the same issues.
Regarding the display LED, we have actually removed this feature for exactly the reason you mentioned. It wasn’t providing useful illumination of the screen. We’ve communicated this change several times on the forum and have also updated our knowledge base and firmware to reflect it.
The interface lag and difficulties switching modes are also worth investigating. Could you let us know which firmware version you’re running? These are areas where we can make improvements through firmware updates, although I’d like to better understand the specific behaviour you’re experiencing. Maybe you could send a video via our support form.
We know there are areas where the Go needs improvement, and we’re actively working on them but if you’d prefer to return the device, please contact our support team with your order number so we can review the options with you.