-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] LTE modem cell info #249
Comments
I can see how this would help, but I dont have any LTE modem to test work on this. Monitor commands can be tricky. |
If you need any debug - no problem, I can do this for you. |
that wont work unfortunatly. api is not fully documented so I dont know interface attribute name for monitor command. it will require lot of trial and error work just to get to debug output I need to implement this functionality. |
/interface/lte/print will show you all lte interfaces - see firs output in my initial message |
thats not what I mean. that part is simple and will work. |
I'm not able to get one. can you recommend something? if I can get it cheap, I will consider it. |
Better to ask your cell operator. Here simpliest LTE modem cost is around $40. You can find much cheaper on Aliexpress if you use it. |
Unfortunatly, all offers I got are way more I'm willing to put into something I most likely wont ever use.
|
Using API client from https://github.com/DEssMALA/RouterOS_API I've got next: API command: Here we can take interface name from "name" field. API command:
Output: I've removed imei, imsi and uicc manually from output. Is this enough for implementation? I can test your changes on my installation. |
Thats wont help me much, since I need to know how to access it. That API uses something custom, as "numbers" field does not exist.
My guess this should give a response if it is working like most command queries. Also, which information from both print and monitor is important to have in HA? I never used custom LTE, so I would be guessing. |
Added as next lines after Command:
Error in log with answer:
Command:
Error in log is "None" and secondary error from mikrotik api is "item not found" Then command argument changed to:
And this gives answer:
I don't know why id is not same as in "print" command, probably it's re-numerated in monitor? And need to enum interfaces from "print" command from 0 incrementally if few interfaces available? I don't have secondary modem to check. Regarding information - I've already listed it earlier, for me interesting: Also "name" from "print" command may be used as interface name. |
Yea, thats really weird behaviour. ".id" should be exact match for interface ".id". Could be a bug, or maybe something that is not implemented in this command. what if you try:
if that works, change lte1 to something that does not exist to see if you get error. it could also be
or default-name instead of name Also, is current-operator really empty, or did you just removed it? Also 2, what are you looking to do with this functionality/how do you plan to use it? |
This one working excellent, all info returned. |
Empty. Probably firmware just don't know my operator code/name :)
I wrote at beginning - monitor stability of channel. Week ago my closest cell breaks and I had 2 days of fun looking in WinBox how modem tried find another ways to connect - changed LTE/3G protocols, changed channels and other things. Especially interesting rssi/rsrp/rsrq/sinr in a case if you want to adjust antenna position to find best signal. Of course I can see all of this in WinBox, but HA is much interesting in sight of statistics, for example how signal changing depends on weather conditions - may be much better to setup antenna to less powerful cell station but more stable instead of powerful one but with unstable signal. |
Forget to add - if I set ".id" anything else than 0 or 'lte1' - I've got error "item not found" - I had same when ".id" was set to 6 earlier if you remember. |
thanks, I just need one more thing.
Can you temporary rename the interface to anything else and test it again? I need to know if monitor it is accepting 'default-name' or 'name' as a parameter. could be actually both, but it is important to know this one. |
Renamed to lte1m
|
ok, so it takes "name". thanks, thats all I needed for implementation. |
Hi. |
Very nice. It looks exactly as I would like it to. Could you please share your knowledge. And write what and where to put it? |
@mimiromik for Huwei I’m just using the default HA-integration and it shows also the signal qualityparameters. for plotting, I’ve used histogram. For speed testing and ping I used speedtest-integration. |
@heikkimu Who is talking about Huawei? The topic is about MikroTik. And it does not offer the necessary values in integration. |
@tomaae I can give you remote access to Mikrotiks with different LTE modems. Mail me — acidsas at gmail.com |
This is my current setup with 2 LTE dishes (LHG & ATL), I've been following this thread for some time and managed to get this working without the integration, just using the new REST api from ROS.
config is the same for LTE2 as well |
Is it possible to implement cell info for LTE modem connected to router?
Here how to know lte interface:
How to collect info:
For me interesting next sensors:
for interface sensors:
current-cellid (numeric)
enb-id (numeric)
sector-id (numeric)
phy-cellid (numeric)
data-class (text)
session-uptime (timestamp)
primary-band (text)
ca-band (text, in my example earlier it is not exist because of my cell does not support aggregation, but for future and another places)
rssi (numeric)
rsrp (numeric)
rsrq (numeric)
sinr (numeric)
This can help to monitor connection stability and quality.
Thank you!
The text was updated successfully, but these errors were encountered: