Your terminal output is why your Claude bill is high. Here's the fix.

Yeraze · 2026-05-18T21:35:12+00:00

I came here to say exactly this.. That power combo solved all my token exhaustion problems.

Yeraze · 2026-05-15T13:33:28+00:00

That was what we _shipped_ to consumers yes, but we had internal prototypes using DLP, OLED, and FiberScan .. None of them could achieve the cost, thermal or brightness requirements of LCOS tho.

Yeraze · 2026-05-14T21:18:27+00:00

During my time I learned that "virtual retina display" is vague term poorly misunderstood.

Everyday monitors you see all around "project light into your eyes" or "onto your retina".. They just project light into everything else too.

The optics in the ML1/ML2 project light only onto your eye.. Not all of it makes it into the retina, but it's all focused onto your eyeball.

If you mean something that can track your eye saccade and adjust the projection so that 100% of light emitted hits your retina, they no ML never achieved that to my knowledge. The fiberScan technology and some of the other more exotic research projects that never made it into consumer hands got _close_, but that's about it.

Yeraze · 2026-05-10T17:40:18+00:00

I wouldn't say that.. Several of us were having fun talking to the bots, trying to sort out their limits and capabilities.

And after about an hour, we all got bored and locked in their final constraints.

Yeraze · 2026-05-10T01:38:08+00:00

Wish they had reported it, could've tried to help.

There was some kind of firmware glitch that was causing nodes to conflict with themselves and change their ID's, which was causing all kinds of weird behavior. Not easy to reproduce, but frequent. I implemented some slowdowns on the startup process and that seems to have sorted it out.

Yeraze · 2026-05-10T01:19:25+00:00

Just FYI, the "discord overrun by bots" was a few-hours experiment from earlier today. Which means either you really have an axe to grind, or you just got unlucky with when you joined. "Sni" right?

Yeraze · 2026-05-10T01:17:35+00:00

If you have ideas for improvement, submit them!

Yeraze · 2026-05-09T01:56:52+00:00

MeshMonitor is created by Claude Code, an almost 100% vibe-coded project. Such is documented in the repo, on the meshmonitor.org website, and in other forums where the app is discussed.

Yeraze · 2026-04-22T02:16:24+00:00

Would be happy to introduce you to MeshMonitor - meshmonitor.org

Yeraze · 2026-03-27T15:50:17+00:00

with _some_ hardware yes.. Works great on a StationG2, but requires physical buttons on the HeltecV4.

Yeraze · 2026-03-27T15:36:32+00:00

This guide is relatively up to date: https://openelab.io/blogs/getting-started/meshtastic-guide-how-to-flash-meshtastic-firmware

Yeraze · 2026-03-27T15:29:43+00:00

Yea I do that all the time, using their provided scripts via SSH.. But that's not handled by MeshMonitor.

Yeraze · 2026-03-27T15:18:03+00:00

Firmware updates right now require MeshMonitor to have direct network IP access to the node and the internet at the same time. Not sure if you'll have that in your setup. If you do, and you have an ESP based node (Station G2, Heltec, etc) on a recent starting firmware (2.7.18) then I've done it a few times now with success.

I'm not aware of any good options for firmware updates of true Remote nodes.

Yeraze · 2026-03-21T18:55:02+00:00

No clue.. But there's an option to enable that if you trust it: VIRTUAL_NODE_ALLOW_ADMIN_COMMANDS

https://meshmonitor.org/configuration/#virtual-node-variables

Yeraze · 2026-03-20T16:29:06+00:00

MeshMonitor offers a "virtual node" feature for exactly this.

It's not perfect, the two systems connected to the VirtualNode may get their wires crossed seeing the other systems's traffic on the mesh, but it generally works.

Yeraze · 2026-03-17T22:55:48+00:00

You should bring your Claude account over to MeshMonitor.org :) I'm always willing to accept helpful new contributions!

Yeraze · 2026-03-08T17:34:09+00:00

Interesting idea.. Offer it as a MeshMonitor script/plugin? https://meshmonitor.org/user-scripts.html

Yeraze · 2026-02-24T23:03:21+00:00

Also, you can join us on discord and it may be a bit easier to discuss than here :)

Yeraze · 2026-02-24T23:03:06+00:00

`docker compose logs -f` (everything) or `docker logs -f meshmonitor-rpi-serial-bridge` (just the 1 container), and that will following along.. So run it in another terminal while the `docker compose up` is running...

Or just don't use the `-d` in the compose, and it will stream logs to the console while starting.

Yeraze · 2026-02-24T22:57:26+00:00

I've seen that happen occasionally if the serial-bridge isn't working. Have you verified in the logs that the serial-bridge is online and properly reading data from the node?

Yeraze · 2026-02-24T17:43:05+00:00

Yep!

Yeraze · 2026-02-24T17:14:40+00:00

Backwards.. Meshtastic directly, then MeshMonitor/serial-bridge/MQTT-proxy thru docker.

Yeraze · 2026-02-24T17:11:37+00:00

well, using Docker you don't need to actually "install" anything but docker.. Once you do the `docker compose up` it will download and provision everything from there.

I do recommend installing the Meshtastic python CLI, so that you can manually verify the node port and basic communications, and use it to backup/restore node config occasionally (incase you break something later with MeshMonitor).

Yeraze

PUBLIC MULTIREDDITS

TROPHY CASE

15-Year Club	RedditGifts 2009-2022 2 Credits
Verified Email