crwdns2933423:0crwdne2933423:0
crwdns2918538:0crwdne2918538:0

Getting WiFi working

crwdns2936025:01crwdne2936025:0 —

crwdns2935477:0crwdne2935477:0:

crwdns2935483:0crwdne2935483:0

The JuiceBox doesn't talk directly to your phone, or anything local. It talks only to JuiceNet - the cloud server that crunches all the data.

The box remembers one WiFi network, and only one WiFi network. It will constantly try connecting to this last-known network as long as it's powered up, retrying every few seconds, for all eternity until the heat death of the universe.

The WiFi processor is independent of the safety/J1772 processor. That is to say, it'll charge without WiFi, and the only thing WiFi can do to affect charging is change settings - like a schedule or access control.

There are no settings or history stored on the box (technically, history IS stored on the box, but the server/app-side UX is god-awful and doesn't retrieve or process the locally-stored event and energy data). So, everything about the box is done remotely - user control, what car it is, time-of-use, cost, etc., is all cloud-based.

The only persistent settings stored in the box are three: WiFi name, WiFi password, and the "offline amperage" - known in the web interface as "Wire Rating". The offline amperage is used when the box first starts, until the box gets a run-time charging rate command from JuiceNet. Anything below 6 amps is "stop charging".

You cannot connect JuiceBox to a network that requires web-based login. Networks like "xfinitywifi" won't work because they need a web browser to open to sign-in, and the JuiceBox isn't a web browser. If you can add its MAC address (10.10.10.1/command/get wlan.mac - see PC setup instructions) to your whitelist, it may work.

crwdns2944171:0crwdnd2944171:0crwdnd2944171:0crwdnd2944171:0crwdne2944171:0