Can't connect after updating firmware to 3.2

pvvx / ATC_MiThermometer

Custom firmware for the Xiaomi Thermometers and Telink Flasher

https://github.com/pvvx/pvvx.github.io/tree/master/ATC_MiThermometer

Other

2.95k stars 205 forks source link

Can't connect after updating firmware to 3.2 #118

Closed acronce closed 3 years ago

acronce commented 3 years ago

I flashed an LYWSD03MMC to v3.2 and after it succeeded I could not reconnect to the device. It doesn't even show up as a bluetooth device any more in the Windows -> Settings -> Bluetooth.

The device itself seems happy. It's displaying the temp and humidity like before.

I power cycled it by removing the battery and putting it back in. It still displays the temp, but now longer appears as a Bluetooth device.

Any suggestions?

pvvx commented 3 years ago

https://github.com/pvvx/ATC_MiThermometer/issues/100

acronce commented 3 years ago

That seems to be a different problem. In my case after flashing I cannot see the device in the Telink Flasher. It basically disappeared after flashing and will not reconnect.

jddonovan commented 3 years ago

I have zero issues with my Windows computer with a relatively new bluetooth adapter, supporting BT5.0. I also have an atomic pi with BT 4.0 using bluetooth2mqtt and I couldn't get any sense on why it wouldn't connect or read the mi-thermometer whereas e.g. my smart band was detected ok.

Someone in the review section mentioned that they could not get this to work on BT 4.0 adapter, but using a BT 4.2 it worked fine. Could this be the reason? The sensor requiring version 4.2 minimum for successful broadcast after flashing..?

Edit: nevermind! I can read the broadcast with Atomic Pi using standard Linux tools. I suspect some BT driver issue.

MiguelCosta commented 3 years ago

I also have issues after update to firmware 3.2

In my case, after flashing I can't configure the settings. When I try to connect, the device disconnects after a few seconds 😢

acronce commented 3 years ago

I moved to a different computer (a Mac running Chrome) and was able to connect to the thermometer. This allowed me to configure the device with no further issues.