Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple radios into single Weewx instance? #165

Closed
vmstan opened this issue Aug 24, 2022 · 2 comments
Closed

Multiple radios into single Weewx instance? #165

vmstan opened this issue Aug 24, 2022 · 2 comments

Comments

@vmstan
Copy link

vmstan commented Aug 24, 2022

I'm currently monitoring multiple devices on two frequencies, 433.920M and 915M, hopping between them. It generally works but occasionally I miss packets depending on when devices broadcast them, polling intervals, etc. It seems like the solution to my problem is two SDRs to constantly monitoring each. I think I understand from an rtf_433 command perspective how to trigger a specific device, but how would I configure weewx.conf to poll both?

@matthewwall
Copy link
Owner

matthewwall commented Aug 24, 2022

you probably want to run two weewx instances - one weewx for each sdr, with one sdr looking at 915Mhz and one sdr looking at 433Mhz

each weewx instance would have its own conf file, database, and html report(s).

then you can combine the output into a single report using wee_reports

@vmstan
Copy link
Author

vmstan commented Aug 24, 2022

Ah, wee_reports might be what I've been missing. I saw where you could have multiple instances of Weewx on the same box, but the documentation mentioned it's own database and reports, but nothing about a single report. I dump to an external SQL server on a Synology so I wasn't sure if there was a way to share, but having a unified report from both datasets would be fine. Thanks.

@vmstan vmstan closed this as completed Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants