A few suggestions: 1. Could be a permissions problem. Did you try running as root?
2. The te923 driver has moved on since v3.5.0. Try the current version <https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/te923.py> . 3. Try the diagnostic program included with the driver: cd /home/weewx/bin PYTHONPATH=. ./weewx/drivers/te923.py --help -tk On Sun, Aug 7, 2016 at 2:38 PM, J.L. Blom <[email protected]> wrote: > On 07/08/16 17:37, vince wrote: > >> On Sunday, August 7, 2016 at 8:28:55 AM UTC-7, Joep L. Blom wrote: >> >> Thanks for your reply. No, I have no instance of weewx running. The >> peculiar thing is that weewx simply won't start. I would like to >> trace >> everything from the start of the command:"sudo service weewx >> start" but >> I have forgotten which tools I have to use and the time is becomming >> very short or I will loose weeks of data. >> >> >> You shouldn't lose data if it's in the weewx database from before you >> started unplugging and moving hardware around. >> >> te923: Found device on USB bus=001 >> device=005 >> Aug 7 08:37:17 kangoo weewx[695]: te923: read: address 0x0000fc >> Aug 7 08:37:19 kangoo weewx[695]: engine: Unable to load driver: >> Connection timed out >> Aug 7 08:37:19 kangoo weewx[695]: **** Exiting... >> >> >> That looks to me like weewx is unable to talk to the weather station >> hardware. Did you power everything down before plugging it back in ? Did >> you ensure that whatever you plugged in was connected well before powering >> up the pi ? >> >> It's pretty hard to work these things remotely, but in general whenever >> you start unplugging/plugging hardware in that's a good place to start >> debugging.... >> > > Thanks for your reply. Yes I did that several times but it will not start > up. Both methods have the same effect. Mysterious for me is the syslog > entry \ > > 10:45:40 kangoo systemd[1]: Started LSB: weewx weather system. > > Vince, > Thanks for your reply. Well, the fact that the device is found on USB > bus-001 says that the device is connected and the fact that it knows which > driver to load indicates, in my opinion, that it knows which driver to use. > However. the fact that it says "unable to load driver" can mean that the > driver is not found but how can it read address 0x0000fc? But maybe > mysteriously has between the unplugging and connecting of the device the > driver mysteriously disappeared? > However, it is still in /home/weewx/bin/drivers/te923.py so I don't think > that is the reason. > In short I am stumped. > Joep > > > -- > 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. > -- 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.
