All devices are not connecting
- Use the HomePass app to check that your new network name matches your previous SSID.
- Check the Home password also matches what was previously used on the old network.
- Make sure you have disabled the old Wi-Fi on your router or router/combo.
- If you did not re-use the same SSID and password of your previous network, check to make sure your device settings match what has been set up in the app.
- If you have not re-used the same SSID and password as your old network, you need to make sure you have forgotten the old network on every device, although disabling the old Wi-Fi entirely makes this unnecessary.
A group of devices is not connecting to Plume
Listed here are some common reasons for this to occur after you've completed setup:
- You previously had separate 2.4 and 5 GHz networks (SSIDs) on your old wireless router.
- Since you previously had two separate SSIDs, you'll have to check that all your devices have the updated Wi-Fi credentials. If you reused the credentials of one of these SSIDs, devices using the other will need to be updated with new credentials since Plume uses a single SSID for both bands.
- Likewise, you will need to disable both 2.4 GHz and 5 GHz radios, otherwise, devices will not disconnect from the old network and connect to Plume.
- Certain 2.4 GHz only IoT (Smart Home) devices are not connecting to the new Wi-Fi even though the SSID and password match the previous router.
- There are some smart home devices that use a control app running on mobile for setup, that have issues connecting to Wi-Fi networks that use a single SSID for both bands like Plume.
- These 2.4 GHz only devices are actually using the BSSID to connect instead of the SSID. Because of this, even if you set up Plume's SSID and password to match the old 2.4 GHz network's, these devices will not be able to immediately connect. Click here to learn more about this behavior and how to connect these devices to Plume.
- If you are still using you old router, check the DHCP settings.
- If there is a limit set on the IP address pool, it will need to increased to accommodate the IPs required for your new pods.