Re: [weewx-user] Re: first user - a lot of issues

2022-11-04 Thread Alex Vanuxem
hey, It was under wsl. but now i installed under windows 11, hyper-v and installed an ubuntu latest version under a virtual machine, i have the full program; now i'm struggling again; again no syslog, it says its installed, but cant start it i can invoke ./bin/weewxd , i see a lot of data coming

Re: [weewx-user] Re: first user - a lot of issues

2022-11-04 Thread Rainer Lang
When you want to use weewx under WSL (which works perfectly by the way - at least with the Interceptor and the Ecowitt Gateway driver), you need to make sure that the connectivity between the virtual machine in which WSL is running and the local network the WSL host computer is running in has

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2022-11-04 Thread vince
You can also use the -n switch to go back in the file longer. For example to go back 500 lines: sudo tail -n 500 -f /var/log/syslog On Friday, November 4, 2022 at 12:46:56 PM UTC-7 Tom Keffer wrote: > You're starting up weewxd, then doing tail -f /var/log/syslog. By the time > you do the

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2022-11-04 Thread Tom Keffer
You're starting up weewxd, then doing tail -f /var/log/syslog. By the time you do the "tail", you've missed the critical information about how weewxd is starting up. Please follow the directions in *Posting to weewx-user *. That

Re: [weewx-user] Re: first user - a lot of issues

2022-11-04 Thread vince
We really need more information on your setup. It 'seems' like you are trying to run a rather unusual configuration. I noticed this in your errors.txt file: - "Linux-5.10.102.1-microsoft-standard-WSL2-x86_64-with-glibc2.29" ==> are you trying to run weewx under Windows WSL

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2022-11-04 Thread Günther Wrana
I don't think anything has changed with the killall command. pi@wetterpi:/$ sudo killall weewxd weewxd: Kein Prozess gefunden pi@wetterpi:/$ sudo killall weewxd weewxd: Kein Prozess gefunden pi@wetterpi:/$ sudo /etc/init.d/weewx start [ ok ] Starting weewx (via systemctl): weewx.service.

Re: [weewx-user] Re: first user - a lot of issues

2022-11-04 Thread Alex Vanuxem
the first is an errorlog when i start weewx the second is errorlog of syslog thx Op vr 4 nov. 2022 om 19:07 schreef Alex Vanuxem : > > > Op vr 4 nov. 2022 om 19:07 schreef Alex Vanuxem : > >> hi thx >> >> i forgot to init.d the rsyslog. >> >> now i have syslog see attach. I can connect to my

Re: [weewx-user] Re: first user - a lot of issues

2022-11-04 Thread Alex Vanuxem
Op vr 4 nov. 2022 om 19:07 schreef Alex Vanuxem : > hi thx > > i forgot to init.d the rsyslog. > > now i have syslog see attach. I can connect to my ftp through the linux > gui. > > but since today no data is coming in, ??? > sorry i'm a newbie. > > > > > > > > > > > Op do 3 nov. 2022 om 23:24

Re: [weewx-user] Re: first user - a lot of issues

2022-11-04 Thread Alex Vanuxem
hi thx i forgot to init.d the rsyslog. now i have syslog see attach. I can connect to my ftp through the linux gui. but since today no data is coming in, ??? sorry i'm a newbie. Op do 3 nov. 2022 om 23:24 schreef Tom Keffer : > (Vince, I think he went to the correct link.) > > Alex,

Re: [weewx-user] $almanac varying values

