What feature do you want to see?
HW: 3.4-DC
FW: 2.2.1(4)
Issue:
The current code locks the SSID to a BSSID, and incorrectly doesn't change channel when the AP changes channels. This disables the ESP's capabilities to support a standard operation and tenant, channel hoping, of modern WiFi systems. These are presented this way as channel hopping is an interrelated bug in the code with the inability to configure to a WiFi mesh network.
Expectation:
The device correctly handles SSID and channel hopping, including within a mesh network.
Current workaround channel hopping:
Reboot
Current workaround mesh WiFi:
Set IoT SSID on ONLY the base node station (e.g. disable mesh for that SSID).
Program the OpenSprinkler to have a static IP address within the correct subnet range.
Note: setting the SSID to the mesh node station only fails.
Result:
OpenSprinkler connects to the AP successfully.
Per previous emails:
APs in the mesh:
Base station: RT-BE96U
Meshed Station (over ethernet 2.5GB/s): Asus ZenWiFi DB5
Network SSID settings: 2.4GHz only WPA/WPA 2 Personal
Various settings have been disabled/reduced to prevent excessive roaming. I attempted to "bind" the OpenSprinkler to the mesh station, and I've tried disabling both the SSID on the base station, and the base station's 2.4GHz subsystem but that didn't work either, it will not pass the "connecting" state in all of these conditions. These methods are all forcing functions to ensure that connection to the mesh'd station is the only available connection. The unit will not work on the "reduced mesh", meanwhile a laptop or phone handle all similar conditions fine.
The base station in my preferred location is between -76dBm to -82dBm in the connection page, while the mesh station is -56dBm to -59dBm.
What feature do you want to see?
HW: 3.4-DC
FW: 2.2.1(4)
Issue:
The current code locks the SSID to a BSSID, and incorrectly doesn't change channel when the AP changes channels. This disables the ESP's capabilities to support a standard operation and tenant, channel hoping, of modern WiFi systems. These are presented this way as channel hopping is an interrelated bug in the code with the inability to configure to a WiFi mesh network.
Expectation:
The device correctly handles SSID and channel hopping, including within a mesh network.
Current workaround channel hopping:
Reboot
Current workaround mesh WiFi:
Set IoT SSID on ONLY the base node station (e.g. disable mesh for that SSID).
Program the OpenSprinkler to have a static IP address within the correct subnet range.
Note: setting the SSID to the mesh node station only fails.
Result:
OpenSprinkler connects to the AP successfully.
Per previous emails:
APs in the mesh:
Base station: RT-BE96U
Meshed Station (over ethernet 2.5GB/s): Asus ZenWiFi DB5
Network SSID settings: 2.4GHz only WPA/WPA 2 Personal
Various settings have been disabled/reduced to prevent excessive roaming. I attempted to "bind" the OpenSprinkler to the mesh station, and I've tried disabling both the SSID on the base station, and the base station's 2.4GHz subsystem but that didn't work either, it will not pass the "connecting" state in all of these conditions. These methods are all forcing functions to ensure that connection to the mesh'd station is the only available connection. The unit will not work on the "reduced mesh", meanwhile a laptop or phone handle all similar conditions fine.
The base station in my preferred location is between -76dBm to -82dBm in the connection page, while the mesh station is -56dBm to -59dBm.