Is there a way to send a ping from ESP8266 without the ping library .. this might solve the warming up of the receivers in my previous question above ? Or is the only way to just send it a connection request to a non-existent page (like this GET /gpio/1 HTTP/1.1\r\nHost: 192.168.1.126\r\n\r\n) in a loop ?
If you want one master and several slaves, I'd say UDP broadcast, and check that you get all replies. To account for missed replies I'd do a "soft" reply check, i.e.: if I miss 10 consecutive replies from one slave, then he's considered dead.
@Devleo Hi there how are you ? Ty for reply .. I get that but I'm not trying to establish if he's dead or not .. I need a reliable way of knowing he received my packet or not .. and the slave has to reply saying "I received it " ...
just to elaborate .. take for example a button on a remote control (the master) .. one click ... only one .. and the receiver (slave) gets it ...I need to make sure it does indeed arrive and the same packet is not responded to several time .. for example as you suggest send it 10 UDP packets
at the moment the webServer seems to work for this but I'm finding I have to kind of warm the receiver (slave) up with a few requests (pakets) first as the first packet is not always acknowldged by the slave
@Develo yes thats exactly why i posed the question here .. when i was working with NRF and also 433MHZ .. i would send a few warm up packets to get the receiver stabilized .. this was achieved by send junk at it
slaves could indeed be only limited by IP range on a given subnet
what would be ideal is a kind of broadcast and each slave in a sort of promiscuous mode
currently i am using webserver example (modified) on each slave .. but as i said after an intermittent amount of idle time they need a little wakeup .. for this i have managed to see a ping works and gets them ready for the client connection (from master (actually webClient example) and then i make the connection (http://whatever/whatever/gpio etc
I'm not sure if the apparent no response is a code/code buffer or delay issue or a hardware issue on the ESP ?
I've tried same on esp12f and 12EX and SONOFF and nodemcu ..
@denman0000_gitlab : First : I am not using MQTT myself and only have done some limited testing/use of MQTT but there are (a lot of) open source MQTT brokers which you can install and use in your own environment. MQTT client is avaible for esp8266 & esp32.