I have 2 soil sensors that I'm trying to put this firmware onto. One is working great but now that I've flashed the second one, I can't get past the part where I move it from USB-C to AA battery.
When I put the AA battery into the device, it's getting extremely hot within minutes. It's happened with 2 different batteries and I just burned/zapped my fingertip pretty badly on the spring area of the negative terminal of the battery compartment.
I thought there was a mention of something like this in the docs, but upon further inspection it seems the failures outlined there are all related to water damage or (relatively) fast battery drain, where mine seems like it's draining so fast that it would ignite if left alone. It's brand new besides the reflash, and has never touched soil or water.
I'm a little nervous to take it up with seeedstudio since I have the custom firmware on it, but it seems like a clear HW issue. Does this sound like any of the faults you dealt with?
This is the first time I've submitted an issue on GitHub - sorry for any failures to follow conventions. Please lmk if there's a better way to submit things that are more of a question than action item. Thanks for all the improvements you made here.
I have 2 soil sensors that I'm trying to put this firmware onto. One is working great but now that I've flashed the second one, I can't get past the part where I move it from USB-C to AA battery.
When I put the AA battery into the device, it's getting extremely hot within minutes. It's happened with 2 different batteries and I just burned/zapped my fingertip pretty badly on the spring area of the negative terminal of the battery compartment.
I thought there was a mention of something like this in the docs, but upon further inspection it seems the failures outlined there are all related to water damage or (relatively) fast battery drain, where mine seems like it's draining so fast that it would ignite if left alone. It's brand new besides the reflash, and has never touched soil or water.
I'm a little nervous to take it up with seeedstudio since I have the custom firmware on it, but it seems like a clear HW issue. Does this sound like any of the faults you dealt with?
This is the first time I've submitted an issue on GitHub - sorry for any failures to follow conventions. Please lmk if there's a better way to submit things that are more of a question than action item. Thanks for all the improvements you made here.