Closed brotherdust closed 4 years ago
Ok. I think I have an idea why this is happening, either: a) my meter(s) don't output some of the expected fields b) the decoder isn't decoding the fields and/or outputting them
As I'm not a Go developer, I have no idea how to make these fields optional. I guess it's time to learn Go! ha.
The version of rtlamr you are using is not compatible with rtlamr-collect, the output is missing the Type
field.
The version of rtlamr you are using is not compatible with rtlamr-collect, the output is missing the
Type
field.
Oh. I just pulled from master. What version should I be using?
It would seem that rtlamr
should be outputting the Type
field:
https://github.com/bemasher/rtlamr/blob/22749a729e9dfb82be1016d2454026ca74126480/main.go#L249
Yeah nevermind. I was telling nix
to build from an old tag, not master. Serves me right. Thanks!
I found the issue. I had made a new tag including the commits necessary for compatibility with this version of rtlamr-collect, but had not pushed it to the repository, new clones should behave as intended.
Hi! Thanks for making this great software!
I've run into a bit of a problem... when I run
rtlamr-collect
, I get the messagemain.go:427: json unmarshal: json: Unmarshal(nil)
. I've verified thatrtlamr
is outputting valid JSON:Any ideas why unmarshaling is returning nil?
Thanks much!