Hi Matthew,

Thanks for the hint. I just got the router to sniff the network traffic 
between the hub and the weewx server (it's Fedora not Debian BTW) and as 
it's HTTP and not HTTPS I can set every update unencrypted
e.g.
HTTP 124 GET 
/weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1&id=24C86E090EC1&mt=tower&sensor=00004036&humidity=32&tempf=76.0&baromin=30.24&battery=low&rssi=3
 
HTTP/1.1 

All my sensors are model 06044 indoor temperature/pressure/humidity 
sensors. I can see updates for the 5 other sensors coming from the hub, but 
there's no updates from any other sensor ID, yet this sensor is on 
flickering transmit every minute with a good battery, and its on the desk 
2m from the hub. So it's a complete mystery to me why the hub is not seeing 
it.

That's why I wondered if the hub needs to have it registered, but you say 
that the hub should pick up everything within range regardless,

Anything else I could try?


On Monday 22 January 2024 at 13:56:22 UTC+1 matthew wall wrote:

> On Monday, January 22, 2024 at 2:46:51 AM UTC-5 ken.r...@gmail.com wrote:
>
> Recently I moved home and lost a sensor in one of the packing boxes and 
> then found it again after the battery had been flat for almost 6 months. It 
> displays temperature and humidity and the repeater flickers when it 
> transmits, but weewx is not recording any data for that sensor ID#.
>
>
> what kind of sensor is it?  beware that the 606TX changes its identifier 
> when it is power cycled (when you replace batteries).  that might not 
> affect your configuration since you're going through the bridge/smarthub.
>
> https://github.com/weewx/weewx/wiki/sdr-rpi-recipe
>
>

-- 
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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b98e6aed-ec7c-4616-bcba-0694631fd074n%40googlegroups.com.

Reply via email to