Not getting archived data on console of WS2080

[Jens-Jørgen Kjærgaard]

I have for some years been running weewx on raspberry in my camping hut, solar powered.

In dark winter days, the raspberry is sometimes loses power for maybe a day or two. However, the WS2080 is running on battery, so all data are archived on the console. When the raspberry starts up again after the break, weewx is not downloading the stored data from the console, so my weewx archive will have gaps corresponding to the gaps in solar power.

But as I understand it, weewx should download all data from console? 

[Andrew Milner]

1. what does the log show during the startup process??

2. make sure that weewx does not start until after the RPI has got the time set correctly - else you will probably lose data by not attempting to get the archived data from the station

[Thomas Keffer]

In addition to Andrew's suggestions, run wee_device with the --info option.

wee_device /path/to/your/weewx.conf --info

-tk

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

[Jens-Jørgen Kjærgaard]

The log file is shown after a gap, 01.28 to 11.03 ( syslog).

I also found another section with an error message (syslog2), though this is maybe not related.

Jens-Jørgen Kjærgaard
www.jensjk.dk

--
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/azG9h2BG6qA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+unsubscribe@googlegroups.com.

[Jens-Jørgen Kjærgaard]

wee_device gives " command not found".

Do I need to reinstall? I am on weewx 3.1

Jens-Jørgen Kjærgaard
www.jensjk.dk

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/azG9h2BG6qA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+unsubscribe@googlegroups.com.

[Thomas Keffer]

These are two separate problems.

First, I think you are having a clock problem. See the Wiki for an explanation of how the RPi clock works and how to fix the problem. Note that one solution requires weewx v3.4 or later.

Second, either you are having a DNS problem, or the host name you gave in the FTP section of weewx.conf is wrong.

-tk

--

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+unsubscribe@googlegroups.com.

[Jens-Jørgen Kjærgaard]

And the wee_device problem?

Jens-Jørgen Kjærgaard
www.jensjk.dk

[Jens-Jørgen Kjærgaard]

And the wee_device problem?

Jens-Jørgen Kjærgaard
www.jensjk.dk

On 17 Dec 2017 12:56 pm, "Thomas Keffer" <tke...@gmail.com> wrote:

[Thomas Keffer]

It's not really a "problem," you just needed to specify the path to wee_device. It appears that you used the setup.py method of install, so it would be:

cd /home/weewx

./bin/wee_device weewx.conf --info

-tk

[Jens-Jørgen Kjærgaard]

Thanks - again.

As evident, I understand only a little of the logics of all this :-).

But I will try to implement your suggestions - being a little difficult, as the rpi is on a remote location in my hut, with only intermittent power in our dark midwinter, and I can't ssh into it, as it is on a mobile network, changing ip with every reboot (you wouldn't have any suggestions to solve this? Googled some answers, but it seems rather complicated).   

Jens-Jørgen Kjærgaard

Sønderstrand 5

9300 Sæby

+45 21204417
www.jensjk.dk

[mwall]

On Sunday, December 17, 2017 at 8:12:19 AM UTC-5, Jens-Jørgen Kjærgaard wrote:

But I will try to implement your suggestions - being a little difficult, as the rpi is on a remote location in my hut, with only intermittent power in our dark midwinter, and I can't ssh into it, as it is on a mobile network, changing ip with every reboot (you wouldn't have any suggestions to solve this? Googled some answers, but it seems rather complicated).   

the standard way of dealing with this is to use dyndns.  you can do it all on the pi, or you can do it on the router.  usually easier to do it on the router.  the router tells the dyndns service what its public-facing IP address is, then you can connect to your router using a name of your choice, no matter what the IP address is.

1) set up a dyndns account at any dyndns service.  i like freedns, but many are available.  choose a hostname that you can remember, e.g., yourname.mooo.com.  http://freedns.afraid.org/ 

2) configure your router to talk to the dyndns service you set up.

3) configure your router to forward port 22 to the rpi.  this will be called 'port forwarding' in the router configuration.  forward port 22 on the WAN of the router to port 22 at the LAN ip address of the rpi.

4) be sure that sshd is enabled on the rpi

5) connect to your pi with 'ssh p...@yourname.mooo.com`

you should also ensure that root is not allowed to remotely access the pi, and you should ensure that the password for the pi account is secure and not trivial.  for additional security, use only PKI certificates to connect to the pi - no passwords.

m

[Jens-Jørgen Kjærgaard]

Well, it is a stand-alone installation, no router, the rpi connects directly to the internet via a usb-dongle.

But it can be done anyway?

Jens-Jørgen Kjærgaard

Sønderstrand 5

9300 Sæby

+45 21204417
www.jensjk.dk

--

[mwall]

On Sunday, December 17, 2017 at 10:11:16 AM UTC-5, Jens-Jørgen Kjærgaard wrote:

Well, it is a stand-alone installation, no router, the rpi connects directly to the internet via a usb-dongle.

But it can be done anyway?

yes.  in that case you run the dyndns client software on the pi, and you do not have to do any port forwarding.

1) create account and choose a computer name at your dynamic dns provider, e.g., http://freedns.afraid.org

2) configure the pi to talk to your dynamic dns provider

3) ensure that sshd is running on the pi

4) connect to the pi using ssh

details vary from one dynamic dns provider to another.  one of the reasons i like freedns is that the service is as simple as it gets.  there is no fancy software required - you can do it with a one-line crontab.

here is a guide that takes you through every step of the process:

https://thelastmaimou.wordpress.com/2014/03/23/find-pi-everywhere-freedns-a-free-dynamic-dns-service/

[Jens-Jørgen Kjærgaard]

Thanks for all - will try it!

Jens-Jørgen Kjærgaard

Sønderstrand 5

9300 Sæby

+45 21204417
www.jensjk.dk

[Jens-Jørgen Kjærgaard]

Works fine - but unfortunately my ISP apparently doesn't allow incoming connections on their mobile broadband. No route to host.

Jens-Jørgen Kjærgaard
www.jensjk.dk

[Andrew Milner]

I'm a little confused now - you say

1) works fine

2) ISP does not allow incoming connections

what exactly works, and what doesn't??

To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.

[Jens-Jørgen Kjærgaard]

The redirect of the request from a name to an IP works fine - except when that IP belongs to a mobile device

Jens-Jørgen Kjærgaard
www.jensjk.dk

To unsubscribe from this group and all its topics, send an email to weewx-user+unsubscribe@googlegroups.com.

[Andrew Milner]

I assume that you still have to open the port on the mobile device, and may need some assistance from your IP in order to achieve that goal.