[weewx-user] WH65B no pressure

[Zsolt Máté]

Hi everyone,
I recently purchased a PWS in NZ, model number XC0370.
As far as I can tell it's a Chinese clone of the WS2902.
rtl_433 it identifies it as Fine Offset WH65B reporting only the following 
values:

{"time" : "2019-01-01 05:06:08", "model" : "Fine Offset WH65B", "id" : 70, 
"temperature_C" : 27.000, "humidity" : 51, "wind_dir_deg" : 330, 
"wind_speed_ms" : 2.741, "gust_speed_ms" : 4.080, "rainfall_mm" : 10.668, 
"uv" : 1400, "uvi" : 3, "light_lux" : 45337.000, "battery" : "OK", "mic" : 
"CRC"}

Is there a way to get the barometer readout as well?


-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Zsolt Máté]

I'm getting the following error. Am I missing a path or something? 

> Using configuration file /etc/weewx/weewx.conf
> Generating for all time
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> obj.start()
>   File "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> self.run()
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
> ngen = self.generate(gen_dict[section_name], self.gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> ngen += self.generate(section[subsection], gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> ngen += self.generate(section[subsection], gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
> default_binding)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in 
> _getSearchList
> searchList += obj.get_extension_list(timespan, db_lookup)
>   File "/usr/share/weewx/user/belchertown.py", line 297, in 
> get_extension_list
> year_rainiest_month_tuple = (year_rainiest_month_query[1], rain_unit, 
> 'group_rain')
> TypeError: 'NoneType' object has no attribute '__getitem__'
> Traceback (most recent call last):
>   File "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> obj.start()
>   File "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> self.run()
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
> ngen = self.generate(gen_dict[section_name], self.gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> ngen += self.generate(section[subsection], gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> ngen += self.generate(section[subsection], gen_ts)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
> default_binding)
>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in 
> _getSearchList
> searchList += obj.get_extension_list(timespan, db_lookup)
>   File "/usr/share/weewx/user/belchertown.py", line 297, in 
> get_extension_list
> year_rainiest_month_tuple = (year_rainiest_month_query[1], rain_unit, 
> 'group_rain')
> TypeError: 'NoneType' object has no attribute '__getitem__'
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WH65B no pressure

[Zsolt Máté]

I ran tcpdump on my router an I got this:
GET 
/weatherstation/updateweatherstation.php?ID=*==72.5=64.4=59.7=64.4=52=85=0.0=0.0=198=29.63=29.60=0.00=0.00=0.31=0.00=0.00=0=2019-1-1%2011:38:47=EasyWeatherV1.2.3=updateraw=1=5
 
HTTP/1.0

The question is, how can I intercept and interpret this communication from 
my raspi?

On Wednesday, January 2, 2019 at 12:32:34 AM UTC+13, Zsolt Máté wrote:
>
> The console has no USB port, it's communicating via WiFi.
>
> On Tuesday, January 1, 2019 at 8:05:28 PM UTC+13, mwall wrote:
>>
>>
>>
>> On Tuesday, January 1, 2019 at 12:10:46 AM UTC-5, Zsolt Máté wrote:
>>>
>>>
>>> Is there a way to get the barometer readout as well?
>>>
>>
>> not using rtl_433/weewx-sdr.  the pressure sensor is located in your 
>> weather station console, so the pressure data are never sent.  rtl_433 
>> picks up only the transmissions from the instrument cluster (and any remote 
>> temperature/humidity sensors), not the console.
>>
>> you'll have to intercept the data sent by the console (e.g., using the 
>> weewx-interceptor driver) or figure out some way to probe the console for 
>> data (does it have a usb port that responds to data requests?)
>>
>> m 
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WH65B no pressure

[Zsolt Máté]

The console has no USB port, it's communicating via WiFi.

On Tuesday, January 1, 2019 at 8:05:28 PM UTC+13, mwall wrote:
>
>
>
> On Tuesday, January 1, 2019 at 12:10:46 AM UTC-5, Zsolt Máté wrote:
>>
>>
>> Is there a way to get the barometer readout as well?
>>
>
> not using rtl_433/weewx-sdr.  the pressure sensor is located in your 
> weather station console, so the pressure data are never sent.  rtl_433 
> picks up only the transmissions from the instrument cluster (and any remote 
> temperature/humidity sensors), not the console.
>
> you'll have to intercept the data sent by the console (e.g., using the 
> weewx-interceptor driver) or figure out some way to probe the console for 
> data (does it have a usb port that responds to data requests?)
>
> m 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WH65B no pressure

[Zsolt Máté]

I tried, something is not working or I'm doing something wrong.

On Wednesday, January 2, 2019 at 12:53:42 AM UTC+13, Andrew Milner wrote:
>
> with the interceptor driver
>
>
>
> On Tuesday, 1 January 2019 13:42:18 UTC+2, Zsolt Máté wrote:
>>
>> I ran tcpdump on my router an I got this:
>> GET 
>> /weatherstation/updateweatherstation.php?ID=*==72.5=64.4=59.7=64.4=52=85=0.0=0.0=198=29.63=29.60=0.00=0.00=0.31=0.00=0.00=0=2019-1-1%2011:38:47=EasyWeatherV1.2.3=updateraw=1=5
>>  
>> HTTP/1.0
>>
>> The question is, how can I intercept and interpret this communication 
>> from my raspi?
>>
>> On Wednesday, January 2, 2019 at 12:32:34 AM UTC+13, Zsolt Máté wrote:
>>>
>>> The console has no USB port, it's communicating via WiFi.
>>>
>>> On Tuesday, January 1, 2019 at 8:05:28 PM UTC+13, mwall wrote:
>>>>
>>>>
>>>>
>>>> On Tuesday, January 1, 2019 at 12:10:46 AM UTC-5, Zsolt Máté wrote:
>>>>>
>>>>>
>>>>> Is there a way to get the barometer readout as well?
>>>>>
>>>>
>>>> not using rtl_433/weewx-sdr.  the pressure sensor is located in your 
>>>> weather station console, so the pressure data are never sent.  rtl_433 
>>>> picks up only the transmissions from the instrument cluster (and any 
>>>> remote 
>>>> temperature/humidity sensors), not the console.
>>>>
>>>> you'll have to intercept the data sent by the console (e.g., using the 
>>>> weewx-interceptor driver) or figure out some way to probe the console for 
>>>> data (does it have a usb port that responds to data requests?)
>>>>
>>>> m 
>>>>
>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Interceptor setup

[Zsolt Máté]

Thanks, I was running it with sudo.

On Saturday, January 5, 2019 at 4:17:32 PM UTC+13, Scott Grayban wrote:
>
> Run that as root
> On Jan 4, 2019, at 7:15 PM, "Zsolt Máté" > 
> wrote:
>>
>> I can't execute sudo iptables-save > /etc/iptables.ipv4.nat
>> It returns:  -bash: /etc/iptables.ipv4.nat: Permission denied
>>
>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Interceptor setup

[Zsolt Máté]

I can't execute sudo iptables-save > /etc/iptables.ipv4.nat
It returns:  -bash: /etc/iptables.ipv4.nat: Permission denied

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Interceptor setup

[Zsolt Máté]

The issue is not the eth0, that I've reserved in my router.
The problem could be the indoor unit, that connects to wlan0 and receives 
the 10.*.*.* IP address.

On Sunday, January 6, 2019 at 12:24:48 PM UTC+13, Scott Grayban wrote:
>
> Glad you got it working !!
>
> Most routers have reserve DHCP settings. So I'm sure yours does also.
>
> On Saturday, January 5, 2019 at 3:18:33 PM UTC-8, Zsolt Máté wrote:
>>
>> That's what I'm researching right now.
>>
>> On Sunday, January 6, 2019 at 12:11:31 PM UTC+13, Scott Grayban wrote:
>>>
>>> Use reserved DHCP then.
>>>
>>> On Saturday, January 5, 2019 at 3:09:42 PM UTC-8, Zsolt Máté wrote:
>>>>
>>>> If you're asking me, yes, I did. After reading your reply, I switched 
>>>> to su and ran the command as root. Tanks for the tutorial.
>>>>
>>>> The only thing I don't like (but I can live with it) is the DHCP. In 
>>>> case the indoor unit looses DC power for any reason, it may receive a new 
>>>> IP address. Then someone has to either sniff the network for the new IP or 
>>>> log into the Pi to find it out.
>>>>
>>>> On Sunday, January 6, 2019 at 9:15:31 AM UTC+13, Scott Grayban wrote:
>>>>>
>>>>> Did you get it working ?
>>>>>
>>>>> On Friday, January 4, 2019 at 7:21:17 PM UTC-8, Zsolt Máté wrote:
>>>>>>
>>>>>> Thanks, I was running it with sudo.
>>>>>>
>>>>>> On Saturday, January 5, 2019 at 4:17:32 PM UTC+13, Scott Grayban 
>>>>>> wrote:
>>>>>>>
>>>>>>> Run that as root
>>>>>>> On Jan 4, 2019, at 7:15 PM, "Zsolt Máté"  wrote:
>>>>>>>>
>>>>>>>> I can't execute sudo iptables-save > /etc/iptables.ipv4.nat
>>>>>>>> It returns:  -bash: /etc/iptables.ipv4.nat: Permission denied
>>>>>>>>
>>>>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Interceptor setup

[Zsolt Máté]

Good to know. Thanks for the information.

On Sunday, January 6, 2019 at 2:38:32 PM UTC+13, Scott Grayban wrote:
>
> Oh that IP for the LAN with hotsapd won't change. So your weather 
> station won't get a new IP on the 10.x network.
>
>
> On Saturday, January 5, 2019 at 5:34:57 PM UTC-8, Zsolt Máté wrote:
>>
>> The issue is not the eth0, that I've reserved in my router.
>> The problem could be the indoor unit, that connects to wlan0 and receives 
>> the 10.*.*.* IP address.
>>
>> On Sunday, January 6, 2019 at 12:24:48 PM UTC+13, Scott Grayban wrote:
>>>
>>> Glad you got it working !!
>>>
>>> Most routers have reserve DHCP settings. So I'm sure yours does also.
>>>
>>> On Saturday, January 5, 2019 at 3:18:33 PM UTC-8, Zsolt Máté wrote:
>>>>
>>>> That's what I'm researching right now.
>>>>
>>>> On Sunday, January 6, 2019 at 12:11:31 PM UTC+13, Scott Grayban wrote:
>>>>>
>>>>> Use reserved DHCP then.
>>>>>
>>>>> On Saturday, January 5, 2019 at 3:09:42 PM UTC-8, Zsolt Máté wrote:
>>>>>>
>>>>>> If you're asking me, yes, I did. After reading your reply, I switched 
>>>>>> to su and ran the command as root. Tanks for the tutorial.
>>>>>>
>>>>>> The only thing I don't like (but I can live with it) is the DHCP. In 
>>>>>> case the indoor unit looses DC power for any reason, it may receive a 
>>>>>> new 
>>>>>> IP address. Then someone has to either sniff the network for the new IP 
>>>>>> or 
>>>>>> log into the Pi to find it out.
>>>>>>
>>>>>> On Sunday, January 6, 2019 at 9:15:31 AM UTC+13, Scott Grayban wrote:
>>>>>>>
>>>>>>> Did you get it working ?
>>>>>>>
>>>>>>> On Friday, January 4, 2019 at 7:21:17 PM UTC-8, Zsolt Máté wrote:
>>>>>>>>
>>>>>>>> Thanks, I was running it with sudo.
>>>>>>>>
>>>>>>>> On Saturday, January 5, 2019 at 4:17:32 PM UTC+13, Scott Grayban 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Run that as root
>>>>>>>>> On Jan 4, 2019, at 7:15 PM, "Zsolt Máté"  wrote:
>>>>>>>>>>
>>>>>>>>>> I can't execute sudo iptables-save > /etc/iptables.ipv4.nat
>>>>>>>>>> It returns:  -bash: /etc/iptables.ipv4.nat: Permission denied
>>>>>>>>>>
>>>>>>>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Interceptor setup

[Zsolt Máté]

If you're asking me, yes, I did. After reading your reply, I switched to su 
and ran the command as root. Tanks for the tutorial.

The only thing I don't like (but I can live with it) is the DHCP. In case 
the indoor unit looses DC power for any reason, it may receive a new IP 
address. Then someone has to either sniff the network for the new IP or log 
into the Pi to find it out.

On Sunday, January 6, 2019 at 9:15:31 AM UTC+13, Scott Grayban wrote:
>
> Did you get it working ?
>
> On Friday, January 4, 2019 at 7:21:17 PM UTC-8, Zsolt Máté wrote:
>>
>> Thanks, I was running it with sudo.
>>
>> On Saturday, January 5, 2019 at 4:17:32 PM UTC+13, Scott Grayban wrote:
>>>
>>> Run that as root
>>> On Jan 4, 2019, at 7:15 PM, "Zsolt Máté"  wrote:
>>>>
>>>> I can't execute sudo iptables-save > /etc/iptables.ipv4.nat
>>>> It returns:  -bash: /etc/iptables.ipv4.nat: Permission denied
>>>>
>>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] can not install paho-mqtt

[Zsolt Máté]

I'm trying to set up weewx with mqtt, but my installation fails with paho

sudo: pip: command not found

tried installing it with pip3, it installs, but weewx crashes with the 
following log:

Jan 24 12:57:24 raspberrypi weewx[7712]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
Jan 24 12:57:24 raspberrypi weewx[7712]:   
self.loadServices(config_dict)
Jan 24 12:57:24 raspberrypi weewx[7712]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
Jan 24 12:57:24 raspberrypi weewx[7712]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
Jan 24 12:57:24 raspberrypi weewx[7712]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1132, in _get_object
Jan 24 12:57:24 raspberrypi weewx[7712]:   mod = 
__import__(module)
Jan 24 12:57:24 raspberrypi weewx[7712]: File 
"/usr/share/weewx/user/mqtt.py", line 63, in 
Jan 24 12:57:24 raspberrypi weewx[7712]:   import 
paho.mqtt.client as mqtt
Jan 24 12:57:24 raspberrypi weewx[7712]:   ImportError: No module 
named paho.mqtt.client
Jan 24 12:57:24 raspberrypi weewx[7712]:   Exiting.

Any help is appreciated.
Thanks.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: can not install paho-mqtt

[Zsolt Máté]

damn, I was trying with apt-get install pip and not python-pip.
Thanks a lot.

On Thursday, January 24, 2019 at 1:16:06 PM UTC+13, vince wrote:
>
> On Wednesday, January 23, 2019 at 3:59:04 PM UTC-8, Zsolt Máté wrote:
>>
>> I'm trying to set up weewx with mqtt, but my installation fails with paho
>>
>> sudo: pip: command not found
>>
>>
> install the pip package for your operating system
> command is likely 'sudo apt-get install python-pip'
>
>  
>
>> tried installing it with pip3, it installs, but weewx crashes with the 
>> following log:
>>
>>
> weewx uses python2 not python3, so you need 'pip' not 'pip3'
>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Zsolt Máté]

I can't get the MQTT work.
weewx is plublishing the values via MQTT but the skin is failing to connect 
and get the data.
I have to mention that I'm using hassio's MQTT broker.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown skin for weewx now available!

[Zsolt Máté]

Now I just have to find out how to enable or to connect to hassio 
websockets.

On Monday, January 28, 2019 at 4:45:10 AM UTC+13, Pat wrote:
>
> The skin uses mqtt websockets to connect. Make sure websockets is 
> available and the skin is configured to use it. 
>
> On Sunday, January 27, 2019 at 10:43:58 AM UTC-5, Johannes Ebner wrote:
>>
>>
>>
>> Am Donnerstag, 24. Januar 2019 07:59:16 UTC+1 schrieb Zsolt Máté:
>>>
>>> I can't get the MQTT work.
>>> weewx is plublishing the values via MQTT but the skin is failing to 
>>> connect and get the data.
>>> I have to mention that I'm using hassio's MQTT broker.
>>>
>>
>> Hi, I have the same issue. IT just says "connecting". I am using an 
>> UnRaid Docker for MQTT. If testing with public Websocket Clients I can 
>> connect. 
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Interceptor setup

[Zsolt Máté]

Anyone having issues with this?
I had a power outage a few days ago and ever since I can't get hostapd to 
work/start.
Somehow my wlan0 is not starting up and not broadcasting it's SSID anymore.

-- 
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/ee380b93-3f09-4a0c-8385-aa34a483%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Interceptor setup

[Zsolt Máté]

To be honest, I can't find anything related to hostapd in the logs.
sudo cat /var/log/syslog | grep hostapd returns nothing.
If I search my archived logs I can see the handshakes, etc, but nothing in 
my latest ones.

On Thursday, June 6, 2019 at 4:48:51 PM UTC+12, Scott Grayban wrote:
>
> Have you looked at the logs when starting hostapd? 
> On Jun 5, 2019, at 9:24 PM, "Zsolt Máté" > 
> wrote:
>>
>> Anyone having issues with this?
>> I had a power outage a few days ago and ever since I can't get hostapd to 
>> work/start.
>> Somehow my wlan0 is not starting up and not broadcasting it's SSID 
>> anymore.
>>
>>

-- 
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/0a4bb20d-b1a2-499a-9351-bd657e0d95a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Interceptor setup

[Zsolt Máté]

Reinstalling hostapd solved the issue.

On Thursday, June 6, 2019 at 4:57:26 PM UTC+12, Zsolt Máté wrote:
>
> To be honest, I can't find anything related to hostapd in the logs.
> sudo cat /var/log/syslog | grep hostapd returns nothing.
> If I search my archived logs I can see the handshakes, etc, but nothing in 
> my latest ones.
>
> On Thursday, June 6, 2019 at 4:48:51 PM UTC+12, Scott Grayban wrote:
>>
>> Have you looked at the logs when starting hostapd? 
>> On Jun 5, 2019, at 9:24 PM, "Zsolt Máté"  wrote:
>>>
>>> Anyone having issues with this?
>>> I had a power outage a few days ago and ever since I can't get hostapd 
>>> to work/start.
>>> Somehow my wlan0 is not starting up and not broadcasting it's SSID 
>>> anymore.
>>>
>>>

-- 
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/bc79d274-9d5d-4b1e-93fc-0c69800bc221%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

docker network ls returns:
Enter code here...NETWORK ID  NAMEDRIVER   
   SCOPE
416109297adbbridge  bridge  local
6bad4fea28c7hosthostlocal
05ffebe199bcnonenulllocal

First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
The one in /network returns
docker@docker:~/weewx/network$ docker-compose up -d
WARNING: Some networks were defined but are not used by any service: 
macvlan_network

the one in weewx is complaining that the network is not there, which is 
correct.
docker@docker:~/weewx$ docker-compose up -d
ERROR: Network macvlan_macvlan_network declared as external, but could not 
be found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.





On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>
> You have to run two "docker-compose up -d":
> - One in the network directory
> - One in the weewx directory
>
> Can you check you networks with "docker network ls"?
> Then maybe you shall adapt the weewx docker-compose with the given name of 
> the network
>
> Le 14/04/2020 02:05:10, Zsolt Máté > a 
> écrit :
> Yes, I did.
> networks:
>   macvlan_macvlan_network:
> external: true
> I renamed the file to docker-compose.yml, as well
>
>
> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>>
>> Hi, 
>>
>> Did you specify the network at the end of the docker-compose?
>> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>>
>> networks:
>> macvlan_macvlan_network:
>> external: true
>>
>> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
>> Hi Bruno.
>> I'm getting an error while setting up my network.
>>
>> WARNING: Some networks were defined but are not used by any service: 
>> macvlan_network
>> Attaching to
>>
>> My docker compose looks like this:
>> version: '2'
>> networks:
>>   macvlan_network:
>> driver: macvlan
>> driver_opts:
>>   parent: ens18
>> ipam:
>>   config:
>> - subnet: 192.168.2.0/24
>>   gateway: 192.168.2.1
>>   ip_range: 192.168.2.240/28
>>
>> my network interfaces are:
>> docker@docker:~/weewx/network$ ifconfig -s -a
>> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP 
>> TX-OVR Flg
>> docker0   150010611  0  0 0 18836  0  0  
>> 0 BMRU
>> ens18 1500   434686  0 67 0 24242  0  0  
>> 0 BMRU
>> lo   65536  190  0  0 0   190  0  0  
>> 0 LRU
>> veth1a31  1500 1299  0  0 0  1680  0  0  
>> 0 BMRU
>>
>> Do you have an idea what am I doing wrong?
>>
>>
>> On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>>>
>>> Dear weewx users.
>>>
>>> After dozens hours of researches and tries, I'm proud to provide my own 
>>> docker image of weewx. 
>>>
>>> It runs on Debian stretch, build from sources, with the interceptor 
>>> driver and neowx skin.
>>>
>>> I use it with Pihole to grab the data.
>>> Everything (I hope) is written in the repo you can find here: 
>>> https://github.com/MrNonoss/WeewX-Docker
>>>
>>> Feel free to review and comment it. 
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>

-- 
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/96c7213f-baf8-4cc1-a968-054292e59a74%40googlegroups.com.

Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

I ran docker create network manually
docker@docker:~/weewx$ docker network create macvlan_macvlan_network
e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
Now running docker-compose -d in /weewx returns:
docker@docker:~/weewx$ docker-compose up -d
Starting weewx-core ...
Starting weewx-core ... error

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets

ERROR: for weewx-core  user specified IP address is supported only when 
connecting to networks with user configured subnets
ERROR: Encountered errors while bringing up the project.




On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>
> Well, that's weird...
> I would try to manually create the network.
>
> But it's what I used on my setup, so...
> Please let me know if it works
>
> Le 14/04/2020 02:39:10, Zsolt Máté > a 
> écrit :
> docker network ls returns:
> Enter code here...NETWORK ID  NAMEDRIVER 
>  SCOPE
> 416109297adbbridge  bridge  local
> 6bad4fea28c7hosthostlocal
> 05ffebe199bcnonenulllocal
>
> First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
> The one in /network returns
> docker@docker:~/weewx/network$ docker-compose up -d
> WARNING: Some networks were defined but are not used by any service: 
> macvlan_network
>
> the one in weewx is complaining that the network is not there, which is 
> correct.
> docker@docker:~/weewx$ docker-compose up -d
> ERROR: Network macvlan_macvlan_network declared as external, but could not 
> be found. Please create the network manually using `docker network create 
> macvlan_macvlan_network` and try again.
>
>
>
>
>
> On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>>
>> You have to run two "docker-compose up -d":
>> - One in the network directory
>> - One in the weewx directory
>>
>> Can you check you networks with "docker network ls"?
>> Then maybe you shall adapt the weewx docker-compose with the given name 
>> of the network
>>
>> Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
>> Yes, I did.
>> networks:
>>   macvlan_macvlan_network:
>> external: true
>> I renamed the file to docker-compose.yml, as well
>>
>>
>> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> Hi, 
>>>
>>> Did you specify the network at the end of the docker-compose?
>>> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>>>
>>> networks:
>>> macvlan_macvlan_network:
>>> external: true
>>>
>>> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
>>> Hi Bruno.
>>> I'm getting an error while setting up my network.
>>>
>>> WARNING: Some networks were defined but are not used by any service: 
>>> macvlan_network
>>> Attaching to
>>>
>>> My docker compose looks like this:
>>> version: '2'
>>> networks:
>>>   macvlan_network:
>>> driver: macvlan
>>> driver_opts:
>>>   parent: ens18
>>> ipam:
>>>   config:
>>> - subnet: 192.168.2.0/24
>>>   gateway: 192.168.2.1
>>>   ip_range: 192.168.2.240/28
>>>
>>> my network interfaces are:
>>> docker@docker:~/weewx/network$ ifconfig -s -a
>>> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP 
>>> TX-OVR Flg
>>> docker0   150010611  0  0 0 18836  0  0  
>>> 0 BMRU
>>> ens18 1500   434686  0 67 0 24242  0  0  
>>> 0 BMRU
>>> lo   65536  190  0  0 0   190  0  0  
>>> 0 LRU
>>> veth1a31  1500 1299  0  0 0  1680  0  0  
>>> 0 BMRU
>>>
>>> Do you have an idea what am I doing wrong?
>>>
>>>
>>> On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>>>>
>>>> Dear weewx users.
>>>>
>>>> After dozens hours of researches and tries, I'm proud to provide my own 
>>>> docker image of weewx. 
>>>>
>>>> It runs on Debian stretch, build from sources, with the interceptor 
>>>> driver and neowx skin.
>>>>
>>>> I use it with Pihole to grab the data.
>>>> Everything (I hope) is wri

[weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

Hi Bruno.
I'm getting an error while setting up my network.

WARNING: Some networks were defined but are not used by any service: 
macvlan_network
Attaching to

My docker compose looks like this:
version: '2'
networks:
  macvlan_network:
driver: macvlan
driver_opts:
  parent: ens18
ipam:
  config:
- subnet: 192.168.2.0/24
  gateway: 192.168.2.1
  ip_range: 192.168.2.240/28

my network interfaces are:
docker@docker:~/weewx/network$ ifconfig -s -a
Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR 
Flg
docker0   150010611  0  0 0 18836  0  0  0 
BMRU
ens18 1500   434686  0 67 0 24242  0  0  0 
BMRU
lo   65536  190  0  0 0   190  0  0  0 
LRU
veth1a31  1500 1299  0  0 0  1680  0  0  0 
BMRU

Do you have an idea what am I doing wrong?


On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>
> Dear weewx users.
>
> After dozens hours of researches and tries, I'm proud to provide my own 
> docker image of weewx. 
>
> It runs on Debian stretch, build from sources, with the interceptor driver 
> and neowx skin.
>
> I use it with Pihole to grab the data.
> Everything (I hope) is written in the repo you can find here: 
> https://github.com/MrNonoss/WeewX-Docker
>
> Feel free to review and comment it. 
>
>

-- 
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/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com.

Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

If I'm trying to run docker-compose in the weewx folder, I get this:
ERROR: Network macvlan_macvlan_network declared as external, but could not 
be found. Please create the network manually using `docker network create 
macvlan_macvlan_network` and try again.
Should I run "docker network create macvlan_macvlan_network" manually?

On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>
> Hi, 
>
> Did you specify the network at the end of the docker-compose?
> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>
> networks:
> macvlan_macvlan_network:
> external: true
>
> Le 14/04/2020 01:13:47, Zsolt Máté > a 
> écrit :
> Hi Bruno.
> I'm getting an error while setting up my network.
>
> WARNING: Some networks were defined but are not used by any service: 
> macvlan_network
> Attaching to
>
> My docker compose looks like this:
> version: '2'
> networks:
>   macvlan_network:
> driver: macvlan
> driver_opts:
>   parent: ens18
> ipam:
>   config:
> - subnet: 192.168.2.0/24
>   gateway: 192.168.2.1
>   ip_range: 192.168.2.240/28
>
> my network interfaces are:
> docker@docker:~/weewx/network$ ifconfig -s -a
> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR 
> Flg
> docker0   150010611  0  0 0 18836  0  0  0 
> BMRU
> ens18 1500   434686  0 67 0 24242  0  0  0 
> BMRU
> lo   65536  190  0  0 0   190  0  0  0 
> LRU
> veth1a31  1500 1299  0  0 0  1680  0  0  0 
> BMRU
>
> Do you have an idea what am I doing wrong?
>
>
> On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>>
>> Dear weewx users.
>>
>> After dozens hours of researches and tries, I'm proud to provide my own 
>> docker image of weewx. 
>>
>> It runs on Debian stretch, build from sources, with the interceptor 
>> driver and neowx skin.
>>
>> I use it with Pihole to grab the data.
>> Everything (I hope) is written in the repo you can find here: 
>> https://github.com/MrNonoss/WeewX-Docker
>>
>> Feel free to review and comment it. 
>>
>> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>

-- 
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/1a3dff8a-1459-42c0-88a4-1396c5c5774f%40googlegroups.com.

Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

I have portainer installed.
If you think It's faster, and you've got time, I can give you access to my 
system via SSH.

[image: 2020-04-14 13_17_06-Window.png]


On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
>
> I do use portainer to have a better view of my containers, images and 
> networks:
> https://www.portainer.io/installation/
>
> The install il very straigtforward:
>
> docker volume create portainer_data && docker run -d -p 8000:8000 -p 
> 9000:9000 --name=portainer --restart=always -v 
> /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data 
> portainer/portainer tf
>
> With this, you have a web page at localhost:9000 allowing you to monitor 
> and configure networks.
>
> I'm still trying to understant why you can't create network with compose
>
> Le 14/04/2020 03:07:29, Zsolt Máté > a 
> écrit :
> Well, I just ran that command, I have no docker knowledge.
> What can I do next?
>
> On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
>>
>> Yeah, probably because you didn't specify networks options, like iface, 
>> etc...
>>
>> Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
>> I ran docker create network manually
>> docker@docker:~/weewx$ docker network create macvlan_macvlan_network
>> e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
>> Now running docker-compose -d in /weewx returns:
>> docker@docker:~/weewx$ docker-compose up -d
>> Starting weewx-core ...
>> Starting weewx-core ... error
>>
>> ERROR: for weewx-core  user specified IP address is supported only when 
>> connecting to networks with user configured subnets
>>
>> ERROR: for weewx-core  user specified IP address is supported only when 
>> connecting to networks with user configured subnets
>> ERROR: Encountered errors while bringing up the project.
>>
>>
>>
>>
>> On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> Well, that's weird...
>>> I would try to manually create the network.
>>>
>>> But it's what I used on my setup, so...
>>> Please let me know if it works
>>>
>>> Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
>>> docker network ls returns:
>>> Enter code here...NETWORK ID  NAMEDRIVER   
>>>SCOPE
>>> 416109297adbbridge  bridge  local
>>> 6bad4fea28c7hosthostlocal
>>> 05ffebe199bcnonenulllocal
>>>
>>> First, "docker-compose d" has to be run in /weewx/network, then in 
>>> /weewx.
>>> The one in /network returns
>>> docker@docker:~/weewx/network$ docker-compose up -d
>>> WARNING: Some networks were defined but are not used by any service: 
>>> macvlan_network
>>>
>>> the one in weewx is complaining that the network is not there, which is 
>>> correct.
>>> docker@docker:~/weewx$ docker-compose up -d
>>> ERROR: Network macvlan_macvlan_network declared as external, but could 
>>> not be found. Please create the network manually using `docker network 
>>> create macvlan_macvlan_network` and try again.
>>>
>>>
>>>
>>>
>>>
>>> On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>>>>
>>>> You have to run two "docker-compose up -d":
>>>> - One in the network directory
>>>> - One in the weewx directory
>>>>
>>>> Can you check you networks with "docker network ls"?
>>>> Then maybe you shall adapt the weewx docker-compose with the given name 
>>>> of the network
>>>>
>>>> Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
>>>> Yes, I did.
>>>> networks:
>>>>   macvlan_macvlan_network:
>>>> external: true
>>>> I renamed the file to docker-compose.yml, as well
>>>>
>>>>
>>>> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>>>>>
>>>>> Hi, 
>>>>>
>>>>> Did you specify the network at the end of the docker-compose?
>>>>>
>>>>> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>>>>>
>>>>> networks:
>>>>> macvlan_macvlan_network:
>>>>> external: true
>>>>>
>>>>> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
>

Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

Yes, I did.
networks:
  macvlan_macvlan_network:
external: true
I renamed the file to docker-compose.yml, as well


On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>
> Hi, 
>
> Did you specify the network at the end of the docker-compose?
> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>
> networks:
> macvlan_macvlan_network:
> external: true
>
> Le 14/04/2020 01:13:47, Zsolt Máté > a 
> écrit :
> Hi Bruno.
> I'm getting an error while setting up my network.
>
> WARNING: Some networks were defined but are not used by any service: 
> macvlan_network
> Attaching to
>
> My docker compose looks like this:
> version: '2'
> networks:
>   macvlan_network:
> driver: macvlan
> driver_opts:
>   parent: ens18
> ipam:
>   config:
> - subnet: 192.168.2.0/24
>   gateway: 192.168.2.1
>   ip_range: 192.168.2.240/28
>
> my network interfaces are:
> docker@docker:~/weewx/network$ ifconfig -s -a
> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR 
> Flg
> docker0   150010611  0  0 0 18836  0  0  0 
> BMRU
> ens18 1500   434686  0 67 0 24242  0  0  0 
> BMRU
> lo   65536  190  0  0 0   190  0  0  0 
> LRU
> veth1a31  1500 1299  0  0 0  1680  0  0  0 
> BMRU
>
> Do you have an idea what am I doing wrong?
>
>
> On Monday, November 11, 2019 at 7:09:15 AM UTC+13, Bruno BORDAS wrote:
>>
>> Dear weewx users.
>>
>> After dozens hours of researches and tries, I'm proud to provide my own 
>> docker image of weewx. 
>>
>> It runs on Debian stretch, build from sources, with the interceptor 
>> driver and neowx skin.
>>
>> I use it with Pihole to grab the data.
>> Everything (I hope) is written in the repo you can find here: 
>> https://github.com/MrNonoss/WeewX-Docker
>>
>> Feel free to review and comment it. 
>>
>> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/Rr_XyWLONZ4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/2f63f6cb-5116-4f5c-98c2-d85bf7dc9892%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>

-- 
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/ae038e0b-2e57-4130-9bb0-8bc1314bcf12%40googlegroups.com.

Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

I've cloned your git into my home directory.
so it is /home/docker/weewx

Can I send you an email to this address with the ssh credentials?

On Tuesday, April 14, 2020 at 1:24:52 PM UTC+12, Bruno BORDAS wrote:
>
> But tell me where is your work directory
>
> Le 14/04/2020 03:23:04, Zsolt Máté > a 
> écrit :
> I can open a port to my portainer as well, that's not an issue. Just tell 
> me what you need.
>
> On Tuesday, April 14, 2020 at 1:20:50 PM UTC+12, Bruno BORDAS wrote:
>>
>> I won't have access to the portainer ui.
>> However, as you can notice, this network does not use the macvlan driver, 
>> but the bridge one.
>> This is probably why it does not work
>>
>> Le 14/04/2020 03:18:36, Zsolt Máté  a écrit :
>> I have portainer installed.
>> If you think It's faster, and you've got time, I can give you access to 
>> my system via SSH.
>>
>> [image: 2020-04-14 13_17_06-Window.png]
>>
>>
>> On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> I do use portainer to have a better view of my containers, images and 
>>> networks:
>>> https://www.portainer.io/installation/
>>>
>>> The install il very straigtforward:
>>>
>>> docker volume create portainer_data && docker run -d -p 8000:8000 -p 
>>> 9000:9000 --name=portainer --restart=always -v 
>>> /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data 
>>> portainer/portainer tf
>>>
>>> With this, you have a web page at localhost:9000 allowing you to monitor 
>>> and configure networks.
>>>
>>> I'm still trying to understant why you can't create network with compose
>>>
>>> Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
>>> Well, I just ran that command, I have no docker knowledge.
>>> What can I do next?
>>>
>>> On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
>>>>
>>>> Yeah, probably because you didn't specify networks options, like iface, 
>>>> etc...
>>>>
>>>> Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
>>>> I ran docker create network manually
>>>> docker@docker:~/weewx$ docker network create macvlan_macvlan_network
>>>> e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
>>>> Now running docker-compose -d in /weewx returns:
>>>> docker@docker:~/weewx$ docker-compose up -d
>>>> Starting weewx-core ...
>>>> Starting weewx-core ... error
>>>>
>>>> ERROR: for weewx-core  user specified IP address is supported only when 
>>>> connecting to networks with user configured subnets
>>>>
>>>> ERROR: for weewx-core  user specified IP address is supported only when 
>>>> connecting to networks with user configured subnets
>>>> ERROR: Encountered errors while bringing up the project.
>>>>
>>>>
>>>>
>>>>
>>>> On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>>>>>
>>>>> Well, that's weird...
>>>>> I would try to manually create the network.
>>>>>
>>>>> But it's what I used on my setup, so...
>>>>> Please let me know if it works
>>>>>
>>>>> Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
>>>>> docker network ls returns:
>>>>> Enter code here...NETWORK ID  NAMEDRIVER 
>>>>>  SCOPE
>>>>> 416109297adbbridge  bridge  local
>>>>> 6bad4fea28c7hosthostlocal
>>>>> 05ffebe199bcnonenulllocal
>>>>>
>>>>> First, "docker-compose d" has to be run in /weewx/network, then in 
>>>>> /weewx.
>>>>> The one in /network returns
>>>>> docker@docker:~/weewx/network$ docker-compose up -d
>>>>> WARNING: Some networks were defined but are not used by any service: 
>>>>> macvlan_network
>>>>>
>>>>> the one in weewx is complaining that the network is not there, which 
>>>>> is correct.
>>>>> docker@docker:~/weewx$ docker-compose up -d
>>>>> ERROR: Network macvlan_macvlan_network declared as external, but could 
>>>>> not be found. Please create the network manually using `docker network 
>>>>> create macvlan_macvlan_network` and try aga

Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

Well, I just ran that command, I have no docker knowledge.
What can I do next?

On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
>
> Yeah, probably because you didn't specify networks options, like iface, 
> etc...
>
> Le 14/04/2020 02:59:14, Zsolt Máté > a 
> écrit :
> I ran docker create network manually
> docker@docker:~/weewx$ docker network create macvlan_macvlan_network
> e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
> Now running docker-compose -d in /weewx returns:
> docker@docker:~/weewx$ docker-compose up -d
> Starting weewx-core ...
> Starting weewx-core ... error
>
> ERROR: for weewx-core  user specified IP address is supported only when 
> connecting to networks with user configured subnets
>
> ERROR: for weewx-core  user specified IP address is supported only when 
> connecting to networks with user configured subnets
> ERROR: Encountered errors while bringing up the project.
>
>
>
>
> On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>>
>> Well, that's weird...
>> I would try to manually create the network.
>>
>> But it's what I used on my setup, so...
>> Please let me know if it works
>>
>> Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
>> docker network ls returns:
>> Enter code here...NETWORK ID  NAMEDRIVER 
>>  SCOPE
>> 416109297adbbridge  bridge  local
>> 6bad4fea28c7hosthostlocal
>> 05ffebe199bcnonenulllocal
>>
>> First, "docker-compose d" has to be run in /weewx/network, then in /weewx.
>> The one in /network returns
>> docker@docker:~/weewx/network$ docker-compose up -d
>> WARNING: Some networks were defined but are not used by any service: 
>> macvlan_network
>>
>> the one in weewx is complaining that the network is not there, which is 
>> correct.
>> docker@docker:~/weewx$ docker-compose up -d
>> ERROR: Network macvlan_macvlan_network declared as external, but could 
>> not be found. Please create the network manually using `docker network 
>> create macvlan_macvlan_network` and try again.
>>
>>
>>
>>
>>
>> On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> You have to run two "docker-compose up -d":
>>> - One in the network directory
>>> - One in the weewx directory
>>>
>>> Can you check you networks with "docker network ls"?
>>> Then maybe you shall adapt the weewx docker-compose with the given name 
>>> of the network
>>>
>>> Le 14/04/2020 02:05:10, Zsolt Máté  a écrit :
>>> Yes, I did.
>>> networks:
>>>   macvlan_macvlan_network:
>>>     external: true
>>> I renamed the file to docker-compose.yml, as well
>>>
>>>
>>> On Tuesday, April 14, 2020 at 12:00:04 PM UTC+12, Bruno BORDAS wrote:
>>>>
>>>> Hi, 
>>>>
>>>> Did you specify the network at the end of the docker-compose?
>>>> https://github.com/MrNonoss/WeewX-Docker/blob/master/docker-compose0.yml
>>>>
>>>> networks:
>>>> macvlan_macvlan_network:
>>>> external: true
>>>>
>>>> Le 14/04/2020 01:13:47, Zsolt Máté  a écrit :
>>>> Hi Bruno.
>>>> I'm getting an error while setting up my network.
>>>>
>>>> WARNING: Some networks were defined but are not used by any service: 
>>>> macvlan_network
>>>> Attaching to
>>>>
>>>> My docker compose looks like this:
>>>> version: '2'
>>>> networks:
>>>>   macvlan_network:
>>>> driver: macvlan
>>>> driver_opts:
>>>>   parent: ens18
>>>> ipam:
>>>>   config:
>>>> - subnet: 192.168.2.0/24
>>>>   gateway: 192.168.2.1
>>>>   ip_range: 192.168.2.240/28
>>>>
>>>> my network interfaces are:
>>>> docker@docker:~/weewx/network$ ifconfig -s -a
>>>> Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP 
>>>> TX-OVR Flg
>>>> docker0   150010611  0  0 0 18836  0  0
>>>>   0 BMRU
>>>> ens18 1500   434686  0 67 0 24242  0  0
>>>>   0 BMRU
>>>> lo   65536  190  0  0 0   190  0  0
>>>>

Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : Re: Re : [weewx-user] Re: Docker image with interceptor driver and neowx skin

[Zsolt Máté]

I can open a port to my portainer as well, that's not an issue. Just tell 
me what you need.

On Tuesday, April 14, 2020 at 1:20:50 PM UTC+12, Bruno BORDAS wrote:
>
> I won't have access to the portainer ui.
> However, as you can notice, this network does not use the macvlan driver, 
> but the bridge one.
> This is probably why it does not work
>
> Le 14/04/2020 03:18:36, Zsolt Máté > a 
> écrit :
> I have portainer installed.
> If you think It's faster, and you've got time, I can give you access to my 
> system via SSH.
>
> [image: 2020-04-14 13_17_06-Window.png]
>
>
> On Tuesday, April 14, 2020 at 1:12:01 PM UTC+12, Bruno BORDAS wrote:
>>
>> I do use portainer to have a better view of my containers, images and 
>> networks:
>> https://www.portainer.io/installation/
>>
>> The install il very straigtforward:
>>
>> docker volume create portainer_data && docker run -d -p 8000:8000 -p 
>> 9000:9000 --name=portainer --restart=always -v 
>> /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data 
>> portainer/portainer tf
>>
>> With this, you have a web page at localhost:9000 allowing you to monitor 
>> and configure networks.
>>
>> I'm still trying to understant why you can't create network with compose
>>
>> Le 14/04/2020 03:07:29, Zsolt Máté  a écrit :
>> Well, I just ran that command, I have no docker knowledge.
>> What can I do next?
>>
>> On Tuesday, April 14, 2020 at 1:03:03 PM UTC+12, Bruno BORDAS wrote:
>>>
>>> Yeah, probably because you didn't specify networks options, like iface, 
>>> etc...
>>>
>>> Le 14/04/2020 02:59:14, Zsolt Máté  a écrit :
>>> I ran docker create network manually
>>> docker@docker:~/weewx$ docker network create macvlan_macvlan_network
>>> e3550d13e1334022c28620d71a6aaf8182b6ef1cea33ac279456c16b55267832
>>> Now running docker-compose -d in /weewx returns:
>>> docker@docker:~/weewx$ docker-compose up -d
>>> Starting weewx-core ...
>>> Starting weewx-core ... error
>>>
>>> ERROR: for weewx-core  user specified IP address is supported only when 
>>> connecting to networks with user configured subnets
>>>
>>> ERROR: for weewx-core  user specified IP address is supported only when 
>>> connecting to networks with user configured subnets
>>> ERROR: Encountered errors while bringing up the project.
>>>
>>>
>>>
>>>
>>> On Tuesday, April 14, 2020 at 12:45:09 PM UTC+12, Bruno BORDAS wrote:
>>>>
>>>> Well, that's weird...
>>>> I would try to manually create the network.
>>>>
>>>> But it's what I used on my setup, so...
>>>> Please let me know if it works
>>>>
>>>> Le 14/04/2020 02:39:10, Zsolt Máté  a écrit :
>>>> docker network ls returns:
>>>> Enter code here...NETWORK ID  NAMEDRIVER   
>>>>SCOPE
>>>> 416109297adbbridge  bridge  local
>>>> 6bad4fea28c7hosthostlocal
>>>> 05ffebe199bcnonenulllocal
>>>>
>>>> First, "docker-compose d" has to be run in /weewx/network, then in 
>>>> /weewx.
>>>> The one in /network returns
>>>> docker@docker:~/weewx/network$ docker-compose up -d
>>>> WARNING: Some networks were defined but are not used by any service: 
>>>> macvlan_network
>>>>
>>>> the one in weewx is complaining that the network is not there, which is 
>>>> correct.
>>>> docker@docker:~/weewx$ docker-compose up -d
>>>> ERROR: Network macvlan_macvlan_network declared as external, but could 
>>>> not be found. Please create the network manually using `docker network 
>>>> create macvlan_macvlan_network` and try again.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tuesday, April 14, 2020 at 12:32:04 PM UTC+12, Bruno BORDAS wrote:
>>>>>
>>>>> You have to run two "docker-compose up -d":
>>>>> - One in the network directory
>>>>> - One in the weewx directory
>>>>>
>>>>> Can you check you networks with "docker network ls"?
>>>>> Then maybe you shall adapt the weewx docker-compose with the given 
>>>>> name of the network
>>>>>
>>>>> Le 14/04/2020 02:05:10, Zsolt Máté

[weewx-user] GUI date/time and current conditions frozen

[Zsolt Máté]

My current conditions are "frozen".

Date is waaay in the future. I'm located in NZ, local time/date is 4:47PM, 
the 21st of May.
Since we're UTC-12, nobody passed the dateline yet.

I've checkt the date/time and timezone and these are correct on my server.

The graphs are correct.

What could cause this?

[image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
I'm running weewx 4.0.0 and capturing my data using interceptor.

-- 
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/415a838d-8a59-44be-9679-d72cce319c7d%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Tried, twice.

On Thursday, May 21, 2020 at 8:54:18 PM UTC+12, gjr80 wrote:
>
> Just force all your plots to be regenerated by deleting them from your 
> WeeWX machine.
>
> Gary
>

-- 
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/116a2884-3258-431d-b03e-a5a648087bd1%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

It looks like I messed up something. I've deleted the two rows from the 
"future", but now weewx wont start.
root@weewx:~# service weewx restart
root@weewx:~# tail -f /var/log/syslog
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 158, in run
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.STARTUP))
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   
callback(event)
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 522, in startup
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   _nrecs, 
_ndays = dbmanager.backfill_day_summary()
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 1012, in backfill_day_summary
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   
timestamp_to_string(lastRecord)))
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   
ViolatedPrecondition: lastUpdate(2020-05-22 06:00:00 NZST (1590084000)) > 
lastRecord(2020-05-21 19:00:00 NZST (1590044400))
May 21 20:30:32 weewx weewx[8599] CRITICAL __main__:   Exiting.


On Thursday, May 21, 2020 at 8:22:31 PM UTC+12, gjr80 wrote:
>
> Brain fade on my part, I should have tweaked earlier. I would go in and 
> delete the future records from the archive then rebuild the daily 
> summaries. You could just let it be and it will (seemingly) fix itself come 
> 6am tomorrow (albeit with a couple of duplicate index errors in the log) 
> but those bogus records will remain.
>
> Gary
>

-- 
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/f7ffb497-286f-47da-bb8d-37215eebdfa6%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Nice catch.
I'm using mysql as database. Via phpmyadmin I've managed to sort the 
database to date, max is 1590084000, converted:
GMT: Thursday, 21 May 2020 6:00:00 PM
Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00
Relative: In 10 hours

On Thursday, May 21, 2020 at 7:32:26 PM UTC+12, gjr80 wrote:
>
> Aha, look at your wind direction and wind vector plots, you have a wind 
> direction dot at midnight and likewise a vector. Are you using SQLite? If 
> so try the following (you may have to install the sqlite3 package first if 
> sqlite3 is not found - just use sudo apt-get install sqlite3):
>
> $ sqlite /var/lib/weewx/weewx.sdb
> > SELECT MAX(datetime(dateTime,'unixepoch','localtime')) FROM archive;
>
> (.q to exit the sqlite3 command prompt)
>
> What does that show?
>
> Gary
>
>
> I suspect There will be a data point in your archive for direction 
>
> On Thursday, 21 May 2020 16:43:47 UTC+10, Zsolt Máté wrote:
>>
>> I've ruled out browser cache. Tested on multiple devices within my 
>> network and even asked friends abroad to test. You can give it a try, as 
>> well. https://weather.zmate.nz
>>
>> 1. 22nd of May, 12:00:00 is not changing.
>> 2. I've deleted the contents of the www and it has been automatically 
>> regenerated, without forcing it.
>> 3. plots are being generated correctly, and the hour/minute looks correct.
>> 4. the timestamp below the plots is showing 05/22/2020 12:00:00 AM - good 
>> that you asked.
>> On Thursday, May 21, 2020 at 6:13:44 PM UTC+12, gjr80 wrote:
>>>
>>> Thanks, that is bizarre, I expectedt to see something in the log about 
>>> record timestamps being less than the last, but no everything is normal. 
>>> Archive records are bing generated with the correct timestamps, reports are 
>>> being generated without issue. I can't see it being a browser cache issue, 
>>> it would be stuck in the past not the future. A few (random) things to 
>>> check:
>>>
>>> 1. does the time change or is it always 22 May 00:00 (guessing it stays 
>>> put).
>>> 2. is the Seasons skin index.html file being generated every 5 minutes 
>>> (ie does its timestamp change) (again guessing it does as Seasons should 
>>> generate eight report files each report cycle and that is what it is doing)
>>> 3. do the current observations on the Seasons page change and are they 
>>> correct.
>>> 4. do the timestamps below the plots on the Seasons 'Day' tab show the 
>>> correct current time.
>>>
>>> Gary
>>>
>>> On Thursday, 21 May 2020 15:44:02 UTC+10, Zsolt Máté wrote:
>>>>
>>>> Thanks for the fast reply Gary.
>>>> Here's the log -> https://pastebin.com/4zNJEJea
>>>>
>>>> On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Could be any one of a number of causes, should be easily diagnosed 
>>>>> with a debug log extract 
>>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user> 
>>>>> from WeeWX startup.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:
>>>>>>
>>>>>> My current conditions are "frozen".
>>>>>>
>>>>>> Date is waaay in the future. I'm located in NZ, local time/date is 
>>>>>> 4:47PM, the 21st of May.
>>>>>> Since we're UTC-12, nobody passed the dateline yet.
>>>>>>
>>>>>> I've checkt the date/time and timezone and these are correct on my 
>>>>>> server.
>>>>>>
>>>>>> The graphs are correct.
>>>>>>
>>>>>> What could cause this?
>>>>>>
>>>>>> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
>>>>>> I'm running weewx 4.0.0 and capturing my data using interceptor.
>>>>>>
>>>>>

-- 
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/92e5453b-3715-41ae-ae8a-a96cba42a3ec%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

I've ruled out browser cache. Tested on multiple devices within my network 
and even asked friends abroad to test. You can give it a try, as well. 
https://weather.zmate.nz

1. 22nd of May, 12:00:00 is not changing.
2. I've deleted the contents of the www and it has been automatically 
regenerated, without forcing it.
3. plots are being generated correctly, and the hour/minute looks correct.
4. the timestamp below the plots is showing 05/22/2020 12:00:00 AM - good 
that you asked.
On Thursday, May 21, 2020 at 6:13:44 PM UTC+12, gjr80 wrote:
>
> Thanks, that is bizarre, I expectedt to see something in the log about 
> record timestamps being less than the last, but no everything is normal. 
> Archive records are bing generated with the correct timestamps, reports are 
> being generated without issue. I can't see it being a browser cache issue, 
> it would be stuck in the past not the future. A few (random) things to 
> check:
>
> 1. does the time change or is it always 22 May 00:00 (guessing it stays 
> put).
> 2. is the Seasons skin index.html file being generated every 5 minutes 
> (ie does its timestamp change) (again guessing it does as Seasons should 
> generate eight report files each report cycle and that is what it is doing)
> 3. do the current observations on the Seasons page change and are they 
> correct.
> 4. do the timestamps below the plots on the Seasons 'Day' tab show the 
> correct current time.
>
> Gary
>
> On Thursday, 21 May 2020 15:44:02 UTC+10, Zsolt Máté wrote:
>>
>> Thanks for the fast reply Gary.
>> Here's the log -> https://pastebin.com/4zNJEJea
>>
>> On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> Could be any one of a number of causes, should be easily diagnosed with 
>>> a debug log extract 
>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user> from 
>>> WeeWX startup.
>>>
>>> Gary
>>>
>>> On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:
>>>>
>>>> My current conditions are "frozen".
>>>>
>>>> Date is waaay in the future. I'm located in NZ, local time/date is 
>>>> 4:47PM, the 21st of May.
>>>> Since we're UTC-12, nobody passed the dateline yet.
>>>>
>>>> I've checkt the date/time and timezone and these are correct on my 
>>>> server.
>>>>
>>>> The graphs are correct.
>>>>
>>>> What could cause this?
>>>>
>>>> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
>>>> I'm running weewx 4.0.0 and capturing my data using interceptor.
>>>>
>>>

-- 
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/b1f2edb8-eb4a-49e7-bd96-08aa362ae943%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

wee_database --check runs OK (I assume), but --rebuild-daily return an error

root@weewx:~# wee_database --check
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
Checking daily summary tables version...
Daily summary tables are at version 2.0
Interval Weighting Fix is not required.
Daily summary tables version check completed in 0.02 seconds.
Preparing Null String Fix, this may take a while...
 Checking record: 135849; Timestamp: 2020-05-21 19:00:00 NZST (1590044400)
No null strings found.
Completed Null String Check in 12.25 seconds.
root@weewx:~# ^C
root@weewx:~# wee_database --rebuild-daily
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
All daily summaries will be rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx' ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 974, in 
main()
  File "/usr/share/weewx/wee_database", line 169, in main
rebuildDaily(config_dict, db_binding, options)
  File "/usr/share/weewx/wee_database", line 275, in rebuildDaily
trans_days=20)
  File "/usr/share/weewx/weewx/manager.py", line 1012, in 
backfill_day_summary
timestamp_to_string(lastRecord)))
weewx.ViolatedPrecondition: lastUpdate(2020-05-22 06:00:00 NZST 
(1590084000)) > lastRecord(2020-05-21 19:00:00 NZST (1590044400))

-- 
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/a65c193b-9b19-4253-b5a7-625002268ac1%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Thank you, it worked. Interestingly that rogue spike is still showing up at 
the wind vector plot.

On Thursday, May 21, 2020 at 8:42:17 PM UTC+12, gjr80 wrote:
>
> No, —check just checks a couple of unrelated things, will not help you at 
> all. You need to use —drop-daily before —rebuild-daily. 
>
> Gary

-- 
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/4cdb3cdd-94c3-4f62-9beb-9c86bc0ea978%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Thanks for the fast reply Gary.
Here's the log -> https://pastebin.com/4zNJEJea

On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote:
>
> Hi,
>
> Could be any one of a number of causes, should be easily diagnosed with a 
> debug 
> log extract 
> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user> from 
> WeeWX startup.
>
> Gary
>
> On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote:
>>
>> My current conditions are "frozen".
>>
>> Date is waaay in the future. I'm located in NZ, local time/date is 
>> 4:47PM, the 21st of May.
>> Since we're UTC-12, nobody passed the dateline yet.
>>
>> I've checkt the date/time and timezone and these are correct on my server.
>>
>> The graphs are correct.
>>
>> What could cause this?
>>
>> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png]
>> I'm running weewx 4.0.0 and capturing my data using interceptor.
>>
>

-- 
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/94f3ce14-f8d0-4ed1-a48d-72a825a41bed%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

I'm confident that the date/time will jump. I'm going to leave it run for 
the night.
I went through Matthew's wiki/how to/issues multiple times, and this is the 
best what I was able to do. I wasn't able to make interceptor listen to my 
network traffic and sniff out the communication between my PWS and WU.
If nothing helps, I'm going to clean up my database, export it, set up 
another virtual machine and install weewx.

-- 
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/4e47eabe-e605-46e8-8d7e-de963637e28e%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Disabling WU didn't help.
>
> May 23 15:00:19 weewx weewx[10289] DEBUG user.interceptor: raw packet: {
'wind_speed': 2.0, 'humidity_in': 46.0, 'temperature_in': 72.9, 
'solar_radiation': 134.81, 'windchill': 54.9, 'dewpoint': 47.8, 
'humidity_out': 77.0, 'uv': 1.0, 'rain': 0.0, 'dateTime': 1590242400, 
'pressure': 30.11, 'temperature_out': 54.9, 'wind_dir': 61.0, 'barometer': 
30.071, 'rain_total': 0.0, 'usUnits': 1, 'wind_gust': 3.4}

I thought using pcap filter is better than in my case.
Switched to "address = 192.168.2.41", cleaned the database, deleted the 
html and started weewx.

-- 
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/116e2a0f-bcaa-483c-aa5b-e67b76f7b862%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Here's the log -> https://pastebin.com/B2zFhnje

-- 
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/d0ad85c0-ef6a-4b9c-ba7b-9fe6467cdc37%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

We have 8:22PM, it stopped at last report wast generated at 8PM.
Here's the log of the first 30 minutes, of the actual run
https://pastebin.com/uhyCkPvX

-- 
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/02730962-94ae-4b07-ac7b-8612c286aceb%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Weird, I really don't know what's happening. This morning, I've deleted 
everything related to the past day from the database.

1. done
2. deleted two records, see attached image 
3. I've deleted all the files from /var/www/html/weewx/
4. ran wee_database --drop-daily and --rebuild-daily
5. debug is set to 1
6. restart WeeWX
7. as soon as the web pages are generated, the date and time is correct.

I've started weewx right now, let's see what's happening.

What I've noticed today, the www data wasn't updated every 5 minutes, 
sometimes the website got updated only after 10-15 or even 30 minutes.

debug info here -> https://pastebin.com/k519Squx

Thanks for trying to help me.


PS, now that I've finished writing this reply, I noticed that the date and 
time below the plots is already wrong. Date and time in the top left corner 
is still OK.

-- 
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/1518e2d9-e9b8-434f-829e-bbaace17c6ab%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

It stopped updating the html at local 08:00PM, and in the log I see an MQTT 
message dated tomorrow.
It's MQTT related: May 22 20:00:20 weewx weewx[5569] INFO weewx.restx: 
MQTT: Published record 2020-05-23 07:00:00 NZST (1590174000)

Log from 10 minutes before until 10 minutes after 8PM -> 
https://pastebin.com/K7s8e60V

-- 
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/e07a45fc-c8ea-4706-875d-b44916f9cf91%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Update, without any intervention time jumped to 6PM. 10hrs ahead.

On Friday, May 22, 2020 at 7:22:48 AM UTC+12, Zsolt Máté wrote:
>
> Sorry, my bad. New Zealand is UTC+12.
>
> My issue didn't disappear. Now is showing the time is showing 2PM and not 
> updating, but local time is 07:15AM.
> Data in the plots is scattered.
>
> I've double checked the date/time on my PWS and is correct.
>
> On Thursday, May 21, 2020 at 10:41:21 PM UTC+12, Jacques Terrettaz wrote:
>>
>> Hi,
>>
>> You said on your top message that  your timezone is UTC - 12
>>
>> But below I see UTC + 12
>>
>> Could it be the problem ?
>>
>>
>> Le jeudi 21 mai 2020 10:08:43 UTC+2, Zsolt Máté a écrit :
>>>
>>> Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00
>>>
>>>

-- 
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/b114c35f-1695-4f0f-b3be-2b0ea30473bb%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Sorry, my bad. New Zealand is UTC+12.

My issue didn't disappear. Now is showing the time is showing 2PM and not 
updating, but local time is 07:15AM.
Data in the plots is scattered.

I've double checked the date/time on my PWS and is correct.

On Thursday, May 21, 2020 at 10:41:21 PM UTC+12, Jacques Terrettaz wrote:
>
> Hi,
>
> You said on your top message that  your timezone is UTC - 12
>
> But below I see UTC + 12
>
> Could it be the problem ?
>
>
> Le jeudi 21 mai 2020 10:08:43 UTC+2, Zsolt Máté a écrit :
>>
>> Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00
>>
>>

-- 
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/3adc91ad-f4ce-4146-b4da-791540908c20%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

As an update, I didn't restart or modified anything since my last message, 
and it just started working.
I really don't understand what happened, now I'm afraid now to stop/restart 
it.

-- 
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/a8c7a43d-9c27-4931-8a5f-751a03a8ccc7%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Update, disabling MQTT didn't help. My time just jumped 10 hours in 
advance. From 12PM to 10PM.
>
> Log 10 minutes +/- 12PM -> https://pastebin.com/FjkM7Mg8
Problem occurs here
May 23 12:00:19 weewx weewx[9805] DEBUG user.interceptor: raw packet: {
'wind_speed': 1.8, 'humidity_in': 46.0, 'temperature_in': 71.2, 
'solar_radiation': 296.66, 'windchill': 55.8, 'dewpoint': 48.6, 
'humidity_out': 77.0, 'uv': 3.0, 'rain': 0.0, 'dateTime': 1590231600, 
'pressure': 30.207, 'temperature_out': 55.8, 'wind_dir': 74.0, 'barometer': 
30.169, 'rain_total': 0.0, 'usUnits': 1, 'wind_gust': 2.2}

Right now I've disabled WU in my weewx.conf, deleted html and cleaned the 
database.
Let's see.

>

-- 
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/aecadd5c-0ea6-4da5-8be2-782b8b256b5a%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

Right now I've disabled MQTT in weewx.conf, cleaned the future records from 
the database, dropped and rebuild the daily stats. Last HTML generated is 
more than 30 minutes old.

To paint a picture of my setup:
I'm running this weather station -> 
https://www.jaycar.co.nz/7-inch-colour-wireless-weather-station/p/XC0370 - 
IP address 192.168.2.60 that sends data to WU (intercepted)
weewx is running in a proxmox container with the IP's 192.168.2.40 and 
192.168.2.41, 41 being the interceptor.
On my router (openwrt), I've set up a rule, that the traffic from my PWS 
should be forwarded to 192.168.2.41.
iptables -t nat -A PREROUTING -s 192.168.2.60 -p tcp --dport 80 -j DNAT 
--to-destination 192.168.2.41:80
iptables -t nat -A POSTROUTING -j MASQUERADE
Weewx is forwarding the intercepted data to WU.
MQTT is used for the Belchertown skin (right now uninstalled) and to 
integrate my weather data into Home Assistant.


On Saturday, May 23, 2020 at 10:57:43 AM UTC+12, gjr80 wrote:
>
> Thanks. I am trying to get my head around what is going on here. There 
> seems to be a lot of double handling (posting) of records, for example the 
> 22 May 19:50:20 record is published by the MQTT uploader six times:
>
> May 22 19:50:28 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:50:29 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:50:44 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:50:50 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:51:00 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
> ...
> May 22 19:51:16 weewx weewx[5569] INFO weewx.restx: MQTT: Published 
> record 2020-05-22 19:50:20 NZST (1590133820)
>
> I also see the interceptor is picking up a lot of what appears to be 
> duplicate records some of which are HTTP POST and others HTTP GET. Can you 
> clarrify your configuration? From the wee_debug report you have WeeWX 
> uploading to WU both normal (every archive record) updates and rapid fire 
> and you have WeeWX uploading to a MQTT broker every archive record and loop 
> packet. Do you have your weather station uploading to WU? I am thinking it 
> might be time to pare back to a bare bones setup by turning off a few 
> services.
>
> Gary
>
> On Friday, 22 May 2020 18:36:29 UTC+10, Zsolt Máté wrote:
>>
>> It stopped updating the html at local 08:00PM, and in the log I see an 
>> MQTT message dated tomorrow.
>> It's MQTT related: May 22 20:00:20 weewx weewx[5569] INFO weewx.restx: 
>> MQTT: Published record 2020-05-23 07:00:00 NZST (1590174000)
>>
>> Log from 10 minutes before until 10 minutes after 8PM -> 
>> https://pastebin.com/K7s8e60V
>>
>

-- 
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/f157cdae-64f3-4c7c-9a3f-d2b0b73141a0%40googlegroups.com.

[weewx-user] Re: Interceptor setup

[Zsolt Máté]

Did anything change with the latest raspberry pi images? I'm trying to do a 
clean install, downloaded the last image (based on Debian Buster), 
installed and configured hostapd as per wiki.
Now the DNS is not resolving any address. I can ping external IP addresses 
while I'm connected to the pi via LAN or WLAN.

-- 
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/6908abaa-d068-42da-a291-420581309a05o%40googlegroups.com.

[weewx-user] Re: Interceptor setup

[Zsolt Máté]

There was a typo in the wiki, edited it.
Instead of domain_name_servers there was domain_name_server.



On Tuesday, June 30, 2020 at 7:39:11 PM UTC+12, Zsolt Máté wrote:
>
> Did anything change with the latest raspberry pi images? I'm trying to do 
> a clean install, downloaded the last image (based on Debian Buster), 
> installed and configured hostapd as per wiki.
> Now the DNS is not resolving any address. I can ping external IP addresses 
> while I'm connected to the pi via LAN or WLAN.
>

-- 
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/f27fbef2-f041-4617-9654-4c80259fa7d9o%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Zsolt Máté]

Did anyone find a fix for this?
I'm in the same boat. Fresh raspberry pi image, clean install.

sudo PYTHONPATH=/usr/share/weewx python 
/usr/share/weewx/user/interceptor.py --device=observer --mode=sniff 
--iface=wlan0 --filter="src 10.3.141.115 and dst port 80"
mapped packet: {'barometer': 29.986, 'windchill': 45.5, 'dewpoint': 39.7, 
'pressure': 30.024, 'outHumidity': 77.0, 'UV': 1.0, 'radiation': 105.33, 
'rain': None, 'dateTime': 1593561263, 'windDir': 244.0, 'outTemp': 46.6, 
'windSpeed': 3.4, 'inHumidity': 44.0, 'inTemp': 69.6, 'windGust': 4.5, 
'usUnits': 1}


Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>   Observer.Parser(), handler=Observer.Handler, **stn_dict)
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/interceptor.py", line 427, in __init__
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>   iface, pcap_filter, promiscuous)
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/user/interceptor.py", line 469, in __init__
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>   self.sniffer.open_live(iface, snaplen, pval, timeout_ms)
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>> File "/usr/lib/python2.7/dist-packages/pcap.py", line 108, in open_live
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>   def open_live(self, *args): return _pcap.pcapObject_open_live(self, *args)
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>> TypeError: in method 'pcapObject_open_live', argument 2 of type 'char *'
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__: Unable to load 
>> driver: in method 'pcapObject_open_live', argument 2 of type 'char *'
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__:   
>> Exiting...
>
>
>

-- 
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/c16c9c11-7dac-41b9-b73f-79ee2e856edco%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Zsolt Máté]

Solved by uninstalling python3 and installing 2.7.

On Wednesday, July 1, 2020 at 12:06:44 PM UTC+12, Zsolt Máté wrote:
>
> Did anyone find a fix for this?
> I'm in the same boat. Fresh raspberry pi image, clean install.
>
> sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=observer --mode=sniff 
> --iface=wlan0 --filter="src 10.3.141.115 and dst port 80"
> mapped packet: {'barometer': 29.986, 'windchill': 45.5, 'dewpoint': 39.7, 
> 'pressure': 30.024, 'outHumidity': 77.0, 'UV': 1.0, 'radiation': 105.33, 
> 'rain': None, 'dateTime': 1593561263, 'windDir': 244.0, 'outTemp': 46.6, 
> 'windSpeed': 3.4, 'inHumidity': 44.0, 'inTemp': 69.6, 'windGust': 4.5, 
> 'usUnits': 1}
>
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>>   Observer.Parser(), handler=Observer.Handler, **stn_dict)
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/user/interceptor.py", line 427, in __init__
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>> iface, pcap_filter, promiscuous)
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/user/interceptor.py", line 469, in __init__
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>> self.sniffer.open_live(iface, snaplen, pval, timeout_ms)
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>>   File "/usr/lib/python2.7/dist-packages/pcap.py", line 108, in open_live
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>> def open_live(self, *args): return _pcap.pcapObject_open_live(self, 
>>> *args)
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>> TypeError: in method 'pcapObject_open_live', argument 2 of type 'char *'
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__: Unable to load 
>>> driver: in method 'pcapObject_open_live', argument 2 of type 'char *'
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__:   
>>> Exiting...
>>
>>
>>

-- 
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/210d119f-7d07-4493-9c1e-4e98ca3e2fd3o%40googlegroups.com.

[weewx-user] Re: GUI date/time and current conditions frozen

[Zsolt Máté]

After a month of trial and error, I'm still struggling with this issue.
I've changed my VM from turnkey linux to a full ubuntu server, didn't help. 
Tried minimal installations, mysql vs sqlite, no joy. My date is being 
messed up somehow.

-- 
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/c130bebe-ae49-4064-9a76-1d441d57a20eo%40googlegroups.com.

[weewx-user] Database vs MQTT published data

[Zsolt Máté]

What could be the reason of data (in 30 minute groups) missing from my sql 
database?
I started publishing weewx data via MQTT, logged with infludb and displayed 
with grafana. While there's nothing missing in influx, my msql is dropping 
lots of data.

I am using interceptor as driver.
[image: 2021-01-26 13_57_25 chrome_2pzzr0Betn.png]
[image: 2021-01-26 13_58_04 chrome_ePWeWxyOw2.png]

-- 
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/ea2019db-67ec-4597-be09-75207b974892n%40googlegroups.com.

[weewx-user] Re: Database vs MQTT published data

[Zsolt Máté]

I am missing the data in mysql.
See the two attachments. The last hour in phpmysql vs grafana.
There are just 7 records in the last hour, but AFAIK my interceptor gets 
data every ~16 seconds - see the graph drawn by grafana using influxdb data.
[image: 2021-01-26 14_36_41 chrome_daC10v9WCb.png]
[image: 2021-01-26 14_37_31 chrome_YnEe2grkwc.png]

On Tuesday, January 26, 2021 at 2:08:22 PM UTC+13 vince wrote:

> Are you sure you're not just seeing gaps in the 'graphs' of the data ?
>
> See if you're really missing intervals in the db by querying your db 
> directly.
>
>

-- 
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/fd9dab82-7f31-450e-9f0c-44e1d136e6a4n%40googlegroups.com.

[weewx-user] Re: Database vs MQTT published data

[Zsolt Máté]

The dropouts have no pattern. I have a few days without any issues, and 
then for 24hrs mysql starts choking.
At the beginning I didn't have the influx/grafana part. I've set it up for 
testing purposes, to see if mqtt is pushing out data even if the mysql is 
behaving.
Previously I tried setting up a vm/ct just for weewx, but I didn't manage 
to get interceptor working on virtual interfaces. 

For now I've set the debug flag to 1, so as soon as I see any issue I'll 
mark the time and start looking and posting the syslog.


On Thursday, January 28, 2021 at 2:41:43 PM UTC+13 vince wrote:

> On Wednesday, January 27, 2021 at 4:33:25 PM UTC-8 lop...@gmail.com wrote:
>
>> As an extra info, weewx is failing to generate the html during these 
>> periods, but interceptor and mqtt are able to function.
>>
>
> As Tom asked, we're going to need to see your syslogs with weewx debug=1 
> set in order to work this one.
>
> You have a lot of things running on that pi.  Pat's skin is pretty 
> heavyweight.  Do you have other skins enabled too ?  You have the box 
> acting as an access point.  You're running interceptor.  You're running 
> mysql.   You're feeding influxdb in your remote vm.   That's a lot of 
> things expecting the pi network stack to work with multiple NICs and the 
> processor to be able to keep up with.  And it's a pi3 so it's 2.4 GHz which 
> can be bouncy as well.  That's a lot of things to have to be perfect.
>
> So we need to see some syslogs for the weewx stuff, but I'd suggest taking 
> grafana out of the picture completely and just doing influxdb queries and 
> weewx db queries for the same time periods so we can verify that there 
> really is data missing in one db or the other.   Find a one-hour period and 
> just query each directly.
>
>

-- 
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/d27090e9-e3b9-4c51-8228-5c27c054e146n%40googlegroups.com.

Re: [weewx-user] Re: Database vs MQTT published data

[Zsolt Máté]

Since 04:30AM the data stream is continuous again, see attachment. For the 
record, the dropouts were 30 minutes long, followed by a 30 minutes good 
data logs.
The mysql server is running on the same raspberry pi as weewx. I think this 
rules out the possibility of having an unreliable network link.
I've restarted weewex after setting the debug flag to 1. I'll keep an eye 
on the server and check the log when it happens again.

/var/log/mysql/error.log is empty

[image: 2021-01-27 10_29_04 chrome_Wf7wVUdOQL.png]
On Wednesday, January 27, 2021 at 12:35:03 AM UTC+13 tke...@gmail.com wrote:

