I created an environment in routerOS, that enables IoT-like (i.e. the server doesn't talk to the router, but the router talks to the server) operation. it works in a reasonable way, but i'd think i'd be better of with a proper MQTT client implementation in the device, that enables subscribing and posting to topics:
- performance data, state, logs, idk - so in general "a routerOS variable"
- trigger a script / feed the input of an event that is sent to a subscribed topic

i might say, this shouldn't be a big performance issue as teeny-tiny micros can accommodate one and live on, so i thought i might ask the scripting community whether it would spark some ideas/interest on someone else's side, and create a demand so the next minor release of RouterOS (or maybe #RouterOS7) will suddenly include this functionality.
my explanation for it is that i don't want to track devices, i might not will be able to talk to them (behind nat, behind firewall), but in many cases they could just talk to my server. this would also enable some sort of ZTP/ZTO environment as well.

imagine something like
and you'll be able to use a script to write a routerOS variable or just a string to a publish-mode topic:

MQTT support would be great. A definite requirement would be SSL/TLS connections for each broker.

As a Smart Home user and possibly enthusiast and a multiple Mikrtik user this would be very useful. IE the ability to interact with my MQTT server running elsewhere and subscribe to topics that are being used in our Smart Home. Mikrotik anybody .... ?

+1 for this feature. Would love to be able to have Mikrotik devices subscribe to a central MQTT server over TLS/SSL to trigger scripts on topic updates. Perfect for doing lightweight automation and control and not need to poke any inbound holes through firewalls! We currently do this through some script magic but it only checks for updates once a day to keep traffic low...

+1 for MQTT client

+1

/tool fetch which supports TLS 1.2 and can provide CA, public and private key will work for me too.

+1 for MQTT client

+1 for MQTT :-)
would also be interesting as transport protocol for LoRaWAN

+1 for MQTT client

News about mqtt and mqtts?
Mikrotik could think develop a tool for iot and dedicating devices, exactly like years ago he started with the rb112 or rb532 when WiFi cards were only PCMCIA....

I do also have several Mikrotik units and more to come.
Also running MQTT servers and alot of "things" connected to openhab trough my WiFi.
Next on the list is LoRa for outdoor appliances, and if we get mqtt sub/pub on the unit, I can test several scenarios in my home.

Also HIGHLY supporting this request.

+1 for MQTT :-)
would also be interesting as transport protocol for LoRaWAN

Would be a perfect companion!

+1 for MQTT client

+1 Publish/Subscribe with encryption feature will be great!!

I do also have several Mikrotik units and more to come.
Also running MQTT servers and alot of "things" connected to openhab trough my WiFi.
Next on the list is LoRa for outdoor appliances, and if we get mqtt sub/pub on the unit, I can test several scenarios in my home.

Also HIGHLY supporting this request.

@hawkn
Have you seen the wAP LR8 kit? Its a lora base station but I think it does not do MQTT. Sadly.
https://mikrotik.com/product/wap_lr8_kit

there's now an IoT package available in 7b5.
and it is available on all platforms:
https://help.mikrotik.com/docs/pages/vi ... d=41680915

Hi,
In version 7.1b5 there isn't LORA package... How could test mqtt with lora ?
Ciao Carlo

The IoT package is in the “extra packages” for 7.1b5.

I hope this IoT package makes it’s way into the 6.48 series with the release of the KNOT. The MQTT and Modbus functions are quite useful!

Yes I know.

I hope there is the functionality to handle payload and then to use mqtt ....
AES decrypting would be appreciated

FYI, the iot package is now in "extra" packages of 6.48.3. From the change log:

*) package - added new "iot" package with Bluetooth (KNOT only) and MQTT publisher support;

For those that might be tripped up by this like I was, it seems that using the /iot mqtt publish command in scripts oddly requires the "test" permission.
Also, the toJson function from viewtopic.php?t=120441#p790680 combos with mqtt publish nicely.

Hi wonderful feature, but I tried it and doesn't work for me.

[admin@jindra] > iot export
/iot mqtt brokers
add address=192.168.12.2 client-id=test name=kancl password=***** username=user

[admin@jindra] > iot mqtt publish broker=kancl message="test" topic=mikrotik

No traffic in sniffer to address 192.168.12.2...

Any advice? Thanks!

Hi wonderful feature, but I tried it and doesn't work for me.

[admin@jindra] > iot export
/iot mqtt brokers
add address=192.168.12.2 client-id=test name=kancl password=***** username=user

[admin@jindra] > iot mqtt publish broker=kancl message="test" topic=mikrotik

No traffic in sniffer to address 192.168.12.2...

Any advice? Thanks!

Please create a ticket (https://mikrotik.com/support) and provide supout.rif file with the packet capture for analysis.

+1 for MQTT client

... as there was a recent post in the topic, I'm adding my 5c: I guess it is already included into ROS7 release (so check it out in extra packages)