2022-11-04 Thread Tom Keffer
Makes sense. Sounds like for your application constant values for temperature and pressure would probably be best. On Fri, Nov 4, 2022 at 10:36 AM Karen K wrote: > tke...@gmail.com schrieb am Freitag, 4. November 2022 um 17:01:25 UTC+1: > >> $almanac(almanac_time=1655805600, >>

Re: [weewx-user] $almanac varying values

2022-11-04 Thread Karen K
tke...@gmail.com schrieb am Freitag, 4. November 2022 um 17:01:25 UTC+1: > $almanac(almanac_time=1655805600, > temperature=$current(timestamp=1655805600).outTemp.raw, > pressure=$current(timestamp=1655805600).barometer.raw).sunrise > > Hopefully that works! > It works perfect! > Are you

Re: [weewx-user] $almanac varying values

2022-11-04 Thread Tom Keffer
This is a good point. I had it wrong. The value for almanac_time is used for the position of the heavenly body. The database lookup is done with whatever the "current time" is, generally the last timestamp in the database. So, to set both, you'd have to do something like:

Re: [weewx-user] $almanac varying values

2022-11-04 Thread Karen K
tke...@gmail.com schrieb am Freitag, 4. November 2022 um 13:38:42 UTC+1: > If you provide almanac_time, then it looks them up in the database. > Otherwise, it uses the last time stamp in the database. > >> >> In my first example I provided an almanac_time. And there was a database record for

[weewx-user] Re: UDP listener (for Weatherflow Tempest) won't run

2022-11-04 Thread weatherl...@gmail.com
Dumb on my part. I'm on a VM and didn't have the network set up right. All fixed, many thanks On Thursday, November 3, 2022 at 5:01:05 PM UTC-4 vince wrote: > It's not hearing anything. Your hub is either offline or your network > isn't getting the broadcast messages to the system you're

Re: [weewx-user] $almanac varying values

2022-11-04 Thread Greg Troxel
Tom Keffer writes: > If you provide almanac_time, then it looks them up in the database. > Otherwise, it uses the last time stamp in the database. > > If the database is not available, then it defaults to 15°C and 1010 mbar. I am curious about the rationale for 1010, vs 1013.25. And,

Re: [weewx-user] $almanac varying values

2022-11-04 Thread Tom Keffer
If you provide almanac_time, then it looks them up in the database. Otherwise, it uses the last time stamp in the database. If the database is not available, then it defaults to 15°C and 1010 mbar. On Fri, Nov 4, 2022 at 5:14 AM Karen K wrote: > tke...@gmail.com schrieb am Donnerstag, 3.

Re: [weewx-user] $almanac varying values

2022-11-04 Thread Karen K
tke...@gmail.com schrieb am Donnerstag, 3. November 2022 um 23:42:17 UTC+1: > Pressure and temperature also factor into the calculation. If you want to > hold them constant as well, then use something like: > > $current.dateTime , $almanac(almanac_time=1655805600, temperature=20.0, >

Re: [weewx-user] Re: cant registrer my weather stations

2022-11-04 Thread matthew wall
On Thursday, November 3, 2022 at 5:06:41 PM UTC-4 tke...@gmail.com wrote: > The problem is the "location" option. Here's the error showing up on > weewx.com: > > 2022.11.03 17:45:34 execute failed: Incorrect string value: > '\xCE\x9C\xCE\xB5\xCF\x84...' for column 'description' at row 1 >

Re: [weewx-user] Time and date format in Weewx database

2022-11-04 Thread Tom Keffer
Not to be too terribly pedantic, but unix time does deal with leap seconds. It's just that it deals with them using a discontinuity at midnight. The result is that if you calculate the difference in unix epoch time between, say, 23:55 and 00:10, it will *always* be 900 seconds, even if a leap

Re: [weewx-user] Time and date format in Weewx database

2022-11-04 Thread Greg Troxel
Phillip Fischer writes: > Thank You! I am fairly new to the world of linux and learning new things > each day! I appreciate your time to answer my question. This is likely beyond what you care about, but note that the time values are the number of seconds since January 1, 1970 UTC **as if

Re: [weewx-user] Time and date format in Weewx database

2022-11-04 Thread Phillip Fischer
Thank You! I am fairly new to the world of linux and learning new things each day! I appreciate your time to answer my question. I've successfully converted the time and date stamps! On Friday, 4 November 2022 at 11:33:50 UTC+2 peterq...@gmail.com wrote: > A little more background. It's a unix

Re: [weewx-user] Time and date format in Weewx database

2022-11-04 Thread p q
A little more background. It's a unix epoch datetime. The number of seconds since 1970 iirc. Google unix epoch. On Fri, Nov 4, 2022, 10:14 AM Glenn McKechnie wrote: > unixepoch, epochtime, unixtime > > from a linux terminal... > > $ date -d now +'%s' > 1667553105 > > $ date -d @1667553105 > Fri

Re: [weewx-user] Time and date format in Weewx database

2022-11-04 Thread Glenn McKechnie
unixepoch, epochtime, unixtime from a linux terminal... $ date -d now +'%s' 1667553105 $ date -d @1667553105 Fri 04 Nov 2022 20:11:45 AEDT man date within a mysql (mariadb)... SELECT FROM_UNIXTIME(datetime, '%d-%m-%Y %H:%i') from archive WHERE dateTime = 166734; there'll be something

Re: [weewx-user] Time and date format in Weewx database

2022-11-04 Thread Stephen Hocking
Hi Phillip, It's in Unix Epoch time - this website will help you on how to convert it to a sensible date & time. https://www.epochconverter.com/#:~:text=The%20Unix%20epoch%20(or%20Unix,01T00%3A00%3A00Z) . On Fri, 4 Nov 2022 at 19:38, Phillip Fischer wrote: > I hope that someone would be able

[weewx-user] Time and date format in Weewx database

2022-11-04 Thread Phillip Fischer
I hope that someone would be able to point me in the right direction. I am aiming to use Weewx to log data from a weather station console of a station that is set up in a remote, out of the way area as part of my research. Due to an oversight in Station specs, I was given a station that will