> Hard to say without seeing the log. Is the MySQL server located on an 
> unreliable network link? Unfortunately, WeeWX cannot recover from a MySQL 
> write error (see issue #259 <https://github.com/weewx/weewx/issues/259>).
>
> Take a look in your system log for any WeeWX errors, and in the MySQL log 
> for any database errors.
>
> On Mon, Jan 25, 2021 at 5:45 PM Zsolt Máté  wrote:
>
>> I am missing the data in mysql.
>> See the two attachments. The last hour in phpmysql vs grafana.
>> There are just 7 records in the last hour, but AFAIK my interceptor gets 
>> data every ~16 seconds - see the graph drawn by grafana using influxdb data.
>> [image: 2021-01-26 14_36_41 chrome_daC10v9WCb.png]
>> [image: 2021-01-26 14_37_31 chrome_YnEe2grkwc.png]
>>
>> On Tuesday, January 26, 2021 at 2:08:22 PM UTC+13 vince wrote:
>>
>>> Are you sure you're not just seeing gaps in the 'graphs' of the data ?
>>>
>>> See if you're really missing intervals in the db by querying your db 
>>> directly.
>>>
>>> -- 
>> 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/fd9dab82-7f31-450e-9f0c-44e1d136e6a4n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/fd9dab82-7f31-450e-9f0c-44e1d136e6a4n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/08529f65-a866-430f-b05d-a8cda42de4e9n%40googlegroups.com.

[weewx-user] corrupt mysql?

[Zsolt Máté]

Hi everyone

my weewx mysql database is acting weird.

I've logged into phpmysql and I'm getting the following error, no matter 
what table I'm trying to open

*Warning* in ./libraries/sql.lib.php#613
 count(): Parameter must be an array or an object that implements Countable

*Backtrace*

./libraries/sql.lib.php#2128: PMA_isRememberSortingOrder(array)
./libraries/sql.lib.php#2062: PMA_executeQueryAndGetQueryResponse(
array,
boolean true,
string 'weewx',
string 'archive_day_appTemp',
NULL,
NULL,
NULL,
NULL,
NULL,
NULL,
string '',
string './themes/pmahomme/img/',
NULL,
NULL,
NULL,
string 'SELECT * FROM `archive_day_appTemp`',
NULL,
NULL,
)
./sql.php#221: PMA_executeQueryAndSendQueryResponse(
array,
boolean true,
string 'weewx',
string 'archive_day_appTemp',
NULL,
NULL,
NULL,
NULL,
NULL,
NULL,
string '',
string './themes/pmahomme/img/',
NULL,
NULL,
NULL,
string 'SELECT * FROM `archive_day_appTemp`',
NULL,
NULL,
)

Can anyone help me out to fix this?

-- 
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/7d00ce09-09a0-4766-9b3b-3d45df44d08dn%40googlegroups.com.

[weewx-user] Re: corrupt mysql?

[Zsolt Máté]

Via console I'm not getting the error.
What I've noticed, my data is missing from the beginning of December until 
yesterday, when I discovered that my weewx instance was acting weird. The 
webpage was showing the data, but the css was all messed up.
I decided to reboot my pi, and when I checked the phpmysql I discovered 
that error and the missing data.
Can confirm, that weewx was working during the previous days. Even measured 
the Tonga eruption shockwave.

CLI looks like this (truncated).

MariaDB [weewx]> SELECT * FROM `archive_day_altimeter`;
++--++--++--+---+--+-+
| dateTime   | min  | mintime| max  | maxtime   
 | sum  | count | wsum | sumtime |
++--++--++--+---+--+-+
| 1546254000 | NULL |   NULL | NULL |   
NULL |0 | 0 |0 |   0 |
| 1546340400 | NULL |   NULL | NULL |   
NULL |0 | 0 |0 |   0 |
| 1546426800 | NULL |   NULL | NULL |   
NULL |0 | 0 |0 |   0 |
| 1546513200 | NULL |   NULL | NULL |   
NULL |0 | 0 |0 |   0 |
| 1546599600 | 29.5787168389751 | 1546668900 | 29.7356344094877 | 
1546686000 | 2491.12247214729 |84 | 747336.741644186 |   25200 |
| 1546686000 | 29.7379600887755 | 1546686900 |  29.897817590659 | 
1546772400 | 8586.04835004087 |   288 | 2575814.50501226 |   86400 |
| 1546772400 | 29.8940858215625 | 1546784100 | 30.0371979903682 | 
1546853400 | 8630.46742018693 |   288 | 2589140.22605608 |   86400 |
| 1546858800 | 30.0289331555921 | 1546868700 | 30.1481570023865 | 
1546920600 |  8670.2210690116 |   288 | 2601066.32070348 |   86400 |
| 1546945200 | 29.5891566447423 | 1547014800 | 30.1157605167892 | 
1546945500 | 8593.32919113824 |   288 | 2577998.75734147 |   86400 |
| 1547031600 | 29.7387938229121 | 1547031900 | 29.9388899419505 | 
1547118000 | 8587.75150853799 |   288 |  2576325.4525614 |   86400 |
| 1547118000 | 29.9397236755119 | 1547119500 | 30.3299107560163 | 
1547201700 | 8674.08376892149 |   288 | 2602225.13067644 |   86400 |
On Wednesday, January 26, 2022 at 10:00:33 PM UTC+13 Cameron D wrote:

> Firstly, you would want to rule out that phpMyAdmin is not the problem.
> Try the same commands with mysql shell/client or even with mysql workbench 
> on a windows system.
>
> On Tuesday, 25 January 2022 at 5:47:42 pm UTC+10 lop...@gmail.com wrote:
>
>> Hi everyone
>>
>> my weewx mysql database is acting weird.
>>
>> I've logged into phpmysql and I'm getting the following error, no matter 
>> what table I'm trying to open
>>
>> *Warning* in ./libraries/sql.lib.php#613
>>  count(): Parameter must be an array or an object that implements 
>> Countable
>>
>> *Backtrace*
>>
>> ./libraries/sql.lib.php#2128: PMA_isRememberSortingOrder(array)
>> ./libraries/sql.lib.php#2062: PMA_executeQueryAndGetQueryResponse(
>> array,
>> boolean true,
>> string 'weewx',
>> string 'archive_day_appTemp',
>> NULL,
>> NULL,
>> NULL,
>> NULL,
>> NULL,
>> NULL,
>> string '',
>> string './themes/pmahomme/img/',
>> NULL,
>> NULL,
>> NULL,
>> string 'SELECT * FROM `archive_day_appTemp`',
>> NULL,
>> NULL,
>> )
>> ./sql.php#221: PMA_executeQueryAndSendQueryResponse(
>> array,
>> boolean true,
>> string 'weewx',
>> string 'archive_day_appTemp',
>> NULL,
>> NULL,
>> NULL,
>> NULL,
>> NULL,
>> NULL,
>> string '',
>> string './themes/pmahomme/img/',
>> NULL,
>> NULL,
>> NULL,
>> string 'SELECT * FROM `archive_day_appTemp`',
>> NULL,
>> NULL,
>> )
>>
>> Can anyone help me out to fix this?
>>
>

-- 
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/3a69a117-df6c-4d94-afc3-29cc0cb8334an%40googlegroups.com.

Re: [weewx-user] Re: EcoWitt GW2000 - anyone working on a driver?

[Zsolt Máté]

Install FOSHKplugin and all your headaches are gone. I was struggling with 
the drivers, interceptors, observers, whatnot, but ever since I've 
installed it everything is back to normal.

On Monday, April 18, 2022 at 4:41:05 AM UTC+12 xzei...@googlemail.com wrote:

> My modified driver from Gary (now named gw2000.py) supports the GW2000 and 
> GW1100 with Firmware V2.1.3 (piezo_rain)
> https://www.pc-wetterstation.de/weewx/gw2000.zip
> The piezo_gain_values are at the moment not supported. 
> The hour piezo rain and hour rain aren't right, the pdf-docu isn't here 
> correct, seems this values are gain factors
> I use the hail database value for  piezo rain (WS90)
> [[field_map_extensions]]
> rain_piezo = rain_piezo
> erain_piezo = erain_piezo
> rrain_piezo = rrain_piezo
> hrain_piezo = hrain_piezo
> drain_piezo = drain_piezo
> wrain_piezo = wrain_piezo
> mrain_piezo = mrain_piezo
> yrain_piezo = yrain_piezo
>
> hail = rain_piezo
> hailrate = rrain_piezo
> stephen...@gmail.com schrieb am Sonntag, 17. April 2022 um 06:46:23 UTC+2:
>
>> Hi Gary,
>>
>> I have abused my credit card and ordered a WH40 rainfall sensor (along 
>> with the AQ & lightning sensior), so that readings from both it & the piezo 
>> sensor can be compared. Will let you know when it turns up and is installed.
>>
>> On Sun, 17 Apr 2022 at 13:52, Stephen Hocking  
>> wrote:
>>
>>> Hi Gary,
>>>
>>> I've just set up weewx with the gw1000 driver, and it appears to have 
>>> picked up the gw2000 just fine - I'm getting observations coming in. I'm 
>>> reassured, as a recent git pull of the rtl_433 code doesn't decode anything 
>>> from the sensors at all, and while going down that rabbit hole of banging 
>>> on the code would be entertaining, I'm pretty sure that more talented minds 
>>> than mine are already on it.
>>>
>>> I currently have the WittBoy (with the aforementioned piezo rain 
>>> detector) only at the moment, although I'm planning on ordering the indoor 
>>> & outdoor air quality sensors, as well as the lightning one. This thing 
>>> seems to be head & shoulders over the AcuRite Atlas I was using with the 
>>> SDR driver (plus scraping pressure off the webpage on the Atlas hub). 
>>>
>>> Please let me know if I can test any code for you.
>>>
>>> On Sun, 17 Apr 2022 at 11:05, gjr80  wrote:
>>>
 The current GW1000 driver will speak to a GW2000 and should return all 
 obs except for WS90 rain and WS90 signal/battery states. I am working on 
 the v0.5.0 driver but the behaviour of the GW2000 API with various 
 combinations of the 'traditional' and 'piezo' rain gauges (Ecowitt's 
 terms) 
 is not very clearly defined. I will likely need some assistance from 
 GW2000 
 users with various rain gauge combinations to tie this down. WS90 signal 
 and battery states are already working in the v0.5.0 driver.

 Not sure how long the piece of string is.

 Gary
 On Sunday, 17 April 2022 at 02:08:31 UTC+10 vince wrote:

> A little searching here seems to indicate the gw1000 driver should 
> possibly work for you.  Give it a try
>
> On Friday, April 15, 2022 at 11:10:06 PM UTC-7 stephen...@gmail.com 
> wrote:
>
>> From the web page the device serves up, it appears you can tell it to 
>> upload data  in ecowitt or wunderground format to your own server/port.
>>
>>
>> [image: image.png]
>> -- 
>>
>>   "I and the public know
>>   what all schoolchildren learn
>>   Those to whom evil is done
>>   Do evil in return" W.H. Auden, "September 1, 1939"
>>
>>
>> -- 
 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/02ed201f-1f74-4543-94b1-6c144cc9c51bn%40googlegroups.com
  
 
 .

>>>
>>>
>>> -- 
>>>
>>>   "I and the public know
>>>   what all schoolchildren learn
>>>   Those to whom evil is done
>>>   Do evil in return"W.H. Auden, "September 1, 1939"
>>>
>>>
>>>
>>
>> -- 
>>
>>   "I and the public know
>>   what all schoolchildren learn
>>   Those to whom evil is done
>>   Do evil in return" W.H. Auden, "September 1, 1939"
>>
>>
>>

-- 
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