Are you opening a local copy of a remote database file, an copy it back to
the origin, after storing? I did this a lot over the years, using WinSCP
and DB Browser for SQLite on Windows, editing a remote database on a
Raspberry Pi. I also encountered this message, although I managed to do the
When I edit the weewx database with the DB Browser for SQLite and finally
click on Write change, I sometimes get the message that the write operation
is blocked because the database is busy elsewhere.
Therefore I imagine that copying is not possible as long as weewx is
writing data to the DB,
I don't think it has changed ... why would it ?
It's a reasonable approach for how and when to copy an active database.
That's independent of the weewx version.
Safest way is always to shutdown weewx (best immediately after the last
archive records were written), then copy, then restart weewx
Are the instructions from the user's guide still up to date?
"Do not make the copy of the SQLite database while in the middle of a
transaction! Schedule the backup for immediately after an archive record is
written, and then make sure the backup completes before the next archive
record arrives.
