Well, there are some problems, when going into the database: My Weewx runs
on a headless Raspi4, thus needing cli based interactions. I could stop
Weewx, copy the database file to a Desktop PC, where Heidi (or a similar
SQL editor) is installed. And there I should find the data, which were
introduced during the short time, when the simulator driver had been
running. Then I should delete all data from this time segment, save the
database file, and copy it back to the original place. Then, I could start
Weewx again. I also could edit the database directly, using sqlite3, but my
skills for entering the correct syntax are underdevelopped. I do not even
know the structure of the database, containing archive data to search for.
So, it was much easier, and less dangerous for makeing mistakes, to edit
this part in skin.conf:
[DisplayOptions]
sensor_connections = NoSensors # original list
sensor_batteries = hailBatteryStatus, txBatteryStatus, batteryStatus1 #
remains of original list
sensor_voltages = NoVoltage # original list
Just take care of the commas.
That‘s it!
Conz schrieb am Samstag, 21. Februar 2026 um 01:51:58 UTC+1:
> If the sqlite database is anything like the mysql database you can just
> open the file in something like 'HeidiSQL'
> I only just installed weewx and my data is in mysql but it just puts
> everything in the archive table.
> Just be sure to stop the service, make a backup of the sqlite file, edit
> the db and start it back up.
>
> Op vrijdag 13 februari 2026 om 16:49:09 UTC+1 schreef Vetti52:
>
>> Just to inform others, that have read my question, but had no answer yet:
>> There would be a sophisticated way to delete the simulator data from the
>> database. But the - at least for me - most conveniant way was to edit
>> skin.conf. It is pretty simple to comment out those sensors, which had been
>> filled with simulator data. And more over, I did not even need to restart
>> weewx. In case, I will use one or more of these sensors in future, I can
>> simply put them back to the sensors list.
>>
>> Thats it!
>> Peter
>>
>> Vetti52 schrieb am Mittwoch, 11. Februar 2026 um 11:20:18 UTC+1:
>>
>>> Well, to make a long story (a couple of days) short: After upgrading my
>>> Raspi to Raspian Trixie, i first stayed with Weewx 5.1, until I got it
>>> running properly, as all to be done, I read the hints in the weewx wiki -
>>> afterwards… Then I wanted to update to version 5.2 in the regular way.
>>> After updating, I played back the backup for the weewx database and started
>>> the new 5.2 version. However, it had changed unexpectedly the driver from
>>> my old gw1000 to simulator. I immediately stopped weewx, replaced the
>>> weewx.conf with the previous 5.1 version and established the only obvious
>>> diff entry, for the new version. Then restarted. Everything looked fine, as
>>> there were no obvious data from the simulator existent.
>>> No, after a few days I checked the entries in the seasons skin and
>>> detected additional sensor entries with no data, such as signal quality and
>>> some others. These entries seem not to disappear, when no data come in.
>>> It is just cosmetic, but what would be the best way to clean up the
>>> presentation in the skin? I could, as in former days, explicitely enter
>>> only those sensors in the skin, which I have. Or, is there an easy way to
>>> delete the dummy simulator entries from the database and leave the more
>>> sophisticated skin as is?
>>>
>>> Sorry for bothering you, because I was too lazy while upgrading.
>>> Any ideas are welcome
>>> Peter
>>>
>>>
--
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 visit
https://groups.google.com/d/msgid/weewx-user/65abbe2e-ccb0-4ec0-944d-702126324061n%40googlegroups.com.
