# Wismesh 1W Node (3400) compatibility with 4630 config (and meshchat x UI issues) _Help · started by [P] on Thu, Aug 20, 2026 4:05 PM_ Tags: Question, LoRa, RNode, Help --- ## Original post **[P]** · Thu, Aug 20, 2026 4:05 PM Hello yall! I (and @oatmilk!) are working on getting one of my wismesh 1w kits running rnode. ive been trying to find anything pre-existing that isn't vibecoded and nonfunctional but im not having much luck. i was reading through this documentation [https://github.com/liberatedsystems/RNode_Firmware_CE/blob/master/Documentation/CONTRIBUTING.md] along with the datasheets for the 4630 [https://docs.rakwireless.com/product-categories/wisblock/rak4631/datasheet/] and the 3400 [https://docs.rakwireless.com/product-categories/wisblock/rak3401/datasheet/] and realized that the footprint, pinout, chipset, transceiver, etc. is all the same. the only big difference is that the SX1262 is built into the 4630 and in the 1w board it is in a module with a SKY66122 FEM booster and RF filter. There isn't even a software config in the documentation for the 1w booster (rak13302), just some example code. [https://docs.rakwireless.com/product-categories/wisblock/rak13302/quickstart/#set-up-rak13302-as-the-receiver-with-the-rak3401]. Some of the earlier attempts included running microRNS [https://github.com/attermann/microReticulum_Firmware] with one of my 4630s as this build includes a 3400 config and i am less worried about bricking the cheaper one. It switched between not exiting DFU mode, changing its port during flashing, and failed to start. This was attempted over python over powershell, a windows install of meshchatx, and the same python script but on linux. We could not do it on meshchat on linux due to UI issues when trying to use serial support [see image 1]. ![image.png](/storage/forum/T9iJcSEvw9PdKP7sWytRHczZ3ZvEZLx02PNnyryi.png) I also tried using this [https://github.com/thatSFguy/reticulum-lora-repeater/tree/master] which i later realized is not made for client use and is vibecoded. The 4630 did work using the standard firmware [https://github.com/liberatedsystems/RNode_Firmware_CE] while the heltec esp32 lora v3 cooked itself alive dropping packets everywhere. however that still leaves me trying to figure out the following; Can I either run the 4630 config on the 3400 as-is, has anyone made a config that actually works, or do i need to figure out writing a new config? and if so, how would one do that? --- ## Reply 1 **oatmilk!** · Fri, Aug 21, 2026 6:32 PM i too am here --- ## Reply 2 **Nickie** · Sat, Aug 29, 2026 10:20 PM Since this device is already properly supported on MeshCore/Meshtastic, I've taken the liberty of rigging up an **untested** build of my RNode_Firmware fork for it. You can check it out if you're interested. https://flasher.rns.moscow/?d=rak3401-1w&v=863-928-classic --- ## Reply 3 **Cleeyv** · Sun, Aug 30, 2026 2:56 AM **Nickie** wrote: > https://flasher.rns.moscow/?d=rak3401-1w&v=863-928-classic I tried flashing from this link and got the following error: ``` $ Downloading rnode_firmware_rak3401.zip... ✗ HTTP 404 fetching /firmware/classic/latest/rnode_firmware_rak3401.zip ``` --- ## Reply 4 **Cleeyv** · Sun, Aug 30, 2026 3:12 AM I figured out the issue. The rnode_firmware_rak3401 files are in https://flasher.rns.moscow/firmware/classic/1.86.1024/ but not in https://flasher.rns.moscow/firmware/classic/latest/ which is where the flasher tries to find them. --- ## Reply 5 **Cleeyv** · Sun, Aug 30, 2026 4:15 AM I did a devtools local override of the javascript file for the flasher and replaced `latest` with `1.86.1024` and that allowed the flash to proceed successfully. However, after the reboot following the flash the flasher is no longer able to connect to the device and after timing out on attempts, it returns the following error: ``` ✗ Device not responding as RNode — press RST to reboot, then use "Detect RNode" to reconnect. ``` This is not just a problem with the flasher, the serial device for the board is no longer showing up in /dev at all. There are no changes to /dev when the board is reset or unplugged and plugged back in. However, the serial device does reappear when the reset button is double-pressed and the board enters DFU mode. --- ## Reply 6 **Nickie** · Sun, Aug 30, 2026 12:44 PM Fixed the symlinks, but as I don't have the hardware, there is only so much I can do... If you're interested in tackling this, drop me a message on LXMF! Alternatively, you can try entering the nRF-bootloader mode and dropping an .uf2 there. ---