Eero 2nd Gen issues #77
Comments
|
have you tried the esphome firmware, and does it behave any different? can you get a pcap of the ratgdo traffic? |
|
No sorry, I really should have done that. I was about to give up and try homebridge-ratgdo (my original plan). ESPHome didn't even cross my mind. I was so happy once it worked after hours of messing around, wondering if my lights/furnace were causing interference that once I got it going I put the cars back in. On the next firmware update I'll try to grab a PCAP. Capture off the wifi right? Should be able to do that. |
|
I have a first gen Google WiFi mesh and just spent an hour battling it to get my ratgdo reconnected. Similar to the experience above, pings all over the place even with a satellite in the garage 6 ft from the device. Watching ping times and it looked like my unit had 3 ping times (6-10ms, 200-400ms, 600-800ms) that it would do 2-3 pings at a time interval then timeout for a few and then ping 2-3 times at a different one of the ping times. This lines up with 3 mesh nodes I have in the house. In an attempt to reduce hopping I unplugged the unit in the garage closest to the unit and my pings instantly dropped to the 6-10ms range and no more timeouts. Seems like the unit has a hard time when it can see multiple nodes of the same network and is constantly hopping between. |
|
+1 I am having the same issue with a multi-AP Eero network and a ratgdo (Homekit flashed) that has constant dropouts and returns pings between 4ms to 6-700ms (on the occasions it doesn't timeout). It's unusable and totally unresponsive in Home.
Eero reports a perfect connection (as it should, the area has ideal signal)
|
|
I last wrote code (Rails, lol) like 15 years ago so ... take this with appropriate caution. Simply trying to help. Downloaded the repo, installed VSCode, and monkeyed around enough to figure out how to build and monitor using PlatformIO. Here's the log showing disconnects (from the HomeKit class) that perfectly align (well, they seem to immediately precede) ping timeouts. You'll see me turning the light on and off a few times when it stayed connected long enough for a command to go through. One thing I noticed is that every time it disconnects and reestablishes it increments the HomeKit server port by 1 or 2. Assuming this ... isn't great. I am giving up for now, so I put the MQTT firmware on and there are zero dropped packets or issues with connectivity. So, definitely an issue with this projects implementation of Wifi (or its dependencies implementation). LOG:
(Nevertheless, this all seems to be happening in the Arduino-HomeKit-ESP8266 code, not this project's.) Going to play with the code to learn more. What could go wrong!?
|
it does seem that way, more likely than an issue with mesh management per my original report. All my satellites are reachable throughout my home, including when it works successfully when connected to the master AP - so perhaps there is a signal strength threshold issue that causes flip-flopping, and that in turn causes a more serious resource or other issue in the stack. Thanks for everyone's efforts, this is a very cool project. I'm sure this'll get fixed. |
|
It would be really helpful if you can get a pcap of the traffic when this is happening. you can apply a host filter for just the ratgdo ip . But debugging network issues without seeing what's happening on the network is really hard. When I first connected my ratgdo, I was seeing similar issues and I traced it back to a problem where a device on my network was spamming it with bad mdns packets and overwhelming the network stack. You don't need to share your pcap here as it may contain information you don't want on the internet, but you should at the very least scan it for yourself and see if you see anything unusual. you can send the pcap privately if you need help looking at it. |
Is there a generic Something like this? Hosyond 3Pcs ESP8266 ESP-12E CP2102 NodeMCU Lua Wireless Module Development Board for Arduino IDE/Micropython https://a.co/d/62J6OSw |
|
+1 I too am having similar issues with a Muti-AP Eero network. I suspect the issue is that I have multiple AP's that share the same SSID but have different BSSID's. I wonder if we are not storing the BSSID in the flash so that we can't reliably connect to the correct one? Or maybe the code that removes "duplicate" networks should be taking the BSSID into account? |
I just grabbed a PCAP but it does have a ton of info that's hard to scrub. Is there a more private way of sharing or scrubbing? Here's an example: 
|
|
The only thing I see there is mdns and arps and they look ok. The key would be to capture when you see it go unresponsive or if you are pinging it to get a capture when a packet is dropped or when you see really high latency. |
|
Not sure how to implement in this firmware, and although not directly related, it can’t hurt if it’s relevant: |
|
Neat. I'll give this a try. But probably not before the end of the week. |
|
I have a pro 6 gateway that my ratgdo connects to (2.4Ghz) and I am not having any issues. --- 192.168.5.157 ping statistics --- |
|
Mine works fine on the gateway. It's as soon as there are satellites close by it gets really wobbly. I upgraded to 0.9 yesterday and switched back to my Eero network to grab a PCAP. It connected and I got nothing: no ping, no response in HK, no packets in wireshark. I reset it multiple times didn't help. Switched back to my non-mesh WiFi and it was back up and running with no issue. To be clear I'm not blaming 0.9, I seem to recall I experience the same issue before. It may have been a glitched set up. Then I ran out of time. In the coming days I'll have another go. I wish it were possible to switch WiFi remotely, but IIUC that's not technically possible. |
|
Can someone with an eero network try version 1.0 and report back if there is any improvements |
Very preliminary feedback, but so far results are promising on 1.0. I just re-installed it and I've got an uptime of 26 mins and counting, which I was not able to achieve prior to this release. The system also didn't reset during the pairing process which was also very promising. I'll make sure to provide further info on uptime as I monitor. Update: |
|
Bummer. If you can get logs that would be helpful |
|
I wonder what it is about these eero networks. I think this is the biggest outstanding issue. Some things I can try:
On my device with the 1.0 firmware, I now see very responsive pings like you see with the mqtt firmware. Can someone with eero network see if their pings are back to normal or if you still see the wildly varying results? Since I don't have an eero network, a serial log with a crash dump would go a long way to helping me find the issue. |
Seems like it survived the night at least. 7 hours and counting at the moment, but it must have rebooted again just before midnight. Is there a way to get logs to stream wirelessly or do I have to keep my computer attached and tail USB logs? |
|
I use two Eero Pro 6 nodes in bridge mode with wired backhaul and haven't had any network issues since v0.9 (and v0.6 prior to that is what fixed my pings). Before updating to version 1.0 yesterday it had been connected for over 21 days and was working great. Checking uptime now I see it's been connected for over 16 hours which is when I updated. I'd check the wiring and power source on the ratgdo to make sure there isn't something that's loose causing it to disconnect abruptly. |
You really need to be connected to the usb port and get the logs from serial. The problem with streaming the logs wirelessly is there would be no way to capture the crash. |
|
Anyone here want to try PR #133 |
I do think that a few of the items in the feature request will benefit overall useability and stability; if not both. |
|
I'm happy to report 1.0 has been working well for me. Uptime has lasted about 3 days as of the time of writing this. It's clearly still rebooting, but far less frequently than before and it has not (yet) impacted my usability. |
|
Allow forcing 11G mode in #133 . Build v1.1.0 |
|
Should be fixed as of 1.3.0. You can now force 802.11g and reduce your tx power. |
and others
Follow-up to my comment here, because this is potentially useful info
#24 (comment)
There is a problem when connected to Eero (Gen 2) satellites - loss of connection, No Response, pings all over the place (up to 1000ms and drops). I moved the ratgdos next to the master Eero Pro AP, far away from the garage and other satellites, and all these issues vanished.
This is the case with 0.7 & I also built the firmware per #24 (comment) - there was no improvement.
So, I dug out an ancient OpenWRT reflashed-TP-Link (irrelevant but it was a fun find) and installed it in my garage as an additional AP and now the ratgdos are rock solid, with steady 5ms ping times, no dropouts. It works perfectly.
For what it's worth: my wifi is very stable across the whole mesh, the satellites give me 300Mbps all day long with no issues on my phone, laptops etc. So it really seems like there is perhaps something in Eero mesh management that messes with the wifi stack.
I'll keep an eye out for any improvements in the firmware and give them ago if they might address this.
The text was updated successfully, but these errors were encountered: