> For the complete documentation index, see [llms.txt](https://andlo.gitbook.io/mycroft-skills-list/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://andlo.gitbook.io/mycroft-skills-list/skills/not-in-market/iot/mesh-skill.pcwii.md).

# Mesh

#### *mesh-skill.pcwii*

### Description:

A flock of Seagulls, a pride of Lions, a swarm of Bees, and a "mesh of Mycrofts".

This skill utilizes the lightweight MQTT messaging protocol to connect a group ("mesh") of Mycroft units together. The skill has the ability to send messages (intercom) and commands (messagebus) to one or more remote Mycroft units.

1. Each Mycroft unit has the ability to publish both Mycroft requests and responses to the the MQTT broker. The MQTT Topics for this communication is...

* `/RemoteDevices/deviceUUID/request`
* `/RemoteDevices/deviceUUID/response`

1. The deviceUUID is a unique ID created from the MAC of the sending Mycroft unit. \*This is intended to be a general MQTT broadcast and can be subscribed to by any MQTT client (ie. Home Assistant?).
2. Each Mycroft unit has it's own Device Name (location\_id) that can be set in the web interface.
3. The Mycroft unit will automatically subscribe to all messages sent to it's own Device Name (location\_id).

* `/RemoteDevices/`
* The is automatically obtained from the Mycroft Device Settings web page... ![location\_id](https://github.com/andlo/mycroft-skills-list-gitbook/blob/master/images/location_id.png)
* location id's are automatically converted to lowercase to avoid confusion

1. When a message is sent from any Mycroft unit, the message will be published to "Mycroft/RemoteDevices/location\_id".
2. The destination location\_id is specified in the skill dialog.
3. The message payload will contain the following Json...

* `{"source":"", "message":"is dinner ready yet"}`

![](/files/-LzXeYK0f0z3-8Qh6IKn) ![](/files/-LzXeYK0f0z3-8Qh6IKn) ![](/files/-LzXeYK0f0z3-8Qh6IKn) ![](/files/-LzXeYK0f0z3-8Qh6IKn) ![](/files/-LzXeYK0f0z3-8Qh6IKn) ![](/files/-LzXeYK0f0z3-8Qh6IKn) ![](/files/-LzXeYK0f0z3-8Qh6IKn)

#### Platform:

![Mark I](/files/-LzXeYK2dsk17gI0OA2k) ![Mark II](/files/-LzXeYK4JDAbBvHqrpNo) ![Picroft](/files/-LzXeYK6KhCZdb637YLQ) ![plasmoid](/files/-LzXeYK8Pp4IO4mdH0ax)

#### Examples:

> Send a remote message.\
> Send a remote command.

{% hint style="danger" %}
This skill dosnt have any license attatched. It is not adviasable to use this skill nor fork or clone, as you don't know if you are legaly allowed to do so by the auhtor.
{% endhint %}

### Summary:

**Github:** <https://github.com/pcwii/mesh-skill>\
**Owner:** [@pcwii](https://github.com/pcwii)\
**Created:** 2019 Dec 21 13:58:30 UTC **Last updated:** 2020 Apr 28 07:51:42 UTC\
**License:** No License

**Categories:** \[ IoT ]\
**Tags:** #mesh #remote #connect #control #MQTT #HA #Homeassistant


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://andlo.gitbook.io/mycroft-skills-list/skills/not-in-market/iot/mesh-skill.pcwii.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.