DSMR module does not add extra gas sensor for second obis gas meter channel (obis ID 1-2:24.2.1)

[subNiels]

The problem

The network operator replaced my gas meter for a new one. This one is connected to the same power meter. When reading the output of my energy meter using the P1 serial converter I see that the new gas meter is available on a new obis ID (0-2:24.2.1):

As seen below the old meter is still available in the telegram data and the new meter is added on the second gas slot (maximum reserved in protocol is 4)
0-1:24.1.0(003)
0-1:96.1.0(47303003138)
0-1:24.2.1(220302095001W)(04225.102m3)
0-2:24.1.0(003)
0-2:96.1.0(47303003231)
0-2:24.2.1(220303100006W)(00003.745m3)

However in home assistant the DSMR module does not add a new gas sensor, tried reloading re adding the module without any success.
The DSMR is configured to automatically add new sesnors:

Only the first gas meter is shown as device sensor

Below the protocol description of the gas data

The used energy meter is a ISKRA AM550 using DSMR version 5

What version of Home Assistant Core has the issue?

core-2022.3.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

DSMR

Link to integration documentation on our website

https://www.home-assistant.io/integrations/dsmr/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant]

dsmr documentation
dsmr source
_{^{(message by IssueLinks)}}

[probot-home-assistant]

Hey there @RobBie1221, @frenck, mind taking a look at this issue as it has been labeled with an integration (dsmr) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[subNiels]

The problem may lie in the dsmr-parser itself.

The code below is from https://github.com/ndokter/dsmr_parser/blob/master/dsmr_parser/parsers.py
Line 52 and below

The code loops trough all objects of the telegram specifications, but on the first hit in the telegram_data it stops. Instead of reading all lines and match those with the objects. So when it reads the first gas meter addressed on 0-1:24.2.1 it is a match and never parses the second gas meter 0-2:24.2.1.

[subNiels]

See also ndokter/dsmr_parser#51

I posted a work around so at least one value of an other channel can be read out. However I think it needs some adjustments on both modules. So when a extra gas meter is made available form the dsmr parser, this will be added as an extra sensor in the gas meter device.

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.