I might have figured something out. After moving homeassistant from one host to another, it had changed its IP from 192.168.2.100(static) to 192.168.2.239(dhcp).
After that i added the SMA inverter to my fresh installation of homeassistant. Everything was working fine and my SMA Inverter was responding to requests from 192.168.2.239.
Once hassio had been fully restored/installed (and the old host had been phased out) i changed the IP to what i had once intended it to be: 192.168.2.100. From that point onwards the connection between Hassio and my SMA suddenly stopped working.
I was able to
ping the SMA Inverter from hassio, but when i tried to
wget the web-address of my SMA Inverter, i received no response at all. I figured that the inverter somehow blacklisted that IP, so i tried to change it.
The connection to the SMA inverter was re-established once i manually changed the IP (of hassio) to litterally something else, in this case: 192.168.2.101.
Then i tried something funky: change the IP of my workstation to the IP that was once hassio’s, and guess what? i wasn’t able to reach the SMA from my workstation.
I dont know what is going on here, the SMA Inverter somehow refuses to respond to hosts with the static ip that was once hassio’s. My guess is that SMA blocks requests from what it thinks is it’s DNS server? So it might have something to do with pi-hole or AdGuard.
Try changing the IP of hassio, i think the SMA Inverter is blocking the DNS server from connecting to it.