Configuring RUTX50 so Home Assistant can monitor data via MQQT

NETWORKING SOLUTIONS
1

Hi, I’ve done a search and haven’t really found the answer to how to configure this.

I found @RobLitjens topic here which suggests it’s possible to do, but I’ve tried various settings and have failed to get it working.

Desired result:
Create local LAN based Home Assistant Dashboard which can display RUTX50 info using MQQT Topics (e.g. operator, connection, network etc) - if there’s a better protocol to use then I’m happy to try that.

Current known working:
Mosquito Add On / Integration in Home Assistant tested and working by publishing Topic from MQQT Explorer installed on local PC.

Current issue:
I can see connections coming from the RUTX50 in the Mosquito logs in Home Assistant, and I have created a user/pass in HA specifically for MQTT so it doesn’t clash with any default users. However, the connections are closed as the client is ‘not authorised’

I initially tried setting up the Publisher, Broker and Bridge MQTT settings in the RUTX50 interface, and have now also tried setting up the MODBUS MQTT (I didn’t see it to start with!) but no matter what settings I’ve tried I always get some variant of ‘not authorised’ in the Mosquito Log on HA.

This is all being done locally, the router and HA are on static IPs, the HA (11.11.11.150) is connected by ethernet to the router (11.11.11.1).

I haven’t created any certificates - but from what I’ve managed to understand this shouldn’t be necessary.

Any help greatly appreciated as I’m completely new to Home Assistant and MQTT so I’m hoping it’s just something simple.

