I figured it out! Just in case you’re still stuck - I followed the flow chart on Monitoring via MQTT - Teltonika Networks Wiki and realised that you need to first publish to topic “router/get” the payload “temperature” and your subscriber (Home Asisstant) will recieve the temperature value at your sensor topic above. To do it regularly, just create an automation using the MQTT Publish service to regularly publishes “router/get” “temperature” as above so the routers listening publish their latest temperature.
The slightly longer explanation - first you need to publish to topic “router/get” payload “id” just to make sure you get your id correct - which will be returned on the topic “router/id” with the serial/id as the payload. You can use the general “router/get” above to ask all the routers on the network to publish - but if you just want a response from a single router - you can instead publish to topic “router/111887•••••/temperature” payload “temperature” just to seek an update from that individual router.
Hi, create a “bridge connection” on the teltonika mqtt-broker to your home-assistant server with remote id “core-mosquitto”, your user and pass set in the mqtt-settings of home-assistant.
Add an topic called “router/yourrouterserial123456/#” to the “bride connection”.
Enable it.
Configure the mqtt-publisher to point to your local broker of the teltonika and start it. If this was already done, restart(!) it.
Go to the routers console:
opgk update
opkg install mosquitto-client-nossl
Create a script on the router, which is calling the topics you want. This is mine:
So far, yes. Needed it for more connected wifi devices. Mostly it runs with 4G because we do not have 5G at home. On the road it is fast, but I guess a 4G router like the RUTX14 will be suitable for that too.
Thanks! For me it’s the same plus I will try 5G for speed. I suppose to have 5G but not sure how stable it is but it will have 4G fall back. So let’s see.
I have a Huawei now with a nice integration. That I will miss. Are you using RMS which comes with Teltonika ?
I did try again and I get some login attempts from the router. But always this result:
2023-03-17 20:05:36: New client connected from 192.168.1.1:56656 as core-mosquitto (p1, c0, k60, u'mqtt-user').
2023-03-17 20:05:36: New connection from 192.168.1.1:56660 on port 1883.
2023-03-17 20:05:37: Client <unknown> closed its connection.
2023-03-17 20:05:37: New connection from 192.168.1.1:56662 on port 1883.
2023-03-17 20:05:37: Client <unknown> disconnected, not authorised.
2023-03-17 20:05:37: New connection from 192.168.1.1:56674 on port 1883.
2023-03-17 20:05:37: New connection from 192.168.1.99:51859 on port 1883.
Tried to put up new user but nothing changed! Any ideas? @Chris19 ?
You do need a subscription for RMS, and they have various levels of credit which can be a bit confusing. I was initially buying monthly credits, but switched to a 10 year service pack (10 years of RMS remote access tied to one router) which is a pretty damn good deal if you consider the hassle of remote access without RMS.
I got it from here, same day response, but there are numerous RMS dealers:
Incidentally … RMS remote access to the router WebUI is cool but the real power feature is the remote CLI … with this I can ssh into anything on my local network. which is a massive bonus.
Yes, if you buy credits / the 10yr pack / etc. etc. you are given a code from the retailer which you enter into the RMS website. After that, you assign those credits / pack to a specific device and job done.
Also yes, WebUI and CLI remote access are both default services for every device in RMS.
I think every new Teltonika device comes with 1 month of free RMS, so I suggest getting connected first, test everything works before buying credits. Any Q’s just ask me.
