Nuno Tavares

@SuperQ : cleaned it up.

ping @SuperQ

It's been a while, I've rebased against latest master.

I really appreciated this thread. I'm just thinking... wouldn't it make more sense to just export the value, instead of trying to translate it in the code? Or maybe not...

Yes, I'm definitely convinced the first compromise should be in. We can leave a remark in the code about the uncertainty of the "BBU Status" value, and point it to...

Actually, if you don't mind, I'd change my PR a bit this way: * Remove any parsing from Cachevault_Info in handle_megaraid_controller; because of the detailed metrics, I'll have to iterate...

Hi @dswarbrick thanks for sharing! The refered issues are very enlightening in regards to reverse-engineering the BBU Status :-) Indeed I couldn't get feedback from the vendor either but, there...

Refactor a bit based on the discussing in #27: * cv_temperature and battery_backup_healthy now come from the dedicated CV/BBU parser loops, instead of the "/call show all" (handle_megaraid_controller) parser; *...

Hi @candlerb, thanks for taking the time to go through this. > It means we probably know more about the BBU than the adapter itself! I don't see a problem...

Hi @infrastation! 0.22.0 is out, any chance to merge this?