I just got an T114 nrf52840 (muzi.works H2T) and I am having lots of issues getting it to connect to my phones (Samsung S9, Nexus 6P) through bluetooth. I’ve tried factory resetting, flashing new firmware (2.4.2.5b45303 Beta , and 2.4.3.91d6612 Alpha (Hotfix)), reinstalling the app, unpairing, and restarting both devices.
It even has issues pairing with fixed/no pin, but will occasionally get past and load all of the modules and have no issues until the next reconnect. Unfortunately it usually doesn’t get that far and just loops trying to load the modules.
When I received my (screenless) T114 I immediately erased it then installed the latest 2.5 firmware. I couldn’t use the standard 123456 password, so had to use the Serial console on my windows computer to see the Randomly generated password. It has worked fine ever since.
I wrote to Heltec when I couldn’t get things to work and they have just written back (english/kanji) - saying to use 123456 (!)
Using the flasher webpage: https://flasher.meshtastic.org/#
Select the bin icon and download the “nrf_erase2.uf2” file.
Drag and drop to the Drive that represents your T114 - E:\ perhaps?
I’ve left out steps. I’m at work.
I had huge problems with it last night. At first I couldn’t get it to pair and once it had paired it repeatedly connected then disconnected. Eventually it seemed to sort itself out.
I’m using the latest version of the iOS app and the latest beta.
Mine arrives today. It has a screen. Bluetooth (BLE) connected fine but it loses the BLE connection frequently with my Sony Xperia 5 V Android 14 phone: even when the node and phone are right next to each other. I think there is an antenna issue and by random chance the connection fails for a second. To connect to phone again I have to go to the settings and select “none” in node list and then select it again BUT sometimes pressing the cloud (when it is struck through indicating no BLE connection) make the connection come back. Will add comments later if the issue gets major.
I purchased the device with a 1200 mAh battery before the case became available, then I purchased the case/battery combo from muzi.works. The unit worked just fine with the 1200 mAh hour battery, but as soon as the 2200 mAh was plugged in, the bluetooth disconnections began. Switched back to the smaller 1200 mAh battery, and all is working just fine.
2nd day. Bluetooth worse. Loses connection over and over even when phone and node right next to each other. Madening.
Perhaps this is the solution?
This device design might not have been tested before being sold?
Update: with usb c power plugged in and at 96% the blueooth is stable but the andoid app updated in the interim so no sure why it suddenly works nicely for now…
I purchased my kit from muzi.works before the case was available. I had the unit in a makeshift case made from the container it was shipped in, and it worked flawlessly. I ordered the case and upgraded battery from muzi.works when it was made available, and it shipped completely separately. I really think this is a case design issue, rather than a T114 hardware issue. For the time being, it’s been running just fine with a smaller battery and the gps unit in the empty space above the battery rather than in the slot above the bluetooth antenna. For what it’s worth, I did wrap my gps and parts of my board in kapton tape in the troubleshooting process, in an effort to not short anything out.
The meshtastic Android app just updated itself… and my T114 when on USB charger at 96 % appears to have a stable bluetooth connection again … very odd. Will report here when tested for longer…
Does it behave OK if you leave it plugged into usb C power ? (Mine seems to be ok in that state… though my meshtastic android app just updated so might be another cause of its bluetooth connection being stable suddenly.)
I contacted Muzi.works about this and they have found a potential bug. They are looking to have a fix sometime next week.
Just wanted to give you a quick follow up on this - we have found that there is a potential bug with the Heltec T114 board inside our H2T device that is causing the bluetooth connection issues that you’re experiencing. We are currently performing extensive tests and working to resolve this issue, and it looks like we will have a resolution early next week.
Kind regards,
