Nevermind, found it, thx. http://www.weewx.com/docs/customizing.htm#Adding_2nd_source
Am Montag, 4. Februar 2019 16:05:51 UTC+1 schrieb Michi Kaa: > > I think I've understood the point of your posting but stll need a little > bit of an input, since I don't really understand what a REC event is, how > to configure one an how to bind it. Is this all pointed out in the > user/customisation guide? Where can I find further explanation? > > Am Montag, 4. Februar 2019 15:22:24 UTC+1 schrieb Andrew Milner: >> >> You could have your task create a text file and have a service that binds >> to a REC event, reads the text file and adds the radiation to the archive >> record. Weewx would then take care of the daily stats in >> archive_day_radiation for you. >> Alternatively your service could still bind to the REC, but instead of >> reading the text file it could retrieve via the API the current radiation >> value and thus do away with the cron task altogether. >> >> >> >> On Monday, 4 February 2019 13:27:27 UTC+2, Michi Kaa wrote: >>> >>> Hi, >>> >>> I run weewx on a raspberryPi with a WS28xx station. I also have a 3kW >>> peak solar panel on the roof of my house. The solar power inverter logs a >>> lot of data which can be read over a JSON API. So what I am doing right now >>> is running a cron job every 5min that looks into the weewx database for >>> archive entries without a radiation value, then asks the inverter for the >>> values for that particular time window and stores it into weewx database >>> and calculate archive_day_radiation also (is this calculation needed or is >>> it made automatically, when "radiation" column in "archive" table has >>> values?). >>> >>> This works. But is there an "official" way to do things like that? >>> >>> >>> -- 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.
