As a client developer, I do wish a lot of the important values & variable names were standardized and made available in the developer docs. I was unaware of the docs/new-drivers.txt file so I'll give that a look.
I've been dealing with quite a few edge cases of OEMs taking creative liberties with their server and driver distributions. Synology is a common offender with undocumented behavior in their NUT server, the ECO status popped up too as mentioned, and there's also handling several different load calculations from the UPS drivers, to name a few of my experiences so far. I understand that not all OEMs can be expected to implement every possible point of measurement and functionality in their hardware/software, but if we can start to move towards some basic standards (and have this thoroughly documented), I'd be a happy camper. Thanks for gathering our feedback Jim, I hope this was helpful in some way. Let me know if you want this crossposted to the issue on GH. Glen
_______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
