Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DSMR Slimme Meter - Iskra IE.5 #90797

Closed
3djc opened this issue Apr 4, 2023 · 3 comments
Closed

DSMR Slimme Meter - Iskra IE.5 #90797

3djc opened this issue Apr 4, 2023 · 3 comments

Comments

@3djc
Copy link

3djc commented Apr 4, 2023

The problem

Belgian Iskra IE.5 do not seem to work with DSMR intergation

What version of Home Assistant Core has the issue?

core-2023.3.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

DSMR

Link to integration documentation on our website

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

Diagnostics information

I had a new smart meter installed (Iskra IE.5) and I cannot get data from it. This issue is similar to #87155 where it is suggested that a PR has been opened with 'dsmr_parser' lib

I found said PR that has been merged since (ndokter/dsmr_parser#126), but the DSMR integration seems still unable to parse the data.

That PR suggest to use ISKRA_IE parser (https://github.com/jchevalier7/dsmr_parser/blob/78880a1881a6748865efa45e6d89de7cf917be0e/dsmr_parser/clients/protocol.py#L51) , but that's not in DSMR integration option

Meter data:

1-0:0.0.0(00000000)
0-0:96.1.0(89547619)
0-0:1.0.0(230404213104)
1-0:1.8.1(000016.854kWh)
1-0:1.8.2(000040.107
kWh)
1-0:2.8.1(000126.212kWh)
1-0:2.8.2(000003.603
kWh)
0-0:96.14.0(0001)
1-0:1.7.0(01.449kW)
1-0:2.7.0(00.000
kW)
1-0:21.7.0(01.033kW)
1-0:41.7.0(00.000
kW)
1-0:61.7.0(00.415kW)
1-0:22.7.0(00.000
kW)
1-0:42.7.0(00.000kW)
1-0:62.7.0(00.000
kW)
1-0:32.7.0(234.5V)
1-0:52.7.0(000.0
V)
1-0:72.7.0(236.1V)
1-0:31.7.0(004
A)
1-0:51.7.0(000A)
1-0:71.7.0(003
A)
0-0:96.3.10(1)
0-0:96.13.0()
0-1:96.1.1()
!CC43
/ISk5\2MIE5T-200

1-0:0.0.0(00000000)
0-0:96.1.0(89547619)
0-0:1.0.0(230404213105)
1-0:1.8.1(000016.854kWh)
1-0:1.8.2(000040.107
kWh)
1-0:2.8.1(000126.212kWh)
1-0:2.8.2(000003.603
kWh)
0-0:96.14.0(0001)
1-0:1.7.0(01.462kW)
1-0:2.7.0(00.000
kW)
1-0:21.7.0(01.034kW)
1-0:41.7.0(00.000
kW)
1-0:61.7.0(00.428kW)
1-0:22.7.0(00.000
kW)
1-0:42.7.0(00.000kW)
1-0:62.7.0(00.000
kW)
1-0:32.7.0(234.3V)
1-0:52.7.0(000.0
V)
1-0:72.7.0(236.0V)
1-0:31.7.0(004
A)
1-0:51.7.0(000A)
1-0:71.7.0(003
A)
0-0:96.3.10(1)
0-0:96.13.0()
0-1:96.1.1()
!0D82
/ISk5\2MIE5T-200

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Apr 4, 2023

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.

(message by CodeOwnersMention)


dsmr documentation
dsmr source
(message by IssueLinks)

@3djc
Copy link
Author

3djc commented Apr 5, 2023

I did some test to ensure dsmr_parser 1.2.0 can actutally read my values correctly using a python shell command on another PC. The result seems ok and is this one:

EQUIPMENT_IDENTIFIER_GAS: 89547619 [None]
P1_MESSAGE_TIMESTAMP: 2023-04-05T07:58:03+00:00 [None]
ELECTRICITY_USED_TARIFF_1: 18.370 [kWh]
ELECTRICITY_USED_TARIFF_2: 43.912 [kWh]
ELECTRICITY_DELIVERED_TARIFF_1: 126.308 [kWh]
ELECTRICITY_DELIVERED_TARIFF_2: 3.603 [kWh]
ELECTRICITY_ACTIVE_TARIFF: 0001 [None]
CURRENT_ELECTRICITY_USAGE: 0.000 [kW]
CURRENT_ELECTRICITY_DELIVERY: 0.445 [kW]
INSTANTANEOUS_ACTIVE_POWER_L1_POSITIVE: 0.000 [kW]
INSTANTANEOUS_ACTIVE_POWER_L2_POSITIVE: 0.000 [kW]
INSTANTANEOUS_ACTIVE_POWER_L3_POSITIVE: 0.000 [kW]
INSTANTANEOUS_ACTIVE_POWER_L1_NEGATIVE: 0.363 [kW]
INSTANTANEOUS_ACTIVE_POWER_L2_NEGATIVE: 0.000 [kW]
INSTANTANEOUS_ACTIVE_POWER_L3_NEGATIVE: 0.079 [kW]
INSTANTANEOUS_VOLTAGE_L1: 238.7 [V]
INSTANTANEOUS_VOLTAGE_L2: 0.0 [V]
INSTANTANEOUS_VOLTAGE_L3: 242.2 [V]
INSTANTANEOUS_CURRENT_L1: 4 [A]
INSTANTANEOUS_CURRENT_L2: 0 [A]
INSTANTANEOUS_CURRENT_L3: 1 [A]
ACTUAL_SWITCH_POSITION: 1 [None]
TEXT_MESSAGE: None [None]
EQUIPMENT_IDENTIFIER: None [None]
MBUS DEVICE (channel 1)
EQUIPMENT_IDENTIFIER: None [None]

@issue-triage-workflows
Copy link

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.

@issue-triage-workflows issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 11, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Aug 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants