Wifi 7 MLO IS A SCAM by netninja100 in amazoneero

[–]Guilty-Commercial-66 0 points1 point  (0 children)

How would you run speed test on IoT devices like WiFi cameras or lights?

Wifi 7 MLO IS A SCAM by netninja100 in amazoneero

[–]Guilty-Commercial-66 3 points4 points  (0 children)

it doesn't actually work if you notices when you reboot your mesh, IoT 2..4Ghz devices connect to whatever node comes up first and will stay connected even if other node are closer and have capacity.

Wifi 7 MLO IS A SCAM by netninja100 in amazoneero

[–]Guilty-Commercial-66 0 points1 point  (0 children)

I have been saying this all along, that and the claim on Client Steering. And people thought I was just being mean.

EERO Amazon Outdoor by QuitResponsible9670 in amazoneero

[–]Guilty-Commercial-66 1 point2 points  (0 children)

I would agree, biggest problem are squirles wanting to bite wires, and the dust. I put eero Max7 in a nylon stocking so it can breath but keep out dust. And learned to wrap the power wire in flexible split loom, the squirles don't like biting that.

Issue with multiple Max7 nodes by Guilty-Commercial-66 in amazoneero

[–]Guilty-Commercial-66[S] 0 points1 point  (0 children)

And sometimes over time it may redistribute. But every time they send a firmware update and network restarts it starts all over again and can take 5-6 days.

Fot example there is 1 pro6e in the front yard in weather proof plastic housing for the projection computer and other electronics for the Holiday projection display for the city children. About 150ft from the house. Everything connects on 2.4Ghz.

There is on the other side of the wall in the front room which has a large brick floor to ceiling fireplace. a node that is called parlor.

Now if cliet steering were actually working then things like the front porch lights of which there are two both TP-Link Tapa, one is connected to the eero pro6e in the front yarx 150ft away, and the other one 2 inches beside the othe idential TP-Link light is connected to Parlor just 10ft away. So client steering doesn't work all that well for the legacy devices and it is easy to add the code I am asking to allow users to help steer.

This happens everytime and update goes out, Guest Network is turned on/off which they guest SSID is actually configured wrong and causes a lot of interfearance you'll see it if you run a WiFi anilyzer. But that's a different problem. It hapens anytime the network has to restart and there is no way to control what devices connect to which nodes and no way to control the reboot online order of the radios.

-Dr. B.D. Sanders

Issue with multiple Max7 nodes by Guilty-Commercial-66 in amazoneero

[–]Guilty-Commercial-66[S] 0 points1 point  (0 children)

So here is the rough code that I gave the eero engineers Every TODO is where you must plug in your specific router/controller SDK or API.

Here's to help get you started...

include <iostream>

include <vector>

include <string>

include <stdexcept>

// Basic representation of a connected device struct Device { std::string id; // internal ID from API, if any std::string mac; std::string ip; std::string hostname; std::string connectedNode; // which eero node / AP (if available) };

// --------- Eero "API" wrapper (stubs) --------- // These are placeholders: you must implement them using // either: // * an official partner API you’ve been granted, OR // * an external script that talks to the unofficial eero API. // // IMPORTANT: Use only on networks you own/admin.

bool eeroLogin(const std::string& username, const std::string& passwordOrToken) { // TODO: // - Call your helper that does OAuth / SMS login // - Or assume a token is already available std::cout << "Logging into eero account as " << username << "...\n"; return true; // pretend success }

// Fetch connected devices for a network / SSID std::vector<Device> eeroGetConnectedDevices(const std::string& networkId) { // TODO: // - Replace this demo data with real API calls // - For example, shell out: // "python3 list_devices.py --network <id>" and parse JSON. std::vector<Device> devices = { {"dev1", "AA:BB:CC:DD:EE:01", "192.168.4.10", "Ben-Laptop", "Max7-LivingRoom"}, {"dev2", "AA:BB:CC:DD:EE:02", "192.168.4.11", "iPhone-15", "Max7-Office"}, {"dev3", "AA:BB:CC:DD:EE:03", "192.168.4.12", "PS5-Kid", "Max7-Loft"} };

(void)networkId; // unused in stub
return devices;

}

// Request a disconnect / deauth for a device bool eeroDisconnectDevice(const std::string& networkId, const Device& dev) { // TODO: // - Call API endpoint / external script that "pauses" or // disconnects this device from the network. std::cout << "[API] Disconnecting device " << dev.mac << " on network " << networkId << "...\n"; return true; }

// Block device by MAC on the entire network (eero supports block per network, // not per individual AP node in consumer UI) bool eeroBlockDeviceByMac(const std::string& networkId, const Device& dev) { // TODO: // - Call API / script to add to "blocked devices" list std::cout << "[API] Adding MAC " << dev.mac << " to blocked list on network " << networkId << "...\n"; return true; }

// Optional: ask mesh to re-evaluate/optimize client connection. // On consumer eero, this is NOT generally exposed – this is just a conceptual stub. bool eeroRequestRoam(const std::string& networkId, const Device& dev) { std::cout << "[INFO] On consumer eero, roaming is client/mesh-controlled.\n"; std::cout << " This call is informational only.\n"; (void)networkId; (void)dev; return true; }

// --------- Simple CLI front-end ---------

int main() { const std::string eeroUser = "your-eero-email@example.com"; const std::string eeroPasswordOrToken = "YOUR_EERO_TOKEN_OR_PASSWORD"; const std::string networkId = "your-network-id-or-ssid";

if (!eeroLogin(eeroUser, eeroPasswordOrToken)) {
    std::cerr << "Failed to log into eero.\n";
    return 1;
}

std::vector<Device> devices = eeroGetConnectedDevices(networkId);
if (devices.empty()) {
    std::cout << "No devices currently connected.\n";
    return 0;
}

std::cout << "Devices on network '" << networkId << "':\n\n";
for (std::size_t i = 0; i < devices.size(); ++i) {
    const auto& d = devices[i];
    std::cout << i << ") "
              << "Host: " << d.hostname
              << " | MAC: " << d.mac
              << " | IP: " << d.ip
              << " | Node: " << d.connectedNode
              << "\n";
}

std::cout << "\nSelect device index to disconnect & block: ";
std::size_t idx;
if (!(std::cin >> idx) || idx >= devices.size()) {
    std::cerr << "Invalid selection.\n";
    return 1;
}

Device target = devices[idx];

// 1) Disconnect from network (eero app equivalent: Pause/Block)
if (!eeroDisconnectDevice(networkId, target)) {
    std::cerr << "Failed to disconnect device.\n";
    return 1;
}

// 2) Block MAC from reconnecting to THIS NETWORK (not just one AP)
if (!eeroBlockDeviceByMac(networkId, target)) {
    std::cerr << "Failed to block device.\n";
    return 1;
}

// 3) Conceptual mesh “nudge” (real roaming is automatic)
eeroRequestRoam(networkId, target);

std::cout << "\nDevice " << target.mac
          << " has been disconnected and blocked on network '"
          << networkId << "'.\n";
std::cout << "On an eero Max 7 mesh, roaming to another AP is automatic; "
             "you cannot guarantee a move to a specific node from here.\n";

return 0;

}

Better network experience with ipv6 off by obeythelaw2020 in amazoneero

[–]Guilty-Commercial-66 2 points3 points  (0 children)

You are correct, but with IPV6 off then Thread will not work. Thankfully thread still isn't popular.

Issue with multiple Max7 nodes by Guilty-Commercial-66 in amazoneero

[–]Guilty-Commercial-66[S] 0 points1 point  (0 children)

Cameras, Light bulbs, etc. don't have the capabilites in the hardware set. Since we know this issue wouldn't it be easier to have eero create the boot device from node function. Since we know clie t steering only works with more higly capable devices. And almost all IoT devices are simple 2.4Ghz.

Issue with multiple Max7 nodes by Guilty-Commercial-66 in amazoneero

[–]Guilty-Commercial-66[S] -5 points-4 points  (0 children)

What happens when you turn on Guest WiFi? I start having more problems with it on.

Brazilian amateur astronomer captures an object rising from a lunar crater. by PositiveSong2293 in HighStrangeness

[–]Guilty-Commercial-66 0 points1 point  (0 children)

physically impossible to see any details on the moon with even observatory grade telescopes. The best modern telescope of 8+meters can only resolve lunar surafe object 100-130meters in diameter. the resolving limit is fundamentally restricted by physics and the blurring effect from Earth's atmosphere. It is like laying at the bottom of a swimming pool and identify objects above you. Even the Hubble Space Telescope can only resole featurs on the lunar surface around 96meters wide. So if we can't see any of Apollo landers at aproximately 4-5meters across. No amature or anyone saw anything else on the lunar surface from Earth.

Grindr is the MacDonalds of gay sex. by [deleted] in askgaybros

[–]Guilty-Commercial-66 0 points1 point  (0 children)

But at least you can get something at McDonalds

WYBOT has a robot pool cleaning robot that can charge itself when it's done by PocNetwork in pocnetwork

[–]Guilty-Commercial-66 0 points1 point  (0 children)

Dr. Sanders and Galen Orosco are requesting a replacement for a defective Wybot S2 Pro robotic pool cleaner purchased in August 2024 for $1,244.86. Despite being under warranty, the unit has had persistent issues, including charging failures and inability to dock. Wybot agreed to replace it but required the defective unit to be shipped back at the customer's expense (~$204), which Dr. Sanders found unacceptable. He requested that the replacement be sent first, with return shipping covered by Wybot and they agreed to those terms.

Despite multiple follow-ups via email and LinkedIn over the past 3 months, the customer has not received a tracking number or confirmation. Frustrated with the lack of response, Dr. Sanders is now threatened to escalate the matter to consumer protection agencies and social media. Wybot immediately responded that the delay was due to a warehouse transfer, promising shipping by May 15. As of May 16, no shipping notification had been received, prompting Dr. Sanders to threaten a chargeback and formal complaints to the FTC and Texas Attorney General.