This forum is for LoRaWAN on TTN/TTI only as it is funded by TTI who provide LoRaWAN services - if you’d spent more than 12 minutes on the forum & used search, you’d find that there are no discussions of a non-LoRaWAN nature.
And it might of filled in some of the missing details for you - like a gateway concentrator card being almost entirely for LoRaWAN use and that LW is a standard so cards are universal to all LW networks and that CS is a different LW Network Server so you end up in the same place as running it against TTN.
Also, this forum is for the TTN community and running private networks rather goes against the community ethos. And there’s no context to why you need a private network or how you arrived at the older design of the SparkFun Pro board - unless you aren’t powering via batteries …
Thanks for your reply and apologies if my post caused offence which was not my intention. Also I did read quite a few other posts (on this forum and others) before posting, but perhaps not enough…
Anyway, just to clarify, it’s not that I have any objection to being on TTN, it just seemed to potentially introduce additional complexity that I didn’t need but perhaps that is based upon misunderstandings on my part.
Funnily enough I was about to post a postscript to my original post asking if it might be easier to have a LoraWAN gateway and then integrate my public website (as an applications server) with the TTN network server?
More lack of knowledge - LW isn’t WiFi, it doesn’t just fall out the box - but it’s a known system that if you have mainstream parts then you can be supported along with all the Learning materials provided.
If you want to roll your own then you are going to have to look at a lot of code & kiss a lot of frogs to get something working.
No, not at all, lack of knowledge - look at https://www.thethingsnetwork.org/docs/lorawan/ - you get a free AS with a free NS - that’s a LW server stack with TTN. You setup an integration that sends your data from the AS to your server to do as you wish.
The Learn section will fill in much of the knowledge gaps and is strongly recommended reading before anything else.
It is also strongly recommended not to buy anything without finding out what you can get hold of, how much and then asking for comments on your shortlist. This saves us saying things like “if you’d bought X, then you’d be OK, but as you have Y, you need to do these 37 complex things to get it to do it”. This implies you tell us what sensors, data, how often etc etc. Like a project plan.
