Tried reverting the driver but it seemed to be causing problems. I've given up and changed the config on my two sensors: sensor3 is now sensor4 and sensor2 is now sensor3. Everything seems to be working after the changes. I don't have a need for additional sensors so this will work.
On Saturday, December 17, 2016 at 7:37:26 AM UTC-8, [email protected] wrote: > > Trying this now... > > On Saturday, December 17, 2016 at 5:41:44 AM UTC-8, Tom Keffer wrote: >> >> Yes, I see the problem. The corrections are stored in a dictionary, which >> has an undefined ordering, so they do not necessarily get applied in the >> order they need to be. >> >> How about reverting to the older version of the driver >> <https://raw.githubusercontent.com/weewx/weewx/46e6867f12ef9a61930e82458e3d8856cff31d70/bin/weewx/drivers/wmr200.py> >> >> until Matthew finishes his more general sensor mapping plan? >> >> Just replace weewx/drivers/wmr200.py with the file. They are identical >> except for the sensor mapping. >> >> -tk >> >> >> >> On Fri, Dec 16, 2016 at 11:01 PM, <[email protected]> wrote: >> >>> Yes, what you have stated is my goal. However, I made the additions to >>> the weewx.conf file and restarted weewx, but it doesn't seem to have taken >>> effect. I'll reboot the system tomorrow and tinker with it some more. >>> >>> Thanks for your response. It has been very helpful. I wish I had found >>> out about the change before I updated. >>> >>> On Friday, December 16, 2016 at 5:09:24 PM UTC-8, Tom Keffer wrote: >>>> >>>> I'll try and be as explicit as possible. >>>> >>>> For the WMR200 sensor #2, your old driver emitted extraTemp2, and, I >>>> presume, it was recorded in your database as extraTemp2. >>>> >>>> The new driver will emit extraTemp1. If you do nothing, it will be >>>> recorded in the database as extraTemp1. >>>> >>>> My suggestion copies the data from extraTemp1 to extraTemp2, then sets >>>> extraTemp1 to null. This way, the data will be recorded in the database as >>>> extraTemp2, just as before. I assume this is what you want. >>>> >>>> -tk >>>> >>>> On Fri, Dec 16, 2016 at 4:59 PM, <[email protected]> wrote: >>>> >>>>> Trying to clarify this in my own mind... >>>>> >>>>> In the corrections you listed which items represent the data as >>>>> understood by the WMR200? I wan't extraTemp3 from the WMR200 to be >>>>> extraTemp3 for weewx. With the updated driver, as I understand it, >>>>> extraTemp3 is now read from the station as extraTemp2 (sensor number >>>>> minus >>>>> 1), yes? Is that what these "corrections" do? >>>>> >>>>> >>>>> On Friday, December 16, 2016 at 4:44:00 PM UTC-8, [email protected] >>>>> wrote: >>>>>> >>>>>> Has this been implemented? From the issue posting it seemed that >>>>>> this wasn't available yet. >>>>>> >>>>>> On Friday, December 16, 2016 at 4:37:17 PM UTC-8, Tom Keffer wrote: >>>>>>> >>>>>>> I realized my response does not help you very much. >>>>>>> >>>>>>> One thing you could do is remap them using the StdCalibrate facility: >>>>>>> >>>>>>> [StdCalibrate] >>>>>>> [[Corrections]] >>>>>>> extraTemp3 = extraTemp2 >>>>>>> extraTemp2 = extraTemp1 >>>>>>> extraTemp1 = None >>>>>>> >>>>>>> This would cause the value in extraTemp2 to appear as extraTemp3, >>>>>>> the value in extraTemp1 to appear as extraTemp2. I believe this is what >>>>>>> you >>>>>>> had before. >>>>>>> >>>>>>> I also know that Matthew is working on a more general mapping >>>>>>> facility, but it probably won't be available for a while. >>>>>>> >>>>>>> -tk >>>>>>> >>>>>>> On Fri, Dec 16, 2016 at 4:33 PM, Thomas Keffer <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Sorry, I did not see this message before replying to your other >>>>>>>> message. >>>>>>>> >>>>>>>> The sensor mappings were changed in v3.6.1 (released 10/13/2016). >>>>>>>> See issue #164 <https://github.com/weewx/weewx/issues/164>. >>>>>>>> >>>>>>>> -tk >>>>>>>> >>>>>>>> On Fri, Dec 16, 2016 at 4:24 PM, <[email protected]> wrote: >>>>>>>> >>>>>>>>> I just upgraded my weewx installation to version 3.6.2 from an >>>>>>>>> earlier version. I have two extra temperature/humidity sensors >>>>>>>>> attached to >>>>>>>>> my system as devices 2 and 3 on the console. They were reporting >>>>>>>>> properly >>>>>>>>> under the earlier version of weewx but now they are out of sequence. >>>>>>>>> It >>>>>>>>> seems device three is now recorded as device two and device two isn't >>>>>>>>> captured. >>>>>>>>> >>>>>>>>> I believe there was an update to the WMR200 driver that caused >>>>>>>>> this (from various postings I've found) but I can't find any >>>>>>>>> information on >>>>>>>>> how to fix the problem. I'm not really happy with the idea that I >>>>>>>>> should >>>>>>>>> reconfigure my sensors, but I suspect that might work. Any help >>>>>>>>> would be >>>>>>>>> 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 [email protected]. >>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- >>>>> 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]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> 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]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- 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]. For more options, visit https://groups.google.com/d/optout.
