Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

ESP IOT net

Hamid s k last edited by

I was wondering if anyone could help me to my idea about making Hme IOT project with networks of ESP modules , The idea is using async webserver on AP ESP module and other ESP station enabled sensor devices can send the data and receive the commands from server, the rate of data logging wont be rather than 1 request per second
what strategy should I use ? sync or async
what header type? TCP or MQTT
I might add, the ESP AP server host the webpage , which is user can login and watch data or activities
also on net configuration when we intend to add new node to this net , how ESP client introduce itself to ESP AP server and send its information such as IP address, Number of sensor attached , type of sensor,...so after user can configure the sensor on the web page
Reply Quote 0
1 Reply Last reply

1
Posts

877
Views

Suggested Topics

Update RF24 library to latest version
Bug Reports • • andriej

4

0
Votes

4
Posts

2570
Views

@andriej Hi, I had problem using the main branch mysensors/Raspberry, that because of the bit-field struct (header_s) in Sensor.h They will get packed in different order on the arduino compared to the RPi (at least with my compiler, gcc). In order to fix this I created the 1.4dev branch. It uses full bytes instead of the bit-fields, but you need (of cause) to compile both the sensors (arduino) and the gateway (RPi) using the 1.4dev branch. We need to fix this in the main branch later on (and use the same files as in mysensors/Arduino/libraries/MySensors)
Gateway on Raspberry pi 1
General Discussion • • mimaret

9

0
Votes

9
Posts

44
Views

@mimaret It was a pleasure. Thank you for your feedback!
Need advice on solar powering with LiFePo4 battery
General Discussion • • willemx

17

0
Votes

17
Posts

166
Views

LiFePO4 batteries are a great choice because they have a long life cycle and are much safer than other lithium-based batteries. However, you need a solar charge controller that’s compatible with LiFePO4 to prevent overcharging and maintain efficiency. A good MPPT controller can significantly boost energy harvest from your panels. Also, ensure your solar panel output matches your power needs. If you're in solar ireland, you might find some local companies that offer tailored solutions for maximizing solar efficiency in lower light conditions.
Anybody got one / a few spare minimalist rfm69hw shields for wemos d1 mini?
General Discussion • • kiesel

4

0
Votes

4
Posts

21
Views

Thanks for the offer @TheoL ! I have moved on to a differenct project. Also, a lesson that I have learned many times, "If it works, don't fix it!" -OSD
What's a good power bank for use with IoT?
General Discussion • • NeverDie

20

1
Votes

20
Posts

179
Views

@OldSurferDude Thanks a very valued to know. I was wondering today why my (big) powerbanks fall down after short time. I have small 1 & 2-pieces powerbanks, they work very well. I use also BSM hw-168 or hw-107 for charging single 18650. Will try to use them outside also with small solarpanels.
Running out of nodeId's
General Discussion • mysensors • • NielBierman

8

3
Votes

8
Posts

47
Views

@TheoL Not only did I put in delays, too, but I put in delays that were based upon the ID (which was stored in NVRAM)! This helped. caveat: This is probably not accurate be helps to explain the challenges with a large network. My initial experience with Arduino/nRF24 was using the libraries from TMRh20. Those libraries allowed a node to be a repeater, but only for 6 nodes. The primary node 0, master, only allowed 6 nodes to connect to it. The nodes connected to it also allowed 6 nodes. Subsequent nodes had to go through one of these repeating nodes. But the depth was only 4 deep. The master assigned node IDs if the node didn't already have one; similar to a MAC address. The master also kept track of the addresses (ARP table?). Addresses were 4 octets (base in the form of D/C/B/A. A node connected directly to the master had an address of 0/0/0/a (where 0/0/0/0 was reserved for the master). A node connected through another node had an address of 0/0/b/a, and so forth. But what happens is that a parent node has to mange the data from all its child nodes and their child nodes and their child nodes. Thus a node would get so bogged down dealing with this traffic that it din't do its sensor task very well. It is my belief that MySensors either uses TMRh20's libraries or has developed some aspects based on his initial work. I see that that TMRh20 has a version 2 and I have not experimented with it. I did find that MySensors worked better than version 1. Thus, my curiosity. I am also duly impressed at the magnitude of hardware. Currently a nano like device from Aliexperss is US$2-3, nRF24 ~ US$1, power supply ~ US$1.50, power cord ?, case?, sensors!? While the hardware cost is daunting, even with a PCB it's a lot of work building those up. So, yeah, I'm impressed! -OSD