No longer data from solaredge

whitefarmer1 commented 3 months ago

Hi Edwin,

Thanks for creating the app, unfortunately it no longer sends data to my homey. (6 days now).

I have restarted the app, but with no succes.

As far as i know, no changes have been made.

(Greetings John Mierlo the Netherlands)

biemond commented 3 months ago

hey , can you send me a report , probably your ip changed.

whitefarmer1 commented 3 months ago

Hoi Edwin, Onderstaand de code:

e97e646f-3182-42e4-9bbd-a9530803498f

Laat me weten als je meer info nodig hebt.

Dank voor je App!

Laat me weten waar ik wat kan doneren aub.

Groet John

Op ma 1 apr 2024 18:17 schreef Edwin Biemond @.***>:

hey , can you send me a report , probably your ip changed.

— Reply to this email directly, view it on GitHub https://github.com/biemond/solaredge.modbus/issues/69#issuecomment-2030081680, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHJ4BEUNSAHSSCHKWPQSC33Y3GCBTAVCNFSM6AAAAABFGYYAX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZQGA4DCNRYGA . You are receiving this because you authored the thread.Message ID: @.***>

biemond commented 3 months ago

yep

[Driver:invertor] [Device:16033500-61bf-499f-8551-03c3d59090b2] 192.168.2.2
Error: connect EHOSTUNREACH [192.168.2.2:1502](http://192.168.2.2:1502/)
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
  errno: -113,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: '192.168.2.2',
  port: 1502
}
Client closed

whitefarmer1 commented 3 months ago

DANK!

Op di 2 apr 2024 20:26 schreef Edwin Biemond @.***>:

yep

[Driver:invertor] [Device:16033500-61bf-499f-8551-03c3d59090b2] 192.168.2.2 Error: connect EHOSTUNREACH 192.168.2.2:1502 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) { errno: -113, code: 'EHOSTUNREACH', syscall: 'connect', address: '192.168.2.2', port: 1502 } Client closed

— Reply to this email directly, view it on GitHub https://github.com/biemond/solaredge.modbus/issues/69#issuecomment-2032756940, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHJ4BER6MVYN47OUNICH45LY3LZ67AVCNFSM6AAAAABFGYYAX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZSG42TMOJUGA . You are receiving this because you authored the thread.Message ID: @.***>

luccie007 commented 2 months ago

Just hijacking this thread as its IP related.

I use EVCC as a modbus relay due to solaredge accepting only 1 connection sometimes EVCC goes offline and i lose solar data. Is there a way to make the IPadres and Port available to set in a flowcard? So when i detect this i can route the ip directly (as EVCC then has no connection there is only homey that connects)

biemond commented 2 months ago

I know there is some modbus proxy / docker is that not more stable.

you can setup 2 devices , 1 on your evcc and 1 directly ( this will fail or work, depends on the 1st ). I retry it every 30 seconds.

there is also modbus app so checking some value but I think you want to change the settings of a device. maybe there is homey api for this.

whitefarmer1 commented 2 months ago

Please take me out of the conversation. Mine works (wrong ip)

Thanks John

Op do 4 apr 2024 14:52 schreef Edwin Biemond @.***>:

I know there is some modbus proxy / docker is that not more stable.

you can setup 2 devices , 1 on your evcc and 1 directly ( this will fail or work, depends on the 1st ). I retry it every 30 seconds.

there is also modbus app so checking some value but I think you want to change the settings of a device. maybe there is homey api for this.

— Reply to this email directly, view it on GitHub https://github.com/biemond/solaredge.modbus/issues/69#issuecomment-2037129618, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHJ4BEULQ7RR4N4JIGJJ6JTY3VEJRAVCNFSM6AAAAABFGYYAX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZXGEZDSNRRHA . You are receiving this because you authored the thread.Message ID: @.***>

biemond / solaredge.modbus

No longer data from solaredge #69