[email protected] schrieb am Montag, 26. Dezember 2022 um 13:41:28 UTC+1:
> I am not familiar with the skins you are using, but why store beaufort in > the database? Starting with V4.2, WeeWX treats it as just another unit, > albeit a funny one. You need only override the units. > > For example, you can say: > > <p>The wind speed is $current.windSpeed.knot, or > $current.windSpeed.beaufort on the beaufort scale.</p> > > That will give you something like: > > The wind speed is 8.3 kn, or 3 on the beaufort scale. > Hi Tom, thanks for your reply, but as I wrote im my origin post I cannot use a version above 3.9.1 because I don't get appTemp in the never version. I've tried all available rpm's for CentOS/RH but no one works for me, there is no appTemp stored in my db :( The next point is: Looking in the specifications book my wife gave me I have to use an analog display permanently actualised (SteelSeries) for wind in Beaufort and show the historical data in m/s in graphs. This is very nice because you can see actual wind changes in bft. on a clock instrument with movies fingers and the real max/min values on a graph. (That is useful because the bft.-scale ends with 12 but the wind may be faster than 34.x m/s). So I thought to work with a calculated column or a wiew - there is no permanent saving of the bft value, it is just a value given on request. Does weewx work with MySQL 5.7 with a calculated colum in table archive? Using MySQL would be a possibility but for the use with weewx ist's a little bit oversized - usually sqlite would be enough... So: next idea, please ;) Best regards Max -- 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/d112b8b3-f14f-40b4-b97b-4c9385e1642en%40googlegroups.com.
