some issues with driver 0.3.1 and weewx 4.5.1 #42
Comments
|
Am going to need some more information on this. Is this repeatable (ie does it happen regularly), sporadic (does it happen irregularly) or a one off occurrence? If repeatable can you edit Can you post the output from the following commands: and (depending on your system you might need to replace |
|
Thanks for your quick reply. Yesterday i restarted the gw1000 device, since this reboot the issue didnt occur again. I will provide you the details if the issue will popup again. BR |
|
OK errors are back again, so there is a issue with driver 0.3.1 and weewx 4.5.1 and the newest GW1000 firmware. Error occurs directly after weewx restart, i attached the debug log... |
|
Thanks, am going to seen in detail the response from the GW1000. Can you edit This will put a lot of data in your log so once the error occurs stop WeeWX and revert to |
|
ok i will prepare the new debug output. meanwhile here is the output of... `root@sandbox:/var/log#PYTHONPATH=/usr/share/weewx python3 -m user.gw1000 --sensors IP address obtained from station config Interrogating GW1000 at 192.168.XXX.XXX:45000 Sensor Status |
|
|
debug output with |
|
Thank you. Are you running the GW1000 driver simultaneously as both a driver and a service? |
|
oh yes, thats possible.... should i remove this line from my conf file: or what would be the recommend use case? |
|
without this this service line i still have the following errors in the log... |
|
The only use case I could think of to use both the driver and service would be if you had two GW1000, but then I would recommend running two instances of WeeWX rather than both the driver and service. I have never tested both the driver and service on a single WeeWX instance. WeeWX must run with a driver but it can only run one driver. You might chose to run the GW1000 driver as a service if you had two (different) stations, for example an Acurite weather station and a GW1000. You would run the Acurite driver as the WeeWX driver and the GW1000 driver as a service. In this arrangement the Acurite driver creates the loop packets and the GW1000 driver (run as a service) augments those Acurite loop packets with data from the GW1000. Not every driver can be run as a driver or as a service, in fact most can only run as a driver. In your case if the GW1000 is your only 'station' you should run the GW1000 driver as a driver (only). If you have another station and a GW1000 and want to amalgamate the data from both stations in the one WeeWX instance then you will need to run one driver as a driver and the other driver as a service. If your other station's driver cannot run as a service then you have no choice, it must be run as a driver and the GW1000 driver run as a service. Hope that makes sense. Bottom line is running the GW1000 driver as a driver and service simultaneously on a single WeeWX instance is an untested configuration. |
I am guessing your GW1000 firmware is up to date? The CMD_READ_SENSOR_ID_NEW command was only implemented in firmware version 1.5.4. Assuming the firmware is up to date can you show me a startup log with debug = 3. Same procedure as before, need to see the log from startup through until the error hits. |
|
Yes GW1000 is up to date, Firmware GW1000A_V1.6.8 is installed. The last log which i attached "weewx_issue_debug3.txt" should include the startup process, if you look at the line....
|
|
Yes, but that log was when you were running both the driver and the service and it showed no |
|
At the moment it looks good... no errors |
|
OK. I will close this. If it recurs you can re-open this issue. |
some issues with driver 0.3.1 and weewx 4.5.1 too.
Originally posted by @Zaschii in #41 (comment)
The text was updated successfully, but these errors were encountered: