Do any of you guys know or are aware of a way to grab temperature of the access points provisioned and managed by CAPsMAN and show it in the dashboard?
I figured if its fully managed by CAPsMAN it would show its basic "access point health" which most of the metrics are already there like its name, band channel, ssid, etc etc... Could just add another column in "Remote CAP" tab which would be "Health" or "Temperature" and have it readout the temp that gets reported by access points back to the controller (in this case rb5009Upr)
(The reason i think that health metrics in CAPsMAN dashboard would be extremely useful is just general monitoring instead of logging into one by one and checking the health tab)
I also find it weird how Upgrading/Upgrading policy doesn't upgrade the RouterBOOT/Bootloader while being under CAPsMAN management.
[Network layout is rb5009UPr -> 2x cAP ax]
Temperature
No. You may have to use snmp for that.
Routerboard
Normal behavior. This always requires a second reboot.
You can always file a support ticket and put it in as a feature request.
I've sent a ticket for a "suggest a feature" with the thread attached, so i guess now we wait.
This is the last Reply i got from the ticket i sent, so get going people ![]()
Deniss M.
10 hours ago
We do not have any plans to add such a feature at the moment, but if more users will request it, we will >see how this can be implemented.
Not likely for the CAPSMAN as it is "wifi" specific tab/menu, but in other ways.`
Why would knowing the cap temperature important or useful?
because i want to know it and its useful for troubleshooting if people want to know if its theirs problem that their access point is overheating because they hypothetically had a problem with speed or if it something else thats a configuration error, because they do naturally run hot, mine do, mine run from 60-68C depending on which one and id love to have that under control and i bet a lot of other people would have that stuff there especially with wifi 7 stuff comming.
I am just asking questions. It is more likely that Mikrotik implements this feature when they can see a use case.
is not a big motivation for Mikrotik.
And it can already be done using snmp... so even less motivation.
You can read the usecase in the root write-up of my forum discussion that i made, i basically wrote the same thing in the support ticket, as they said they just would need more people wanting the feature to look into it.
I personally think it would help a lot especially the Routerboard updating through capsman, and temperatures would be just a bonus but a very welcome and a good change imho.
Snmp is too much effort, i looked into it.
To be honest, reboot is even the lesser problem.
When power goes out in the building, it is solved automatically if you set it to update automatically.
Saves a reboot.
Thats not a solution and thats not called "having control over ur hardware".
Two different feature requests:
- read health
- upgrade routerboard
Yeah, its two feature requests, you can send two tickets then ![]()
I would not request the health thing myself. That's nothing capsman should care for. I'll file a request for Mikrotik RouterOS Controller instead.
Upgrading the routerboard firmware sounds reasonable, as upgrading ROS is already possible.
So the thinking behind the "health thing" is that, if i already have everything about the Remote AP thats managed by CAPSMAN there, why is something as trivial as accesspoint temperature thats managed by the "capsman controller" not showed there, its probably the most basic troubleshooting info about a product underperforming or performing not as expected.
I might just be wrong on that one i dont know, but as a "network or wifi controller" we should get that readout somewhere thats not the accesspoint itself because its literally useless there, i dont want to login into each accesspoint one by one and look at its health, thats the whole point why i assigned my rb5009 as a controller to Control and supervise them.
It's not most basic. Some devices dont have health reading/sensors at all.
Then thats just badly designed from the get-go, sorry to say.
Eitherway your ticket for the firmware updating is appriciated, each and every one counts ![]()
As things are right now, CAPsMAN only provisions wifi interfaces. Nothing more (not even wired interfaces and bridge which sometines are crucial for basic wifi functionality such as data flows). As @infabo wrote, the scope you're asking for is broader, some kind of ROS controller ... which could use existing possibilities (e.g. SNMP) behind the scenes. There used to be something similar, called "the dude" ... but got left behind with conception of ROS v7.
MT universe has some strengths ... central control is not one of them. I'm not saying that we wouldn't like to have it, but I guess most of MT affectionadoes are used to live (a quality life
) without it. And most of us feel that there are more pressing issues for MT to fix before ...