This is the code from the log from Mosquito in Home Assistant when I start it up. It just loops the same error after that point.

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/mosquitto.sh
[08:44:28] INFO: SSL is not enabled
cont-init: info: /etc/cont-init.d/mosquitto.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[08:44:28] INFO: Starting NGINX for authentication handling...
[08:44:28] INFO: Starting mosquitto MQTT broker...
2025-03-18 08:44:28: Warning: Mosquitto should not be run as root/administrator.
2025-03-18 08:44:28: mosquitto version 2.0.20 starting
2025-03-18 08:44:28: Config loaded from /etc/mosquitto/mosquitto.conf.
2025-03-18 08:44:28: Loading plugin: /usr/share/mosquitto/go-auth.so
2025-03-18 08:44:28:  ├── Username/password checking enabled.
2025-03-18 08:44:28:  ├── TLS-PSK checking enabled.
2025-03-18 08:44:28:  └── Extended authentication not enabled.
2025-03-18 08:44:28: Opening ipv4 listen socket on port 1883.
2025-03-18 08:44:28: Opening ipv6 listen socket on port 1883.
2025-03-18 08:44:28: Opening websockets listen socket on port 1884.
s6-rc: info: service legacy-services successfully started
2025-03-18 08:44:28: mosquitto version 2.0.20 running
2025-03-18 08:44:28: New connection from ::1:36890 on port 1883.
2025-03-18 08:44:28: Client <unknown> disconnected due to protocol error.
2025-03-18 08:44:28: New connection from 11.11.11.36:64639 on port 1883.
2025-03-18 08:44:28: New client connected from 11.11.11.36:64639 as mqtt-explorer-7dc28af6 (p2, c1, k60, u'**MY EDITED USERNAME**').
[08:44:28] INFO: Successfully send discovery information to Home Assistant.
2025-03-18 08:44:29: New connection from 11.11.11.1:38672 on port 1883.
error: received null username or password for unpwd check
2025-03-18 08:44:29: Client auto-3C5EAC40-EA81-A871-EBBB-C09450243E9E disconnected, not authorised.
2025-03-18 08:44:29: New connection from 11.11.11.1:38680 on port 1883.
[08:44:29] INFO: Successfully send service information to the Supervisor.
2025-03-18 08:44:30: Client <unknown> closed its connection.
2025-03-18 08:44:30: New connection from 11.11.11.1:38694 on port 1883.
error: received null username or password for unpwd check
2025-03-18 08:44:30: Client auto-AF4DB794-D85F-FFEC-F352-109581A94573 disconnected, not authorised.
2025-03-18 08:44:30: New connection from 11.11.11.1:38696 on port 1883.
2025-03-18 08:44:31: Client <unknown> closed its connection.
2025-03-18 08:44:31: New connection from 11.11.11.1:38712 on port 1883.
error: received null username or password for unpwd check
2025-03-18 08:44:31: Client auto-A2340CA4-5844-BD36-FB63-4ED8978EFBC2 disconnected, not authorised.
2025-03-18 08:44:31: New connection from 11.11.11.1:38718 on port 1883.
2025-03-18 08:44:32: Client <unknown> closed its connection.
2025-03-18 08:44:32: New connection from 11.11.11.1:38720 on port 1883.
error: received null username or password for unpwd check
2025-03-18 08:44:32: Client auto-36DF050F-CAB0-03F9-B6C3-FF6A99A890BD disconnected, not authorised.
2025-03-18 08:44:32: New connection from 11.11.11.1:38732 on port 1883.
2025-03-18 08:44:32: New connection from 11.11.11.150:50631 on port 1883.
2025-03-18 08:44:32: New client connected from 11.11.11.150:50631 as 5ZQ0ZkI5nhylz5zFg5DuP1 (p2, c1, k60, u'FNSMQTT').
2025-03-18 08:44:33: Client <unknown> closed its connection.
2025-03-18 08:44:33: New connection from 11.11.11.1:38738 on port 1883.```
2

Can I also make a feature request to provide a proper Home Assistant Integration.

I think a lot of people in boats / vans would find this particularly helpful

4

Hey there!

Thanks for reaching out. After a first look at the logs that you’ve provided, it looks like this could be due to an authorization (or for that matter, even configuration) fail. Ideally, the simple solution would be double-checking the services.log and system.log files from the RUTX50 troubleshooting file.

To get a troubleshoot file:

  1. Log in to WebUI
  2. Press on System → Maintenance → Troubleshoot
  3. Scroll down to Troubleshoot section and press “Download”

Additional checks from the other end (your home assistant) would also be needed to make sure that the configuration is 100% correct.

My best suggestion for the time being would be to continue this conversation via an internal messaging system to avoid leaking any sensitive information. Once we find a solution, you can freely share it here afterward. I’ve sent you a request privately, in the Ticket ID field, simply enter this topic ID which is 12850

Regards,
M.

1 Like
5

Thanks @MatasR - I’ve followed the link from your email and it came back with a message saying “thank you for submitting the support form” - but there was no option to upload the Troubleshoot file I downloaded.

I’m guessing it’s probably raised a support ticket and I should wait for a reply in due course, but I thought I would mention it here just in case that’s not how it works and you’re expecting the file!

6

Hey there,

You did everything perfectly, I’ve already reached out to you via e-mail.

BR,
M.

1 Like
7

Well, I’ve not really had a reply from Teltonika based on the logs I sent.

However, having just left this overnight and logging in again seems to have cured the password error.

Beyond that, I’ve read every article I could find on the internet and on discord servers and…

…no one seems to have successfully integrated a Teltonika router with home assistant using MQTT.

It seems like a lot of people want to do it, but the documentation just doesn’t seem to work or there are references to opgk commands which have since been disabled.

I’ve managed to establish a connection, but nothing more. No way of pulling the data in.

Has anyone managed this?

I really only want to add a badge that will give me an ‘at a glance’ signal indication rather than running a speedtest in order to get that information.

It should be the simplest thing in the world!

8

Well, the good news is that the Teltonika team are looking into this with me. I’ll wait until we’ve got it working and then post up a ‘how to’ guide based on my experience.

If we can’t get it working then I’ll let you know, but I have full confidence in Teltonika!

9

Hi, Just wondering if you had any feedback from Teltonika, I want to do the same to send my position from the RUTX50 to HA via Mosquito. No matter what I simply cannot get HA Mosquito to see anything from the router, you have at least manage to create a connection, more than I have. I set up the MQTT Publisher ON the router and trying to listen on the Mosquito Broker and nothing is being heard. perhaps you may be so kind and share what you do know to get the connection working - Thanks

10

Hi,

We’re working on it and I’ll post the results once we have a working solution.

I’m away until the end of the week but hope to post something at the weekend.

I’ve managed to pull data using Modbus and the next step is to push that to HA using the Data to Sever feature

1 Like