I have esp with teleinfo board running tasmota. Everything works fine.
I now just discovered that my induction heating stove drains about 10W on standby and whopping 200VA of reactive power! apparently this is common thing with induction stoves. My energy provider charges only for active power, so this does not matter for billing. But for data logging this matters. Because the linky is showing and sending to teleinfo only Apparent power (total power). The easy fix is just deduct 200 from all my graphs, but I don't like this solution.
Is there a way to get Real (active )power from Linky meter? Or Apparent power and power factor ?
This is so stupid that I get charged for one thing (active power) but the screen on meter shows another thing (App. power)

@charles
I think I found the solution. I needed to enter two lines

EnergyConfig Historique
EnergyConfig full

Now the updates are consistent.

Now I have PAPP update every 1.4 s.
Tasmota works much better than custom arduino program using the library. Even on softserial with esp8266.
Thanks
The problem solved.

@charles I am sure the connection is ok you don't need to see the assembly. because it worked 1 hour before with serial.swap and I did not change anything apart from the software. The red light that indicated the TIC serial activity is flashing as before.

"that Tinfo RX pin is on GPIO13 (template should have set it) ?" - Yes the 13 is set to tinfo rx. In my custom arduino software I used

SoftwareSerial serialsoft1(13, 12);

And it worked. So it is fine with connection on 13.

I don't want to waste any of your time. I will do it again with esp32, it should work better.

@charles I tried serial.swap . It worked! But it works pretty much the same way as before serial.swap. Still the interval between updates is reaching 10-20 seconds sometimes.

I also tried making tasmota teleinfo as you described previously. I applied the template

{"NAME":"Wemos Teleinfo","GPIO":[1,1,1,1,640,608,1,1,1,5152,1376,1,1,1],"FLAG":0,"BASE":18}

(The one that you wrote in previous message is for esp32)
and put in two command into console.

14:09:57.984 CMD: EnergyConfig Changed
14:09:57.987 TIC: Raw to 'changed'
14:09:57.991 MQT: tic/RESULT = {"EnergyConfig":"Done"}

I can change the RGB led via the web interface,
I see that it is connected to mqtt but is sends no data to specified topic. and the web interface show this

Probably resoldering the shield to esp32 board is the simplest solution.

@charles Yes, I use gpio13 like so:

SoftwareSerial serialsoft1(13, 12); // Teleinfo Serial

My setup contains

void setup(void)
{ 
Serial.begin(115200);  
serialsoft1.begin(1200);
tinfo.init();
Serial.swap();
tinfo.attachData(print_values);
Serial.println(F("Teleinfo started"));
}

Now after I added the swap() it stopped receiving anything on that port. It senses no teleinfo data. swap is some kind of magic

@charles Thanks. I will try that.
I did not know that esp8266 has this limitations. I should have just soldered the esp32 board to the shield that I bought from you.

I am using wemos clone and wemos shield.
I want to send the current power level value over mqtt every time it is received from Linky (even if it was not changed).
I use this function to find the PAPP and send it over mqtt:

void print_values(ValueList * me, uint8_t  flags)
{
   while (me)
  { 
   String a= (me->name);
   String b= (me->value);
   if (a=="PAPP"){
    Serial.println("I found PAPP !!!!!!");
    client.publish(MQTTChannelToPublish, b.c_str());
   }  
    me = me->next;
  }
}

This function is attached to

tinfo.attachData(print_values);

The main loop contains this :

if (WiFi.status() != WL_CONNECTED) connecttobestwifi();
  else  if (!client.connected()) connecttoMQTT();
  client.loop();

  if ( serialsoft1.available() ) {
    tinfo.process(serialsoft1.read());
  }

It works fine. Now if i use node-red functionality to measure the interval between messages I observe this:

As one might see the time between PAPP updates are different. Sometimes is reaching 30 seconds! The second graph shows a number of updates per 10 seconds, a lot of times this value goes to zero.
Is this normal for Linky meter? Or maybe there is a problem with my softserial that is missing packets? It looks like the frequency of mqtt updates are much less than frequency of updates that are coming from the linky.