Just to follow up.
Were you able to find the fileparser driver from the info I sent you?
And I saw that they also recommended studying the simulation driver, too.
I hope my email doesn't goof up again, and loose some bookmarked
messages, so I just wanted to check in. Dale
--
You
The|fileparse|driver is perhaps the simplest example of a WeeWX driver.
It reads name-value pairs from a file and uses the values as sensor
'readings'. The code is actually packaged as an extension, located
in|examples/fileparse|, making it a good example of not only writing a
device driver,
Dale,
Can you let me have a link for the file parser as I am missing it here. I
will take a look and get some help from a python expert at work to get some
guidance..
Jon
On Saturday 9 March 2024 at 22:41:18 UTC Jon Fear wrote:
> Hi Dale
>
> Not sure |I have seen the file parser, need to
Hi Dale
Not sure |I have seen the file parser, need to look at that. Using the
clientraw file would be a good idea. It does everything I need. Also shared
with others around the district to monitor variations and differences.
I am using Matt's driver but it si not doing the whole job and
I am getting a Campbell Scientific running with major help from a user who
has accomplished that already but am thinking while focused drivers are no
doubt the best interface, I was next going to try using Weather Display to
write the clientrawtext.txt file and the modify Mr Wall 's file parser to
Nice station.
Did you try Matthew Wall's driver?
https://github.com/matthewwall/weewx-wxt5x0
Also, if it has an MQTT interface, you could integrate it into WeeWX that
way.
On Sat, Mar 9, 2024 at 6:42 AM 'Jon Fear' via weewx-user <
weewx-user@googlegroups.com> wrote:
> Hi folks
>
> It is time
Hi folks
It is time for the silly question to be asked.
I have a Vaisala WXT536 which is well supported under Weather Display
whereas the support is limited here under weewx. Not a criticism given it
is such a unique high value device which will have limited appeal.
Is there a way of taking
