LoRaWAN Water Quality Monitoring Sensors device to device communication and data acquisition
Budget: $1,500 – $3,000 USD
LoRaWAN sensor devices currently send periodic reports to “The Things Network”, which are recorded by TTN’s server. There is a series of objectives that must be accomplished by the applicant in order to make this useful to WaterLine Inc., as follows:
A MySQL or similar database will be setup on a stable server platform.
Report records gathered by TTN must be forwarded to the established database MIRROR the lorawan server.
A web-based facility to provide access to reports stored in the database will then be required. The database will collect reports from sensors which can belong to different Waterline clients. It will be necessary to manage those clients including association of sensor subsets to specific clients. Access will be private within client datasets.
The database must next be expanded to provide for outgoing controls to specific LoRaWAN devices. Those controls would be forwarded to TTN’s server for outbound queing to LoRaWAN nodes.
Certain LoRaWAN devices will send messages to other devices by way of TTN’s server. Devices paired in this manner are usually sensor/actuator systems. Receiving devices will operate in the class C mode. (Always available)
The initial node reports three water level probes and one digital input. That node is capable of reporting temperature, but does not at this time. The system shall be capable of supporting different types of nodes; and, each node type is subject to growing feature sets.
Eventually, the LoRaWAN server that is in the public domain (The one TTN uses) will be cloned to run on the server that hosts the database.
A mobile app for this project.
The packets MUST be in a plain UDP message only.
A MySQL or similar database will be setup on a stable server platform.
Report records gathered by TTN must be forwarded to the established database MIRROR the lorawan server.
A web-based facility to provide access to reports stored in the database will then be required. The database will collect reports from sensors which can belong to different Waterline clients. It will be necessary to manage those clients including association of sensor subsets to specific clients. Access will be private within client datasets.
The database must next be expanded to provide for outgoing controls to specific LoRaWAN devices. Those controls would be forwarded to TTN’s server for outbound queing to LoRaWAN nodes.
Certain LoRaWAN devices will send messages to other devices by way of TTN’s server. Devices paired in this manner are usually sensor/actuator systems. Receiving devices will operate in the class C mode. (Always available)
The initial node reports three water level probes and one digital input. That node is capable of reporting temperature, but does not at this time. The system shall be capable of supporting different types of nodes; and, each node type is subject to growing feature sets.
Eventually, the LoRaWAN server that is in the public domain (The one TTN uses) will be cloned to run on the server that hosts the database.
A mobile app for this project.
The packets MUST be in a plain UDP message only.