MeshCom-Client
A MeshCom-Client, written in Python, for using with MeshCom (https://icssw.org/meshcom/) Nodes
What is this about?
This is a MeshCom-Client, that is written in Python for simple usage on a compatible computer system. Initially it is with very basic functionality but I think it will grow up over the next weeks :-)
How to start
- Install python3 and fullfill requirements by installing all missing libraries.
- Connect your MeshCom-Node to your serial terminal and issue the following commands, to start the node to transfer data via udp to your computer:
- --extudpip [ip of your computer]
- --extudp on
- Go to Settings and put in the new destination ip address = ip of your node.
Now it should be running!
Key features
- Grouping messages into tabs by destination (GRC or callsign)
- Alerting sound for new message
- Watchlist and alerting sound for callsigns in watchlist
- Restoring of chat-history on reopening chat-tabs
- Reopen specific chat on demand
- Delete complete chat history (also from restoring-source)
- Multiple languages (actually German and English)
Functional areas
Message area upper left
This is the place where you type your message and give the target group id or callsign. With a click on the send-button your message would be transfered via Lora to the next node and maybe to the internet server.
Timestamp upper right
Within this box the timestamp transfered by the network every 5 minutes is shown. This is used as an indicator that the network is still alive.
reopen previous chat upper left
As the MeshCom-Client is saving chat-history you are able to reopen chat-tabs and reload the content. With the selectbox you can select any stored chat-history and with the button you can reopen and reload the chat-history of this chat.
chat message tabs in the lower half
This is the area where each group chat is grouped into a single tab per target. you can easily switch between the chats by selecting another tab. If there is any new message within a chat, it would be shown with a (new)-label on the tab-rider.
There are also two buttons: delete chat deletes the chat (and it's stored history) and X closes only the tab (to be reopened, if a message comes in or if you reopen it manually).
If you click on the target label, the (new)-marker would disappear in the opened tab, same if you switch over to another tab, then the label there would disappear.
Using Watchlist
via Settings - Watchlist you can configure your personal watchlist. Here you add callsigns without SSID to be alerted with alert.wav-sound (you can replace individually to your favor).
Easy Installation and Upgrade
Easiest way to install this is to use pipx install MeshCom_Client.
If you have a previous installation done with pipx you just have to use pipx upgrade MeshCom_Client for getting the lastest version. Maybe you have to do this more than once till it says that meshcom-client is already at latest version.
If you want to know, how to install pipx on your system, consult GitHub - pypa/pipx: Install and Run Python Applications in Isolated Environments
After installation, you can simply start the client running MeshCom-Client from console.
Settings-file and chat-log could be found at .local/pipx/venvs/meshcom-client/lib/python3.11/site-packages/MeshCom_Client/ or similar.
Troubles?
If you have issues with emojis under linux, you could try sudo apt-get install fonts-noto* to install needed fonts
ToDos
- View counter of new messages in tab
- Integration in "flutter"(Android and iOS-compatibility)
- Displaying positions of stations (when receiving a pos-message) on a map (OSM)
Contributions
Sound Effect by freesound_community from Pixabay
Sound Effect by Rescopic Sound from Pixabay
Metadata
Release files for MeshCom-Client 1.0.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| meshcom_client-1.0.13.tar.gz | 410.6 kB | Without provenance | Details for meshcom_client-1.0.13.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| meshcom_client-1.0.13-py3-none-any.whl | Python 3 | none | any | Details for meshcom_client-1.0.13-py3-none-any.whl |
Total release size: 827.7 kB
Release files / meshcom_client-1.0.13.tar.gz
| Download URL | meshcom_client-1.0.13.tar.gz |
|---|---|
| Size | 410.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9bd284c565ddb904a7a39a72f360bf5e684b713b5ecb4bb561291491e9cb83ea
|
|
BLAKE2b-256 checksum How to use checksums |
dbaf1118d02da5bac15010a3ca5c241e47d4f4840a5f51da7d5b34abf4c3ffb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Release files / meshcom_client-1.0.13-py3-none-any.whl
| Download URL | meshcom_client-1.0.13-py3-none-any.whl |
|---|---|
| Size | 417.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6aea4440efe668d4946e4239d7bc7189063bd704c938e555515e7a375d504319
|
|
BLAKE2b-256 checksum How to use checksums |
f7da45fd4c7909246e4b95f189372f2782ed5b25e65d50cc2455d5de968abf80
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.2
|
Security for MeshCom-Client 1.0.13
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.