DSMR slimme meter intergration with new Sagemcom XT211 problem

[jacoch]

The problem

Hi,

My previous device was a Sagemcom T211 and was working fine for a long time. It has been replaced by the new XT211. Since then, I'm unable to configure the integration. If I use the same 5B version, it just times out when adding it. The only version that is working is 5S that seems to do less validations on setup. But a lot of data is missing. I've included the log that shows some errors and telegrams while trying to add that device.

Is there any chance to make that version be readable by DSMR slimme meter? Or is there another way to setup that device? Thanks

What version of Home Assistant Core has the issue?

2024.4.3

What was the last working version of Home Assistant Core?

2024.4.3

What type of installation are you running?

Home Assistant Container

Integration causing the issue

DSMR slimme meter

Link to integration documentation on our website

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

Diagnostics information

home-assistant_dsmr_2024-04-23T19-28-39.514Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

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!

Code owner commands

Code owners of `dsmr` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign dsmr` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[jacoch]

I've been in touch with my electricity provider and he confirmed that Sagemcom made a mistake in the current firmware. They will fix this in a futur update at end of the year. In the meantime, what do you recommend to fix this? Is there a way I can reformat the data between the counter and HA? Here is a table with the errors (the second column is the sent code and the last one it's the expected code):

By looking at HA log, I notice that another entry has a problem. I indeed see that this line is sent:

0-0:98.1.0(2)

It seems incomplete. I tried to modify parsers.py to fix that error and accept the wrong entries, but it wasn't successful. It seems something else is causing an issue.

[jacoch]

After comparing more in detail the data received and the expected data, I've notice that another line is wrong. It's that one:

0-0:0.0.0(123456789012)

I replaced my real id. It should indeed be

0-0:96.1.1(123456789012)

After modifying the parser to read equipment id from that value and ignore the line 0-0:98.1.1 that is incomplete, I've been able to setup DSMR slimme meter again. It's a temporary fix that need to be applied on each reboot of my NAS, but at least it works in the meantime. I've returned this information to our electricity provider so that it can ask Sagemcom to fix this in a future update.

[issue-triage-workflows[bot]]

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.