Re: [weewx-user] working weewx 4.5.1 - errors after Ubuntu OS update

[Eric K]

I forgot to post this:
weewx@Ubuntu20-WEEWX:~$ python3 -c "import 
paho.mqtt.client;print(paho.mqtt.client.__file__)"
/usr/lib/python3/dist-packages/paho/mqtt/client.py

On Thursday, December 30, 2021 at 10:38:58 PM UTC-6 Eric K wrote:

> Simply reinstalling python3-paho-mqtt has not fixed the system.
>
> I tried the mosquitto_sub command and mosquitto refused the connection.
> weewx@Ubuntu20-WEEWX:~$ mosquitto_sub -h 192.168.7.22 -p 1883 -t 
> tele/BMP280/SENSOR -d
> Error: Connection refused
>
> I've got mosquitto.conf set to accpet anymous logins:
> protocol mqtt
> port 1883
> allow_anonymous true
>
> and I've got weewx.conf set for:
> [MQTTSubscribeService]
> enable = true
> host = localhost
> port = 1883
> keepalive = 60
> username = None
> password = None
>
> I tried to manually force mosquitto to start - NO-GO.
> I followed the instructions to get some debug info.
>
> weewx@Ubuntu20-WEEWX:~$ sudo systemctl start mosquitto
> Job for mosquitto.service failed because the control process exited with 
> error code.
> See "systemctl status mosquitto.service" and "journalctl -xe" for details.
>
> weewx@Ubuntu20-WEEWX:~$ systemctl status mosquitto.service
> ● mosquitto.service - Mosquitto MQTT Broker
>  Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; 
> vendor preset: enabled)
>  Active: failed (Result: exit-code) since Thu 2021-12-30 22:23:26 CST; 
> 3min 56s ago
>Docs: man:mosquitto.conf(5)
>  man:mosquitto(8)
> Process: 2797 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto 
> (code=exited, status=0/SUCCESS)
> Process: 2798 ExecStartPre=/bin/chown mosquitto: /var/log/mosquitto 
> (code=exited, status=0/SUCCESS)
> Process: 2799 ExecStartPre=/bin/mkdir -m 740 -p /var/run/mosquitto 
> (code=exited, status=0/SUCCESS)
> Process: 2800 ExecStartPre=/bin/chown mosquitto: /var/run/mosquitto 
> (code=exited, status=0/SUCCESS)
> Process: 2801 ExecStart=/usr/sbin/mosquitto -c 
> /etc/mosquitto/mosquitto.conf (code=exited, status=1/FAILURE)
>Main PID: 2801 (code=exited, status=1/FAILURE)
>
> I'm not sure how many of weewx's dependencies have to be reinstalled?
>
> On Wednesday, December 29, 2021 at 10:36:37 AM UTC-6 vince wrote:
>
>> On Tuesday, December 28, 2021 at 7:45:22 PM UTC-8 Eric K wrote:
>>
>>> After re-installing python3-paho-mqtt into Ubuntu 21.04 with "sudo 
>>> apt-get install python3-paho-mqtt"
>>> /usr/local/lib/python3.9/dist-packages/ is empty
>>> I'm not sure where the reinstalled python3-paho-mqtt files got installed?
>>> Back in /usr/local/lib/python3.8/dist-packages/ ?
>>>
>>
>> Does it really matter as long as it works ?
>>
>> As I mentioned earlier, if you use pip it goes under /usr/local/lib, but 
>> if you use apt then it goes under /usr/lib.
>>
>> But it doesn't really matter.  Just go with it.  It works.
>>
>>

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/5c5ed098-a6e5-4a49-97e6-c5dd55464686n%40googlegroups.com.

Re: [weewx-user] working weewx 4.5.1 - errors after Ubuntu OS update

[Eric K]

Simply reinstalling python3-paho-mqtt has not fixed the system.

I tried the mosquitto_sub command and mosquitto refused the connection.
weewx@Ubuntu20-WEEWX:~$ mosquitto_sub -h 192.168.7.22 -p 1883 -t 
tele/BMP280/SENSOR -d
Error: Connection refused

I've got mosquitto.conf set to accpet anymous logins:
protocol mqtt
port 1883
allow_anonymous true

and I've got weewx.conf set for:
[MQTTSubscribeService]
enable = true
host = localhost
port = 1883
keepalive = 60
username = None
password = None

I tried to manually force mosquitto to start - NO-GO.
I followed the instructions to get some debug info.

weewx@Ubuntu20-WEEWX:~$ sudo systemctl start mosquitto
Job for mosquitto.service failed because the control process exited with 
error code.
See "systemctl status mosquitto.service" and "journalctl -xe" for details.

weewx@Ubuntu20-WEEWX:~$ systemctl status mosquitto.service
● mosquitto.service - Mosquitto MQTT Broker
 Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2021-12-30 22:23:26 CST; 
3min 56s ago
   Docs: man:mosquitto.conf(5)
 man:mosquitto(8)
Process: 2797 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto 
(code=exited, status=0/SUCCESS)
Process: 2798 ExecStartPre=/bin/chown mosquitto: /var/log/mosquitto 
(code=exited, status=0/SUCCESS)
Process: 2799 ExecStartPre=/bin/mkdir -m 740 -p /var/run/mosquitto 
(code=exited, status=0/SUCCESS)
Process: 2800 ExecStartPre=/bin/chown mosquitto: /var/run/mosquitto 
(code=exited, status=0/SUCCESS)
Process: 2801 ExecStart=/usr/sbin/mosquitto -c 
/etc/mosquitto/mosquitto.conf (code=exited, status=1/FAILURE)
   Main PID: 2801 (code=exited, status=1/FAILURE)

I'm not sure how many of weewx's dependencies have to be reinstalled?

On Wednesday, December 29, 2021 at 10:36:37 AM UTC-6 vince wrote:

> On Tuesday, December 28, 2021 at 7:45:22 PM UTC-8 Eric K wrote:
>
>> After re-installing python3-paho-mqtt into Ubuntu 21.04 with "sudo 
>> apt-get install python3-paho-mqtt"
>> /usr/local/lib/python3.9/dist-packages/ is empty
>> I'm not sure where the reinstalled python3-paho-mqtt files got installed?
>> Back in /usr/local/lib/python3.8/dist-packages/ ?
>>
>
> Does it really matter as long as it works ?
>
> As I mentioned earlier, if you use pip it goes under /usr/local/lib, but 
> if you use apt then it goes under /usr/lib.
>
> But it doesn't really matter.  Just go with it.  It works.
>
>

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/3ed31c0e-80ee-453d-9f5c-024c750df0c9n%40googlegroups.com.

Re: [weewx-user] weewx-influx crashing

[JJ]

