Bascom - Atmega1284P + ESP8266 + Domoticz - random JSON data sending

I have a circuit with the configuration as in the title ( to which DS sensors, BME280, SD recording, RFM12 )

The last step is to send via JSON to Domoticz. Unfortunately the sending fails and does it randomly, sometimes after sending data from several sensors, sometimes it will go through the whole "cycle"
The interval between sending is between 20 and 30 seconds, while the interval between sending data for a specific sensor is 11 minutes.
The whole code is attached, I paste only the part responsible for Domoticz + the Select Case fragment. For the reception of the UART, I used Serial0charmatch according to Niveasoft's idea.
.

And now connecting to the UART from the Tx side of the ESP8266 I have:
.

It looks like the Atmega stops responding to the "OK" response - to the AT+PING="192.168.0.92" command. The ESP8266 is unlikely to be at fault - it sends back "OK" and the Atmega should start sending at that point. I reset it while it was running, this didn't change anything, only a reset of the whole chip helps - for a while.

In addition, as a "bonus" ( but this requires a look at the code ) up to the moment when sending to Domoticz still works, communication with Master 2 does not work, at the moment when sensor data is no longer sent to Domoticz, receiving data from Master 2 starts to work as it should. And, of course, apart from this problem, the whole thing works - whether data is sent or not - reading sensors, sending to clients and writing to SD - it all works.

What could be the reason for this behaviour of the Atmega UART ?

I converted the program to Atmega328. Now it just has to receive data from the master on the Atega1284p and send to Domoticz.
.

I also changed the IP address where it sends the PING to 8.8.8.8

But nothing has changed. Sometimes a "+timeout" pops up
.


Maybe Domoticz itself ( installed on Orange PI Zero ) is doing some problems ? Maybe I am updating too often ?
I guess it will come to wait for someone smarter to brag about their achievements.

Eventually I send to Domoticz like this:
.

It works, but only once after a power on/reset.
Maybe someone can suggest what is wrong ? The only idea is that the UART is not handled properly. Maybe you need to throw away that extra flag Domoticz_en , just in the first Case of the Domoticz_send subroutine to parse it ?

I know and use the other UART, even just to know where the program is.
But it seemed to me that plugging in the Tx of the ESP8266 would make the most sense.
RealTerm showed the CrLF characters
.

Note that the first time is fine - it passes all 28 entries. Maybe the ESP8266 is sending something and this is "clogging up" the UART. So far RealTerm is only showing CrLf characters after CLOSED

.

If you have the ability to do so, that would be great. As you can see the Atmega is behaving strangely. As if it doesn't work at all I would look for the problem in the code.
It's not likely a hardware problem, the operating conditions don't change.

Well it's Orange Pi Zero easier, all you need is a terminal set to 115200 and Putty, to start with I was connecting via terminal, now I'm connecting via SSH.
I've done a little bit of work with it, i.e. activated the ports, tried to control them from Python, installed a server with PHP 5, MySql, Apache 2.

The Orange Pi Zero doesn't have HDMI, only composite I think.
Even a DUC program to communicate with the Noip - except that something doesn't work Noip - I can see the address from the Noip on the local computers, i.e. I either type in the IP or the address from the Noip and it works, but externally it doesn't work - I even ventured a topic on the forum.

Unfortunately today I had to change my router for a TP-Link TD-W8970 ( I just had one )
The result is that even after a reset it does not send - it is as follows
.

Maybe some router setting is causing the problem.

I have converted it so that it only sends a test value ( random ) every 8 seconds



there is a problem with receiving from ESP

Communication with tx ESP:
.

After AT ( or after Ping, depends how I initiate ) the module does not send OK. Then after the connection it does not answer CONNECT, so it is probably about the answer "Link is not valid".

Added after 18 [hours] 29 [minutes]: .

I added
Clear Serialin0
Com1_str = ""

i.e.

and it works. I'm going to try to adjust this for bulk shipping.

The final result looks like this:
.

Admittedly, after several hours of operation, sometimes only the first sent record arrives ( but only the first one ) intermittently ( interestingly there are entries in the database but with the last received value ). I need to hook it up to the UART and see what happens.

Hello
This is how I read it today, and I don't know if you have solved the problem.
But I don't see anywhere in the code the command AT+CIPCLOSE=5
and it is needed for the ESP8266 to work properly
maybe I'm wrong.
Greetings Marian