The reason I map things to existing fields is that it's upgrade proof. If you extend the db then you need to remember to do that if you rebuild your system from scratch. Same reason I do the edits in weewx.conf rather than skin.conf for the skin. It keeps the skin upgrade proof.
On Wednesday, June 21, 2023 at 2:57:41 PM UTC-7 gjr80 wrote: > Or you can modify your database with wee_database and add fields > wh31_ch1_batt, wh31_ch2_batt etc to the database schema. Utilising the > existing batteryStatus1, batteryStatus2 fields is arguably simpler and > quicker to implement, adding fields to the database arguably provide self > evident names to the database fields and only involves use of wee_database > and no modification of the field map. > > At the end of the day if you want plots of battery state values you need > to have the battery state data appear in loop packet fields that exist in > the database - how you do that is a matter of personal preference (if you > just want to display the current value there is no need to change the > database or the field map just the skin config). > > Gary > > On Wednesday, 21 June 2023 at 22:05:18 UTC+1 vince wrote: > > This is my 'example' - I have a WH26 outside sensor, four WH31 inside > sensors on channels 1-4, and one WH51 soil moisture sensor so I mapped them > as follows to match my hardware. You'd need to do something similar for > your sensors. > > [GW1000] > [[field_map_extensions]] > outTempBatteryStatus = wh26_batt > batteryStatus1 = wh31_ch1_batt > batteryStatus2 = wh31_ch2_batt > batteryStatus3 = wh31_ch3_batt > batteryStatus4 = wh31_ch4_batt > batteryStatus8 = wh51_ch1_batt > > > -- 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/b4d2dbb7-0915-4457-a4a3-34d5011a1a90n%40googlegroups.com.
