-
Notifications
You must be signed in to change notification settings - Fork 46
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
Version: 2.1.1_0159 is temporarily not supported (!) #31
Comments
It may require additional work from https://github.com/pvvx/ATC_MiThermometer/ project as the current installation heavily relies on the work done by pvvx. You may track pvvx/ATC_MiThermometer#378 for updates. |
To go back to the old version (Original_OTA_Xiaomi_LYWSD03MMC_v1.0.0_0130.bin );
|
Please, track atc1441/ATC_MiThermometer#298 for updates |
Is it possible to use the Xiaomi BLE integration on this new firmware? I guess not is a BindKey cannot be set. |
This firmare is to use the sensor with Zigbee network. For bluetooth support you'd better ask in BLE atc1441/pvvx repos |
I tried this with a FT232 TTL-USB but keep getting the message "Select file is no telink firmware .bin" and the "Write to Flash" button is always greyed out. I do not get the error message with other bins e.g. Z03MMC_v0122 but my H&T does not work even after it succesfully flashes. I originally had 2.1.1_0159 FW but now the thing seems to be bricked. This and anotehr site that pointed ot this, suggested I could upload the old FW but I am struggling to do this. I have GND on the FT232 to the Battery Terminal -ve (Centre of PCB), VCC to Vbat+ (Battery Edge Spring) and TX to Pin14. I also tried conecting the DTR to the Battery Terminal =ve (Battery Edge Spring as suggested by pvvx. Any ideas would be welcomed thank you! [EDIT] OK, I found that if I went to the original repoistory and downloaded the file from there using the downlaod button, I got a smaller file that I could flash, which I tried and it said "Done" at the end a OK next to the write flash box. I tried with 115k baud and 406k baud and 3s activation and 8s activation and shorting the GND RESET during activation, but the the thing remains dead. Any other ideas please? I always used 3.3v. |
Got 5 devices with 2.1.1_0159 firmware, that are incompatible with OOb OTA update. Did what was shown on this issue.
Was using the USB COM flash page with Chrome and firmware 1.0.0_0130. All 5 devices converted to older firmware, and then concerted to custom one. Perfect! |
Well done to you! You gave me hope, but alas, I must have tried 100 times, I cannot revive my device :-(. Despite this site saying (generically) that you cannot brick these chips, I seem to have done just that ... OR my connections are just not taking.
Quick Q; the 4th Wire, DTR to RESET, you mean to the RESET PIN not the the GND Pin (also used to reset), right? |
@jksmurf You'd better use a different UART dongle on a different chip. |
https://barjak.eu/pictures/ft232rl-m.jpg
It worked for me.
jksmurf ***@***.***> ezt írta (időpont: 2024. okt. 9., Sze,
5:49):
… Got 5 devices with 2.1.1_0159 firmware, that are incompatible with OOb OTA
update.
Wll done to you! You have me hope, but alas, I must have tried 100 times,
I cannot revive my device.
Despite this site
<https://smarthomescene.com/guides/convert-qingping-cgdk2-from-bluetooth-to-zigbee/>
saying (generically) that you cannot brick these chips, I seem to have done
that OR my connections are just not taking.
You cannot brick Telink TLSR82xx chips
No matter what you flash, you can always use UART to restore
Quick Q; DTR to reset, you mean the RESET PIN not the the GND Pin (also
used to reset)?
TSLR82xx.Cannot.Brick.jpg (view on web)
<https://github.com/user-attachments/assets/8cdcaa30-7915-4209-92d1-2d036bb911f9>
Trials.jpg (view on web)
<https://github.com/user-attachments/assets/85096722-9ca8-4fd7-a2f9-4b25d3790024>
ThisSetup.jpg (view on web)
<https://github.com/user-attachments/assets/7d22e57f-bd37-4762-b2d8-8fe6426715fd>
Pinouts2.jpg (view on web)
<https://github.com/user-attachments/assets/f90e146d-76fc-4e1d-9fdd-10a4ea384813>
—
Reply to this email directly, view it on GitHub
<#31 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE3B7YM3HRA3R4PTWZI4ESLZ2SRU5AVCNFSM6AAAAABPRH7TIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBRGIYTENJWGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Barják László +36209347499
|
Hmm... @Ibarjak I am now even more confused. Your pic (thank you) shows wiring for a FT232RL chip with what appears to be the1k resistor wiring from https://github.com/pvvx/TlsrComSwireWriter which says "Does not work on USB-COM adapters that have FTDI chip" devbis (above) says use a DIFFERENT USB-COM Adapter, i.e. non -FTI (presumably) which matches what pvxx shows. |
https://www.hestore.hu/prod_10036483.html
Cheap copy, probably not original chip
jksmurf ***@***.***> ezt írta (időpont: 2024. okt. 9., Sze,
12:03):
… https://barjak.eu/pictures/ft232rl-m.jpg It worked for me.
Hmm...
@Ibarjak I am now even more confused.
Your pic (thank you) shows wiring for a FT232RL chip with what appears to
be the1k resistor wiring from https://github.com/pvvx/TlsrComSwireWriter
which says "*Does not work on USB-COM adapters that have FTDI chip*"
devbis (above) says use a DIFFERENT USB-COM Adapter, i.e. non -FTI
(presumably) which matches what pvxx shows.
—
Reply to this email directly, view it on GitHub
<#31 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE3B7YKZ2TRHNCJPM7GVMALZ2T5O3AVCNFSM6AAAAABPRH7TIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBRHA4DKMBUGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Barják László +36209347499
|
Just wanted to report I went and bought some 1kohm (up to 1.8kohm) resistors and (what was marked in the shop), what I thought was a CH340G USB-TTL device with the intention to wire it up like on here and run the Python script ... (that site says no LEDs, no FTDI chip…j. ... but then I thought, just for kicks, why not try the simple 4 wire setup first on this Chip (different pin layout to my red FTI FT232RL), but without the resistor and using the Web-based TX-SWS Flasher. i.e. wiring FROM the Device TO the Board:
And of course, it worked FIRST time, with this model (I bought an old one, with no LEDs that I could see), without resistors or Python scripts. So if you're not having much luck with a board like my red FTI FT232RL then maybe just try a different board with a RTS pin, they are cheap, US$5; or solder a wire to the RTS connector hole. [EDIT] It seems what I thought was a CH340G actually has a FTDI chip, so it might be FT232 (but one without LEDs); maybe what made it work was the RTS-RST connection, which my red UART board did not have (unless you soldered a wire on to the RTS hole). |
Hi there, this gives me hope! You say buy a CH340G but in the image it has printed FT232. Do you have a link to the exact device you used, please? I want to rule out as many variables as possible. I have a pack of 5 mijia thermometers I want to flash for home assistant (already have 5 attached no problem but they were bought 2 years ago!). Thanks. |
I just bought it in a shop, not online. Yes it says FT232 BUT it’s not (supposed to be) an FTI Chip, at least how it was marked in the shop. Looking at a few websites now though, it does actually seem to have the FTDI chipset!. I attach a pic of the back side; with that and the front side you might search FT232 and click images in Google and see what matches? |
Thanks, I'll google around. How do you keep the probes from the chip to the thermometer board steady? I'll be using dupont wires but 2 of the locations on the mijia board look quite hard to either solder (prefer not to solder) or to keep stead while it's flashed 😂 |
Small light sprung crocodile clips on V+ and V-; A very small hole in the housing you can poke a pin through to P14; an extra set of hands for the RST and computer :-) yup very very fiddly … but after many goes it becomes easier … I didn’t use the GND pin, just V- (bottom spring if battery), you can clip onto that. Good luck ! It might be it works with any USB-TTL, that the change was the RTS to RST, it might be that what makes it work, I really don’t know. My FTI board (Red) didn’t have a RTS pin and I couldn’t be bothered trying to solder a wire on to the RTS connector hole you can actually see on that board … |
I’d probably have made the hole quite a bit smaller as it holds the pin better but you’re on the right track. Thanks - pay it forward 👌 |
I've got 5 to do so hopefully the next 4 will have a smaller drill hole if I can find a tiny drill! |
btw if you use these little spring loaded things, they always fall off the V+ and V- as the wires are too soft to grip properly; but I had better luck extending the wires (pressing the spring loaded end) and bending them inwards with a pair of tweezers so they hooked on better. YMMV. Note that the picture below is for demonstrating the clips only not the UART device which is the red FTI Chip based one that didn’t work with pin outs described in one of the much earlier posts above. |
Just a comment on this statement as I wasn’t sure your reasons for wanting to get the USB-TTL device, but presumably you have bought devices with updated FW OR you updated the FW by mistake OR you had a failed update on one or more of those five devices, which is why you’re pursuing the UART route? Asking as just flashing using the Telink Web based flasher should be the first thing you try provided the FW is OK and you don’t have to downgrade it (via UART). See a couple of notes I wrote in the home-assistant forum. Note 1 re downgrading if in BLE Note 2 re downgrading if stuck in Zigbee mode when Telink no longer works. |
Hi, sorry, I might actually have put you wrong with the CH340G note; I’ve amended my notes above to state that it says FT232 on the chip, BUT it was not supposed to be an FTI Chip, at least how it was marked in the shop. Looking at a few websites now though, it does actually seem to have the FTDI chipset! So maybe it does work with any USB-TTL, that the change that made it work was the RTS to RST, I really don’t know. My FTI board (Red) didn’t have a RTS pin and I couldn’t be bothered trying to solder a wire on to the RTS connector hole (that you can actually see on that red board, about three holes down from the GRD pin). |
Oops, I've already ordered some CH340g boards. Yes I have already tried to flash them OTA (I have done this before successfully with older mijia thermometers) but the firmware is incomptible and so needs to be rolled back via UART. |
Darn, my apologies for that you were more eagle eyed than me in your first post. I was just so ecstatic to revive it. If you’re ordering boards plural, can you maybe change the order so you order one CH340G and one FT232 based one (with an RTS pin) instead? |
It's no big deal, these things are so cheap! I've also ordered an FTDI FT232RL (it doesn't have an RTS pin, but there is a hole for RTS on the edge of the board I can connect to, if it can work that way!?) |
Sounds good, I’m sure one of them will work for you. My apologies again, I had so many goes with the red one using the DTR connection pin (as advised elsewhere) I almost gave up, but persistence and sheer bl##dy mindedness made me try a different board with the RTS pin. Best of luck to you 👍 [EDIT] I think this is my one on Amazon and on AliExpress too. |
I'm also getting a blank screen after trying the above method from @jksmurf, flashing direct to v4.8. Attempting to flash v1.0.0 yields the same result. I expect this is a result of a bad firmware write. I'm definitely using 3V3 on my FT232R board. I'm attempting this through the https://pvvx.github.io/ATC_MiThermometer/USBCOMFlashTx.html tool, on macOS 15 and Chrome 130.0.6723.117 |
Above I noted I used this flasher: https://pvvx.github.io/ATC_MiThermometer/TelinkMiFlasher.html can you please give that a try instead? k. |
This is the Bluetooth OTA flasher, isn't it? I get the (!) Version: 2.1.1_0159 is temporarily not supported (!) error using that one. |
lol 😂 my apologies yes, sorry, of course, you’re trying to downgrade using USB UART, doh, my mistake. Not sure, I just persisted with the Telink flasher using the various connections I posted above. |
@lits101, Hi, bugs me that it doesn’t work for you, just reading your post again, presumably you downloaded the v1.0.0_0130.bin correctly, clicking the link to download it and and not right clicking, download? And that you have RTS to RST (Reset) and all the other probes on the correct pins? My only other suggestion is that you order a different USB UART unit, buy one exactly like mine, the one that worked (I think there’s some AliExpress or Amazon links above) and try that, they are quite cheap. According to the note I referenced above I think I was devbis that said you cannot brick these Telink units so if you’re persistent, you might be successful. Best of luck! |
Hello,
is there a plan to support this firmware version? If so, do you have an approximate date?
Thanks!
The text was updated successfully, but these errors were encountered: