Thanks that explains the wee_device. Now wee_device command works 100%, but starting daemon is still failing and I cannot find any reason for that. The only reason which i can find is that in log it says "ee_device[1880]: fousb: found station on USB bus= device=". I don't understand why there is no BUS or Device defined.
Anyways here is what wee_device command no displays when i change setting: ~# wee_device --set-interval=15 Using configuration file /etc/weewx/weewx.conf Using FineOffsetUSB driver version 1.9 (weewx.drivers.fousb) Interval is 15 Set interval to 15 minutes (y/n)? y Interval is now 15 On Saturday, March 2, 2019 at 10:57:18 PM UTC+2, Thomas Keffer wrote: > > It is > > * wee_device --set-interval=15* > > not > > * wee_device --set-interval 15* > > With the latter form, it's thinking that "15" is the name of your > configuration file. > > -tk > > On Sat, Mar 2, 2019 at 12:48 PM gizm0 <[email protected] <javascript:>> > wrote: > >> Thank you for your reply. As you can see from the previous message where >> i attached the config the debug is set to 1. >> >> The system worked until 13:49 then it refused to start the service. So >> that's why there is working record on 13:40 timestamp. >> >> Weewx is running off site where it has worked with the same setup from >> last september. At least during last 1 month I have not touched anything. >> The only thing that system has done is upgrade packages automatically on >> 9.2.2019. >> >> Same hardware has been running the setup from last September. The only >> thing that I changed is that I bought 3months ago original Raspberry pi >> power supply ( >> https://cdon.fi/kodin-elektroniikka/raspberry-pi-3-micro-usb-power-supply-p40237610). >> >> Before that raspberry pi reported low voltage errors and that's why I >> bought better supply. >> >> Here is screenshot when i try to manually start the service, set device >> setting and check device status: >> >> [image: raspi2_weewx_02032019.jpg] >> >> >> On Saturday, March 2, 2019 at 9:35:06 PM UTC+2, vince wrote: >>> >>> On Saturday, March 2, 2019 at 11:04:26 AM UTC-8, gizm0 wrote: >>>> >>>> Sorry about that, but the weewx is not starting process so there is no >>>> activities after it has tried to start. Anyways here is the full log. >>>> Notice that weewx stopped to work around 13:49 and after that i have tried >>>> to manually start the service as you can see from the log. >>>> >>>> >>> Next time you do so, please set debug = 1 in your weewx.conf file so we >>> see more verbose logs. >>> >>> I grepped the file to show only lines with 'weewx' on them, and I don't >>> see any places where it actually stopped. Lots of startups, but no stops. >>> I also see a lot of places where it 'did' save records to the database, at >>> least briefly (most recently 13:40:35) so it worked at least for a while, >>> but it's impossible to know what you touched or when after then. >>> >>> Just to eliminate the possibility, did you change any hardware ? Are >>> you powering things with a 'good' power supply ? That can mess up a raspi >>> pretty consistently ? >>> >>> >>> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
