Re: [weewx-user] is PCE-FWS 20N a re-badged fine offset device?

2022-07-12 Thread Rainer Lang 
This looks like a clone of the old Fine Offset WH1080 weather station 
which is no longer sold by Ecowitt due to old technology.
Console connectivity is USB only, no WiFi, no connection to the weather 
networks. No solar sensor either. (a solar panel for running the outdoor 
array, yes).
The outdoor array is likely to be not compatible to the modern WiFi 
consoles and gateways like GW1000/GW1100/GW2000 due to using a different 
modulation for the sensor signal transmission. This is also true vice 
versa - the WH1080 console cannot receive any of the modern 
FineOffset/Ecowitt sensors.


On 12.07.2022 18:57, Peter Wilkinson wrote:

Certainly looks like it might be but would appreciate confirmation.

Full skinny here:

https://www.pce-instruments.com/english/index.htm?id=google-uk&_artnr=5933243&_p=159.6&_pmode=0&_pbexkey=37&_date=20220711011313&_pbhash=3d8b84805bd95306b3a50a774dd67505122ac3489016cd2c6f36fdfad65bdb14&gclid=CjwKCAjwt7SWBhAnEiwAx8ZLatQOmma6jcmlAcX4VrmK6PGwtHcBqai4WNgA6a3U6YK5dAVj_OUZZBoCo5IQAvD_BwE
--
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/fa97e9d4-7f56-4b64-8f81-59ab915b0519n%40googlegroups.com 
.


--
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/b8403e7e-4d20-5d6d-6498-e06ac4d1c350%40gmail.com.

[weewx-user] is PCE-FWS 20N a re-badged fine offset device?

2022-07-12 Thread Peter Wilkinson 
Certainly looks like it might be but would appreciate confirmation.

Full skinny here:

https://www.pce-instruments.com/english/index.htm?id=google-uk&_artnr=5933243&_p=159.6&_pmode=0&_pbexkey=37&_date=20220711011313&_pbhash=3d8b84805bd95306b3a50a774dd67505122ac3489016cd2c6f36fdfad65bdb14&gclid=CjwKCAjwt7SWBhAnEiwAx8ZLatQOmma6jcmlAcX4VrmK6PGwtHcBqai4WNgA6a3U6YK5dAVj_OUZZBoCo5IQAvD_BwE

-- 
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/fa97e9d4-7f56-4b64-8f81-59ab915b0519n%40googlegroups.com.

Re: [weewx-user] howto fix weewx sqlite database

2022-07-12 Thread Oscar 
The database is corrupt.  Could be caused by a bad SD card, losing power 
during a write, a number of reasons.  I've been able to use this process to 
recover most of a corrupt data base.   With 5 years of data, the recreate 
process will take a long time (days(?)) on a pi.  I recommend coping the 
database to a faster machine to create the database, then copy it back to 
the pi.

# Dump the database as INSERT commands.  
sqlite3 weewx.sdb
.mode insert
.output dump_all.sql
.dump
.exit

# remove unwanted records from the dump file

cat dump_all.sql | grep -v TRANSACTION | grep -v ROLLBACK | grep -v COMMIT 
>dump_all_notrans.sql

# recreate the database using the insert statements.

sqlite3  new-weewx.sdb ".read dump_all_notrans.sql"

make a copy of your existing weewx.sdb file and  then copy new-weewx.sdb to 
weewx.sdb.  
 

On Monday, July 11, 2022 at 7:02:52 AM UTC-6 tke...@gmail.com wrote:

> It is very unlikely that the size of the database is a problem. Like 
> Graham, I have over 15 years of data on mine without a problem.
>
> You did not say what kind of storage you are using, but if it is an old SD 
> card, it is much more likely that the card is corrupt.
>
> You may be able to recover the database by using the utility sqlite3. 
>
> sqlite3 /home/weewx/archive/weewx.sdb
> sqlite> .recover
> sqlite> .quit
>
> However, usually this does not work, in which case you will have to 
> recover from a backup copy. Then, replace the card.
>
> -tk
>
>
> On Sun, Jul 10, 2022 at 10:27 AM Fische Namenlos  
> wrote:
>
>> here it is:
>> Sun Jul 10 19:25:39 2022 user.debug weewx[2812] DEBUG weewx.restx: Shut 
>> down StationRegistry thread.
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: Caught 
>> unrecoverable exception:
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   database disk image is malformed
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   Traceback (most recent call last):
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 214, in run
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   callback(event)
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 634, in check_loop
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   raise BreakLoop
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   weewx.engine.BreakLoop
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   During handling of the above exception, another exception occurred:
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   Traceback (most recent call last):
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewxd", line 153, in main
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   engine.run()
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 221, in run
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   callback(event)
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 644, in post_loop
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   self._software_catchup()
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 715, in 
>> _software_catchup
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   callback(event)
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>