Glad it is working for you. That bit of code was last changed in November, 2014, so it's been that way for a very long time.
However, it should not be so strict on requiring that the first column be dateTime. I've filed an issue to remind myself to relax the restriction. Issue #855 <https://github.com/weewx/weewx/issues/855>. On Sat, Mar 11, 2023 at 1:58 AM Blaise Cacramp <blaise.cacr...@gmail.com> wrote: > As in fact, Tom, the Datetime field was no longer in 1st position. > > I placed it properly while keeping the additional field in 2nd position > and it still did not work, even by placing it in the last position. > > I have resolved it to delete it and it seems to leave, in any case, no > error message. > However, he no longer read the new data ... > > I did a wee_device --dump and (no clear memory) and there, everything > seems to work. > Probably your latest version is strict, because it worked before and for > quite a long time. > > I would put this field in a separate and linked table > > Thank you Tom > Le 10-03-23 à 19:08, Tom Keffer a écrit : > > I have no idea what I'm looking at there. > > The requirements for the database are: > > 1. The first column must be dateTime. > 2. The value for dateTime must never be null. > > Does your database satisfy these two requirements? > > -- 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/CAPq0zEDZvCXBdt2uGR0mPoCaM3XQMU9K3OKeHSPcUoKhLL3%3DCA%40mail.gmail.com.
