Tamas BondarYes, that explains it. Thanks a lot!
Tamas BondarThanks Jason, it’s clear now. I think the logs will be more intuitive when this is fixed.
Tamas BondarThanks for the hint Jason, we will try moving the nodes farther away from the gateway. What I still don’t understand though, how can the same packet on a different channel decoded differently (i.e. frame counter beec010c instead of 00000366 in the example above)?
Tamas BondarThanks a lot Mike, I definitely will have more questions. I will ask them in a separate thread.
Tamas BondarThanks guys, this has been really helpful.
Mike, it makes sense now. It would be great to understand the details of all of the log messages. I guess, there’s no other way than reading the source code, is there? By the way, are the sources publicly available somewhere or it is a closed source product?
Jason, I think I should do a bit more reading about this. Could you recommend me something where these details are documented? Or is it just the source code again?
Many thanks,
-Tamás
Tamas BondarJeff, thanks for your response. So basically, it is not possible to fix it using the current pre-built image. That’s what I was afraid of.
As I’m not sure recompiling it from scratch would worth the hassle, I will just keep using v3.2.0 and wait for the next release, hoping this will be fixed. Any idea when it might come? Hopefully, not another year.
Thanks again!
Tamas BondarVersion 3.3.6 has this problem, v3.2.0 was fine.
Tamas BondarJosh, did you manage to sort out this Python issue?
I guess, the problem is that Python was compiled without SSL support. Any idea how to resolve this? Basically, I want python pip working.