Thanks, though that makes the error I am getting even more puzzling. By 
original code, do you mean this version 
(https://github.com/matthewwall/weewx-influx)? If so, does the original 
code support token-based authentication and connect with influxdb 2.0 
databases? I thought I would need need to use the david lutz version to 
send data to an influx 2.0 database with a token, org and bucket: 
https://github.com/matthewwall/weewx-influx/issues/28

On Thursday, December 30, 2021 at 10:07:04 AM UTC-5 tke...@gmail.com wrote:

> It looks like it does. But, why not use the original code? There have been 
> several modifications since the david-lutz fork.
>
>
>
> On Thu, Dec 30, 2021 at 6:40 AM JJ  wrote:
>
>> I have been getting a similar error with my attempted weewx influx 
>> connection never working with a Raspberry Pi. I get a syslog error message 
>> about thread terminating because "POST data should be bytes, an iterable of 
>> bytes, or a file object. It cannot be of type str". I am using the 
>> Simulator with weewx and I am currently trying the influxdb 2.0 forked 
>> code: https://github.com/david-lutz/weewx-influx2
>>
>> Is it possible that the influx2 code does not have this update that was 
>> made to the influx1 code?
>>
>> On Monday, January 25, 2021 at 7:11:47 AM UTC-5 tke...@gmail.com wrote:
>>
>>> Already done!
>>>
>>> https://github.com/matthewwall/weewx-influx/pull/27
>>>
>>> Thanks for testing it.
>>>
>>>
>>> On Sun, Jan 24, 2021 at 8:20 PM Tom Corbett  
>>> wrote:
>>>
 This seems to have fixed my issues. Has been diligently putting data in 
 every minute for over a week now. What's the protocol for adding a pull 
 request to Matthew's github so that other Python 3 users don't have this 
 issue? It was your change, but happy to do the pull request if it helps 
 others.

 Tom

 On Thursday, January 14, 2021 at 4:17:34 PM UTC+11 Tom Corbett wrote:

> Thanks very much. I have replaced the existing influx.py with your 
> version and restarted weewx. It is putting data into the InfluxDb, so 
> fingers crossed it keeps doing so.
>
> Cheers,
>
> Tom
>
> On Thursday, January 14, 2021 at 2:20:46 PM UTC+11 tke...@gmail.com 
> wrote:
>
>> Normally, I don't deal with the influx driver, but Matthew is swamped 
>> so I took a look.
>>
>> I believe the problem is that the driver was not completely ported to 
>> Python 3. The HTTP response needs to be converted from a byte array to a 
>> string before performing the find() operation.
>>
>> Try this version of influx.py 
>> 
>> .
>>
>> -tk
>>
>>
>>
>> On Wed, Jan 13, 2021 at 5:52 PM Tom Corbett  
>> wrote:
>>
>>>
>>> Hi All,
>>>
>>> I'm new to weewx and  python in general so have been plugging away 
>>> for a couple of weeks getting everything setup and working.
>>>
>>> My hardware is an ecowitt WH9200 and I'm using weewx 4.2 on FreeBSD 
>>> which I setup using the py-setup method. I am capturing the data using 
>>> the 
>>> weewx-interceptor in listen mode. This all seems to be flowing fine 
>>> into 
>>> the sqlite DB.
>>>
>>> I then have the weewx-influx extension sending data to an InfluxDB 
>>> every minute. This will work fine for several hours; ~ 11 hours being 
>>> the 
>>> current record, but will crash with the following in the logs: My take 
>>> on 
>>> that is that for some reason a string is being sent to Influx rather 
>>> than 
>>> an integer or boolean, however I could be seeing the symptom rather 
>>> than 
>>> the cause.
>>>
>>> To investigate I checked the record in the sqlite DB immediately 
>>> after the last one in the InfluxDB, ie the one that caused the crash, 
>>> and 
>>> could see nothing that looked different to all the previous one. IE, I 
>>> couldn't see any strings in the record.
>>>
>>> Any help would be appreciated in tracking this down. I'm a bit 
>>> perplexed as to why it runs happily for hours then has a coniption.
>>>
>>> Thanks,
>>>
>>> Tom
>>>
>>> Here's the relevent section of weewx.conf, nothing too interesting 
>>> AFAIK.
>>>
>>> [[Influx]]
>>> database = weewx_hades_test
>>> host = 192.168.178.25
>>> unit_system = METRICWX
>>>
>>> Logs: 
>>>
>>> Jan 14 10:54:45 28spots kernel: Jan 14 10:54:45 28spots weewx[964] 
>>> ERROR weewx.restx: Influx: Unexpected exception of type >> 'TypeError'>
>>>
>>> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
>>> ERROR weewx.restx: *** Traceback (most recent call last):
>>>
>>> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
>>> ERROR weewx.restx: ***   File "/us

Re: [weewx-user] Upgrade 3.92 direct to 4.5.0??

[Dave, G1OGY]

Thanks, Tom.
Just wanted an easy life.

On Thursday, December 30, 2021 at 11:30:22 PM UTC tke...@gmail.com wrote:

> See the section *From V3.9 or earlier 
> * in the 
> Upgrade Guide.
>
> The only issue you might have is the calculation of derived types and, 
> even then, only if you messed with the [StdWXCalculate] section in 
> weewx.conf.
>
> On Thu, Dec 30, 2021 at 3:23 PM Dave, G1OGY  wrote:
>
>> Greetings
>> Is direct upgrade 3.9.2 --> 4.5.x supported, please?
>> Any specific caveats (other than the usual)?
>> TIA
>>
>> -- 
>> 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 on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/39bb068b-de54-464b-a8e6-0c23454d5975n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/5132ab29-60fb-4110-9658-cd1db2f7ab16n%40googlegroups.com.

Re: [weewx-user] Upgrade 3.92 direct to 4.5.0??

[Tom Keffer]

See the section *From V3.9 or earlier
* in the
Upgrade Guide.

The only issue you might have is the calculation of derived types and, even
then, only if you messed with the [StdWXCalculate] section in weewx.conf.

On Thu, Dec 30, 2021 at 3:23 PM Dave, G1OGY  wrote:

> Greetings
> Is direct upgrade 3.9.2 --> 4.5.x supported, please?
> Any specific caveats (other than the usual)?
> TIA
>
> --
> 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 visit
> https://groups.google.com/d/msgid/weewx-user/39bb068b-de54-464b-a8e6-0c23454d5975n%40googlegroups.com
> 
> .
>

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA9e9Sf%3DhHTrxzZPoFtA1pXMtwwUYnET38idJLw-YMTrQ%40mail.gmail.com.

[weewx-user] Upgrade 3.92 direct to 4.5.0??

[Dave, G1OGY]

Greetings
Is direct upgrade 3.9.2 --> 4.5.x supported, please?
Any specific caveats (other than the usual)?
TIA

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/39bb068b-de54-464b-a8e6-0c23454d5975n%40googlegroups.com.

Re: [weewx-user] weewx-influx crashing

[Tom Keffer]

It looks like it does. But, why not use the original code? There have been
several modifications since the david-lutz fork.



On Thu, Dec 30, 2021 at 6:40 AM JJ  wrote:

> I have been getting a similar error with my attempted weewx influx
> connection never working with a Raspberry Pi. I get a syslog error message
> about thread terminating because "POST data should be bytes, an iterable of
> bytes, or a file object. It cannot be of type str". I am using the
> Simulator with weewx and I am currently trying the influxdb 2.0 forked
> code: https://github.com/david-lutz/weewx-influx2
>
> Is it possible that the influx2 code does not have this update that was
> made to the influx1 code?
>
> On Monday, January 25, 2021 at 7:11:47 AM UTC-5 tke...@gmail.com wrote:
>
>> Already done!
>>
>> https://github.com/matthewwall/weewx-influx/pull/27
>>
>> Thanks for testing it.
>>
>>
>> On Sun, Jan 24, 2021 at 8:20 PM Tom Corbett  wrote:
>>
>>> This seems to have fixed my issues. Has been diligently putting data in
>>> every minute for over a week now. What's the protocol for adding a pull
>>> request to Matthew's github so that other Python 3 users don't have this
>>> issue? It was your change, but happy to do the pull request if it helps
>>> others.
>>>
>>> Tom
>>>
>>> On Thursday, January 14, 2021 at 4:17:34 PM UTC+11 Tom Corbett wrote:
>>>
 Thanks very much. I have replaced the existing influx.py with your
 version and restarted weewx. It is putting data into the InfluxDb, so
 fingers crossed it keeps doing so.

 Cheers,

 Tom

 On Thursday, January 14, 2021 at 2:20:46 PM UTC+11 tke...@gmail.com
 wrote:

> Normally, I don't deal with the influx driver, but Matthew is swamped
> so I took a look.
>
> I believe the problem is that the driver was not completely ported to
> Python 3. The HTTP response needs to be converted from a byte array to a
> string before performing the find() operation.
>
> Try this version of influx.py
> 
> .
>
> -tk
>
>
>
> On Wed, Jan 13, 2021 at 5:52 PM Tom Corbett 
> wrote:
>
>>
>> Hi All,
>>
>> I'm new to weewx and  python in general so have been plugging away
>> for a couple of weeks getting everything setup and working.
>>
>> My hardware is an ecowitt WH9200 and I'm using weewx 4.2 on FreeBSD
>> which I setup using the py-setup method. I am capturing the data using 
>> the
>> weewx-interceptor in listen mode. This all seems to be flowing fine into
>> the sqlite DB.
>>
>> I then have the weewx-influx extension sending data to an InfluxDB
>> every minute. This will work fine for several hours; ~ 11 hours being the
>> current record, but will crash with the following in the logs: My take on
>> that is that for some reason a string is being sent to Influx rather than
>> an integer or boolean, however I could be seeing the symptom rather than
>> the cause.
>>
>> To investigate I checked the record in the sqlite DB immediately
>> after the last one in the InfluxDB, ie the one that caused the crash, and
>> could see nothing that looked different to all the previous one. IE, I
>> couldn't see any strings in the record.
>>
>> Any help would be appreciated in tracking this down. I'm a bit
>> perplexed as to why it runs happily for hours then has a coniption.
>>
>> Thanks,
>>
>> Tom
>>
>> Here's the relevent section of weewx.conf, nothing too interesting
>> AFAIK.
>>
>> [[Influx]]
>> database = weewx_hades_test
>> host = 192.168.178.25
>> unit_system = METRICWX
>>
>> Logs:
>>
>> Jan 14 10:54:45 28spots kernel: Jan 14 10:54:45 28spots weewx[964]
>> ERROR weewx.restx: Influx: Unexpected exception of type > 'TypeError'>
>>
>> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964]
>> ERROR weewx.restx: *** Traceback (most recent call last):
>>
>> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964]
>> ERROR weewx.restx: ***   File "/usr/home/weewx/bin/weewx/restx.py",
>> line 475, in post_with_retries
>>
>> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964]
>> ERROR weewx.restx: *** _response = self.post_request(request,
>> data)
>>
>> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964]
>> ERROR weewx.restx: ***   File "/usr/home/weewx/bin/user/influx.py",
>> line 498, in post_request
>>
>> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964]
>> ERROR weewx.restx: *** return super(InfluxThread,
>> self).post_request(request, payload)
>>
>> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964]
>> ERROR weewx.restx: ***   File "/usr/home/wee

