Ooooohhhh... this is cool! I could always have weewx relay the info to Wunderground (send meteobridge to weewx via the listen driver, then have weewx send to wunderground). I'm not seeing a way to point meteobridge at a different IP, but it could be stashed away somewhere, or as stated, hijack the data via router or DNS.
Something to think about... I'm thinking another option would just be using Meteobridge's HTTP request to send to some php on the weewx server (I say php because I know it and don't know python) and have that write out to a file that just uses fileparse in weewx. That could easily run ever 5-10 seconds and would be quicker than doing a file upload that often. I need to actually start trying these things instead of just thinking about options... lol. I also need to see if I can get my data imported into weewx (or rather, I need to see if I can get my data OUT of Meteobridge). Worst case, I'll get it out of Meteotemplate. =) On Wednesday, May 6, 2020 at 8:06:15 AM UTC-7, mwall wrote: > > On Wednesday, May 6, 2020 at 10:46:21 AM UTC-4, Ryan Stasel wrote: >> >> >> Was curious if there was another way, where Meteobridge remained >> "authoritative" (so to speak) and just handed data to weewx. >> > > you could use the weewx-interceptor driver as device 'wuclient' in listen > mode, then point the meteobridge weather underground uploader to the > computer on which interceptor is running. > > meteobridge thinks it is uploading to wu, weewx thinks it is getting a > feed from a generic wuclient > > if you are already sending to wu and want to continue doing that, then use > sniff mode in interceptor > > m > -- 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/9a013f37-8398-4f8f-adda-8f776e1b3fba%40googlegroups.com.
