Hi Michael, Vince, all appears to be working now, I think! Thank you, Michael - the issue was that I hadn't adjusted the settings in the gateway (using a GW1200 gateway), as you rightly suggested. All done now and please see the image below:
[image: Screenshot from 2025-12-20 18-31-41.png] When visiting 192.168.1.49/weewx, it is now displaying information from my station - thanks so much. The only issue I see is that when I SSH in to the PI, I don't see /data/report/, so I am guessing I should fix this by adding that file path under root? My logs are here: https://pastebin.com/eGmNfhgL and I do notice: Dec 20 18:41:31 weewx-pi weewxd[1111]: INFO weewx.reportengine: Copied 0 files to /var/www/html/weewx Dec 20 18:41:31 weewx-pi weewxd[1111]: DEBUG weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping. Dec 20 18:41:31 weewx-pi weewxd[1111]: DEBUG weewx.reportengine: Report 'MobileReport' not enabled. Skipping. Dec 20 18:41:31 weewx-pi weewxd[1111]: DEBUG weewx.reportengine: Report 'StandardReport' not enabled. Skipping. ... the "INFO" one at the top, is that the path I am supposed to have instead of /data/report/, in the gateway settings (above image)? Sorry, I am a bit confused here! On Saturday, December 20, 2025 at 6:15:09 PM UTC vince wrote: > What model Ecowitt do you have specifically ? Do you really need to use > interceptor ? Will the original GW1000 driver perhaps work with your model > ? > > On Saturday, December 20, 2025 at 9:55:03 AM UTC-8 [email protected] > wrote: > >> Did you set up your ecowitt device to send data to the weewx machine? >> Which ecowitt device are you using? >> >> O S schrieb am Samstag, 20. Dezember 2025 um 15:12:19 UTC+1: >> >>> Hello all, >>> >>> I am new to weewx and I know basic command line stuff, with a basic >>> understanding of linux in general. >>> >>> I have installed weewx on debian (Bookworm) using the command line and >>> *sudo >>> apt install weewx* on a R-Pi version 1 that I had laying around. I am >>> using Apache2 as the web server that I followed an online guide for >>> installation of, and it works straight out of the box with no need to >>> manually point it to the pages I want served. >>> >>> I initially configured it to use the Simulator and have now added my >>> hardware (Ecowitt) and i would like to swap it over. I have followed the >>> guide, configuring it weewx.conf under [Station] and [Interceptor], using >>> *port >>> = 8000* and *device type = ecowitt-client*. >>> >>> Despite restarting weewx, the simulator is still being displayed when I >>> visit http://my.ip/weewx. >>> >>> Another thing is that when I view the logs by running *sudo journalctl >>> -u weewx -f | tee /tmp/mylog*, and then (in a different terminal) *sudo >>> systemctl start weewx*, I get the following line reported over and over >>> in the logs: *Dec 20 13:40:20 weewx-pi weewxd[1016]: DEBUG >>> user.interceptor: empty queue*. >>> >>> I hope that's enough information to help and I am happy to provide more >>> if needed. >>> >>> I've been battling with things for some time and I have managed to fix a >>> couple of errors but I am stumped here. >>> >>> thank you for this awesome project and i would very much like to get it >>> working! >>> >>> All the best :) >>> >>> -- 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]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/565834b5-7c87-45ce-bc41-9d75e0a9334fn%40googlegroups.com.
