This works well getting my home automation working with meshcore. I was able to get some rudimentary functionality happening in one morning, thanks to the well thought out command set, messaging, and excellent readme.
I mainly plan to run this on a frequency away from the common one to link some of the harder to reach spots for my sensor network. The command set is pretty much perfect to make this work with node-red.
There is one command that I would find useful - sending messages to a room server.
Any plans for this?
Great work on meshcore-mqtt!
This works well getting my home automation working with meshcore. I was able to get some rudimentary functionality happening in one morning, thanks to the well thought out command set, messaging, and excellent readme.
I mainly plan to run this on a frequency away from the common one to link some of the harder to reach spots for my sensor network. The command set is pretty much perfect to make this work with node-red.
There is one command that I would find useful - sending messages to a room server.
Any plans for this?
<!-- github-sync-id:3355434834 -->
So, 90% of this service was produced by Claude Code (AI) as a proof of concept for a sensor network I'm working on. I run the service 24/7 and it has a few issues.
So, 90% of this service was produced by Claude Code (AI) as a proof of concept for a sensor network I'm working on. I run the service 24/7 and it has a few issues.
In terms of messaging room servers, I think the only way of doing it is to send a message to the room servers public address as a DM. I don't think the underlying Python library distinguishes for "room server" messages: https://github.com/meshcore-dev/meshcore_py/blob/main/src/meshcore/packets.py
<!-- github-comment-id:3315357739 -->
Claude finished @jinglemansweep's task —— View job
Analysis of meshcore_py room server capabilities
Based on my investigation of the codebase:
Current findings:
No explicit room server support: The meshcore_py library (as used in this project) does not have any explicit room server messaging functionality. There are no room-server-specific methods in the command set.
Available messaging methods: The current implementation supports:
send_msg(destination, message) - Direct messages to nodes
Possible workaround: As @jinglemansweep mentioned, room servers might be reachable by sending a direct message to the room server's public address. This would use the standard send_msg command with the room server's node ID or address as the destination.
Answer to your question:
The meshcore_py library does not have dedicated room server messaging functionality. However, you may be able to message a room server by treating it as a regular node and using the send_msg command with the room server's public address/ID as the destination.
To test this approach:
# Send message to room server via MQTT command
mosquitto_pub -h localhost -t "meshcore/command/send_msg"\
-m '{"destination": "ROOM_SERVER_ADDRESS", "message": "Your message"}'
Where ROOM_SERVER_ADDRESS would be the room server's node ID or public key.
Note: This functionality would depend on how room servers are implemented in the MeshCore protocol itself. If they accept standard direct messages, this approach should work.
**Claude finished @jinglemansweep's task** —— [View job](https://github.com/ipnet-mesh/meshcore-mqtt/actions/runs/17886250904)
---
### Analysis of meshcore_py room server capabilities
Based on my investigation of the codebase:
**Current findings:**
1. **No explicit room server support**: The meshcore_py library (as used in this project) does not have any explicit room server messaging functionality. There are no room-server-specific methods in the command set.
2. **Available messaging methods**: The current implementation supports:
- `send_msg(destination, message)` - Direct messages to nodes
- `send_chan_msg(channel, message)` - Channel messages
3. **Possible workaround**: As @jinglemansweep mentioned, room servers might be reachable by sending a direct message to the room server's public address. This would use the standard `send_msg` command with the room server's node ID or address as the destination.
**Answer to your question:**
The meshcore_py library does not have dedicated room server messaging functionality. However, you may be able to message a room server by treating it as a regular node and using the `send_msg` command with the room server's public address/ID as the destination.
To test this approach:
```bash
# Send message to room server via MQTT command
mosquitto_pub -h localhost -t "meshcore/command/send_msg" \
-m '{"destination": "ROOM_SERVER_ADDRESS", "message": "Your message"}'
```
Where `ROOM_SERVER_ADDRESS` would be the room server's node ID or public key.
**Note:** This functionality would depend on how room servers are implemented in the MeshCore protocol itself. If they accept standard direct messages, this approach should work.
<!-- github-comment-id:3315368537 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Great work on meshcore-mqtt!
This works well getting my home automation working with meshcore. I was able to get some rudimentary functionality happening in one morning, thanks to the well thought out command set, messaging, and excellent readme.
I mainly plan to run this on a frequency away from the common one to link some of the harder to reach spots for my sensor network. The command set is pretty much perfect to make this work with node-red.
There is one command that I would find useful - sending messages to a room server.
Any plans for this?
So, 90% of this service was produced by Claude Code (AI) as a proof of concept for a sensor network I'm working on. I run the service 24/7 and it has a few issues.
In terms of messaging room servers, I think the only way of doing it is to send a message to the room servers public address as a DM. I don't think the underlying Python library distinguishes for "room server" messages: https://github.com/meshcore-dev/meshcore_py/blob/main/src/meshcore/packets.py
@claude Does the
meshcore_pylibrary allow messaging Room Servers?Claude finished @jinglemansweep's task —— View job
Analysis of meshcore_py room server capabilities
Based on my investigation of the codebase:
Current findings:
No explicit room server support: The meshcore_py library (as used in this project) does not have any explicit room server messaging functionality. There are no room-server-specific methods in the command set.
Available messaging methods: The current implementation supports:
send_msg(destination, message)- Direct messages to nodessend_chan_msg(channel, message)- Channel messagesPossible workaround: As @jinglemansweep mentioned, room servers might be reachable by sending a direct message to the room server's public address. This would use the standard
send_msgcommand with the room server's node ID or address as the destination.Answer to your question:
The meshcore_py library does not have dedicated room server messaging functionality. However, you may be able to message a room server by treating it as a regular node and using the
send_msgcommand with the room server's public address/ID as the destination.To test this approach:
Where
ROOM_SERVER_ADDRESSwould be the room server's node ID or public key.Note: This functionality would depend on how room servers are implemented in the MeshCore protocol itself. If they accept standard direct messages, this approach should work.