duke wrote:Steve, other than the tags you mentioned in the release:
I notice the Davis specific tags are not currently populated:
<#DavisFirmwareVersion>, <#DavisMaxInARow>, <#DavisNumberOfResynchs>, <#DavisNumCRCerrors> , <#DavisTotalPacketsMissed> and <#DavisTotalPacketsReceived>
Purely as a comment, I really wonder how useful those stats are. If it's no big deal to implement then I guess no harm done but personally I wouldn't have given them much priority. Three points perhaps:
1. For assessing reception quality then all I tend to use personally are % good packets received in a defined interval (eg a value updated every 10 or 60 minutes perhaps) and RSSI, though the latter isn't currently available via the standard interface, as far as I remember. But although these two parameters are all I'd tend to look at, I'd really want them on a per-transmitter basis.
2. In part, how useful the stats are does depend on how keen you are to cater for Envoy users (probably a fairly small minority of the total for Davis users - 10-20%??). Otherwise, the detailed stats - for anyone who does wish to view them - are obviously available from the wireless diagnostic screens on the standard console, which is simple enough to access (though the stats are not logged at all, meaning you can't easily look back at past hours and days).
3. The ISS can transmit additional data like supercap voltage (for recent ISS units at least), but which isn't currently available via the API. However this might conceivably be made available in future revisions to the API, eg either by utilising some of the unused fields in LOOP2 or maybe by introducing a LOOP3 record. This is nothing more than speculation on my part but just to make the point that it could be useful in principle to have a mechanism to pick up and store additional 'performance' stats, which might well be more useful than eg <#DavisMaxInARow>.