[t3gathome]

Hi Werk,

3 minutes of pull time would be ok. 4 WiFi Sensors also are fine. And mapping them to extra sensor 1 to 7 is a good idea, to include them!
BUT I would also think about preparing for more wifi sensors e.g. provided by a Raspberry Pi/ESPXX in the network (Wifi, or even wired in the same net).

Getting data outside the local network worked with engolling over a static IP and he is preparing right now a WD at his homebase, so I can receive real data of a WD over the net
He had the idea to extend this feature one step further:
Having a gsm sensor pushing data to a webserver (e.g. with a php script and JSON data format) and then the RX pulling data from that web server (also via php, that provides the data).
So we could also include sensors, that are out of range of 433 radio with that technique and already prepared routines (only changing the hostname/ip and port) .

Setting a hostname works also, but one big problem with the OTA name...: it is with an underscore "_" and the esp changes it unfortunately to a minus "-". That's why I think it was not working for you :/.
I have it working again at my setup :

Code:

if (wifi.createTCP(mux_id, "WD-1", 80, 0)) {

and

char *get_json = "GET / HTTP/1.1\r\nHost: WD-1 host:80\r\nConnection: close\r\n\r\n";

for the final setup I would recommend changing to hostnames (the idea also came from engolling). Sometimes users don't have access to ip management... Or they could change because of a dhcp server, that cannot be switched off.