This is required as the first 2 bytes are ignored. It becomes obvious that the 8 byte implementation in #39 has its drawback. While it can serialize/inserialize without loss of the first word, clients using it need to adjust semantics.
To avoid client-side interpretation of the sunspec spec #41 helps to lessen the pain.
For time being this corrects the change but we may need to revisit the design decision.
This is required as the first 2 bytes are ignored. It becomes obvious that the 8 byte implementation in #39 has its drawback. While it can serialize/inserialize without loss of the first word, clients using it need to adjust semantics.
To avoid client-side interpretation of the sunspec spec #41 helps to lessen the pain.
For time being this corrects the change but we may need to revisit the design decision.