Single phase meter Iskra 550 no power values #5
Comments
HarryHase4
changed the title
HarryHase4
changed the title
|
actuel data: |
|
I found an older fork, which i can compile, there i made a "ugly hack" in the decoder. I don't understand why 1-0:2.7.0 is not working |
|
I will fix this soonVerstuurd vanaf mijn iPadOp 15 mei 2023 om 16:03 heeft HarryHase4 ***@***.***> het volgende geschreven:
I found an older fork, which i can compile, there i made a "ugly hack" in the decoder.
if (strncmp(telegram, "1-0:2.7.0", strlen("1-0:2.7.0")) == 0)
getValue(actualElectricityPowerReturned, telegram, len, '(', '*');
if (strncmp(telegram, "1-0:22.7.0", strlen("1-0:22.7.0")) == 0)
getValue(actualElectricityPowerReturned, telegram, len, '(', '*');
I don't understand why 1-0:2.7.0 is not working
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
|
The issue is that your meter terminates the values with the units (e.g. kWh) instead of with * followed by unit (eg *kWh). I will make a fix later this week |
|
The stars are in the telegram, the where killd by this editor here .. (my fault in posting it here .... sorry) |
|
Firmware P1WG2022v1.1be.NL.esp8285.bin
should fix this issue
… On 16 May 2023, at 15:42, HarryHase4 ***@***.***> wrote:
sorry, i don't know from where i post the data before. if if now it is with *
1-0:1.8.2(002020.371kWh)
1-0:2.8.1(004659.584kWh)
1-0:2.8.2(010954.312kWh)
0-0:96.14.0(0002)
1-0:1.7.0(00.000kW)
1-0:2.7.0(02.500kW)
0-0:96.7.21(00010)
0-0:96.7.9(00006)
1-0:99.97.0(4)(0-0:96.7.19)(190111133452W)(0000002779s)(190307113415W)(0000004950s)(210727172710S)(0000003977s)(210727183630S)(0000001107s)
1-0:32.32.0(00093)
1-0:32.36.0(00008)
0-0:96.13.0()
1-0:32.7.0(242.8V)
1-0:31.7.0(010A)
1-0:21.7.0(00.000kW)
1-0:22.7.0(02.499kW)
0-1:24.1.0(003)
0-1:96.1.0(47303033xxxxxxx)
0-1:24.2.1(230516153505S)(03191.607m3)
!B572
/Data
/ISK5\2M550E-1011 1-3:0.2.8(50) 0-0:1.0.0(230516154119S) 0-0:96.1.1(45303033333030xxxxx) 1-0:1.8.1(003201.154kWh) 1-0:1.8.2(002020.371kWh) 1-0:2.8.1(004659.584kWh) 1-0:2.8.2(010954.421kWh) 0-0:96.14.0(0002) 1-0:1.7.0(00.000kW) 1-0:2.7.0(02.502kW) 0-0:96.7.21(00010) 0-0:96.7.9(00006) 1-0:99.97.0(4)(0-0:96.7.19)(190111133452W)(0000002779s)(190307113415W)(0000004950s)(210727172710S)(0000003977s)(210727183630S)(0000001107s) 1-0:32.32.0(00093) 1-0:32.36.0(00008) 0-0:96.13.0() 1-0:32.7.0(243.5V) 1-0:31.7.0(010A) 1-0:21.7.0(00.000kW) 1-0:22.7.0(02.505kW) 0-1:24.1.0(003) 0-1:96.1.0(473030xxxxxx) 0-1:24.2.1(230516154005S)(03191.607*m3) !E66A
—
Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANPIKRNSFG6CQ7RJCWHDQLXGN73DANCNFSM6AAAAAAYBH4LUI>.
You are receiving this because you commented.
|
|
can not find P1WG2022v1.1be.NL.esp8285.bin (and the code for it) .. |
|
Not fixes, the star is not the Problem, please See my comments bevor. |
|
There is something weird with the ISKRA protocol. Will fix it later this week. Can you send me another dump of
p1wifi.local/Raw
and a screenshot?
… On 20 May 2023, at 16:36, HarryHase4 ***@***.***> wrote:
Not fixes, the star was mit the Problem, please See my comments.
<https://user-images.githubusercontent.com/104375025/239693302-8bb4f01e-f253-4992-a44b-fdb38cce36ad.jpg>
—
Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANPIKSGUJM7PWT5G7237JLXHDJH3ANCNFSM6AAAAAAYBH4LUI>.
You are receiving this because you commented.
|
|
|
|
How about this
|
|
no Actueel verbruik, but in the protocol it is `1-0:2.7.0(01.376*kW) 1-0:22.7.0(01.364*kW) |
|
is this better?
substring works differently than I expected.
if (meterId.indexOf("ISK5\2M550E-1011") != -1){
if (strncmp(telegram, "1-0:2.7.0", strlen("1-0:2.7.0")) == 0)
getValue(actualElectricityPowerDelivered, telegram, len, '(', '*'); // kludge for ISKRA meter
// 1-0:22.7.0(00.378*kW) Instantaan vermogen Elektriciteit levering L1
if (strncmp(telegram, "1-0:22.7.0", strlen("1-0:22.7.0")) == 0)
getValue(actualElectricityPowerReturned, telegram, len, '(', '*'); // kludge for ISKRA meter
}
should create an exception for your meter
|
|
I can test it on next monday .. |
|
Was this ever solved? I have the same issue, also with an ISKRA 550 3-phase model, but so far I thought it was only the return value that is broken. I thought the PowerDelivered value works correctly: it is 0 when my solar panels are able to supply the energy the house currently needs, so 0 is what is drawn from the grid at that moment. However, now I can see in the datagram it shows as 1223 W.
|
|
I don’t remember whether this was fixed. I will take another look at it.
… On 25 Jul 2023, at 17:05, emarvegt ***@***.***> wrote:
Was this ever solved? I have the same issue, also with an ISKRA 550, but I think in both cases it's only the return value that is missing. The PowerDelivered value works correctly. It is 0 when my solar panels are able to supply the energy the house currently needs, so 0 is what is drawn from the grid at that moment.
The PowerReturned value shows nothing, but should show the excess solar that isn't consumed by the house and flows back into the grid. And I think I can see it in the datagram:
/ISK5\2M550T-1012 1-3:0.2.8(50) 0-0:1.0.0(230725165848S) 0-0:96.1.1(4530303434303036383432393836313137) 1-0:1.8.1(010022.217*kWh) 1-0:1.8.2(007192.203*kWh) 1-0:2.8.1(003940.472*kWh) 1-0:2.8.2(008902.806*kWh) 0-0:96.14.0(0002) 1-0:1.7.0(00.000*kW) 1-0:2.7.0(01.223*kW) 0-0:96.7.21(00005) 0-0:96.7.9(00002) 1-0:99.97.0() 1-0:32.32.0(00013) 1-0:52.32.0(00011) 1-0:72.32.0(00011) 1-0:32.36.0(00001) 1-0:52.36.0(00001) 1-0:72.36.0(00001) 0-0:96.13.0() 1-0:32.7.0(237.4*V) 1-0:52.7.0(234.0*V) 1-0:72.7.0(236.3*V) 1-0:31.7.0(006*A) 1-0:51.7.0(001*A) 1-0:71.7.0(001*A) 1-0:21.7.0(00.000*kW) 1-0:41.7.0(00.120*kW) 1-0:61.7.0(00.180*kW) 1-0:22.7.0(01.513*kW) 1-0:42.7.0(00.000*kW) 1-0:62.7.0(00.000*kW) 0-1:24.1.0(003) 0-1:96.1.0(4730303339303031383035373739393138) 0-1:24.2.1(230725165507S)(08392.804*m3) !9F4F
—
Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANPIKQNQNPXB5MFSCJZCKLXR7ODXANCNFSM6AAAAAAYBH4LUI>.
You are receiving this because you commented.
|
|
I had less time, to analyse. I must confess, i can't rember, but in my mind it was not fixed and i used my "uply hack" from May, 15th! |
|
Hi , I am having the same issue with newest firmware version 1.1c. I seem to be able to access it through fine but the readout of the iskra is very erratic and often give 0 values. Is there an easy fix? |
|
Can you send me some output obtained with p1wifi.local/DataVerstuurd vanaf mijn iPadOp 2 okt. 2023 om 21:18 heeft artenverho ***@***.***> het volgende geschreven:
Hi , I am having the same issue with newest firmware version 1.1c. I seem to be able to access it through fine but the readout of the iskra is very erratic and often give 0 values. Is there an easy fix?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
Data below is from when it works. I will try to also catch it when it is not reporting correctly. I also noticed it was showing online for only 8 hours. So it might also be a power/reset issue? |
|
So it seems it has become very difficult for me to debug the current situation: I checked domoticz and no data was reported for more than 30 hours. Then I tried to access the p1 gateway through a webbrowser. The page took a while to load and as soon as it did the uptime showed 0 days 0 hours 0 min, but reporting to domoticz did startup correctly again. Perhaps this is a power issue? I am surprised however that it is able to reset as soon as I try to access it via the webserver. I will try to run it with power for a while and see if that fixes the issue. |
|
I am working on the code. This issue is still on my stack. |
|
Let me know if I can provide logs, etc.. I tried whether running it from external power would solve the issue, but this had no effect. |
|
I am working on a telnet debug port. I will uplaod a debug version on Github later this week
… On 10 Oct 2023, at 07:53, artenverho ***@***.***> wrote:
Let me know if I can provide logs, etc.. I tried whether running it from external power would solve the issue, but this had no effect.
—
Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANPIKRCMHIR3ORAN3U5VLTX6TPG3AVCNFSM6AAAAAAYBH4LUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJUGQZTMMRUGM>.
You are receiving this because you commented.
|
|
I can confirm this is fixed with version 1.2ba |
|
Unfortunately the ‘report in W’ does not switch all value ranges in the same way, it seems. And the firmware seems less stable too. |
nice work!
I'm using the binary on a wemos d1. I have some problems with my meter. The current is shown, the power not. Maybe it is a an effect from the single phase!?
Im'not a coder and i can not compile it myself, to much errors ;)
--
/ISK5\2M550E-1011
1-3:0.2.8(50)
0-0:1.0.0(230514205635S)
0-0:96.1.1(4530303333xxxx)
1-0:1.8.1(003198.294kWh)
1-0:1.8.2(002014.469kWh)
1-0:2.8.1(004659.584kWh)
1-0:2.8.2(010943.423kWh)
0-0:96.14.0(0001)
1-0:1.7.0(00.125kW)
1-0:2.7.0(00.000kW)
0-0:96.7.21(00010)
0-0:96.7.9(00006)
1-0:99.97.0(4)(0-0:96.7.19)(190111133452W)(0000002779s)(190307113415W)(0000004950s)(210727172710S)(0000003977s)(210727183630S)(0000001107s)
1-0:32.32.0(00093)
1-0:32.36.0(00008)
0-0:96.13.0()
1-0:32.7.0(232.8V)
1-0:31.7.0(000A)
1-0:21.7.0(00.122kW)
1-0:22.7.0(00.000kW)
0-1:24.1.0(003)
0-1:96.1.0(473030333235363xxxx)
0-1:24.2.1(230514205508S)(03187.803*m3)
The text was updated successfully, but these errors were encountered: