ATC_MiThermometer
ATC_MiThermometer copied to clipboard
pvvx
Doesn't stay connected
Hi,
I OTA-flashed the thermometer but used the act1441 web flasher. It works but cannot stay connected to the phone. Paired it with nRF Connect or act1441's web flasher or pvvx web flasher, it disconnects in 6-10 seconds. Cannot reflash it too 'cause if it disconnects while flashing (and for sure it does) it'll become bricked... Maybe some advices what to do?
- Disable - reload html and flash with original version.
It's really hard to be able to send a setting within 6 seconds but I did it. Nothing changed, it still disconnects.
Sorry for the very large screenshot, don't know how to limit the size. As I expected, the step 3 isn't possible: the device disconnects while flashing and gives, of course, the GATT error. Any idea, why this hapapens?
It's not possible to send any settings, I tried with a smily. In the log it says that "Settings xxx was send successful" but nothing happens. So, the latency cannot be changed either. And, it doesn't stay connected more than 10-11 seconds max. No matter what app or utility has paired the device.
Phone restarted? Is there any other Bluetooth app running in the background or on another device that connects to the sensors? Just started flashing during the connection?
I tried with several phones, but 1 minute ago, I succeeded with my laptop! So, it stayed connected and I reflashed the original FW! Good!
Thank you, Viktor for that amazing FW and Aaron, of course, at the first place!
I had exact the same problem. It wasn't possible to save config. For all with the same problem: Just pull out and reinsert the battery. After that it was possible to save config and update connection latency as shown on pictures above. Now everything works as expected without disconnectiong after few seconds.
I reopened the issue because I found the problem, but a question has arisen. I have 3 sensors and sometimes each of them has the same connectivity problem - after exactly 10 seconds it disconnects while paired, no FW update is possible. I researched the issue with nRF Connect a lot, but the gatt connection timeout error 8 (133) is very common on Android smartphones. Suddenly, one of the thermometers stayed connected and I could reflash the act1441 FW. So, after that, the thermometer begun to be able to stay connected! What??? After hours of thinking and trying, I found that all the batteries were (a little) bad! I had changed a lot of batteries, some of them were bought directly from a store (Duracell) and many had been stored for a year or more. I went through 20+ batteries. One that I measured 3.102V dropped to 2.601V while connected and trying to flash. The best one that helped me to reflash all of the sensors, showed in the device 2.852V but dropped only to 2.822V while connected and for some milliseconds to 2.695V while flashing. This was the only battery that kept each of the devices paired without disconnecting.
Now, there comes a wonder (and this is my question). After reflashing the sensors from the pvvx FW to the atc1441 FW, all 3 devices could stay connected with poorer batteries (but not with very poor ones). These were the batteries that for sure haven't let a device to stay connected. I read that pvvx' FW drained a lot less of power than that of atc1441, have I misunderstood something?
Well, I'm happy that with good batteries all devices work good with both of FW! So, for those who are battling with a disconnecting issue after flashing a custom FW, try to replace the battery with a good one at first! Every battery that is below the 50% can work for displaying and advertising the data, but couldn't work in connected mode or flashing! And a new battery that shows 3 - 3.2 volts out of the circuit, could drop to a critical (or below!) value when put into the circuit (sold half-dead, and lots of them are).
Average consumption is the sum of the consumption per pulse and during the pause between beacons.
RF TX consumption depends on the power supplied to the antenna.
This is a short impulse and does not greatly affect the overall consumption.
But xiaomi saved one cent on tens of thousands of devices and didn't put a capacitor into the PCB.
It also affects the measurement accuracy of the sensor. Apparently, the savings on elements from xiaomi are above all.
Expired CR2032s differ in internal resistance and cannot provide the declared current. After impulse loading, many old elements come back to life...
For tests I use a lot of CR2032s that have been stored for over 10 years. :) All ok.
CR2032 do not like storage at elevated temperatures. Also, in Russia they sometimes die completely when transported in high negative temperatures...
I had changed a lot of batteries, some of them were bought directly from a store (Duracell) and many had been stored for a year or more.
The chip runs at 1.8V. LCD is very dim.
Connect and any operations - ok.
Hello @pvvx ! Thanks for you great improvement to @atc1441 work. Esp. love the improved flasher UI.
Unfortunately I share the same issue like @almostlunatic, but in a different environment. Here are my key points
- I have similar connection stability issues on two PCs:
- One with a Cambridge Silicon Bluetooth Dongle
- and one on a Lenovo Laptop
- Batter replacement or restart did not help.
- Connection always gets lost after 5-20s (latest).
- I had hard time to flash ATC Firmware back.: I tried to play with RF TX Power and Advertising Interval and finally was able to flash ATC firmware back again.
Might my issue arise from some over-conversative default settings regarding the energy management in your version?
Hello @pvvx , thank you for this custom firmware! Great work ! I love every customization, esp. the clock.
I had once the same disconnection issue as @almostlunatic described. After flashing with my laptop, everything worked as expected. Tried every setting on your flasher page, including the pincode. Then I decided to disable pincode. After one undisconnected session, suddenly this issue came. Tried with changing the battery, restart the device, turned off and on the bluetooth, nothing worked. Connection only stayed for around 2 - 5s. I convinced myself there should be something that interrupted the connection as it worked normally before. So I turned off all bluetooth around, leaving only my laptop to connect to. I checked the BL settings and there I found the culprit. Everytime I turned on the BL, the laptop was connected to my device, not only paired. So I removed it. Tried several connecting sessions, the issue never happened again. Everything works normally like before. So I think nothin's wrong with your firmware. Only my settings.
The CGG1 "Qingping Temp & RH Monitor" has tantalum capacitors in the power circuit and works when disconnected for a few seconds without a battery. https://pvvx.github.io/CGG1 There are no capacitors installed in Xiaomi LYWSD03MMC - Xiaomi's greed...
Conducted an experiment with LYWSD03MMC and a dead CR2032 battery, which immediately dropped the voltage at low load (<1mA) below 2 V.
When included in LYWSD03MMC, the custom firmware for it says:
1969 mV and falls into a deep sleep for twenty minutes, then again checks what is wrong with the battery ... The second time it shows 1880 mV, etc.
I switched on the electrolyte to the battery - it has been working amazingly for several days...
@xjustbmw
TI released an application note concerning voltage drop of CR2032 w/ or w/o capacitors in 2017 and the object of study is also a BLE chip. This research used a 22uF or 32uF capacitor as a power supply capacitor in the case where the max impulse current is 6.1mA.
Consider that the max impulse current of LYWSD03MMC is < 8mA in most cases according to @pvvx 's research, a 32 or 47uF capacitor should be enough for extending battery life and reducing voltage drop. Up to hundreds of uF is also OK and usually without any disadvantages (except prices). In my case, I decided to add a 100uF capacitor. As for case codes, C24 should be 1206 and C25 should be 0603 (both in inch)[^1]. They are in parallel, which means that you just need to add a capacitor to one of them. However, since dozens or hundreds of uF is a huge capacitance, 1206 would be cheaper.
MLCC does not have polarity and you should choose it in most cases. However, if you decided to use a tantalum capacitor, or any other type of capacitor that has a polarity, DO NOT REVERSE THEM! Next to the "C24" or "C25" sign is the positive pole.
[^1]: Consider buying a bit smaller one to make soldering easier. The solder pads are too short!
I have noticed that disconnecting problem occurs when there is a low battery. After replacing battery to the new one everything working as expected.
Now, there comes a wonder (and this is my question). After reflashing the sensors from the pvvx FW to the atc1441 FW, all 3 devices could stay connected with poorer batteries (but not with very poor ones). These were the batteries that for sure haven't let a device to stay connected. I read that pvvx' FW drained a lot less of power than that of atc1441, have I misunderstood something?
The initial “connection interval” selects an external adapter. Consumption is highly dependent on the "connection interval". Immediately upon connection, the external system reads all BLE services from the device. In ATC, the firmware - fewer services. Next, the thermometer sends a request to a new interval, and consumption is reduced, if the external adapter confirmed new interval ...