Support wireless metrics for wifiwave2 devices (#155)
#161
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
October 14, 2023 19:21
from https://forum.mikrotik.com/viewtopic.php?t=195124#p999722: wifiwave2 is an implementation of drivers from the manufacturer of the chipset, rather than an in-house written driver (which wireless is). So there are many small details that are missing or incomplete... wifiwave2 has a slightly different API and has fewer properties to query. This means that not all metrics are available for wifiwave2 devices. Also, the implementation aims at keeping the name metric names for wifiwave2 devices to ensure that existing dashboard continue to work without any modification.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
from https://forum.mikrotik.com/viewtopic.php?t=195124#p999722: wifiwave2 is an implementation of drivers from the manufacturer of the chipset, rather than an in-house written driver (which wireless is). So there are many small details that are missing or incomplete...
wifiwave2 has a slightly different API and has fewer properties to query. This means that not all metrics are available for wifiwave2 devices. Also, the implementation aims at keeping the name metric names for wifiwave2 devices to ensure that existing dashboard continue to work without any modification.