Thanks to all of you, I solved it. It appears that in the most current version of the weewx-sdr code, the 6045M is NOT a recognized model. After rerunning find with better search parameters, I found it where it belonged in /usr/share/weewx/user/. Thanks to Andy and his upload of his version of sdr.py, I replaced the version that came with the most recent code on github with Andy's version and it was immediately recognized. It also is using a wild card at this point, but I"m going to edit weewx.conf and try 0009 as the identifier. All I have added now is the temperature reading, but I will be adding lightning readings tomorrow. Thanks again, and I"m going to raise an issue on the github page for weewx-sdr.
Nick Kavanagh On Wed, Feb 10, 2021 at 8:54 PM Mks Mk <mksm1...@gmail.com> wrote: > > try the following > install sdr and follow instructions > https://github.com/matthewwall/weewx-sdr > -update rtl_433 to latest > -edit the sdr.py file and make sure the identifier is "Acurite-6045M" > -add this to sensor map in weewx.conf file > > [[sensor_map]] > extraTemp2 = temperature.0009.AcuriteLightningPacket > On Thursday, February 11, 2021 at 4:46:11 AM UTC+3 kavanag...@gmail.com > wrote: > >> I also ran a find on my system to locate sdr.py and see if there was some >> way to convince it to recognize the 6045M. It appears that I don't have >> this file. I've downloaded it, but I'm unsure where to place it and cause >> it to be run when required. >> >> On Wednesday, February 10, 2021 at 8:23:31 PM UTC-5 Nick Kavanagh wrote: >> >>> I attempted the wildcard with several variatons on the packet name, with >>> no joy. However, with debug set to 1, and log_unknown and _unmapped_sensors >>> true, I am getting two lines in the log: >>> >>> eb 10 19:57:39 weewxserver weewx[31499] DEBUG user.sdr: parse_json: >>> unknown model Acurite-6045M >>> Feb 10 19:57:39 weewxserver weewx[31499] DEBUG user.sdr: punt >>> unrecognized line '{"time" : "2021-02-11 00:57:36", "model" : >>> "Acurite-6045M", "id" : 9, "channel" : "C", "battery_ok" : 1, >>> "temperature_F" : 55.200, "humidity" : 62, "strike_count" : 88, >>> "storm_dist" : 20, "active" : 1, "rfi" : 0, "exception" : 0, "raw_msg" : >>> "00096fbecff0ac14b5"}#012' >>> >>> what I'm confused by is that it is indicating the Acurite-6045M is an >>> unknown model. I see from one of the answers above that, at least in that >>> person's system, it is recognized. Could this be a bug in the latest >>> release of the sdr driver software? >>> >>> Nick Kavanagh >>> >>> On Wednesday, February 10, 2021 at 3:58:34 PM UTC-5 >>> weatherl...@gmail.com wrote: >>> >>>> Try using a wildcard: >>>> >>>> temperature.0009.Acurite6045M >>>> temperature.*.Acurite6045M >>>> >>>> On 10 Feb, 2021, at 12:03, Nick Kavanagh <kavanag...@gmail.com> wrote: >>>> >>>> That is not working. It seems like the problem is the id number of the >>>> sensor. The Id is "9". Converting to hexadecimal, the number is....9. Or >>>> with twos complement 0009. I have tried using both of these in the stanza >>>> as >>>> temperature.9.AcuriteLightningPacket >>>> & >>>> temperature.0009.AcuriteLightningPacket >>>> >>>> Neither have worked. Any suggestions on what that center portion of the >>>> stanza should actually be? >>>> >>>> Nick Kavanagh >>>> >>>> On Tuesday, February 9, 2021 at 9:31:35 AM UTC-5 Andy wrote: >>>> >>>>> out: '{"time" : "2021-02-09 14:22:41", "model" : "Acurite-6045M", "id" >>>>> : 15431, "channel" : "A", "battery_ok" : 1, "temperature_F" : 53.200, >>>>> "humidity" : 78, "strike_count" : 174, "storm_dist" : 24, "active" : 0, >>>>> "rfi" : 1, "exception" : 0, "raw_msg" : "fc476f4e0f5cd7b8fa"}\n' >>>>> >>>>> parsed: {'dateTime': 1612880561, 'usUnits': 1, >>>>> 'channel.3C47.AcuriteLightningPacket': 'A', >>>>> 'temperature.3C47.AcuriteLightningPacket': 53.2, >>>>> 'battery.3C47.AcuriteLightningPacket': 0, >>>>> 'humidity.3C47.AcuriteLightningPacket': 78, >>>>> 'active.3C47.AcuriteLightningPacket': 0, >>>>> 'rfi.3C47.AcuriteLightningPacket': >>>>> 1, 'exception.3C47.AcuriteLightningPacket': 0, >>>>> 'strikes_total.3C47.AcuriteLightningPacket': 174, >>>>> 'distance.3C47.AcuriteLightningPacket': 24} >>>>> >>>>> Try this one. >>>>> >>>>> Andy >>>>> >>>>> >>>>> >>>>> >>>>> On Monday, February 8, 2021 at 5:41:14 AM UTC-8 kavanag...@gmail.com >>>>> wrote: >>>>> >>>>>> >>>>>> I am running the most current versions of weewx, rtl-sdr, rtl_433, >>>>>> and Belchertown. I am attempting to add the temperature parameter from >>>>>> the >>>>>> 6045M to the sensor map as extraTemp2. When I run >>>>>> <c>sudo PYTHONPATH=/usr/share/weewx python >>>>>> /usr/share/weewx/user/sdr.py --cmd="rtl_433 -M utc -F json"</c> >>>>>> >>>>>> I get this as output for the 6045M: >>>>>> out:[u'{"time" : "2021-02-08 13:34:08", "model" : "Acurite-6045M", >>>>>> "id" : 9, "channel" : "A", "battery_ok" : 1, "temperature_F" : 28.900, >>>>>> "humidity" : 70, "strike_count" : 58, "storm_dist" : 12, "active" : 0, >>>>>> "rfi" : 0, "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', >>>>>> u'{"time" >>>>>> : "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : >>>>>> "A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" : 70, >>>>>> "strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, >>>>>> "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n', u'{"time" : >>>>>> "2021-02-08 13:34:08", "model" : "Acurite-6045M", "id" : 9, "channel" : >>>>>> "A", "battery_ok" : 1, "temperature_F" : 28.900, "humidity" : 70, >>>>>> "strike_count" : 58, "storm_dist" : 12, "active" : 0, "rfi" : 0, >>>>>> "exception" : 0, "raw_msg" : "c0096fc68d691d0c1d"}\n' >>>>>> >>>>>> There is no parsed output. >>>>>> >>>>>> My question is: What do I add in my sensor map as the stanza for >>>>>> temperature_F to be mapped to extraTemp2? >>>>>> So far I have attempted multiple versions including: >>>>>> temperature.0009.Acurite6045M >>>>>> temperature_F.0009.Acurite6045M >>>>>> both again as Acurite6045MV2 >>>>>> >>>>>> both again as AcuriteLightningPacket >>>>>> >>>>>> both again as AcuriteLightningPacketV2 >>>>>> >>>>>> as well as several other variations. >>>>>> >>>>>> Does anyone know how to identify the packet from the 6045M? >>>>>> >>>>>> Thank you, >>>>>> Nick Kavanagh >>>>>> stonecressweather(dot)ddns(dot)net >>>>>> >>>>>> (Apologies if this question was not well asked. Any tips on improving >>>>>> the question are greatly appreciated.) >>>>>> >>>>>> >>>>>> >>>> -- >>>> 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 weewx-user+...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/f058e40b-ace0-4ddf-8ef2-1eea1d69b911n%40googlegroups.com >>>> <https://groups.google.com/d/msgid/weewx-user/f058e40b-ace0-4ddf-8ef2-1eea1d69b911n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> >>>> -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/whcxVNC1XLg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > weewx-user+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/c4e3e82f-14c5-41dd-b505-17ae01a347ecn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-user/c4e3e82f-14c5-41dd-b505-17ae01a347ecn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CABp3gvsfXfFsWV_K5L8J2TVh7WptdGU0-gF7wFQSrzJ0jpYdqA%40mail.gmail.com.
