5.2 up and running with simulator in almost no time!

[DR]

Thanks to the quickstart info and the very clear and easy to copy
commands I have the simulator mode of 5.2 up and running on a new Pi5
trixie.

Why, I'm not sure, but I was leery with previous info on all the choices
offered and honestly got a bit scared off in trying to implement this. 
Russ and Vince told me that the virtual environment was a no brainer and
was not only simple, but it seems this method makes it much more clear
where things go..


THANKS!


After the simulator runs for a few days, I'd like to try adding a new
input station. My only reliable source of input is from a Rainwise,
using the IP-100.

I looked at the github and the driver listed has updates from 10 years
to as few as 6 years, but a lot of water has gone under the bridge since
then.  I scanned the Wiki for how to install a driver into 5.2, but
don't see anything specific where the driver code should go, and I doubt
the installation from the github IP-100 knows about virtual drivers and
the two different ways to start and stop WeeWx, etc.


Is there a directory I should put the code into and then add the station
manually to the weewx.conf file?  What is the best way to proceed?


Finally, I am running a pi4 with the IP-100 as data source for an old
but very stable install (4.7.0) and I don't want to goof that up.

Question:  Can an IP-100 drive two WeeWx installs, one on my reliable
pi4 and experimenting with a live data feed as I tweak my Pi5? Would
there be a collision when by chance they both want to grab data at the
same time?  I can set one to get data at 2 second intervals and the
other to three seconds to minimize the chance for simultaneous
requests.  I realize this is no likely a very rare problem and no one
may have experience with such a set up.

Thanks again for all the fun and joy this program and support has given
me in the dark cold months up here in the nort'   Dale

[Vince Skahan]

The best way to proceed is to actually spend the time to read the user guide which tells you how to install a driver and almost anything else you might need to know….

https://www.weewx.com/docs/5.2/usersguide/installing/

If you had your old setup working the new one should work too if the driver is compatible with python3.  Looks like ip100 is ancient so its instructions need tweaking for weewx v5. Basically wee_xyz was replaced with weect. See the utilities guide for weectl usage.

No idea re:multiple instance querying the ip100. Try it and report back.

[John Kline]

The six year old one is mine (at https://github.com/chaunceygardiner/weewx-ip100).

I’ve long since moved on to a Vantage Pro, but this IP100 driver will work on WeeWX 5.2.  Let me know if you need any help.

Driving two weewx instances would be an interesting experiment.  You’ll have to try it.  You could also get another IP100 or a CC3000.  That would definitely work.  I have some lying around.  Where are you located?

On Jan 8, 2026, at 7:19 PM, DR <wxe...@gmail.com> wrote:

Thanks to the quickstart info and the very clear and easy to copy commands I have the simulator mode of 5.2 up and running on a new Pi5 trixie.

Why, I'm not sure, but I was leery with previous info on all the choices offered and honestly got a bit scared off in trying to implement this.  Russ and Vince told me that the virtual environment was a no brainer and was not only simple, but it seems this method makes it much more clear where things go..


THANKS!


After the simulator runs for a few days, I'd like to try adding a new input station. My only reliable source of input is from a Rainwise, using the IP-100.

I looked at the github and the driver listed has updates from 10 years to as few as 6 years, but a lot of water has gone under the bridge since then.  I scanned the Wiki for how to install a driver into 5.2, but don't see anything specific where the driver code should go, and I doubt the installation from the github IP-100 knows about virtual drivers and the two different ways to start and stop WeeWx, etc.


Is there a directory I should put the code into and then add the station manually to the weewx.conf file?  What is the best way to proceed?


Finally, I am running a pi4 with the IP-100 as data source for an old but very stable install (4.7.0) and I don't want to goof that up.

Question:  Can an IP-100 drive two WeeWx installs, one on my reliable pi4 and experimenting with a live data feed as I tweak my Pi5? Would there be a collision when by chance they both want to grab data at the same time?  I can set one to get data at 2 second intervals and the other to three seconds to minimize the chance for simultaneous requests.  I realize this is no likely a very rare problem and no one may have experience with such a set up.

Thanks again for all the fun and joy this program and support has given me in the dark cold months up here in the nort'   Dale

--
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+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/725be903-5e62-4833-b624-0d8866d15a9d%40gmail.com.

[John Smith]

it seems this method makes it much more clear where things go..

Just don't update python versions without backing up. 

[DR]

"The six year old one is mine (at
https://github.com/chaunceygardiner/weewx-ip100).


I’ve long since moved on to a Vantage Pro, but this IP100 driver will
work on WeeWX 5.2.  Let me know if you need any help.
Driving two weewx instances would be an interesting experiment.  You’ll
have to try it.  You could also get another IP100 or a CC3000.  That
would definitely work.  I have some lying around.  Where are you located?"

I will try implementing the one you pointed to and with  your knowledge
of the WeeWx 5.2 and Python requirements feel that it should work, since
I'm trying to keep several options open and while many have  upgraded
their stations to Davis and has a lot of attention.

I'd be interested in an IP-100 maybe and yet will try to see if there
are collisions with two drivers requesting data from one IP-100 as soon
as I get the driver you pointed to installed on my Pi5.  As you imply,
there should be no problem if each WeeWx is pointing to a different IP
address.

Thanks for  you help.  Dale

[Vince Skahan]

Likely comes down to how the device deals with lots of queries in a short time frame. This driver seems to by default poll very frequently. Only testing can say if there is any concern.

I ran multiple weewx polling an ecowitt gw1200 with no problems but that device only gets polled every minute.

The pi5 will not be your limit. Heck go ahead and run 5 instances on the pi and see what https://github.com/weewx/weewx/wiki/weewx-multi

[DR]

Thank  you.

I looked (as best I could) to see that the poll frequency is settable
and that there are number of retries if in error, so both of those are
options to fiddle with.


I know from an entirely different application (cronpakbusnew) from
Weather Display that trying to  have multiple display instances read
from the same Campbell Scientific 3000 will eventually end up with a
collision and it isn't handled gracefully.


More fun to come and I am discovering just how much moxie those Pi5s
have.  Off to read more.  Dale

[Dale]

I've played with setting up my venv and started, stopped,etc.

I went to the IP100 site and got the ip100.py code but there is no
'automated' package that I can find to do the import and have the
station reconfigure do the install, so I put the ip100.py in the
weewx-data/bin/user folder and ran the weectl station reconfigure, and
got this:



Choose a driver. Installed drivers include:
  0) ?               (user.ip100)              No module named 'six'
  1) AcuRite         (weewx.drivers.acurite)
  2) CC3000          (weewx.drivers.cc3000)
  3) FineOffsetUSB   (weewx.drivers.fousb)
  4) Simulator       (weewx.drivers.simulator)
  5) TE923           (weewx.drivers.te923)
  6) Ultimeter       (weewx.drivers.ultimeter)
  7) Vantage         (weewx.drivers.vantage)
  8) WMR100          (weewx.drivers.wmr100)
  9) WMR300          (weewx.drivers.wmr300)
 10) WMR9x8          (weewx.drivers.wmr9x8)
 11) WS1             (weewx.drivers.ws1)
 12) WS23xx          (weewx.drivers.ws23xx)
 13) WS28xx          (weewx.drivers.ws28xx)
driver [4]: 0
Traceback (most recent call last):
  File "/home/dale/weewx-venv/bin/weectl", line 8, in <module>
    sys.exit(main())
             ~~~~^^
  File "/home/dale/weewx-venv/lib/python3.13/site-packages/weectl.py",
line 67, in main
    namespace.func(namespace)
    ~~~~~~~~~~~~~~^^^^^^^^^^^
  File
"/home/dale/weewx-venv/lib/python3.13/site-packages/weectllib/__init__.py",
line 90, in dispatch
    namespace.action_func(config_dict, namespace)
    ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^
  File
"/home/dale/weewx-venv/lib/python3.13/site-packages/weectllib/station_cmd.py",
line 311, in reconfigure_station
weectllib.station_actions.station_reconfigure(config_dict=config_dict,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
driver=namespace.driver,
^^^^^^^^^^^^^^^^^^^^^^^^
    ...<13 lines>...
no_backup=namespace.no_backup,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
dry_run=namespace.dry_run)
^^^^^^^^^^^^^^^^^^^^^^^^^^
  File
"/home/dale/weewx-venv/lib/python3.13/site-packages/weectllib/station_actions.py",
line 164, in station_reconfigure
    config_config(config_dict,
    ~~~~~~~~~~~~~^^^^^^^^^^^^^
                  config_path=config_dict['config_path'],
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<9 lines>...
                  user_root=user_root,
                  ^^^^^^^^^^^^^^^^^^^^
                  no_prompt=no_prompt)
                  ^^^^^^^^^^^^^^^^^^^^
  File
"/home/dale/weewx-venv/lib/python3.13/site-packages/weectllib/station_actions.py",
line 207, in config_config
    config_driver(config_dict, driver=driver, no_prompt=no_prompt)
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File
"/home/dale/weewx-venv/lib/python3.13/site-packages/weectllib/station_actions.py",
line 424, in config_driver
    driver_editor, driver_name, driver_version =
weecfg.load_driver_editor(final_driver)
~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
  File
"/home/dale/weewx-venv/lib/python3.13/site-packages/weecfg/__init__.py",
line 453, in load_driver_editor
    driver_module = importlib.import_module(driver_module_name)
  File "/usr/lib/python3.13/importlib/__init__.py", line 88, in
import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1331, in
_find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 1026, in exec_module
  File "<frozen importlib._bootstrap>", line 488, in
_call_with_frames_removed
  File "/home/dale/weewx-data/bin/user/ip100.py", line 11, in <module>
    import six.moves.urllib.request, six.moves.urllib.error,
six.moves.urllib.parse
ModuleNotFoundError: No module named 'six'


John Kline indicated that the version of ip100.py from 6 years ago
should work with 5.2,

I just need to have a little guidance as to where to put the ip100.py
code and then I would anticipate having to create the lines defining the
station in the weewx.conf file to tell it to use the ip100 driver, with
my IP address for the Rainwise device.


Is this enough info above to be useful or should I load a copy of the
journalctl -u weewx to this message?

Dale

[Vince Skahan]

https://letmegooglethat.com/?q=ModuleNotFoundError%3A+No+module+named+%27six%27

[D R]

Indeed the python level install of the module called six

pip install six

did the trick.

I had no idea what that was compared to python or something that WeeWx
supplied.  I appreciate the pointers you gave.

I did an install on the IP100 driver and the WeeWx 5.2 seems to be
pulling in data from the Rainwise.

So far I've not seen any collisions with the other WeeWx 4.7 running off
the same IP address but I chose 11 second polling for the one and left
the other at 2 seconds, so that may avoid problems.

And to reassure anyone who is using ancient hardware like the IP100,
that driver from John 6 years ago on the Github site does indeed work.

Dale

[D R]

John,

in a message a few weeks or so ago you implied you had some unused
Rainwise IP-100 lying around.

Do you have any spares, and if so, how much are they worth?  I am in
Wisconsin in the US, if that helps.  If you are in another country I'm
thinking import fees would be perhaps overwhelming?

Anyway, thank you for the encouragement  your modifying of Matthew's
original code makes this work and DOES run under 5.2


I am appreciative.

Dale