Thank you for the hint about importing from WU.
In the meantime, I managed to get the SDR dongle to download data from my
home station - a clone of Ambient Weather WS-1002. The tests went well, the
dongle captures packets, I mapped the sensors and compared the readings
from the interceptor controller and directly from the display.
Unfortunately, like many before me, I am having trouble determining the
insolation in W/m2.
When reading from rtl_433, I get this result (JSON format):
{ “time” : “2025-03-23 10:56:53”, “model” : “Fineoffset-WH24”, “id” : 100,
“battery_ok”. : 1, “temperature_C” : 8.500, “humidity” : 69, “wind_dir_deg”
: 100, “wind_avg_m_s” : 1.680, “wind_max_m_s” : 2.240, “rain_mm” : 792.300,
“uv” : 527, “uvi” : 1, “light_lux” : 16065.800, “mic” : “CRC”}
How to convert light_lux to W/m2 for this station?
EDIT: I have already concluded that you need to divide the value in lux by
126.7 to get the value in W/m2. I made the changes in the [StdCalibrate]
section:
[StdCalibrate].
[[Corrections]]
radiation = radiation / 126.7
How do I get Weewx to respect this correction?
I hope that if I was able to “get along” with my station using SDR, I will
repeat this success with Garni 1025.
niedziela, 23 marca 2025 o 10:09:27 UTC+1 Rainer Lang napisał(a):
> I suggest the wee_import approach earlier in the thread
> of course weewx won't do this by itself, the import needs to be triggered
> for such tasks you can create a CRON job - in Linux (derivate)
> installations usually the cronjob config file is /etc/crontab
> if you want to update weewx every five minutes, you have to initiate the
> download and import every five minutes
> for the import there should be an example file in the weewx file system
>
> for the wee_import itself see
> version 4
> https://weewx.com/docs/4.10/utilities.htm#wee_import_utility
> version 5
> https://weewx.com/docs/5.1/utilities/weectl-import-about/
>
> example for an import.conf file attached
>
> to avoid conflicts mentioned in the utilities guide, you better run your
> cronjob in the middle of your archiving interval e.g. not at the full five
> minutes (if that's your interval) but two or three minutes later to avoid
> conflicting access to the database - the same applies to the
> wee_database/weectl_database tool (wee_database --rebuild daily / weectl
> database rebuild-daily) you may want to run after each import to update
> your summary tables
>
>
> On 23.03.2025 08:10, 'Tomasz Lewicki' via weewx-user wrote:
>
> I don't know if this makes sense or not, I simply described my attempts.
> tcpdump is unlikely to lie. But fine. Let's assume I don't have the ability
> (or skill) to use the interceptor driver. Are there other options for
> getting data from the station?
>
> It seems to me that I have two ways - direct and indirect.
>
> 1. Direct
>
> I found information about the weewx-sdr controller. From the description
> it seems to me that it can help me in my situation. It works well, because
> I have an SDR dongle that I use to receive ADS-B signals.
>
> 2 Indirect
>
> Downloading the data sent by the station to the WU and uploading it to
> Weewx. I repeat the question from the previous message - does Weewx allow
> import on the fly from WU, or only from manually fed files?
>
> niedziela, 23 marca 2025 o 02:35:36 UTC+1 vince napisał(a):
>
>> Not sure your description makes much sense. There has to be some traffic
>> from the station to an ip off network. I’d expect ntp and dns traffic as
>> well.
>> On Saturday, March 22, 2025 at 12:48:59 PM UTC-7 Tomasz Lewicki wrote:
>>
>>> Today I had the opportunity to face the Garni 1025 station.
>>> Unfortunately, the issue is much more complex than it might seem at first.
>>> The universal driver “interceptor” is powerless in this case. The station
>>> communicates with the environment in a strange way. It turns out that the
>>> panel with the display does not connect directly to the local network as a
>>> device with an IP address in the range given by the DHCP server of the home
>>> router, but probably forms a kind of bridge between itself and the router.
>>>
>>> The way I came to this was that after connecting the Raspberry Pi with
>>> Weewx installed, I scanned the local network with my smartphone and found
>>> no device in it that could be a Garni panel. From the instructions, I
>>> learned that to configure the panel, you need to press the appropriate
>>> button on the case and enter AP mode. Then you can enter the default
>>> address 192.168.1.1 with a browser and there enter the SSID of your home
>>> network and the password for it. I managed to connect the laptop to the
>>> network created by the Garni panel and started sniffing on the network
>>> traffic. Unfortunately, tcpdump didn't show anything that would give any
>>> meaningful clues. The only packets were sent by the Garni panel to my
>>> laptop. I couldn't see any packets that Garni was routing to the router,
>>> yet it must be transmitting something if data is being sent to the WU,
>>> right?
>>>
>>> Do you see any way that I could still try?
>>>
>>> PS. Does Weewx allow you to import data from WU in "quasi real time"?
>>> What I mean is, can I download data from WU, for example, every 5-10
>>> minutes and feed it to Weewx so that it creates charts locally.
>>>
>>> niedziela, 16 marca 2025 o 10:02:32 UTC+1 Tomasz Lewicki napisał(a):
>>>
>>>> Thank you all for the helpful replies.
>>>>
>>>> As I said, the station is out of my reach so I hoped to prepare "dry
>>>> run" and set up Weewx in my home environment and then just connect in in
>>>> target network, changing only necassary things (WiFi network and so on).
>>>> If
>>>> it is not possible, I have to use tcpdump "in situ", where Garni works.
>>>> But
>>>> - replying to Reiner Lang's suggestion - Garni sends the data to WU
>>>> instantly; you can check it here ->
>>>> https://www.wunderground.com/dashboard/pws/IKOWAL30
>>>>
>>>> In the meantime I got a photo of manual page from the owner of the
>>>> station (Garni doesn't share the manuals on its website - it's strange)
>>>> and
>>>> then I was almost sure that Garni uses Weathercloud protocol because setup
>>>> allows setting my own server (if someone is curious, here is a photo ->
>>>> http://stalker.udl.pl/temp/garni1025.jpeg). So I looked into
>>>> Weathercloud website and can confirm that Garni 1025 uses Weathercloud
>>>> protocol -> https://weathercloud.net/en/compatible-devices List
>>>> contains plenty of manufacturers which I know. Rainer Lang hinted that
>>>> manufacturer is CCL (shame to say it but I did not know this company). I
>>>> found quite old "wcloud" driver from Matthew Wall (
>>>> https://github.com/matthewwall/weewx-wcloud) but if I understand it
>>>> good, it allows only for uploading the data from Weewx to Weathercloud
>>>> server, not downloading it from weather station.
>>>>
>>>> So maybe the clones which Weewx supports are using some "standard"
>>>> protocol (whatever means "standard" when talking about PWS) and I can use
>>>> some known driver here...?
>>>>
>>>> niedziela, 16 marca 2025 o 02:55:59 UTC+1 vince napisał(a):
>>>>
>>>>> Can you perhaps just listen for all tcp traffic and not specify the
>>>>> src address and see what is on your network ?
>>>>>
>>>>> I’d think you might try to listen for tcp src 192.168.0.0/24 dst not
>>>>> 192.168.0.0/24 and not specify any port.
>>>>>
>>>>> Or listen for all tcp traffic for at least 10 minutes and capture to a
>>>>> file, then transfer the pcap file back to your computer to analyze in the
>>>>> wireshark/ethereal gui later. If you could post a pcap file somewhere I’m
>>>>> sure folks will see if they can help determine the correct settings.
>>>>>
>>>>> On Saturday, March 15, 2025 at 6:15:42 PM UTC-7 matthew wall wrote:
>>>>>
>>>>>> tomasz,
>>>>>>
>>>>>> you are correct to first use tcpdump. once you see data using
>>>>>> tcpdump, then you can experiment with interceptor to get the data into
>>>>>> weewx. if the station can successfully post to wunderground, then the
>>>>>> interceptor *should* be able to capture the data. but you should first
>>>>>> use
>>>>>> tcpdump to figure out the settings necessary to capture data.
>>>>>>
>>>>>> is it possible to adjust the destination in the weather station? if
>>>>>> so, you could tell the station to send to the computer running weewx,
>>>>>> instead of wunderground. but still use the wunderground protocol.
>>>>>>
>>>>>> can you control the dns entries on the network? if so, make
>>>>>> weatherstation.wunderground.com resolve to the computer running
>>>>>> weewx, then run interceptor in listen mode. if you already run a web
>>>>>> server on port 80 then you would have to make interceptor listen on a
>>>>>> port
>>>>>> other than 80, then adjust the web server configuration to send traffic
>>>>>> for
>>>>>> /weatherstation/updateweatherstation.php to that port. or do it with
>>>>>> firewall rules.
>>>>>>
>>>>>> does your network switch support port mirroring? if so, mirror the
>>>>>> port that the weather station uses and make interceptor listen on the
>>>>>> mirrored port.
>>>>>>
>>>>>> or if the station is wifi, make interceptor listen on an interface
>>>>>> that can see the wifi traffic.
>>>>>>
>>>>>> but first use tcpdump in one of these configurations to ensure that
>>>>>> you can see the data from the station.
>>>>>>
>>>>>> m
>>>>>>
>>>>>> --
> 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/b9622ebb-15d9-43c8-96e5-083fce340079n%40googlegroups.com
>
> <https://groups.google.com/d/msgid/weewx-user/b9622ebb-15d9-43c8-96e5-083fce340079n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>
--
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/874f863a-9c6f-4d97-b3d9-b352991c240bn%40googlegroups.com.
