Skip to content
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

Mesh workflows #22

Open
kevinmershon opened this issue May 13, 2015 · 2 comments
Open

Mesh workflows #22

kevinmershon opened this issue May 13, 2015 · 2 comments
Assignees

Comments

@kevinmershon
Copy link
Member

  1. When selecting a transmitter using the select box, remove all nodes from the mesh display except the one selected and its immediate neighbors. Add a reset button to go back to viewing all nodes.
  2. When a node is selected, under View Detail add a table with the neighbor name and to/from signal strengths. Clicking on a node in this list should change the selection to that node and update the mesh display.
  3. Above the select box add a Search field that attempts to auto-complete case-insensitive matches to the entry text. Selecting one of the nodes should update the mesh display and neighbors table as described.

When updating the mesh display and table, be sure to reference back-mappings in populating the list of neighbors, because the Gateway itself does not list any neighbors (they list the Gateway, instead), but I should still be able to see all neighbors to the Gateway if I select it.

@darinh
Copy link

darinh commented May 14, 2015

@kevinmershon

  1. Do you have a way to determine battery power level %, and do you want to include that in the transmitter detail?
  2. On the Transmitter Detail View, do you want neighbor information and signal strengths listed as well?

@kevinmershon
Copy link
Member Author

@darinh

  1. Conventionally, QV is assigned to the transmitter's battery voltage (and users will know this), but that is not the case by default, and it doesn't indicate the real remaining life of the device. There is an API to read the battery life remaining in days, but it'll take some prototyping to figure out how to implement. It uses something called a wrapped request.
  2. I don't see a reason to congest the transmitter detail screen with that info.

@darinh darinh closed this as completed May 14, 2015
@darinh darinh reopened this May 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants