MQTT and matrix/riot instant messaging gateway

[rradar]

It would be a great communication channel. If integrated in Home Assistant it could be used with notify: and take immediately advantage of all powers home assistant offers.

For example I could text weather and home assistant can be configured (conversation/intents) to actually reply with the actual weather forecast information I set. ⛅

If I'm right the linux application is written in python already (just like home assistant) so the work is maybe already half done for this 😁

[mehuman]

Hi fellow HA user,
I've brought this up on the forums and have, at least I think, an interesting use case in smarthomeing a small RV and using meshtastic as a source of communication when in the backcountry.

MQTT support is planned link which should get Meshtastic and HA talking. Something beyond that might be out of scope for a project this new, unless someone takes the initiative to code it. I was dreaming of an ESPHome/Meshtastic convergence so I can add modules to the device.

[geeksville]

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/home-assistant-integration/378/4

[geeksville]

(Not exactly home assistant - but I'm going to repurpose this bug for tracking MQTT support)

[rradar]

Despite MQTT (20 year old protocol by now) get's supported I would really like to see a real/native support in home assistant.

I finally turned off my mqtt broker last year and I could not think of a happier moment in my 'technical career'. It just sucks so much time to get server/clients speaking proper to each other and debugging mqtt in general is just a lot of a mess

[geeksville]

I think native home assistant support would be great and would happily accept PRs / help anyone who wants to do it.

…

On Fri, Jun 12, 2020 at 9:03 AM rradar ***@***.***> wrote: Despite MQTT (20 year old protocol by now) get's supported I would really like to see a *real/native support in home assistant*. I finally turned off my mqtt broker last year and I could not think of a happier moment in my 'technical career'. It just sucks so much time to get server/clients speaking proper to each other and debugging mqtt in general is just a lot of a mess — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#169 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABXB2MF23RPUWAG5YB3I2LRWJGV3ANCNFSM4N3QD3WA> .

[slavino]

Hardwiring to any solution doesn't put this project any further. Providing a set of adapters is a much better approach as it literally opens gates for any integrator.

• Easy to use REST API can open gates even to cheap hosting of PHP based solutions.
• Simple MQTT integration can let it grow even further if there will be well maintained versioning of messages (because I believe it will pass JSON strings back and forth). And setting up MQTT broker on RaspberryPi is literally question of few minutes.

So rather than doing proprietary binding to HASS I do suggest to keep it simple and develop a DEMO for cheap and time-wise affordable solutions/integrations. To setup HASS just to tryout Meshtastic capablities in terms of interaction with server backend seems a bit overkill to me...

[geeksville]

possibly use protobufs as an alternative MQTT encoding, which would allow sending tiny ints rather than long topic strings. Mapping from those ints to "standard" MQTT strings would happen automatically inside the node and the gateway.

Try to move as many of the existing services as possible (position and text messaging) to be built on top of this micro-MQTT implementation.

[geeksville]

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/rak815-can-connect-with-thingsboard-platform-using-lora-gateway/721/6

[rradar]

I'm not a developer but from what I can tell there is a python implementation for meshtastic (Python 97.5%) and there is the Home Assistant Integrations which are a 100% Python, maybe most of the work is actually already done? 🤔

[geeksville]

btw - design plan here: https://github.com/meshtastic/Meshtastic-device/blob/master/docs/software/mqtt.md

[geeksville]

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/mqtt-roadmap-and-release/3232/2

[samuk]

Any updates on this one, would like to play with some sensors.

[samuk]

Great to see this happening. Any idea when it will be in a release?

[sachaw]

riot isn't implemented yet, still in 'feature request' stage, but mqtt can be used: https://meshtastic.org/docs/software/settings/mqtt