I have never used 192.168.194.2
That is the VMWARE gateway. The windows VM has address 192.168.194.239 on the VMWARE network. It will ask the VMWARE gateway to send the message. And that is failing for some (yet) unknown reason.
The MAC is on the local network and can talk to the Enphase. As the HA NUC is also on the local network, let’s see what it can reach.
Can you open a console on the HA NUC and try
curl http://192.168.1.192/info
I wasn’t sure if I was already logged in, but in the last part you can see the result…
Looks like from the NUC I can’t approach it either…
I did some similar testing (to router and NVR) and it looks like this:
I think I need to start my Enphase Toolkit and login locally to my Envoy gateway. What are the settings for gateway, net mask etc…
The question though is why can Safari easily get access? My network setup is at 3 sites exactly the same. I use Draytek Vigor routers and normally duplicate the network settings except that they are on a different IP, so 192.168.2.x and 192.168.3.x etc
Weird indeed. On HA you could try a network scan and see what it finds on the network
nmap 192.168.1.1/24
Using this on my HA (in docker on Synology NAS) I get below for my Enphase at 192.168.3.112
Nmap scan report for 192.168.3.112
Host is up (0.00017s latency).
Not shown: 993 closed tcp ports (reset)
PORT STATE SERVICE
22/tcp filtered ssh
53/tcp filtered domain
80/tcp open http
443/tcp open https
8082/tcp filtered blackice-alerts
8100/tcp filtered xprint-server
9091/tcp filtered xmltec-xmlmail
MAC Address: 00:1D:C0:7F:B6:3B (Enphase Energy)
I have tried nmap, but the terminal doesn’t recognise the command.
Meanwhile, I have been checking the Wifi. I have re-assigned 2 internal WiFi networks (one general 5 Ghz/2.4 Ghz and one particular 2.4 Ghz only). Both resulting in nothing. However, one thing I have noticed is the fact that you cannot set anything, like gateway address and/or subnet mask.
The Enphase Toolkit actually mentions:
The gateway has this terrible setting and I cannot change it, 172.30.1.1 !!! I’ve tried everywhere, but I can’t change it and it should be of course 192.168.1.1.
I have removed “Bind IP” based on MAC address, but nothing helps to get resolved automatically the correct network settings for the Enphase Toolkit. Also, at https://enlighten.enphaseenergy.com I can’t change anything at the settings (I think it’s a one time connectivity topic which you can only setup with the Enphase Toolkit).
By the way this site is connected via WiFi, the other site which is also not working has the same setup. At my local site, it’s very hard to connect it via a ethernet cable…
Probably I need to contact Enphase developer team. What do you think? The fact that you cannot assign a fixed IP address is already annoying, the fact that you can’t change the network details is a flaw in my opinion…
Did you configure a dhcp address reservation based on the enphase gateway Mac Address in your router? I don’t use fixed ip in my Enphase and have that set in my router to be sure the router assign the same ip each time. Otherwise the router may assign that address to another device.
When I open the Enphase default web page and login using the token (probably from your MAC for now), and then open the ethernet settings (mine is on wired connection) I see DHCP mode
There is an installer login button there as well, if you have an installer account you might be able to use that login to change network settings to use dhcp.
And in Network diagnostics I see
Probably I need to contact Enphase developer team. What do you think? The fact that you cannot assign a fixed IP address is already annoying, the fact that you can’t change the network details is a flaw in my opinion…
That is always an option. I think what you want is using DHCP with address reservation in your router, based on the enphase Mac Address. If they then change the mode from fixed IP to DHCP it should pick-up its ip and the router gateway ip from your router.
I do/did it via my router as there is no other way to set the IP for Enphase (as it’s not working according to your screenshots):
When using envoy.local I’m trying to get into the WiFi settings. It keeps on circling why trying to obtain the data:
I think it has problems resolving the WiFi connection, similar when typing the curl http://192.168.1.192/info or http://envoy.local on Edge which doesn’t work. If it won’t work, I will never get into the settings for DHCP or fixed IP address…
After a few minutes, the installer login option appears. When trying this route, I get a similar behaviour:
I actually want fixed IP only, no DHCP. But when the MAC address is bind to 192.168.1.192 via the router, the Enphase Toolkit comes automatically with this IP and wrong gateway address. When removing the binding and let Enphase do its job, it comes with the first available IP from the pool (in my case 192.168.1.30) but also comes with a wrong gateway. I think Enphase should allow to set the network details in the Toolkit immediately, this prevents doing it later via envoy.local as this results into problems when it has determined itself a wrong gateway IP.
Hmm, so much for trying that option. Have to admit I’m running out of ideas, not my real expertise.
If it gets gateway 172.30.1.1 it probably would use that to connect to the Enphase cloud to report data, so kind of strange if that is working.
In the network route check, it seems to use an other gateway, but can’t read the gateway ip from the picture.
You probably already tried and found it faling, but is ping from the Enphase Gateway to 192.168.1.1 and/or 192.168.1.140 working and this famous gateway 172.30.1.1 for that matter? (Yes, at the end of my options, just trying 
)
It’s a strange thing… I have reported the issue to support of Enphase at [email protected] as well. Let’s see what kind of answer they return…
I have checked several PING’s, please see below:
It’s indeed very strange, my screenshot shows the gateway is correct here: 192.168.1.1 but the destination IP address is empty to 0.0.0.0
The Envoy gateway can report to the cloud and as my Enphase Toolkit says the connection to cloud and AP are all working fine. The data is also visible of course, which is important evidence… so no further issue.
Looking at the internet the address 172.30.1.1 is mentioned in cases about Enphase. It seems like it’s the default gateway for the Envoy when there is no WiFi connection established yet. But it’s all guessing. I think let’s see what kind of feedback support gives from Enphase…
I should actually try to get it hooked on a wired ethernet cable… let me see what I can do. I actually need a cable junction to extend existing cable which is available…
Reading through some Enphase info it seems that the 172.30.1.1 is the Enphase Gateway IP when in AP mode for configuration with the App on a mobile phone. So that would not be used when normal running.
Is the gateway on the guest wifi, if you have that at all? The other day there was such a case reported, just elimination this one.
Power down/power up the enphase gateway probably also tried before I assume.
Here is some info how to get nmap on HA.
Let’s hope enphase comes back with some usefull info.
Using 192.168.1.192 to track, nothing is detected at the beginning. After a while the following entity is created:
The MAC address is equal to the last 3 parts so it confirms this is my Enovy. I presume it has somehow obtained contact, otherwise how could it get the correct MAC address?
That’s also what I have found… still, I believe there is a flaw at the installer Toolkit, because why is it reporting gateway 172.30.1.1 while it should reports its gateway automatically derived from when it did connect to the new WiFi…
I did it once again to make sure this is not the case. No result.
I have setup Nmap. At the beginning with 192.168.1.1-255 excluding 140. But this resulted in many entities (4 devices). Later I have scanned 192.168.1.192 but then nothing could be found. I wouldn’t expect something else 
I have the feeling the undefined gateway at the Envoy is making the trouble…
I have ordered a ethernet Gigabit Netwerk Extender to extend my current cable. Let’s also see what this brings while having an ethernet connection…
I hope Enphase support comes with some feedback. But the developers tend to respond very slow, given the fact that they said it’s still under investigation the general issue I have asked end of November last year…
Must have seen it passing by over the network at lower network level. The first 3 parts are registered by Texas Instruments, hence that name is showing. Must be using a TI chip inside.
Curious what the cable will do. Have to say that Wifi connections tend to generate more issues that wired connections, if that means anything at all.
mine is also texas instruments
I have found (!! 
!!) the bug for 1 site, mine in the Netherlands.
When I incidentally checked my Ethernet settings I found:
I have tried to fill in the gateway as it was missing before, but I didn’t succeed. Then I wanted to get rid off these settings and I clicked on DHCP.
The result was:
Then I tried to get access to https://192.168.1.192 and voila! Somehow, it has mixed the gateway from ethernet (0.0.0.0) with my WiFi settings and therefore it didn’t work. I think this is a flaw, as if the ethernet is not connected at all, as reported by Envoy as well, it shouldn’t mix ethernet settings with the WiFi which has been resolved automatically.
Whoawwww… I’m so happy. This has cost me about 2 years to find out and finally I can see how much I produce in conjunction with how much I have consumed of it and returned to the grid.
I haven’t accomplished my 3rd site yet. I think there will be the same issue or the least it will be worth to check what settings this Envoy has. The odd thing here was that it has been working, I drove home and a week later while not working on this LAN at all, it didn’t function anymore. Trying with a VPN connection I can’t access https://envoy.local as it will resolve my home address (the 192.168.1.192) while I should get 192.168.3.192. I have to be patient for next visit to this site which is a 1.000 km away…
Finally, I’m very happy. And thanks all, especially @catsmanac bringing me onto the right track.
