search

hombach / ioBroker.kostal-piko-ba

ioBroker Adapter to poll Kostal Pico BA inverter data to monitor your PV-system
https://github.com/hombach/ioBroker.kostal-piko-ba
MIT License
10 stars 7 forks source link

Feature request - Add Power/Current/Volt per AC Line #252

Closed GRaptor closed 2 years ago

GRaptor commented 2 years ago

I use the version 1.2.1 of the adapter with a Piko 12. Works w/o like a charme. Thank you for that!

I don't know about the Piko BA, but on the Piko 12 you may have the current, power and volt per AC line as data available as well. At least, it's shown in the GUI. So, do you think it's easy to make these parameters (in addition to the already existing Surplus object) available as well?

If I can assist in any way please let me know (of course, we can write in German as well)

Thanks GRaptor

hombach commented 2 years ago

Hi Raptor,

keeping conversation in English is welcome. You're welcome, too ;)

Thank's alot for your feedback about a working adapter with Piko 12.

Looking at the feature request - I think you're talking about this grid values:

_// live values - grid phase 1 const ID_L1GridCurrent = 67109377; // in A - not implemented const ID_L1GridVoltage = 67109378; // in V - not implemented const ID_L1GridPower = 67109379; // in W - not implemented // live values - grid phase 2 const ID_L2GridCurrent = 67109633; // in A - not implemented const ID_L2GridVoltage = 67109634; // in V - not implemented const ID_L2GridPower = 67109635; // in W - not implemented // live values - grid phase 3 const ID_L3GridCurrent = 67109889; // in A - not implemented const ID_L3GridVoltage = 67109890; // in V - not implemented const IDL3GridPower = 67109891; // in W - not implemented

This is already prepared... so not that big issue, no help needed, besides some testing ;)

Are just the power values needed? Or also V & A? I think same refresh time than for DC values would be best.

BR Christian

GRaptor commented 2 years ago

Thanks for the fast reply! Yes, that's looks good to me! Geat. For me, power is what I'm looking for. However, bigger is better so to make all three values availble wouldn't hurt. But I really can't think of any usecase to have the volts available. Agree, no different refresh time settings needed. Keep it simple :-) For sure, I can test it. After Kostal changed the com board of my Piko, it finally started publishing data :-)

hombach commented 2 years ago

Looks like changes are done - Voltage is showing up.... for testing amp and power I would need some sun on the panels :) ... tomorrow

hombach commented 2 years ago

Ok looks fine with Piko BA also with some power on the line - release 1.4.0 is published an deployed in iOBroker latest repo. Please test if it works with your PIKO 12, too....

GRaptor commented 2 years ago

Awesome! Just installed it. Seems to work. Will see tomorrow. Only issue: when starting the adapter, it logs an error:

2022-01-31 21:59:26.098 error Please verify IP address: 192.168.2.20 !!! 2022-01-31 21:59:26.097 error Error in calling Kostal Piko API: SyntaxError: Unexpected end of JSON input

besides that it seems to work

hombach commented 2 years ago

You've seen this message only once? Should be more often in case of an "real" error. Please check.

GRaptor commented 2 years ago

For now, only if I (re)start the adapter. But in that case always.

GRaptor commented 2 years ago

Update: P,C,V showing up and are feasible. Better, show same values like the Kostal Piko GUI.

However, the above mentioned error still shows up randomly as well. I turned on the debug log. At least for me, it doesn't give me any hint:

2022-02-01 14:15:48.344 - debug: kostal-piko-ba.0 (5384) Piko-BA live data 2 updated - Kostal response data: {"dxsEntries":[{"dxsId":67109377,"value":2.239990},{"dxsId":67109378,"value":239.435837},{"dxsId":67109379,"value":469.948212},{"dxsId":67109633,"value":2.255249},{"dxsId":67109634,"value":237.104630},{"dxsId":67109635,"value":464.560516},{"dxsId":67109889,"value":2.380371},{"dxsId":67109890,"value":236.638382},{"dxsId":67109891,"value":492.666809}],"session":{"sessionId":0,"roleId":0},"status":{"code":0}} 2022-02-01 14:15:50.600 - debug: kostal-piko-ba.0 (5384) Piko-BA daily data updated 2022-02-01 14:15:58.345 - error: kostal-piko-ba.0 (5384) Error in calling Kostal Piko API: SyntaxError: Unexpected end of JSON input 2022-02-01 14:15:58.346 - error: kostal-piko-ba.0 (5384) Please verify IP address: 192.168.2.20 !!! 2022-02-01 14:15:58.356 - debug: kostal-piko-ba.0 (5384) Piko-BA live data updated - Kostal response data: {"dxsEntries":[{"dxsId":33556736,"value":1529.115723},{"dxsId":67109120,"value":1417.423828},{"dxsId":33555203,"value":804.528320},{"dxsId":33555201,"value":2.088074},{"dxsId":33555202,"value":385.406616},{"dxsId":33555459,"value":724.587341},{"dxsId":33555457,"value":1.214653},{"dxsId":33555458,"value":596.986572},{"dxsId":33555715,"value":0.000000},{"dxsId":33555713,"value":0.000000},{"dxsId":33555714,"value":0.000000},{"dxsId":83888128,"value":null},{"dxsId":83887872,"value":null},{"dxsId":16780032,"value":3},{"dxsId":33556226,"value":0.000000},{"dxsId":33556227,"value":0.000000},{"dxsId":33556229,"value":0.000000},{"dxsId":33556238,"value":0.000000},{"dxsId":33556230,"value":0},{"dxsId":67110144,"value":100.000000}],"session":{"sessionId":0,"roleId":0},"status":{"code":0}}

hombach commented 2 years ago

Ah.... ok - trouble with the daily statistics data... error should repeat every minute.... or whatever you put as timing in there (60000ms is the standard).

Do you have any usefull data in this area? image

Is your system equipped with an consumption sensor?

hombach commented 2 years ago

Errr - no i misunderstood the logging - It's another point.... I'll optimize the logging, you'll get another release - let's say this evening

GRaptor commented 2 years ago

Ah.... ok - trouble with the daily statistics data... error should repeat every minute.... or whatever you put as timing in there (60000ms is the standard).

I checked on that already. It's not linked to daily report. The error really shows up randomly, not linked to the daily report.

One side note: By accident, (means Zufall), my electrician called today. Told me, something is weird with the reporting of my Piko to the Kostal portal. Anyway, in the end Kostal called me, checked online some settings on my Piko by using a Teamviewer connection. Then said, something is wrong, they have to investigate?! They have an issue getting correct data transmitted to their portal. Locally I have no issues (beside the one discussing here). Just want to mention it. I have no clue what they identified as they didn't really tell me. But, maybe our issue here has the same root cause. So don't dig to deep for now in case it's an error of my Piko.

Still, I'm happy to try your updated version :-)

hombach commented 2 years ago

My idea is that your piko has some trouble when I'm polling about cycle times of the battery... you have none ;) There is also the possibility that Piko is reporting the API error we are producing with iOBroker to Kostal.... although I never seen this in my own tests.

GRaptor commented 2 years ago

I have the 1.4.1 running since 1h. Error showed up only at start. Will monitor tomorrow :-)

My idea is that your piko has some trouble when I'm polling about cycle times of the battery... you have none ;) Understand. Could be the case. Another feaure request would be only having objects really existing with the specific Piko. But that would be schöner wohnen

hombach commented 2 years ago

uuhhmmm - i changed nothing besides more logging info - so when you're facing the error again, please post the log like last time

hombach commented 2 years ago

looks like I got the error - root cause was bad timing caused by too much requests for the inverter. Please try 1.4.2. Deployment to latest repo is done... should be viewable in Admin soon.

GRaptor commented 2 years ago

I think good news: 1.4.2 ran whole day w/o any error message. Great job, thanks!