Should run the driver directly so you can capture the packets. Then you can
create your sensor map like Andrew indicated.
Example Capture:
identifiers: {'bridge_id': '24C86E083607', 'sensor_type': '5N1x38',
'sensor_id': '1531'}
raw data:
Is there some documentation somewhere on what the sensor settings should
be? I've not found anything yet on it.
On Tuesday, April 16, 2019 at 6:33:24 PM UTC-4, Jim Snider wrote:
>
> I got my system to connect to everything but solar no data is being
> transmitted to CWOP or PWSWeather.
don't you need a sensor map in the interceptor section??
eg
windSpeed = windspeed.0613.*
outHumidity = humidity.0613.*
outTemp = temperature.0613.*
pressure = pressure.0613.*
etc etc
On Thursday, 18 April 2019 14:50:06 UTC+3, Jim Snider wrote:
>
> Here's the weewx.conf file
Here's the weewx.conf file with the passwords blanked out
On Tuesday, April 16, 2019 at 6:33:24 PM UTC-4, Jim Snider wrote:
>
> I got my system to connect to everything but solar no data is being
> transmitted to CWOP or PWSWeather. Here's what they said that they are
> seeing on their ends.
attaching weewx.conf may also help us a little
On Thursday, 18 April 2019 04:03:24 UTC+3, gjr80 wrote:
>
> Spot on! Same diagnosis though, you need to work through your sensor
> mapping.
>
> Gary
>
> On Thursday, 18 April 2019 10:51:21 UTC+10, Jim Snider wrote:
>>
>> Did another file and I think
Spot on! Same diagnosis though, you need to work through your sensor
mapping.
Gary
On Thursday, 18 April 2019 10:51:21 UTC+10, Jim Snider wrote:
>
> Did another file and I think I caught the startup data
>
>
>
> On Tuesday, April 16, 2019 at 6:33:24 PM UTC-4, Jim Snider wrote:
>>
>> I got my
Did another file and I think I caught the startup data
On Tuesday, April 16, 2019 at 6:33:24 PM UTC-4, Jim Snider wrote:
>
> I got my system to connect to everything but solar no data is being
> transmitted to CWOP or PWSWeather. Here's what they said that they are
> seeing on their ends.
>
Jim,
Better, we can see the activity going on at the end of each archive
interval, archive records being saved, CWOP and WU postings. It confirms
what I said in my previous post regards the interceptor and sensor mapping.
Just one more thing about posting logs, often we ask for the log from
OK. One more time. :-)
I used a different terminal program this time
On Tuesday, April 16, 2019 at 6:33:24 PM UTC-4, Jim Snider wrote:
>
> I got my system to connect to everything but solar no data is being
> transmitted to CWOP or PWSWeather. Here's what they said that they are
> seeing
OK, hopefully 3rd time is a charm :-) Got 5 minutes worth of data
On Tuesday, April 16, 2019 at 6:33:24 PM UTC-4, Jim Snider wrote:
>
> I got my system to connect to everything but solar no data is being
> transmitted to CWOP or PWSWeather. Here's what they said that they are
> seeing on
OK, better but still not quite there yet :)
Easier to read but .txt would be better. Main issue though is that log
extract shows us 37 seconds of activity which is predominantly just chatter
from the interceptor driver. Have a look at the example log extract I
posted, you will notice the
OK, let try this agin with this file.
On Tuesday, April 16, 2019 at 6:33:24 PM UTC-4, Jim Snider wrote:
>
> I got my system to connect to everything but solar no data is being
> transmitted to CWOP or PWSWeather. Here's what they said that they are
> seeing on their ends.
>
>
> *Joe
Thanks but that is not quite what we are after, its very hard to make sense
of and does not contain what we need to see. Really need to see something
like this (but perhaps a bit longer):
Mar 7 13:47:09 stretch7 weewx[16079]: engine: Initializing weewx version
3.8.0
Mar 7 13:47:09 stretch7
On Wednesday, 17 April 2019 08:33:24 UTC+10, Jim Snider wrote:
>
> Any ideas??
>
Yes, edit weewx.conf, set debug = 2, save weewx.conf then restart WeeWX.
Let WeeWX run for at least 2 archive intervals and then take a copy of the
log from when WeeWX was restarted until the 2 archive intervals
14 matches
Mail list logo
