Hi! Now I've got the database correct. Added two new observations in weewx.sdb, lightning_strike and avg_distance. Removes my "data_binding = wx_binding" in [AS3935] also. And modified schema. Followed the weewx documantations.
When I use $day.avg_distance.last in my htmlpage I see the values from my database, but I can't sort this new issue out! Spent hours trying to get it right but, no.... First I want to get the readings in Metric. No matter what I change in skin.conf the values don't show up in Metric on my page... Second, The values have lots of decimals, and maybe that changes when I get the readings in Metric, but the lightning_strikes count shows like for example 35.000000 on my page when it would look much better with just 35. But also this I can't find any solution for....brain overheated now. So a few steps forward but then this happens :) Hope for some help here! Thanks, Mikael Den onsdag 10 juli 2019 kl. 12:35:44 UTC+2 skrev gjr80: > > The issue is indeed to do with missing field ‘interval’. Some background. > The AS3935 service was written back around 2015 when WeeWX was somewhat > more tolerant of the the existence or otherwise of field ‘interval’. Move > forward to WeeWX v3.7.0 and later and WeeWX is much more stringent in > insisting that databases managed by the WeeWX API contain interval data. > > The AS3935 service has the ability to store individual lightning strike > data in a separate database (this is done by setting the config option > ‘data_binding’ in the [AS3935] stanza in weewx.conf, if the ‘data_binding’ > option is omitted or set to None saving of lightning data to an external > database is disabled). In this mode the AS3935 service attempts to save a > record that does not contain the field ‘interval’ to the database specified > by the ‘data_binding’ config option. The WeeWX API rejects this and thus > the error you are seeing. The fix for this issue will require modification > of the AS3935 service to add an ‘interval’ field to the record being saved > to the external database or for the data to be saved to an external > database using other than the WeeWX API. > > The AS3935 service also adds fields ‘avg_distance’ and ‘lightning_strikes’ > to loop packets and archive records (whether this extra data is saved to > the WeeWX archive depends on whether the user has modified the schema for > the WeeWX archive or not). This occurs independently of lightning strike > data being saved to an external database. Folks who are using the AS3935 > service without issue almost certainly do not save individual lightning > strike data to an external database, ie they have not set the > ‘data_binding’ config option under [AS3935]. > > So to a solution, I guess it is hope that Matthew or some other kind > person will update the AS3935 service to operate properly with the WeeWX > API. In the interim the AS3935 service can be used by removing/disabling > ‘data_binding’ config option and making use of the average distance and > lightning strike data being added to loop packets and archive records > (remembering whether this extra data is saved to the WeeWX archive depends > on whether the user has modified the schema for the WeeWX archive or not). > > 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/fbf4125d-34ef-46a3-9490-575de003db6b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
