Anders Höglund

Results 13 comments of Anders Höglund

I have the same problem. I get current power but no life time energy. See screen shot below. ![HA_solaredge_energy_issue](https://user-images.githubusercontent.com/15121917/180754404-8ba33e72-fa7a-4876-a865-4361e3b8a808.png) JSON response: {"overview":{"lastUpdateTime":"2022-07-25 12:00:12","lifeTimeData":{"energy":1685242.0,"revenue":2481.909},"lastYearData":{"energy":1685335.0},"lastMonthData":{"energy":1241580.0},"lastDayData":{"energy":3881.0},"currentPower":{"power":2585.086},"measuredBy":"INVERTER"}}

There is a version issue in the SolarEdge API, the response to the "Inverter Technical Data" ("equipment") query has a "Lifetime energy" and other fields only supported starting communication board...

I think I found the problem. For some reason, SolarEdge reports lifeTimeData.energy smaller than lastYearData.energy. In my case 1685242W vs 1685335W. PRs #68048 and #69998 introduced a fix that requires...

Yeah, I have "Kommunikationskort (CPU) Version 4.15.119". But that number does not look anything like the format of the version number in the API spec. But this is not the...

Yeah, seems we have two problems with the lifeTimeData.energy value in the SE API. Value of zero and value less than lastYearData.energy. PR #68048 tried to fix the first and...

I am testing another integration, trying to avoid the problems with SolarEdge remote API. Instead using Solaredge MODBUS/TCP locally and the custom integration https://github.com/WillCodeForCats/solaredge-modbus-multi . There is also another alternative...

@csomyy Not much happening with the SE-case, and I think it is private. Stale, not any problem for me any more. MODBUS/TCP is enabled by accessing the VR local AP...

Final response on SE case no 3312126 received. Case closed. The data for lifeTimeData.energy and lastYearData.energy are sampled at different times asynchronously and the values can differ in this way....

Comeon. Try to look at the gui as a noob. The layout of buttons and tabs are not very user friendly. I know a few that selected the "Firmware Flasher"...

I have the same problem. How do you revert to v1.6 when it constantly crashes and reboots? I tried to supply the URL: https://github.com/1technophile/OpenMQTTGateway/releases/download/v1.6.0/lilygo-rtl_433-firmware.bin in WebUI and hit "Start Upgrade",...