What you have now done is quite probably the better approach anyway.
On Saturday, 26 May 2018 17:13:46 UTC+3, bdf0506 wrote:
>
> I gave up on this approach.
>
> I updated the database schema and pumped the extra sensors into some
> custom fields. This way, I only need to run one weewx instance.
I gave up on this approach.
I updated the database schema and pumped the extra sensors into some custom
fields. This way, I only need to run one weewx instance. My extra sensors
are only capturing temp and humidity so there isn’t calculations I need
weewx to do on those, and one db is preferred
Hmm that is much more complicated than my setup which consists of a
computer running C7 which has a Davis VantageVue and a LaCross WS
attached and sends the info via rsync to my web server.
Wouldn't you have the same problem with the weewx-multi script? I just
never could get all the
Bummer. But thanks for sharing.
I haven't tried this yet with two separate scripts. I think I am going to
have issues when I do this because of the interceptor driver I am using for
the Acurite smarthub. I have it set to listed on 8080 (traffic is
redirected from port 80). I'll be able to
On 05/25/2018 12:57 PM, bdf0506 wrote:
Once you change the paths, comment out some of the files that aren't
found, still fails as suchclearly you can't comment out some of
the files and expect it to work since it has refrences later in the
script to the commented out files.
Once you change the paths, comment out some of the files that aren't found,
still fails as suchclearly you can't comment out some of the files and
expect it to work since it has refrences later in the script to the
commented out files.
[root@server01 init.d]$ service weewx stop
