[Nut-upsdev] apcsmart and #311678 feature request thoughts

Michal Soltys soltys at ziu.info
Tue Oct 23 21:20:52 UTC 2012


https://alioth.debian.org/tracker/?func=detail&atid=411544&aid=311678&group_id=30602

I wanted to do it somewhat more flexibly/elegantly, so this is what I've 
been thinking about (or rather sitting on mostly implemented piece, 
still needing some testing though):

- any variable that may include multiple data, would be (during runtime) 
split into appropriate *.N.* sets; for example instead of adding 'T' as 
ambient.1.temperature - which is in practice two (or possibly more 
depending on model ?) values - it would be split and added as 
ambient.1.temperature and ambient.2.temperature - in addition to already 
existing 't' as ambient.temperature

- additionally - any enumerable/writable value will also have *.0.* 
variant added, which must be used for the control. This one is always 
added verbatim - no nut <-> apc conversions, but this is in practice not 
a problem as all the interesting stuff in this context is defacto added 
without any conversions.

Is this reasonable approach ?




More information about the Nut-upsdev mailing list