I bought the esphome version. It is unusable for monitoring jk-bms’ as it doesn’t collect all the data and it fails to report most of the time.
I wanted to default the device to the non esphome firmware to try using msqqt instead. After flashing the latest 3.0.3 firmware, all I get on boot is this:
rst:0x10 (RTCWDT_RTC_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57
I can get into recovery still, but the device is uesless now. Does someone have the original FULL firmware? Or a process to recover this? The firmware flashing guide is either incomplete or incorrect. I have tx,rx,grnd connected and am doing the simple flash method.
Hi
Please try flashing the firmware again following this tutorial.
Tutorial: Flash Guide - GL.iNet IoT Docs
BL/Partition/OTA File: S10-V3.selection.zip (860.2 KB)
Firmware Download Link: GL.iNet download center
I’ve tried flashing all the files, all I get is . . . etc. Both when plugging in USB while holding reset, and when having all pins connected without USB plugged in.
I’ve tried flashing the latest from the firmware download link, That will flash if I plug in the usb while pressing the reset button.
I can run the esptool –port 3 chip_id and get results as well as the downloaded bin file working, so I don’t know what’s wrong?
Ok, I got the original software on it and it’s setup and can be configured now. I can get it to connect to my mqtt server. However I don’t understand or see in the api reference, how to use gatt. I want it to query a JK BMS and return the data from it.
The device does appear to be alive again though!
The stock firmware provides limited functionality.
If your scenario requires features beyond what’s currently available, you may need to develop a custom program and compile a custom firmware image to flash onto the device.
Please refer to the following guide for firmware compilation instructions:
2 Likes