[weewx-user] WH65B no pressure

2018-12-31 Thread 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,

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

2018-12-31 Thread 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

[weewx-user] Re: WH65B no pressure

2019-01-01 Thread Zsolt Máté
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

[weewx-user] Re: WH65B no pressure

2019-01-01 Thread 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? >

[weewx-user] Re: WH65B no pressure

2019-01-01 Thread 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 m

Re: [weewx-user] Re: Interceptor setup

2019-01-04 Thread 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 >&

[weewx-user] Re: Interceptor setup

2019-01-04 Thread 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

Re: [weewx-user] Re: Interceptor setup

2019-01-05 Thread Zsolt Máté
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: >>> >>

Re: [weewx-user] Re: Interceptor setup

2019-01-05 Thread Zsolt Máté
t 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

Re: [weewx-user] Re: Interceptor setup

2019-01-05 Thread Zsolt Máté
. 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

Re: [weewx-user] Re: Interceptor setup

2019-01-05 Thread Zsolt Máté
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 rep

[weewx-user] can not install paho-mqtt

2019-01-23 Thread 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,

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

2019-01-23 Thread 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 installati

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

2019-01-23 Thread 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

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

2019-01-30 Thread Zsolt Máté
anuary 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

[weewx-user] Re: Interceptor setup

2019-06-05 Thread 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

Re: [weewx-user] Re: Interceptor setup

2019-06-05 Thread Zsolt Máté
; 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

Re: [weewx-user] Re: Interceptor setup

2019-06-06 Thread 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 han

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

2020-04-13 Thread Zsolt Máté
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,

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

2020-04-13 Thread Zsolt Máté
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/2

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

2020-04-13 Thread 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

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

2020-04-13 Thread Zsolt Máté
orks: > 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 >

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

2020-04-13 Thread Zsolt Máté
un/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, Zso

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

2020-04-13 Thread Zsolt Máté
ub.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 ne

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

2020-04-13 Thread 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

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

2020-04-13 Thread 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

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

2020-04-13 Thread Zsolt Máté
an 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

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

2020-05-20 Thread 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

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

2020-05-21 Thread 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

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

2020-05-21 Thread 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

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

2020-05-21 Thread Zsolt Máté
ur 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.zmat

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

2020-05-21 Thread Zsolt Máté
t;>> >>> 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 >>> >>

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

2020-05-21 Thread 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

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

2020-05-21 Thread 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.

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

2020-05-20 Thread Zsolt Máté
b.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

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

2020-05-23 Thread 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

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

2020-05-23 Thread 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':

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

2020-05-23 Thread 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

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

2020-05-23 Thread 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

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

2020-05-22 Thread 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

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

2020-05-22 Thread 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 ->

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

2020-05-21 Thread 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

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

2020-05-21 Thread Zsolt Máté
, 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

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

2020-05-24 Thread 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

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

2020-05-22 Thread 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,

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

2020-05-22 Thread Zsolt Máté
chive 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 s

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

2020-06-21 Thread 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

[weewx-user] Re: Interceptor setup

2020-06-30 Thread 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

[weewx-user] Re: Interceptor setup

2020-06-30 Thread 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 l

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

2020-06-30 Thread 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':

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

2020-07-01 Thread 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 > /us