This guide sets out the basic steps in getting a charger to point (connect) to Fuuse so that it is online to the Fuuse platform and able to be controlled remotely via Fuuse.
Step 1: Enter the Fuuse websocket URL
- Chargers need to be told where to connect to so there will be an option within the charger configurations that allows you to add a websocket URL. Please refer to the documentation that came with your charger for instructions on where you add this websocket, or contact the charger manufacturer's support
- The websocket for Fuuse is: wss://smes.hw.fuuse.io
Step 2: Connect your charger to the internet
- IF USING ETHERNET OR WIFI: please refer to the documentation that came with your charger for instructions on where you configure the ethernet or WiFi connection. Note that firewalls present on these kinds of networks may prevent the charger from communicating to the internet, so make sure any firewall has the following allowed:
| Environment | Fully qualified domain name (FQDN) | Ports |
| Live (Production) | smes.hw.fuuse.io | WS: 80 WSS: 443 |
-
IF USING MOBILE CELLULAR DATA (SIM CARDS): you will need to configure the APN settings before the SIM card will work. Please refer to the documentation that came with your charger for instructions on where you configure the APN details, and check with the SIM card supplier what the APN details are.
If you are using Fuuse-supplied Mobius Telenor SIM cards then the APN details are as below:
APN: tel.mobius.cxn
Username: mobiustel
Password: mobiustel
Step 3: Check that the configurations on the charger DO NOT have any randomised delays, peak/off-peak schedules or power-deliver profiles set. These will interfere with the charger's functioning with Fuuse so all of these options must be disabled.
Step 4: Save the configuration and reboot the charger
Step 5: Use this tool to see if the charger has connected to the Fuuse servers successfully. You need to have a tick in the third line (Charger Communicating): https://app.fuuse.io/chargeronboarding
Step 6: Once the charger has connected to Fuuse then it will be able to be set-up fully on the Fuuse platform, which maybe something the client or Fuuse will do.