I’m not seeing how this issue can solely be a sensor map issue. The sensor map (whether it be default or custom) is applied in the driver and the driver delivers mapped data to (the rest of WeeWX). We’ve only seen one small syslog extract and it appears to me that the ‘tower’ is attempting to post to WU using RF. Are you having WeeWX post to WU as well? If both the tower and WeeWX are posting to WU that could certainly explain odd behaviour being seen on WU. More so if you add RF into the mix.
Maybe a full wee_debug report and a startup syslog extract might help. Gary -- 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/523b1908-3719-44ac-aaa0-4ff98b0cf609%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
