Currently bit access is done on the raw value, which is the system endian, which in practice means little-endian
This was surprising, as the default for integer retrieval is bigendian.
Also, the endian specification isn't applied for bit access. Which made me sad.
So I had to write this work around in my spreadsheet =if(or(isblank(D84),D84="N/A"),"",if(D84>7,D84-8,D84+8)) which was very sad.
modbus_exporter should support the endian parameter in the configuration. This should be applied before extracting the bit.
To avoid making sad people sadder, the default behaviour should remain system endian, this should be clearly documented as is diverges from the integer retrieval behaviour.
Currently bit access is done on the raw value, which is the system endian, which in practice means little-endian
This was surprising, as the default for integer retrieval is bigendian.
Also, the endian specification isn't applied for bit access. Which made me sad.
So I had to write this work around in my spreadsheet
=if(or(isblank(D84),D84="N/A"),"",if(D84>7,D84-8,D84+8))which was very sad.modbus_exporter should support the endian parameter in the configuration. This should be applied before extracting the bit.
To avoid making sad people sadder, the default behaviour should remain system endian, this should be clearly documented as is diverges from the integer retrieval behaviour.