Integrate Meshtastic (ccnet-wv-meshpoint) MQTT into Home Assistant #57

New issue

Open

opened 2026-08-24 15:07:26 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-08-24 15:07:26 +00:00

Collaborator

Open decision to scope before implementing: broker choice.

Repoint the node at ccnet-mosquitto-swarm (internal broker already
architected for this per CLAUDE.md/ccnet-mosquitto-swarm/README.md)
-- requires adding a meshtastic user via the stack's chained
mosquitto_passwd -b pattern (no -c) plus a new Swarm secret; only
the ccnet user exists in mosquitto-swarm-stack.yml today.
Or have HA reach out to the public broker directly -- adds a WAN
dependency and sits awkwardly against vlan60 being locked down as
tightly as the DMZ.

Either way, the node's local.yaml currently has publish_json: false
and homeassistant_discovery: false (Meshpoint has native HA MQTT
discovery support) -- both need flipping for a clean HA integration
path, since raw protobuf topics are much harder to consume than JSON.

Also note: this node has never received an RF packet from another
Meshtastic node in its 4-week history (self-TX only), and Meshpoint's
MQTT publisher only relays received packets -- so no MQTT traffic will
appear until a neighbor is heard, independent of the HA wiring itself.

RAK7248/Meshpoint node (ccnet-wv-meshpoint, 10.10.60.208, vlan60/IoT) health-checked 2026-08-24 -- service healthy, MQTT connection to the public mqtt.meshtastic.org broker confirmed live (ESTABLISHED socket). Not yet wired into Home Assistant. Open decision to scope before implementing: broker choice. - Repoint the node at ccnet-mosquitto-swarm (internal broker already architected for this per CLAUDE.md/ccnet-mosquitto-swarm/README.md) -- requires adding a meshtastic user via the stack's chained mosquitto_passwd -b pattern (no -c) plus a new Swarm secret; only the ccnet user exists in mosquitto-swarm-stack.yml today. - Or have HA reach out to the public broker directly -- adds a WAN dependency and sits awkwardly against vlan60 being locked down as tightly as the DMZ. Either way, the node's local.yaml currently has publish_json: false and homeassistant_discovery: false (Meshpoint has native HA MQTT discovery support) -- both need flipping for a clean HA integration path, since raw protobuf topics are much harder to consume than JSON. Also note: this node has never received an RF packet from another Meshtastic node in its 4-week history (self-TX only), and Meshpoint's MQTT publisher only relays received packets -- so no MQTT traffic will appear until a neighbor is heard, independent of the HA wiring itself.

claude-bot added the

p:low

infra

labels

2026-08-24 15:07:26 +00:00