Thanks for your answer Adrew,
I undertand what you say.
The power supply is big enough to handle the Raspberry.
In the meantime I recovered an USB powered hub and I started some testing,
I'll let you know if it works
Il giorno sabato 20 gennaio 2018 09:42:53 UTC+1, Andrew Milner ha scritto:
>
> I have never tried the pizero-w with a usb connection, just via Bluetooth
> connected devices - but if it is anything like the other Pis - have you
> tried connecting the station via a POWERED USB hub rather than using the
> micro port of the pizero? It may work more reliably. Certainly I use
> powered hubs on my rpi3 and rpiB with no issues.
>
> Also ensure your supply for the pizero-w itself is up to the task The
> pizero is a low current user, but not necessarily the case for connected
> peripherals - especially if they are also being powered by the usb
> connection.
>
> So - try a powered hub and maybe a different power supply if the hub
> option fails to solve your issues.
>
>
>
> On Saturday, 20 January 2018 10:34:53 UTC+2, cbergy wrote:
>
>> Hi all,
>>
>> I own a brand new LaCrosse ws1640 directly connected to my Raspberry PI
>> Zero W, and I'm trying to collect data using Weewx.
>>
>> Everything sould be up to date, I installed Raspbian recently and I
>> installed Weewx on Raspbian using the repository as shown in the user guide.
>> To get data from the weather station Weewx is configured to use the TE923
>> driver, and data is stored locally on a mySQL database.
>>
>> I'm experimenting a lot of timeout problems, and some minor protocol
>> errors.
>>
>> These problems are not predictable, in the sense that everything may work
>> for hours but suddenly the software starts logging timeout messages and the
>> station gets unreachable.
>> When I restart weewx usually it does't connect immediately; sometimes
>> physically disconnecting the station and reconnecting helps, sometimes not.
>>
>> This is a typical portion of the syslog:
>>
>> Jan 20 08:30:29 raspberrypi weewx[386]: engine: retrying...
>> Jan 20 08:30:29 raspberrypi weewx[386]: engine: Using configuration file
>> /etc/weewx/weewx.conf
>> Jan 20 08:30:29 raspberrypi weewx[386]: engine: debug is 1
>> Jan 20 08:30:29 raspberrypi weewx[386]: engine: Initializing engine
>> Jan 20 08:30:29 raspberrypi weewx[386]: engine: Loading station type
>> TE923 (weewx.drivers.te923)
>> Jan 20 08:30:29 raspberrypi weewx[386]: te923: driver version is 0.24
>> Jan 20 08:30:29 raspberrypi weewx[386]: te923: polling interval is 10
>> Jan 20 08:30:29 raspberrypi weewx[386]: te923: sensor map is {
>> 'extraBatteryStatus1': 'bat_2', 'outTemp': 't_1', 'outHumidity': 'h_1',
>> 'extraHumid4': 'h_5', 'uvBatteryStatus': 'bat_uv', 'extraHumid2': 'h_3',
>> 'extraHumid3': 'h_4', 'rainLinkStatus': 'link_rain', 'extraHumid1': 'h_2'
>> , 'rainBatteryStatus': 'bat_rain', 'extraTemp2': 't_3', 'extraTemp4':
>> 't_5', 'uvLinkStatus': 'link_uv', 'windLinkStatus': 'link_wind',
>> 'outLinkStatus': 'link_1', 'extraBatteryStatus2': 'bat_3',
>> 'extraBatteryStatus3': 'bat_4', 'windBatteryStatus': 'bat_wind',
>> 'outTempBatteryStatus': 'bat_1', 'extraBatteryStatus4': 'bat_5',
>> 'extraTemp3': 't_4', 'extraLinkStatus1': 'link_2', 'extraLinkStatus2':
>> 'link_3', 'extraLinkStatus3': 'link_4', 'extraLinkStatus4': 'link_5',
>> 'inTemp': 't_in', 'inHumidity': 'h_in', 'extraTemp1': 't_2'}
>> Jan 20 08:30:29 raspberrypi weewx[386]: te923: Found device on USB bus=
>> device=
>> Jan 20 08:30:29 raspberrypi weewx[386]: te923: read: address 0x0000fc
>> Jan 20 08:30:30 raspberrypi weewx[386]: te923: Failed attempt 1 of 5 to
>> read data: [Errno 110] Operation timed out
>> Jan 20 08:30:30 raspberrypi weewx[386]: te923: Waiting 5 seconds before
>> retry
>> Jan 20 08:30:37 raspberrypi weewx[386]: te923: Failed attempt 2 of 5 to
>> read data: [Errno 110] Operation timed out
>> Jan 20 08:30:37 raspberrypi weewx[386]: te923: Waiting 5 seconds before
>> retry
>> Jan 20 08:30:43 raspberrypi weewx[386]: te923: Failed attempt 3 of 5 to
>> read data: [Errno 110] Operation timed out
>> Jan 20 08:30:43 raspberrypi weewx[386]: te923: Waiting 5 seconds before
>> retry
>> Jan 20 08:30:49 raspberrypi weewx[386]: te923: Failed attempt 4 of 5 to
>> read data: [Errno 110] Operation timed out
>> Jan 20 08:30:49 raspberrypi weewx[386]: te923: Waiting 5 seconds before
>> retry
>> Jan 20 08:30:55 raspberrypi weewx[386]: te923: Failed attempt 5 of 5 to
>> read data: [Errno 110] Operation timed out
>> Jan 20 08:30:55 raspberrypi weewx[386]: te923: Waiting 5 seconds before
>> retry
>> Jan 20 08:31:00 raspberrypi weewx[386]: import of driver failed: Read
>> failed after 5 tries (<class 'weewx.RetriesExceeded'>)
>> Jan 20 08:31:00 raspberrypi weewx[386]: engine: Unable to load driver:
>> Read failed after 5 tries
>> Jan 20 08:31:00 raspberrypi weewx[386]: **** Waiting 60 seconds then
>> retrying...
>>
>> Sometimes (rarely) instead of the timeout errors I get bad header errors,
>> sometimes (even more rarely) both error messages are mixed.
>>
>> I'm a bit stuck, I don't know how to solve.
>> May someone help?
>>
>> Many thanks in advance
>>
>>
--
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.
