ksheumaker / homeassistant-apsystems_ecur

Home Assistant custom component for local querying of APSystems ECU-R Solar System
Apache License 2.0
166 stars 42 forks source link

Connection fails since today's app update #238

Closed eb-stefan closed 3 months ago

eb-stefan commented 3 months ago

I have a new app since today and can no longer connect to the ECU-B (port 8899 can no longer be opened)

thomasvanhorde commented 3 months ago

Same here :(

HAEdwin commented 3 months ago

What do you mean by "I have a new app"? Help me help you by providing some more info. As always things are running fine here (but that's an ECU-R).

eb-stefan commented 3 months ago

The “EMA app” looks a little different and asked me about new policies.

btw, In addition to HA, I also use Node-Red access directly to the TCP port. This no longer works either.

thomasvanhorde commented 3 months ago

I have this error log 2024-03-08 14:50:54.491 WARNING (SyncWorker_14) [custom_components.apsystems_ecur] Using cached data from last successful communication from ECU. Invalid data error: [Errno 113] Host is unreachable

But in https://www.apsystemsema.com/ all is OK

HAEdwin commented 3 months ago

APsystemsema data is pushed differently from our approach. So are you still able to configure the ECU-B (using the ECU-app or ECUmanager app) when the ECU-B hotspot is active? I'm afraid APsystems will end the undocumented feature, but at the same time I hope for a good alternative that meets the IoT wishes of many APsystems users.

I may have another solution, but I need someone with node-red experience to achieve that (@eb-stefan ?) ModBus seems not supported for ECU-B devices and older ECU-R models. image

thomasvanhorde commented 3 months ago

Hi, I restart ECU and now is ok ! Just waiting tomorrow for datas but is connected to Hass

HAEdwin commented 3 months ago

@eb-stefan Did you allready restart the ECU or do you still have isseus connecting?

HAEdwin commented 3 months ago

@thomasvanhorde @eb-stefan Everything still in working order?

thomasvanhorde commented 3 months ago

@thomasvanhorde @eb-stefan Everything still in working order?

Yes, thank you ! All is okay after reboot ECU

Capture d’écran 2024-03-17 à 20 12 51
eb-stefan commented 3 months ago

Sorry, I was unfortunately sick last week. Everything is working fine again.

What solution do you have? I have moderate experience with Node-Red :-)

HAEdwin commented 3 months ago

Hope all is well again. I'm still working on the proxy method. Before the ECU is sending the data to EMA it passes the proxy integration to register data in Home Assistant. Disadvantage is that signal data is not present, advantage is that current en voltages of each panel is now visible. (have to do some manual calculations that hopefully will get closer to the values EMA calculates. The ECU values are less accurate. image I'll close this issue, feel free to open a new one when ever needed.

eb-stefan commented 3 months ago

I'm currently using a TCP function in NR. It has been running stable for 3 years. I've only been working with HA for a few weeks. But my NR script is similar to this one: https://community.home-assistant.io/t/apsystems-aps-ecu-r-local-inverters-data-pull/260835