I’m trying to make an app for monitoring water level using flutter on android studio (hedge hog). What I understand is that the work I am doing lies in an IoT category. I have made an UI for water level indicator. I also know about blynk app. Point is I want to make an app just like blynk that resembles my UI that I made, so that I can monitor water level. I have also done work on esp module. i have controlled Leds and relays using Esp module. The UI of mobile app has different types of features, but what I want to achieve is how to recieve/send data between esp and mobile app. One thing I know that I have to use an app like blynk app, but I don’t understand how to make.

what I understand is listed below: Basic knowledge of Flutter so that I can make a UI. Understanding of Esp module to control Leds and relays

Following is my code of UI

import 'package:flutter/material.dart'; class RowWithTwoColumns extends StatelessWidget { @override Widget build(BuildContext context) { return MaterialApp( home: Scaffold( body: Container( child: Row( mainAxisAlignment: MainAxisAlignment.spaceAround, children: [ Column( mainAxisAlignment: MainAxisAlignment.start, children: [ Transform.translate( offset: const Offset(20, 40), child: //Image.asset('assets/images/blue_1.png',width: 30,),), Image.asset( 'assets/images/blue_1.png', width: 30, ), ), Transform.translate( offset: const Offset(20, 80), child: Image.asset( 'assets/images/green.png', width: 30, ), ), Transform.translate( offset: const Offset(20, 120), child: Image.asset( 'assets/images/green.png', width: 30, ), ), Transform.translate( offset: const Offset(20, 160), child: Image.asset( 'assets/images/green.png', width: 30, ), ), Transform.translate( offset: const Offset(20, 200), child: Image.asset( 'assets/images/red_1.png', width: 30, ), ), Transform.translate( offset: const Offset(20, 240), child: Image.asset( 'assets/images/red_1.png', width: 30, ), ), Transform.translate( offset: const Offset(20, 280), child: Image.asset( 'assets/images/red_1.png', width: 30, ), ), Transform.translate( offset: const Offset(20, 300), child: Text( 'WATER\nLEVEL', textAlign: TextAlign.center, ), ), ], ), Column( mainAxisAlignment: MainAxisAlignment.start, children: [ Transform.translate( offset: const Offset(20, 40), child: Text( '100 %', style: TextStyle(fontSize: 20), ), ), Transform.translate( offset: const Offset(20, 80), child: Text( '90 %', style: TextStyle(fontSize: 20), ), ), Transform.translate( offset: const Offset(20, 123), child: Text( '75 %', style: TextStyle(fontSize: 20), ), ), Transform.translate( offset: const Offset(20, 163), child: Text( '60 %', style: TextStyle(fontSize: 20), ), ), Transform.translate( offset: const Offset(20, 204), child: Text( '45 %', style: TextStyle(fontSize: 20), ), ), Transform.translate( offset: const Offset(20, 243), child: Text( '30 %', style: TextStyle(fontSize: 20), ), ), Transform.translate( offset: const Offset(20, 285), child: Text( '15 %', style: TextStyle(fontSize: 20), ), ), ], ), Column(mainAxisAlignment: MainAxisAlignment.start, children: [ Transform.translate( offset: const Offset(0, 32), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 55), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 75), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 98), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 120), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 137), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 162), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 175), child: Text( 'ON \n NOTIFY', textAlign: TextAlign.center, ), ), ]), Column(mainAxisAlignment: MainAxisAlignment.start, children: [ Transform.translate( offset: const Offset(0, 32), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 55), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 75), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 98), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 120), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 137), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 162), child: SwitchScreen(), ), Transform.translate( offset: const Offset(0, 175), child: Text( 'OFF \n NOTIFY', textAlign: TextAlign.center, ), ), ]), ], ), ), appBar: AppBar( title: Text( 'Water Level Indicator', style: TextStyle(color: Colors.white), ), backgroundColor: Colors.blueAccent, centerTitle: true, )), ); } } class SwitchScreen extends StatefulWidget { @override SwitchClass createState() => new SwitchClass(); } class SwitchClass extends State { bool isSwitched = false; void toggleSwitch(bool value) { if (isSwitched == false) { setState(() { isSwitched = true; }); } else { setState(() { isSwitched = false; }); } } @override Widget build(BuildContext context) { return Column(mainAxisAlignment: MainAxisAlignment.center, children: [ Transform.scale( scale: 1, child: Switch( onChanged: toggleSwitch, value: isSwitched, )), ]); } }

following is my UI image

Screenshot_20240426-163923.png

I have tried to get an idea of creating alternative of blynk app using different platforms including the following tutorial whose link I’m sharing but since I’m beginner in esp and cloud that’s why I found it difficult to grasp.
https://www.instructables.com/Build-Your-Own-IoT-Platform-Using-Nodejs-and-ESP82/

If any of the respected member could give me a line of action so I would be glad

Hi everybody,

I have been following this forum for quite a while now and it’s great to see how many designers are working with cellular IoT. We had in the past created some designs based on the PyCOM GPy as it was one of the only solutions that was small and fully certified. When the GPy became EOL we were left in the dark and took on the challenge to create a pin and software compatible upgrade. We have called our module Walter and it has the following functionality:

Ultra low 9.8uA deep sleep current in PSM mode Open source and software support for ESP-IDF, Arduino, Micropython and Toit LTE-M, NB-IoT (3GPP rel. 14) GNSS (GPS + GLONASS) WiFi and BLE CE, UKCA, FCC, IC and RCM certifications

I hope this might be of interest to you, please do not hesitate to ask questions. You can read everything on our Crowd Supply page: https://www.crowdsupply.com/dptechnics/walter

Kind regards,
Daan

They are still running, so this seems to be the (temporary) solution.

@uta I might be biased, but I love it. Thanks a lot - great work 👍

@trick2011 I use the following sequence:

AT+UDCONF=1,0

AT+USOCR=17,7000
<rx socket number>
AT+USOCO=<socket>,“172.127.131.100”,<udp port>
AT+USOWR=<socket>,<data length>

<wait for @>
<send user data>
AT+USORF=<socket>,127 #127 is max rx length, depends on yr buffers

+USORF: <socket>,“172.27.131.100”,15683,17,“downstream data”

AT+USOCL=<socket> # close socket

Hi Mario,

Tuino 096 is an Arduino Zero (M0) compatible board. Grove Base Shield V2.0 doesn’t support this explicitity.

I recommand to try"ARDUINO MKR CONNECTOR CARRIER (GROVE COMPATIBLE)" instead. With this shield you can bridge from Zero/M0 to sensors with Grove connectors.

Regards, Roland

@IoT-Arista Interesting combination. You are right, nRF9160 requires a very different development strategy. It uses Zephyr RTOS and c-api’s to control the cellular modem. In my opinion it is much better to work with than the ancient, slow, outdated AT interface. But if you want to use AT commands on nRF9160 you still can:
https://github.com/nrfconnect/sdk-nrf/tree/master/applications/serial_lte_modem

If you don’t want to redesign you should contact SIMCOM and t-mobile ( @Eric-Barten ) to fix your issue

Ah that’s a shame 😞

Good luck with finding solution.

First complete devices for IoT are already available in the market, for example but not limited to Deutsche Telekom’s Park and Joy, IoT Service Button or Low-Cost Tracker. This includes both existing LPWA hardware being adapted to NB-IoT as well as entirely new devices or modules.
An extract of the available hardware can be browsed here.

In Q4 2017 the first modules will be certified by Deutsche Telekom for permanent operation.

List of currently certified modules and chipset can be found here.

Currently almost all available NB-IoT modules support 3GPP Rel. 13 features, whereas some discrepancies in support of Rel. 14 features still exists, as these are only gradually being integrated by the module vendors.

At the launch of the first NB-IoT live networks (Q2/2017) radio modules were only available from early forerunners (U-blox, Quectel). Since then further vendors like Sequans, Gemalto, Telit, Sierra Wireless etc.have entered the NB-IoT market and increase the range of available products and also the competition.

At the beginning of our commercial launch in Q2/2017 first NB-IoT radio modules were more expensive than the industry target of $5. As expected, this was due to initial low lot sizes, i.e. engineering samples. But since then unit costs have strongly decreased due to much higher production quantities, especially due to the Chinese market, where NB-IoT applications are widely being used at large scale. At this point the industry target of $5 has been reached.

In general, there are three types of hardware:

NB-IoT Chipset/Modem (baseband): NB-IoT protocol processing & frequency modulation. NB-IoT Module: Contains the chipset/modem, Antenna Connection, UICC software support, external interfaces. NB-IoT Device: ready to use including all relevant components for the respective use case e.g sensor, antenna, power supply, memory.

A device can also be a developer board, e.g. Arduino or Raspberry Pi.

Deutsche Telekom has certified the LTE-M GM01Q platform from Sequans, and there are no plans currently to certify the NB01Q (NB-IoT variant of the same platform). This affects all modules based off of that platform, including the pycom G01, gpy and fipy modules.