[Feature Suggection] Display last sensor value on sensors page.

[BogusException]

Disclaimer: Everything is so great, I feel this will sound like I'm trying to find something for improvement, but it is from a month of pretty involved use.

Issue

User has to dive deep into each sensor's detail to see that sensor's last value. There is no way to view the last value the sensor received on the pages that the user is already searching for sensor/node status. The option to create a dashboard for all sensors is impractical, plus doesn't compensate for newly added/dropped sensors.

Desired

A way to see all the sensor values last stored, but in a way that all the sensors can be evaluated for errors/disconnectivitiness(?!), comparison with other similar sensors without needing to create/modify a dashboard, and have that display cleanly illustrate the status of the node (red) in case of timeout or other failure (similar to the way the Resources -> Gateways and Resources -> Nodes pages do with their Status column, maybe?).

Suggestion

• [ ] Reflect the status of a sensor in the Sensor detail page somehow (color=red?). Since we can't select columns, perhaps instead of adding two columns, just add one for the last collected value of that sensor, and color either that value or another column's value red to indicate the individual sensor is suspect or Bad(TM).
• [ ] I know this is extra, but what about the GUI indicating the same thing (value & status) in the Topology screens? Like the above, this is already done with the Gateway & Node representations, but why not allow (either with Display names or an additional checkbox) the display of the sensor values?

Thank you so much for not thinking these are too nit-picky, or that I believe them to be urgent. As a developer, I realize that it isn't always possible to see the sw as others do, and a smart group like this to help you develop truly useful software is a rare pleasure. There are areas of the sw that I just haven't had the time/need to explore, but look very interesting, like templates, scripts and variables, so i f you think I should be QA'ing or tire-kicking elsewhere, please holler!

pat :)