Just reread are you looking for my sensor data collection file (it collects
the data from my i2C BMP085) this is done as a service, it gets all my data
creates a csv file in ram which I then read with the piweather Driver in
weewx.
On my new install (from scratch) Adafruit_Python_BMP,
Don’t know, never thought of it.
I included it with another post the other day, but since then modified
because it would not work with new install. Which I have now gone to weewx
v4.1 as well and all OK.
I will experiment and let you know...
Nev
On Thursday, May 28, 2020 at 4:54:37 PM UTC+10,
Hi Neville,
Do you know if the pyweather driver can be used as service not a driver ?
I only need the barometer bit but as you have confirmed it it working with
python3 it might be a better way to go than the other i2c solution.
Gaz
--
You received this message because you are subscribed
Really good to hear of another success!
I've just bumped mine to weewx v4.1.0 and that's also working like a charm.
I know the feeling with the heavy rain. Thankfully it's only ever been
phantom downfalls and therefore easily fixed.
On 28/05/2020, Neville Davis wrote:
> Glenn
>
> Success my
Glenn
Success my system is fully operational with python 3.7 weewx v4.0.0 with
1Wire rain, and my i2C sensor system, with ow-server and pyownet.
For your information Glenn I am using your OWFS-dallas.py downloaded
yesterday.after my silly mistake we are lo longer under several meters
of
Thanks very much Glen I will do the mods in the morning.
I had specified a sensor type in my old system...but just forgot..
Neville
On Wednesday, May 27, 2020 at 5:31:30 PM UTC+10, Glenn McKechnie wrote:
>
> Hi Neville,
>
> Within the [OWFS] section of weewx you need to specify a
Hi Neville,
Within the [OWFS] section of weewx you need to specify a [[sensor_type]]
Firstly, you are correct with the count incrementing when the bucket
tips but you need to turn that into a time based value
A rain value is evaluated as the difference between the current count
and the last
Glen
My solution is proving to be beyond my capabilities to get to be correct,
while I can get the data I have run into several issues that just makes it
too messy.
After reading this and looking at your far more elegant solutions I have
installed and it is has several problems.
First I run
Thanks Neville,
That's interesting and certainly of note. It may be just what we are
looking for.
Stefano Miccoli is the author of pyownet so we are doubly on topic!
The original post is at...
https://sourceforge.net/p/owfs/mailman/message/36765345/
and part of a much longer thread...
Guys I too have been following, I am now running pythonv3 weewxv4 with
1wire rain, my solution is different and messy but seems to work for me,
But while trying to sort out my problem found a report about problems with
owserver on Pi using bustergithub miccoli in the config file edit
On 26/05/2020, Messy Potamia wrote:
>
> *I'm following this because one of my weewx stations rely heavily on OW
> sensors to augment the data from my Davis Vantage pro2. *
> *I'd upgrade to weewx 4.x but really can't lose owfs operability*.
> Thx/mp
By weewx4 I assume you mean python3 and
On 26/05/2020, Gazza wrote:
> Hi Glen,
>
> My interface board is based on one I milled on my CNC a couple of years
> ago, for the new one I had the board made as it makes it much easier to
> assemble that the bare copper ones.
CNC!
As an ex fitter, toolmaker come "jack of all" that's my
*Thanks good to know. I extended my schema ~5 yrs ago, to add some lake
height and wave height measured by a MaxBotix rangefinder, and lightning,
parameters. A couple other params I stuffed into unused columns in the
weewx.sdb and renamed the reports. *
*I'm going to have to rebuild my whole
On Tuesday, May 26, 2020 at 6:18:17 PM UTC+10, Messy Potamia wrote:
>
>
> *I'm following this because one of my weewx stations rely heavily on OW
> sensors to augment the data from my Davis Vantage pro2. *
> *I'd upgrade to weewx 4.x but really can't lose owfs operability*.
> Thx/mp
>
This
>> If you are running the owfs.py from my fork, the syslog message will
>> tell you what module it has opted to run under. That message occurs in
>> the first few log entries after weewx initializes. It's an INFO
>> message
>>
>
> So with python-ow installed I get this in the INFO:
>
> May 26
*I'm following this because one of my weewx stations rely heavily on OW
sensors to augment the data from my Davis Vantage pro2. *
*I'd upgrade to weewx 4.x but really can't lose owfs operability*.
Thx/mp
On Tuesday, May 26, 2020 at 10:06:04 AM UTC+2, Gazza wrote:
>
>
> If you are running the
> If you are running the owfs.py from my fork, the syslog message will
> tell you what module it has opted to run under. That message occurs in
> the first few log entries after weewx initializes. It's an INFO
> message
>
So with python-ow installed I get this in the INFO:
May 26 17:43:02
On 26/05/2020, Gazza wrote:
> OK, I have done some more tests, first I have removed python-ow and now the
> owfs service in weewx is not working.
If you are running the owfs.py from my fork, the syslog message will
tell you what module it has opted to run under. That message occurs in
the first
OK, I have done some more tests, first I have removed python-ow and now the
owfs service in weewx is not working.
When I run systemctl status owserver it shows that it is enabled and
running.
pi@GazPi4:~ $ systemctl status owserver
* owserver.service - Backend server for 1-wire control
The system must be using owserver as the weewx.conf has been changed to
point to localhost:4304.
I haven't removed python-ow should I do that ??
Gaz
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop
Gazza wrote:
>
> Hi Glen,
>
> I don't fully understand the pyownet bit but owserver would not run without
> it being installed.
Okay, that is confusing as pyownet is the client, it needs owserver.
Owserver doesn't care whether pyownet is there or not.
We do, it doesn't.
If you were still
Hi Glen,
I don't fully understand the pyownet bit but owserver would not run without
it being installed.
Gaz
--
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
Hi Gaz,
Excellent.
Good to hear it's working for you, and may it keep doing so!
You've certainly given it a good test, with the Service setup, python
versions, and especially the owserver - pyownet combination!
Great to have your working config setup too. It's always good to have
that sort of
OK, I have had a read of the posts about pyton-ow being no longer supported
and have now installed owserver and owshell and pyownet.
As I am using a DS2482-100 I2C Bus master my owfs.conf contains:
# DS2482-100 I2C Bus master
server: device = /dev/i2c-1
server: port = localhost:4304
I changed
OK, me again, ignore the last 2 posts, I can't spell.
It works fine if you get the file name right !!, the new test 1wire sensor
is the solar hot water, the others are various 433MHz sensors.
[image: hi-lo.JPG]
Gaz
--
You received this message because you are subscribed to the Google
Forgot to add the error file.
Gaz
--
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
Hi Glen,
I still get a crash with your new version of owfs.py.
I am also running a working rtl_sdr install as well and am trying to run
owfs as a service. I don't understand this bit just before the critical
messages.
May 23 22:05:22 GazPi4 weewx[1120] INFO weewx.engine: Main loop exiting.
Tested and updated the owfs.py file in my fork
Changed the encode() suggestions in the thread above to use plain str()
I believe I've caught all instances and that fix should propagate
through to the various functions.
There is also a tweak to get_float(path) that I required (when using
pyownet
Looks like another encoding issue.
You could try changing line 274 in the same fashion. No guarantees, as
I can't test it.
change...
sv = ow.get(path)
to include the encode fix...
sv = ow.get(path.encode())
I've raised it as an issue on github, hopefully mathew will be along
and able to apply
Tried that change and it crashed with a different set of errors.
Gaz
--
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.
Strange, I wouldn't have thought that would bite with python2.7 ?
It's really one for an expert, but you can try the following and see
if it gets you any further.
line 205 in owfs.py
try changing that from...
owbinding.init(iface)
to...
owbinding.init(iface.encode())
On 22/05/2020, Gazza
31 matches
Mail list logo