Re: [weewx-user] weewx-influx crashing

[JJ]

I have been getting a similar error with my attempted weewx influx 
connection never working with a Raspberry Pi. I get a syslog error message 
about thread terminating because "POST data should be bytes, an iterable of 
bytes, or a file object. It cannot be of type str". I am using the 
Simulator with weewx and I am currently trying the influxdb 2.0 forked 
code: https://github.com/david-lutz/weewx-influx2

Is it possible that the influx2 code does not have this update that was 
made to the influx1 code?

On Monday, January 25, 2021 at 7:11:47 AM UTC-5 tke...@gmail.com wrote:

> Already done!
>
> https://github.com/matthewwall/weewx-influx/pull/27
>
> Thanks for testing it.
>
>
> On Sun, Jan 24, 2021 at 8:20 PM Tom Corbett  wrote:
>
>> This seems to have fixed my issues. Has been diligently putting data in 
>> every minute for over a week now. What's the protocol for adding a pull 
>> request to Matthew's github so that other Python 3 users don't have this 
>> issue? It was your change, but happy to do the pull request if it helps 
>> others.
>>
>> Tom
>>
>> On Thursday, January 14, 2021 at 4:17:34 PM UTC+11 Tom Corbett wrote:
>>
>>> Thanks very much. I have replaced the existing influx.py with your 
>>> version and restarted weewx. It is putting data into the InfluxDb, so 
>>> fingers crossed it keeps doing so.
>>>
>>> Cheers,
>>>
>>> Tom
>>>
>>> On Thursday, January 14, 2021 at 2:20:46 PM UTC+11 tke...@gmail.com 
>>> wrote:
>>>
 Normally, I don't deal with the influx driver, but Matthew is swamped 
 so I took a look.

 I believe the problem is that the driver was not completely ported to 
 Python 3. The HTTP response needs to be converted from a byte array to a 
 string before performing the find() operation.

 Try this version of influx.py 
 
 .

 -tk



 On Wed, Jan 13, 2021 at 5:52 PM Tom Corbett  
 wrote:

