TTN-interfacedriver for WeeWX

[Ton vanN]

Question from a friend with a PWS-type Sensecap S2120 feeding it's data through TTN_LoraWAN to an application.

He would like to connect his PWS to a 'real' meteosoftware like WeeWX.

Searched in vain:
is a driver available which allows to get PWS-data from TTN_LoraWAN into WeeWX?

[vince]

Cool gear.  Looks doable.  There are links to example code and formats for how to decode it here https://files.seeedstudio.com/products/SenseCAP/101990961_SenseCAP%20S2120/SenseCAP%20S2120%20LoRaWAN%208-in-1%20Weather%20Station%20User%20Guide.pdf#page40 if there are any others looking for that.

[Graham Eddy]

for my LoRaWAN dragino gear, i wrote an ‘uplinks’ daemon to listen for raw mqtt uplink messages from TTN Network Server (i run my own instance) and publish per-device condensed and digestible mqtt that weewx picks up. note that weewx interface is mqtt service/driver for transport and the ‘uplinks’ daemon for application data. neat & reliable

⊣GE⊢

--
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+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/90d9b658-945a-442a-8582-88ab87b2671cn%40googlegroups.com.

[Ton vanN]

That daemon might be quite useful!
Working with what type of PWS?
😉 Because PWSes hardly have a standard interface for output data, and at least some 'translation' will be required.

Op za 4 jan 2025 00:11 schreef Graham Eddy <g...@geddy.au>:

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/9ED7EABA-8366-410A-BE71-A854A06784BC%40geddy.au.

[Graham Eddy]

the architecture is different from that, but i won’t go into the details

yes, the ‘uplinks’ daemon needs an adapter for each payload type to map from whatever the LoRaWAN Network Server decodes from the device, to convert into a friendlier digestable message. i allow user-defined classes written in python picked up by daemon from /etc/uplinks.d/ - they are very simple (because the decoded payload is extracted and handed to them), usually just changing field names and some simple arithmetic

(e.g. my river level ultrasound sensor just needs to subtract river surface distance distance from known fixed height to deduce the river level)

you might note weewx gets no mention there. the published mqtt messages can go anywhere, including into weewx; e.g. i have an old mobile phone with no SIM card sitting on my fridge that simply runs an mqtt listener inside a browser and display values directly (weewx is for archiving, and publishing to internet)

⊣GE⊢

To view this discussion visit https://groups.google.com/d/msgid/weewx-user/CAGGBBxO4kxOY-Xt4K5VYcG%3DCHj7pFc-9wN8pgyQEddW3DocP-w%40mail.gmail.com.