I just posted a request for help on the weewx-sdr github issues tab.
I demonstrated weewx-sdr working by calling 
'/home/weewx/bin/user/sdr.py' and showing the valid weather station output.
I asked them to look over my weewx.conf file for corrections.

For my own information, I just ran wee_debug and it confirms the database 
is empty.

System info
  Platform:       Linux-5.8.0-50-generic-x86_64-with-glibc2.32
  Python Version: 3.8.6

Load Information
  1 minute load average:  0.00
  5 minute load average:  0.07
  15 minute load average: 0.11

General Weewx info
  Weewx version 4.5.1 detected.

Station info
  Station type: SDR
  Driver:       user.sdr

Driver info

Currently installed extensions
Extension Name    Version   Description
sdr               0.78      Capture data from rtl_433

Archive info
  Database name:        weewx.sdb
  Table name:           archive
  Version               4.0
  Unit system:          None (Unknown unit constant)
  First good timestamp: ******* N/A *******     (    N/A   )
  Last good timestamp:  ******* N/A *******     (    N/A   )
  Number of records:    None (no archive records found)
                        It is likely that the database (weewx.sdb) archive 
table (archive)
                        exists but contains no data.
  weewx (weewx.conf) is set to use an archive interval of 300 seconds.
  The station hardware was not interrogated in determining archive interval.

Databases configured in weewx.conf
  Database name:        weewx.sdb
  Database driver:      weedb.sqlite

  Database name:        weewx
  Database driver:      weedb.mysql
  Database host:        localhost


Parsed and obfuscated weewx.conf

On Tuesday, April 27, 2021 at 11:40:49 AM UTC-5 vince wrote:

> On Tuesday, April 27, 2021 at 9:07:47 AM UTC-7 [email protected] wrote:
>
>> This is difficult to troubleshoot with the system functionality spread 
>> across multiple groups of developers!
>>
>>
> Eric - you are trying to do something relatively difficult.  The SDR stuff 
> is a bit complex.  You using a newer os means you got forced from dpkg to 
> setup.py which ups the ante on the difficulty side a bit.  Once you reached 
> the point where you had to compile anything, it's now in the 'this is gonna 
> be tough' level of effort.
>
> This thread points out why I want to add to that evolving weewx FAQ that I 
> mentioned in another thread.  It points out multiple questions on the to-do 
> list there:
>
>    - how to ask for help
>    - what data to provide and how
>    - should I use setup.py or packaged install
>    - where are my logs
>    - why didn't I get the web pages I expected
>    
>  The main issue here which I speculated last night, and as Gary agreed, is 
> that first you need the driver to get the data into the database.  Take a 
> breath and baseline your system to a known state.  Change one thing at a 
> time.  Go slowly.  It'll get there.
>
>

-- 
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 on the web visit 
https://groups.google.com/d/msgid/weewx-user/fd113075-f269-4a52-a1d9-f335cee8daa9n%40googlegroups.com.

Reply via email to