Hello,
I am new to Meshtastic and really enjoy using it. I recently purchased a Heltec wireless Stick V3 with 0.49 Oled screen. I successfully flashed the heltec v3 firmware. However display output is not scaled to fit into screen. I can’t fully see the BT pairing code on screen. I just used the ST to get the code to pair it with the app. Does any one run into this issue and know how to fix it?
Look like I’m in the same case like you, received mine yesterday still wondering how to use it with Meshtastic. I installed successfully Heltec v3 firmware but wondering if I should install Wireless Stick Lite v3 instead.
Testing changing parameter via https://client.meshtastic.org but nothing are persistent which make me think I have the wrong firmware.
Keep exploring…
Share if you have success.
Either firmware would work. You can’t get the bluetooth code from the screen. So you can connect via the serial terminal to get BT code so you can pair the device with your meshtastic app. It is Bluetooth low energy so you wont see your device under bluetooth. You will use meshtastic to pair it. You need at least another device to try your meshtastic or if you know someone who also use meshtastic. Once you pair your device with meshtastic it will be showed under phone connect bluetooth list. Good luck!
I see Meshtastic_bf39 device under Available devices on my Android phone and when I click it ask pairing code and actually show it on the screen but like you said “display output is not scaled to fit into screen”, so I have one or two digit cut off.
you need to use serial terminal to get the code. make sure you install serial driver for your device. which is CP2102 usb to uart bridge controller. after you install the driver you can use hxxp://serialterminal.com select your serial port then you try to pair your device with your android phone.
2 Likes
Nice!
I will try that. For now I just set a default BT pin using CLI.
- Install : Meshtastic Python CLI installation | Meshtastic
- Set pin:
meshtastic --set bluetooth.mode FIXED_PIN
meshtastic --set bluetooth.fixed_pin 100100
2 Likes
And about the web interface, I realize there is an issue on web client itself.
Do you know why I got this error:
For Serial: On connect
iMeshDevice:SerialConnection] connect ❌ Failed to execute 'open' on 'SerialPort': Failed to open serial port.
For Bluetooth: after activating #enable-experimental-web-platform-features. On save
iMeshDevice:HttpConnection] readFromRadio ❌ GATT Error Unknown.
I’m guessing the development may not be ready.
Edit:
This issue happen only on Linux, it works well once I try it on Windows.
I dont know why you get those error messages. Can you start all over again? Use web flasher to flash your device with Heltec Wireless Stick V3 and pair the device with default 123456 code( thats what get everytime I pair with my Iphone. I have multiple nodes and they all communicating each other without problem. I even setup 1 node as router-client mode to connect to meshtastic mqtt broker to see all the nodes around the world. Good luck!
has anyone found an answer to this problem yet
…it would be really helpful to understand how this scaling problem happens and how to fix it in the code…thank you.
1 Like
The Heltec Wireless Stick V3 is not officially supported by Meshtastic. I think (but I’m not sure) that part of that reason is due to the dinky assed screen issues. Meshtastic does support the Heltec Wireless Stick Lite V3 and that may be the one you want to get.
I would however like to hear if you get it working properly, despite the jank assed screen issue. I don’t care about the screen and you can get these ones cheaper in a lot of cases, so it would be interesting to know if they actually work properly, or not.
It turns out that the information provided by Heltek regarding the display is incorrect.
display.println(display.getWidth());```
They claim it's 64x32, not 128x64 as stated on their website [https://heltec.org/project/wireless-stick-v3/](https://heltec.org/project/wireless-stick-v3/)
[https://github.com/meshtastic/firmware/blob/master/src/graphics/Screen.cpp](https://github.com/meshtastic/firmware/blob/master/src/graphics/Screen.cpp)
Looking into the code, we can see that the entire script is optimized for 128x64. Yes, we can make adjustments, but these would always be scaling changes when using the Wireless_Stick_V3.
So, the issue probably lies with Heltek because they don't provide accurate information.
Even in the example code, there's an extra check specifically for pixels, and the manufacturer's specifications on their website are completely wrong.
Therefore, the problem is that the code needs to be adapted because the display is smaller than the manufacturer claims.
I'll modify the firmware for myself and see if it works. Oh, and the pin layout is also different from the V3 and Lite versions. I'm not sure if that needs to be considered for variants [https://github.com/meshtastic/firmware/tree/master/variants/heltec_v3](https://github.com/meshtastic/firmware/tree/master/variants/heltec_v3) .
4 Likes
Add me to the list of those who rolled the dice and bought one of these little guys. I didn’t much worry about that screen, as I intended it to be my static in the attic, wifi connected, store and forward relay machine.
I’ve also got a heltec lora v3, so I’m not all hot and bothered to get the wireless stick working, but of course I’d love to get some use from it.
Has anyone had any luck configuring it using the CLI? I’ve been able to send it settings, but so far none seem to have any effect. Anyone else?
BTW I’m one of those that use Arch on the desktop 
With my heltec V3 the screen works OK using the last stable version which is 2.2.24.e6a2c06 Beta.
I note that with that version the default setting for bluetooth is Random pin and not fixed pin. There is even an option for No pin if you can get it changed via a serial port connection?
Good luck with it as I am having pairing issues with an elderly Tablet, but luckily phone works OK.
Adrian
It may not be ‘officially’ supported, but as long as you are ok with configuring them with the so-called ‘python cli’ (I actually prefer it and use it on both my wireless stick and heltec v3), but done this way, configuring over the usb port is trivial.
I have one up in my attic right now on wireless+repeater duty, eating up it’s batts at roughy twice the rate as the client-mode Heltec V3.
Oh, and when you flash them, flash them with the Heltec V3 image.
Just remember, just because there is a pinche little screen on the thing, doesn’t mean you have to use it.
Honestly, meshtastic should rephrase their lack of support for the device: “Meshtastic does not support use of the screen on this device”.
Good luck and don’t give up on the wireless stick, it works real good 
2 Likes