>
> Hi All,
>
> I'm new to weewx and  python in general so have been plugging away for 
> a couple of weeks getting everything setup and working.
>
> My hardware is an ecowitt WH9200 and I'm using weewx 4.2 on FreeBSD 
> which I setup using the py-setup method. I am capturing the data using 
> the 
> weewx-interceptor in listen mode. This all seems to be flowing fine into 
> the sqlite DB.
>
> I then have the weewx-influx extension sending data to an InfluxDB 
> every minute. This will work fine for several hours; ~ 11 hours being the 
> current record, but will crash with the following in the logs: My take on 
> that is that for some reason a string is being sent to Influx rather than 
> an integer or boolean, however I could be seeing the symptom rather than 
> the cause.
>
> To investigate I checked the record in the sqlite DB immediately after 
> the last one in the InfluxDB, ie the one that caused the crash, and could 
> see nothing that looked different to all the previous one. IE, I couldn't 
> see any strings in the record.
>
> Any help would be appreciated in tracking this down. I'm a bit 
> perplexed as to why it runs happily for hours then has a coniption.
>
> Thanks,
>
> Tom
>
> Here's the relevent section of weewx.conf, nothing too interesting 
> AFAIK.
>
> [[Influx]]
> database = weewx_hades_test
> host = 192.168.178.25
> unit_system = METRICWX
>
> Logs: 
>
> Jan 14 10:54:45 28spots kernel: Jan 14 10:54:45 28spots weewx[964] 
> ERROR weewx.restx: Influx: Unexpected exception of type  'TypeError'>
>
> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
> ERROR weewx.restx: *** Traceback (most recent call last):
>
> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
> ERROR weewx.restx: ***   File "/usr/home/weewx/bin/weewx/restx.py", 
> line 475, in post_with_retries
>
> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
> ERROR weewx.restx: *** _response = self.post_request(request, 
> data)
>
> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
> ERROR weewx.restx: ***   File "/usr/home/weewx/bin/user/influx.py", 
> line 498, in post_request
>
> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
> ERROR weewx.restx: *** return super(InfluxThread, 
> self).post_request(request, payload)
>
> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
> ERROR weewx.restx: ***   File "/usr/home/weewx/bin/weewx/restx.py", 
> line 537, in post_request
>
> Jan 14 10:54:47 28spots kernel: Jan 14 10:54:47 28spots weewx[964] 
> ERROR weewx.restx: *** _response = 
> urllib.request.urlopen(request, data=data_bytes, timeout=self.timeout)
>>

Re: [weewx-user] Linux Lite 64 bit -- will it run weewx?

[Tom Keffer]

Should not be a problem. Its major difference from the standard Ubuntu is
the lighter weight desktop environment.


On Thu, Dec 30, 2021 at 1:09 AM H Riley  wrote:

> I think it will because it's a flavor of Ubuntu.   I have never used LL64
> and have never tried to install Weewx before under any OS.
>
> Hank
>
> --
> 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 visit
> https://groups.google.com/d/msgid/weewx-user/5879a022-6a5f-48e9-b7f6-31dbf8f8ce6an%40googlegroups.com
> 
> .
>

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECo%3DuW%3Dv-UM2Ns9Ok2e9%2Ba3rjO_vEhyoQ_iONeGbBGq5A%40mail.gmail.com.

[weewx-user] Linux Lite 64 bit -- will it run weewx?

[H Riley]

I think it will because it's a flavor of Ubuntu.   I have never used LL64 
and have never tried to install Weewx before under any OS.

Hank

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/5879a022-6a5f-48e9-b7f6-31dbf8f8ce6an%40googlegroups.com.