I have a strange problem; IotaWatt is connected to WiFi via a Unifi U6-LR AP, and uploads data fine to PVOutput, but for some reason, using the latest UniFi firmware, I cannot get the web interface and cannot be pinged but it is still obviously connected as data is uploaded and the light stays green. Power cycling doesn’t help. When I roll back to an older firmware, it works fine.
Any idea of the cause?
No. What is the version of the AP firmware?
The problem seems to be Unifi firmware 6.0.13 as well as 6.0.15, whereas 5.60.23 seems to work. It’s a very strange issue, as I can’t think of why it will connect, upload data, but can’t access the web interface or ping.
I’ve got a U7-LR in my network. I’m updating it to 6 now. Will see what happens. Sounds like it might have something to do with the UDP broadcast used in resolving the .local name. Have you tried accessing via the IP?
UPDATE: My UAP-AC-LR (U7LR) seems OK with firmware 6.0.18.13660. Tried using both LLMNR (Windows) and mDNS (Apple) zero-config protocols.
I’m accessing via IP address, as my normal connection is from my normal VLAN to my IoT VLAN; the firewall rules do allow connection in case you’re wondering, and it usually works, just not with 6.0.13 nor 6.0.15 (nor 6.0.23 EA); there is still no 6.0.18 for the U6.
I’m now suspecting the UniFi U6 firmware, as looks as if more than one 2.4GHz IoT device has broken connections, whereas my nanoHD appears to be working (although an earlier 6.0.x firmware also broke connection with some 2.4GHz devices).
Perhaps I need to sit out the updates for a while, but this may be of interest for those running the UniFi WiFi 6 series using 6.0.x firmware being unable to connect.
Resurrecting this thread to drop an anecdote that may help others.
I am setting up my IoTaWatt again after having it disconnected for ~6 months while moving house. Tried setting it up on the bench yesterday and had all sorts of issues with not being able to ping or connect to the web interface. Packet logs showed lots of retries on DNS and NTP connections. It’s as if the IoTaWatt had trouble receiving packets from the access point.
I’m running multiple U6 Lite APs which have had firmware upgrades since I last had the IoTaWatt hooked up. It was working flawlessly before on the same AP hardware. Being a new location, I tried different channels, etc. to no avail. At least 10 other ESP devices are on the same network without issues.
After testing different IoTaWatt firmware versions and many flash erases later to connect to different test SSIDs, I set up an old Airport Extreme and it worked perfectly. Okay, so it’s the Unifi gear and not my IoTaWatt.
I was running the latest 6.6.55 release firmware on the U6 Lite APs and found people mentioning issues with different Unifi versions so I took at look at r/unifi_versions and found UniFi Access Point 6.6.65. That’s a little later than what I was running and it contained this interesting entry in the change log:
[Gen4/U6-Lite] Fixed 2.4GHz connectivity issues with some IoT clients (e.g. Netatmo cameras).
I manually installed 6.6.65 over 6.6.55 and problem solved. Buggy UniFi firmware strikes again. I’ve now rolled out this update to all other APs and monitoring for issues. All seems fine so far.
Not so much IoTaWatt alone, but I’ve found all v6 firmware for my U6-LR disconnects several IoT devices, such as doorlocks and IoTaWatt; so I’ve stuck to v5.60.23.
I had to revert back to 6.5.64 on my UniFi APs to get stable IoTaWatt connectivity.