Update – all is happy now. Here’s what I had to do:
1. Append V2 to the sdr 5n1 definitions in weewx.conf
2. Change the 6045 identifier in sdr.py to Acurite-6045M
3. Add a divisor (1.609344) to the wind speed calculation (for the 5n1) in
sdr.py
I ALSO discovered that the auth
Hi Michael,
I just pushed new versions of LoopData and WeatherBoard on the development
branches.
I’ve now tested LoopData with a simulator without barometer and pressure
readings.
I’ve also updated the WeatherBoard JavaScript to be resistant to missing
observations.
If you try these, please
Okay. Any new stuff to test? To take special attention to?
Op zondag 12 juli 2020 om 20:37:04 UTC+2 schreef flor...@pre-vost.fr:
> Hi,
>
> See new git for more visibility :
> https://github.com/Drealine/weatherlinklive-driver-weewx
>
> Le mercredi 8 juillet 2020 à 22:12:44 UTC+2, flor...@pre-
Hi,
See new git for more visibility :
https://github.com/Drealine/weatherlinklive-driver-weewx
Le mercredi 8 juillet 2020 à 22:12:44 UTC+2, flor...@pre-vost.fr a écrit :
> Hi :)
>
> Can you try my fix on the repo ?
>
> Seems that I calculate 0 / 25.4 or 2.54. I fixed it.
>
> Le mercredi 8 ju
Okay, found it. I also run CumulusMX on my production-box, listening to
port 2. It seems that one application at the time can 'lock' onto a
specific port? Maybe CumulusMX claims full ownership of this port, becoming
unavailbe for other applications?
Now I've stopped CumulusMX, and weewx (an
It is unable to open socket 2, it looks like an other weewx is running.
On Sunday, July 12, 2020 at 6:09:14 PM UTC+2, Maarten van der Hoeven wrote:
>
> Strange. I want to use the driver in my 'production'-environment, and got
> this error. Any clue? As on my 'test'-environment it is running
Strange. I want to use the driver in my 'production'-environment, and got
this error. Any clue? As on my 'test'-environment it is running okay.
Jul 12 18:03:16 weewx weewx[907239] INFO __main__: Using configuration file
/etc/weewx/weewx.conf
Jul 12 18:03:16 weewx weewx[907239] INFO __main__: Deb
Hi Michael,
Would you give 2.0.b3 a try and let me know how it goes?
If it doesn’t work, I’ll run with the simulator (and no barometer/pressure)
before I push another version.
Cheers,
John
> On Jul 12, 2020, at 3:39 AM, Michael wrote:
>
>
> Hi John,
>
> I have just tested the version LOOP
Hi John,
I have just tested the version LOOP_DATA_VERSION = '2.0.b2'.
the following error appears after a few minutes runtime:
Jul 12 12:35:08 raspberrypi weewx[31676] CRITICAL user.loopdata:
Traceback (most recent call last):
Jul 12 12:35:08 raspberrypi weewx[31676] CRITICAL user.loop
Hi John,
Unfortunately I was a bit hasty with my message that everything works as
desired.
Unfortunately I only watched the logfile for a short time during startup
and did not see the error message that appeared later:
Jul 11 17:50:11 raspberrypi weewx[15962] CRITICAL user.loopdata:
10 matches
Mail list logo
