After a quick private discussion about rtl_433: The basic issue is probably that rtl_433 simply decodes the fields as transmitted from the 6045M. It does not maintain state; this is a core rtl_433 principle.
Therefore, some code has to take the messages and accumulate strikes, when the count goes up, and basically report a "n strikes happened, last one's distance is X" when the count changes. This code has to deal with wrapping. The 6045M messsages will have a distance field that stays the same until the next strike. In doing all of this, keep in mind that the 6045M might be power cycled. So perhaps the SDR driver needs some attention in this area. It's almost certainly going to take someone who can read/debug/fix the code to improve it. My advice to look at the rtl_433 output stands; if you find problems there or have better codepoint/distance information, it's most welcome on the rtl_433 list. Greg -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/rmi8skjsgwk.fsf%40s1.lexort.com.
