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.
2 Likes
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.
Different router, but same problem.
I am running a bPi -R3 router, running OpenWRT ver 23.05.3 & HA reads the data with no problems. But if I address the IoTaWatt directly, I only see the main menu. When I click on an item, the button shows change, but nothing happens.
This was working up until recently. I am fairly sure I accessed it via the bPi before firmware update. I am running AdGuard within the HA server as well.
Cannot see anything obvious. Any help on where to look, or how to proceed?
What firmware was updated?
Hi,
the IoTaWatt updates automatically (from Home Assistant), but I was referring to my update of my router, bPi-R3, that went from pre-release version to stable ver 23.05.3.
Still at a loss as to why I am not able to log into the Iotawatt.
When I log in I just see 2 graphical B&W lines of boxes, but I am not able to see a result when I click on a box.
Here is the log entry:
cnfstyle.css:1
Failed to load resource: net::ERR_CONNECTION_REFUSED
192.168.1.102/:1
Failed to load resource: net::ERR_CONNECTION_RESET
regards, Doug
This appears to be an issue with your WiFi network. If you believe otherwise, please advise your original order number and I will accept the unit back to test with my WiFi equipment.
Thanks Bob. I know its a router problem, but cannot work out where! The Iotawatt transmits to HA fine, but I cannot interrogate it from a browser.
HA has Adguard set up, so that might be the problem. My router (bPi-r3) runs OpenWRT. Let you know what I find! (This is not a Iotawatt problem, just a comms error)
EDIT: i just read the last reply from doug, so my info below will NOT apply to this issue - what i describe below only applies if you can NOT get the iotawatt to connect to your wifi at all (ie iotawatt never pulls a ip via dhcp from your dhcp-server / router) - but leaving my answer up in-case it helps someone else
i skimmed through the answers, so apologies if this has been suggested- The issue maybe on your access point side (or wifi router / unifi setup) in regards to: OFDM-only (or other names for disabling 802.11b in order to improve wifi performance). I build and manage large and enterprise WiFi networks (and wired), so im very familiar with networks / wifi.
it seems the wifi module in the IOTA watt only supports the oldest wifi standard- 802.11b with a max data-rate (phy-rate) of 11mbit. (This is fine as it’s not pushing much data, and they probably do this to save on costs as well as to get the most possible wifi range).
however, many APs / wifi-routers now disable (or atleaste offer the option to enable/disable 802.11b, and perhaps during a firmware update have set this to disabled by default). Also im pretty sure the iotawatt only supports 2ghz, so be sure you are still running on 2ghz (and not on ONLY 5ghz)
for example on my ruckus standalone firmware setup, 802.11b was enabled, and iotawatt was connected and running fine. however when i updated to ruckus “unleashed” firmware, and redid my config, i was running OFDM-only (ie no 802.11b, only 802g/n) and had my lowest management phy rate set to 24mbit (thus excluding 11mbit and below). as a result my iotawatt did not re-connect (a nice, new feature of v200.15 of unleashed, it will show the failed client, as “un-authorized”). so in my case i made a separate SSID for the iotawatt, which does not use OFDM-only (ie 802.11b is ON), and the iotawatt re-connected just fine.
bottom line - you may need to check if your access points are allowing 802.11b still (some mfgs may call it performance mode / vs compatible mode).
also the antenna / wifi RF performance of the iotawatt is fairly poor, so alot of wifi issues can be attributed to signal issues (w fix being, put a AP very close to the iotaWatt- ideally a hardwired AP, or less ideally a repeater type of AP).
1 Like
For what it’s worth, my IoT network is set to a minimum rate of 12 Mbps to prevent 802.11b and my IoTaWatt is working fine. UniFi Network says WiFi 4, MIMO 1x1, Rx Rate 72.0 Mbps, Tx Rate 54.0 Mbps. I’ve never had any issues with other ESP devices connecting to this network either.
2 Likes
I have been chasing my flaky WiFi problem for some time. I just had to change my install (due to switchboard upgrade), & found the connection was worse. I moved the IoTaWatt near my computer, & it signed in with no problems. (I checked my router setup, & the ´b´ was enabled). I am thinking the problem is related to either shielding or interference to wifi. My EV charger about 4M up the wall communicates reliably, but behind the IoTaWatt there are copper pipes & a mass of AC cables. I tried moving to the limit of the CT cables, & still no reliable comms.
Q: would it be feasible to change the Esp8266 board for one with an external antennae connection? I could install a wifi repeater, but feel it is a bit of an overkill. The router is only abt 7M from the IoTaWatt, but through walls etc.
… or possibly this hack?
I cannot use the model with the antenna connector as it would void the FCC part B certification, but there’s nothing to stop you. I would caution that it’s very difficult to remove the nodeMCU, or also tricky to remove the ESP8266 from the nodeMCU. Probably a hot-plate to the nodeMCU would workbest. In either case, you would need to flash the new ESP8266 with the current firmware.
The hack is looking better in that light.
An extra AP is likely your best bet. If you have the ability to get an Ethernet cable close, you can easily add a cheap AP. You can set it up with a different SSID (used only for this) or the same.