DEMO — all data here is simulated. This is the real bridge interface, rendered offline with SpiderBridge's faker. Built and tested with this ESP32 board · Donate
SpiderBridgeSettingsControlStatusNetworkMQTT logFirmwareAbout

SpiderBridge Settings

Home network (uplink)
Leave empty to keep the stored password.
Connect joins the network right away, without a restart, and stores it once it works; if it fails, the bridge goes back to the previous network. Every step is in the system log (and syslog).
Bridge address on the home networkA fixed address keeps this page at the same URL.
Hotspot for the grow controller Generate fills in a strong random password; save the page to use it. Controllers on the hotspot then need the new password (app or Bluetooth below). First boot and factory reset use SpiderBridge / 12345678.
Hide hotspot name (SSID)
The network is no longer shown in Wi-Fi lists. Controllers that already have its name and password keep connecting. Set controllers up first (app or Bluetooth below), then hide it; the app's network list will not show it while hidden. Changing this restarts the bridge.Any private network in CIDR form, e.g. 192.168.10.0/24, 10.20.0.0/16 or 172.16.5.0/28 (prefix 8 to 30). The bridge takes the first address, DHCP hands out the following ones -- as many as the subnet holds, at most 100 (the DHCP server's lease table). Must not overlap the home network. Changing it restarts the bridge; this page then moves to the new hotspot address.
Add GGS controllers (Bluetooth, optional)

Optional. All the bridge needs is that each GGS controller is connected to this bridge's hotspot. If yours already is, or you prefer the Spider Farmer app, you can ignore this section: in the app, open the controller's Wi-Fi settings and choose this hotspot's name and password. A controller already paired with your phone can stay paired -- nothing has to be removed or reset.

Controllers that are not paired with a phone advertise themselves over Bluetooth (remove one from the Spider Farmer app to make it visible here). Select one controller and send it this hotspot's name and password; it joins on its own. The bridge's Bluetooth is off in normal operation: Scan and Send restart the bridge into a short Bluetooth-only mode (about 30 seconds to a minute) and back -- controllers on the hotspot drop out for that time and reconnect by themselves. The list shows the result of the last scan.How it works: Bluetooth is never on in normal operation -- the bridge needs that memory for the controllers' encrypted connections. A scan or a send restarts the bridge into a Bluetooth-only boot that does that one job, stores the result and restarts straight back into normal operation with Bluetooth off. Nothing has to be switched off by hand.
Loading…
Receiving Wi-Fi settings makes a controller stop advertising by itself. Without this box the bridge deactivates it again right after sending, so it stays visible to the Spider Farmer app. Deactivate any time with the button below -- or on the Control page while the controller is on the hotspot.
Log of the last Bluetooth jobEvery step: connection, the command as plain JSON, its encryption and the frame written to the controller, and each reply decrypted. The hotspot password is shown as *****. Open as text
MQTT Broker (optional)Everything works without a broker: the controllers are driven straight from this interface. Filling this in only makes the devices appear in Home Assistant.Prefix for every MQTT topic.In use: SpiderBridge A1B2C3 (default). Names the bridge device in Home Assistant; one name for the whole bridge, whatever controllers are connected. Leave empty for the default, which ends in this bridge's MAC so several bridges stay apart. Applied immediately, no restart. Controllers are renamed on the Control page.
Syslog server (optional)Every system log line is also sent here, so the complete history is kept even though the bridge itself only holds the last few lines. Applied immediately. Leave the host empty to turn it off.MQTT packets go into the same stream as the system log, tagged mqtt, with topic and complete payload.
Syslog encryption (TLS)Only used with the TLS transport above.
Accept any certificate
Connects to syslog servers with a self-signed certificate. Traffic is encrypted, but the server's identity is not verified.None stored. Paste a PEM certificate to verify the server properly; without one, the built-in list of public CAs is used. Leave empty to keep the stored one; type a single minus sign to remove it.
Broker encryption (TLS)Only used when the URI starts with mqtts://. Leave this alone for a plain mqtt:// broker.
Accept any certificate
Connects to brokers with a self-signed certificate. Traffic is encrypted, but the broker's identity is not verified.None stored. Paste a PEM certificate to verify the broker properly. Leave empty to keep the stored one; type a single minus sign to remove it.
What to publishOnly relevant with a broker. With no broker configured neither layer publishes anywhere, and the interface still controls everything.Ready-made entities: switches, sliders, sensors. Announced via Home Assistant discovery.Every controller packet verbatim on spiderfarmer/<id>/raw.Entities plus the raw stream.
Internet access
Let the controller reach the internet
Turns NAT routing for hotspot clients on or off.
Mirror traffic to the Spider Farmer cloud
Needed for the vendor app. With this off the bridge answers the controller itself and nothing leaves your network. Both have to be off for a fully local setup, because the mirror uses the bridge's own uplink and bypasses NAT.
Schedule, cycle and PPFD values are only read from the controller while cloud mirroring is off. With it on, the cloud closes the session when the bridge queries the stored configuration, so those entities stay empty until something is changed in the Spider Farmer app.
Name and time service for clients
Send all client lookups to this server
Leave the field empty to follow the resolver your router hands out. Lookups are always forwarded and the real answer relayed back; only the Spider Farmer cloud name is redirected to the bridge, which is what makes the proxy work.
Redirect client time requests here
Point it at a local server to keep the clock correct with the internet switched off.
Resolver in use: 192.168.1.1 (DHCP)
Exceptions while internet access is off
Keep name resolution working
Without it the controller cannot resolve anything, not even the bridge.
Keep time sync working
Without it the clock drifts and schedules fire at the wrong time.
Bridge clockUsed by the bridge itself. Separate from the redirect for hotspot clients above.Schedule times on the controller are local, so this decides how they are read.
decided by the zone rules
Follow the zone's own rules
Following the rules is almost always right: the switch happens on the correct date without anything to remember. Unticking this pins the clock and the switch above decides which way.
Apply this to every controller
Sends the zone and daylight-saving choice to each controller as it connects, and puts it back if it is changed from the Spider Farmer app. Leave this off to set the zone per controller on the Control page.
Firmware updatesEither a .bin image or a JSON file of the form {"version":"2.6.0","url":"...bin"}. A JSON file lets the version be compared before anything is downloaded.
Check at startup
Install automatically when newer
Without the second box a newer version is only reported on the Firmware page, where you can install it.
Web interface protection
Require a password
Leave empty to keep the stored password. Unticking the box removes protection entirely.
Backup
A JSON file with every setting, including the WiFi and broker passwords. Keep it somewhere private.
 
Applies a backup and restarts.
Danger zone
Takes about 15 seconds.
 
Clears the WiFi credentials, the broker settings, every device name and both access lists. The bridge comes back unconfigured on its own hotspot at 192.168.10.1.