Bernd's Weblog

https://mimiclaw.io

"workspace": "/home/sysop/.picoclaw/workspace",
"restrict_to_workspace": true,
"allow_read_outside_workspace": true,

The LLMs in the background use statistical data and that can become a problem: Picoclaw changed the name of its configuration file from config.yaml to config.json some time ago. But in some parts of the LLMs the old config.yaml is still present. So picoclaw tries to optimize itself with old files and also with some invalid switches....

Moving picoclaw shows the advantages of a local installation: Transfer of user.md and memory.md keeps the old interaktions, tokens (therefor also a little bit of a problem as picoclaw thought it was still running on the pi4).

Main topic at the moment: API-keys for the LLM connection,´the Pi zero uses openrouter with stepfun-flash-free right now.

As no LLM is installed locally, there is no "big" advantage of picoclaw in this part, but you can train your agent with own data (e.g. my berlin trip last week) and it will remember it, even if you switch the LLM in the bacground. And picoclaw as agent has access to it workspace and can write memories, skills, scripts and so on.

One learning: Never trust the agent. Yesterday "we"/it worked on a news skill which didn't work and I told the agent to deactivate the cron job for it:

That was the crontab I found after the above message:

Different 868MHz antennas for a meshtastic heltec v3 and of course a different signal quality: 9 db +/-.

And the reason, why I can also hear some German nodes via some hops: Zugspitze Node:

Next try: Solar powered meshtastic nodes. The devices come with a 800 mAh battery, peak current is 80 mA. Device is the Meshtastic GAT562 that uses nRF52840 as the main controller.

The device comes preprogrammed with meshtastic 868 with the current firmware 2.6.11 (beta).

battery is pre-loaded as the device has no external connections. Also firmware updates need to solder an USB-plug to the PCB.

It will be intersesting to see, if the device powers on again automatically after a low battery switch off.

Also my node in Wattens was able to hear the node up there, even if my node looks to west and not east:

the meshtastic node up there had some nice side effects: Wide-range to munich and also augsburg and the mesh network really big.

Note the number of hops and also the distances in the following stat:

As the t-deck has an own keyboard, no bluetooth connection with a smartphone is necessary to send messages. The Meshtastic Ui has some nice features, e.g.: Mesh detector: Listens for meshtastic nodes, useful for exploring, if you are within a/the mesh. Can last some time as the nodes only send beacons from time to time.

RSSI and SNR tool: Useful for detecting the appr. position of nodes. By the way: When they send gps data, you can also use the map feature (at the moment I copy positron 0-14 to my sd card).

Austria with tiles sized 1-12 only has apprx. 200 MB and 8000 tiles, now trying up to 13 and 14.

Update: Austria 0-13 has 31000 tiles

It is also possible with the Meshtastic UI to use a "map feature" but therefore you have to copy map tiles onto a SD card.

Some tile sets are available for download e.g. here

But the system has some implications: You have different zoom levels and the zoom is done by splitted up tiles. So all of Europe has 15 GB of data, but the main problem: More than a million files and all are small, only some kilobytes.

Means: You have to format the SD card with very small blocks and also then the unzipping and copying of the tiles takes a loooot of time

First result: Nearly the same amount of nodes as "down" in the Inntal valley. But: The Node "IBK Nord" could be received with a good signal of -113 dBm. Crazy, a WLAN worse than -80 or -90 dBm would be rated not working...

Node "IBK Nord" has a very good position indeed: I can also receive and use it from Wattens (with a weaker signal).

For my tests, this means: A message sent from Kellerjoch first traveled to IBK Nord and was then relayed back to my device in Wattens. We will see this in the message history later.

But first I did try a long-fast message to all reachable nodes (up to 3 hops) and got some replies. Please note the node Weerberg, this one was new for me. Meshtastic devices everywhere ;-) And you can see the hops (Sprungweite) already visible here.

Now I did send messages to my node in Wattens, they were acked by the mesh:

Back at home I looked into the meshtastic device there and the test messages were there, not received directly but via one hop:

And finally the stats of the device at Kellerjoch before switching it off: