New Alpha - Port 17777 - Project Dead?

[mrrodge2020]

Thanks for updating yesterday. It's looking like Alpha have changed some stuff - motivation for using this was the local and more frequent updates so I could feed in live data to HA.

First obstacle - I couldn't change the server IP on the menu of the SMILE5 inverter I have. It's locked, even though I'm the installer and have the password to all settings. I then moved on to doing it with a transparent proxy.

I tried to use a NAT rule on my OPNSense firewall to point traffic destined for 52.230.104.147:7777 but the addon didn't pick anything up. I then did a packet capture on the Alpha and saw it was communicating with the same IP, but port 17777.

I then set up the proxy and NAT rule to use that port instead, still nothing received by the addon - stuck listening.

I turned off the firewall rule and did a packet capture again, this time loading into Wireshark and it looks like the packets are all TCP encrypted (though I've never done this before, it may be that it's encoded using a difference character set).

I tried to block the 17777 port altogether in hope that the system would revert to 7777 but it didn't; it went to Google DNS to look for a server IP address, which obviously just returned the same address.

That's about as far as my knowledge goes, but I'm guessing that port 7777 is an older, unencrypted protocol that older hardware is using. Any thoughts?

Thanks again.

[230delphi]

Will review my system for version number for comparison, and check logs if I've inadvertently blocked the firmware upgrade that switches to secure.
if you could get your firmware/model version?

[robotfishe]

I'm in a similar situation - packet capture shows traffic from the Alpha to 52.230.104.147.17777, but even with a NAT rule rerouting all outgoing TDP traffic from the Alpha's IP to (HA-IP):27777, I'm still stuck at "listening for connections".

I know the forwarding rule works, because if I set the rule to redirect traffic from my PC instead and do a test-netconnection from the PC, the addon log goes nuts trying to handle unrecognised traffic.

Are there any logs or other details that would help diagnose?

[robotfishe]

Update: I tried resetting the Alpha's wifi connection, and that produced some mixed results. Traffic did find its way to the proxy, but the addon couldn't do anything with it; it logged "MQTTInjectProxyConnection: CopyAndInjectProxyConnection() is in testing only!" about a hundred times a second for a couple of minutes, then:

INFO[2023-05-31T23:43:27+01:00] dial(): ERR: could not connect to 192.168.1.90:27777: dial tcp 192.168.1.90:27777: connect: cannot assign requested address 
INFO[2023-05-31T23:43:27+01:00] DIRECT|192.168.1.90:58533->?|Could not connect, giving up: dial tcp 192.168.1.90:27777: connect: cannot assign requested address 
/run.sh: line 89:  1441 Killed                  ./alphaESS-proxy -config ${CONFIG} < /dev/null
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

The Alpha's webserver said "connect fail" at this point.