Station G2 - Router Role

Support
1

I picked up a station G2 recently and it is working well, unless I set the role in Router mode. If I do this, the device appears to bootloop, and I cannot use the bluetooth, web, or serial interface. The only way to get the device back is to do an erase and flash. Has anyone else had this issue? Is there any downside to running as “Router Client” instead of “Router”, as Router Client appears to work. Version v2.4.2.5b45303

EDIT: I can’t set it to Router Client… if I do, it just goes back to Client.

EDIT 2: Apparently this is expected based on this: Device Configuration | Meshtastic… however, I am still confused by Router Client…

Thanks!

1 Like
2

Try a WisBlock as your router. It works well see my Idaho backcountry post.

1 Like
3

@tebrown >Have one on order for same application. Following to hear what the community has to say as I will likely face the same issue you are having.

@Ttabs > I’m currently running a Wisblock for my application. While it’s beautiful for remote nodes and solar application such as the one you’ve deployed in Idaho b/c of its low power req, the G2 can transmit at higher much higher levels (both at the top encryption level and even beyond into the Ham levels at max output of ~5 watts). It can also pickup transmissions much deeper into the noise floor beyond the WisBlock’s capability.

4

@iggy So far, it actually works well, but trying to figure out the best way to configure it. Router mode is good, but if I want to use the wifi to connect to the MQTT, that is not going to work. Still experimenting, but I think it was a solid purchase, fwiw.

1 Like
5

WoW, It looks like you have found the problem and submitted it to github, thanks :slight_smile:

1 Like
6

Cool. I should probably get the debugger working so I can figure this out myself… but it’s been a LONG time since I used the Arduino toolkit!

1 Like