In the Android SimpliSafe App the Video Doorbell Pro camera keeps spinning when attempting to bring on line?

@stevefortuna Do you notice this behavior when trying to livestream your Video Doorbell Pro on the Online Account as well? I recommend logging into the Online Account using the browser of your choice and trying to launch a livestream from there.

 

If the livestream does not load on your computer, that may indicate a connectivity issue with the Video Doorbell Pro. In that case, I recommend using our in-app Connection Check tool for tips on how to strengthen the camera's Wi-Fi connection. Check out the How to Troubleshoot Your Camera's Connection article for steps on how to use the Connection Check tool and details on what your results mean.

Using the web interface I received the following. I did this with disabled and enabled VPN.

@simplisafe_admin  I have done all that you have asked, and the problem still exists.

What is the quality of the wifi network device being used in the doorbell device?

As this is a critical component for security and safety, is there any program in place to replace the wifi device in the doorbell camera with a higher-quality component?

Given there is a power source, the replacement wifi component would have a power source to ensure the camera wifi remains functional connecting to the wifi network.

@simplisafe_admin 

I have performed a doorbell camera connection test and both metrics come back blue and good. Then I attempted to connect and the app interface just spins. 

This almost appears to be an issue with SimpliSafe app controlling the doorbell camera as when I click on the  indoor camera the camera engages and there was no occurrence of the spinning wheel.

Does the SimpliSafe doorbell camera have a sleep mode? If it does, could this be causing the issue?

SimpliSave Wifi device firmware client net-mesh connection implementation:

A separate issue, the doorbell camera at times does not connect to the Mesh node 5 feet away, as the mesh network I have has one router and one satellite. I placed the satellite five (5) from the SimpliSafe doorbell camera. 

Using the vendor interface I verified the doorbell wifi connection and a times it does not connect  to the mesh node 5 feet away. I attempt to force it to connect by using the routers ACL interface to deny and allow access to the mesh network. I will deny the doorbell access to the the network, wait 15 minutes, then allow the doorbell camera access. This action would eventually get the doorbell camera to connect to the mesh node about 5 feet from away.

IEEE 802.11s Specification for mesh network

Does the doorbell wifi firmware or all SimpliSafe wifi products firmware follow IEEE 802.11s Specification for mesh network including a client, i.e. SimpliSafe products wifi firmware? 

After doing some research there is a beacon handshake that wifi clients should implement to find the "best" wifi mesh node to connect. 

The IEEE specification governing wireless mesh networking, including how clients (non-mesh stations) connect to mesh nodes, is IEEE 802.11s. 

This is an amendment to the IEEE 802.11 standard (Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications), ratified in 2011 and incorporated into the base 802.11-2012 standard.

It defines protocols for peer-to-peer wireless mesh topologies, enabling multi-hop forwarding among mesh nodes while supporting integration with traditional 802.11 clients.

Key Concepts in 802.11s

Mesh Basic Service Set (MBSS): 

The core structure of an 802.11s network, forming a self-organizing, multi-hop cloud of mesh stations (mesh STAs). This appears as a single logical broadcast domain to connected devices.

Mesh Station (Mesh STA): 

Any device supporting 802.11s mesh functionality. This can include access points (APs) acting as mesh portals/gateways or even non-AP stations (e.g., clients) if they implement mesh features.

Mesh STAs form peer links with each other for backhaul (multi-hop routing) using protocols like Hybrid Wireless Mesh Protocol (HWMP).

Portal: 

A mesh STA that connects the MBSS to external networks (e.g., wired Ethernet or the internet). It acts as a bridge, translating between mesh and non-mesh addressing.

Mesh Access Point (MAP): 

A mesh STA that also functions as an AP, providing a traditional Basic Service Set (BSS) for client associations. This is the primary way clients connect to the mesh.

How a Client Connects to a Mesh Node

In 802.11s, a "client" typically refers to a non-mesh station (non-mesh STA)—a standard 802.11 device (e.g., a smartphone or laptop) that does not participate in mesh routing or forwarding. 

These clients connect to the mesh network via a Mesh Access Point (MAP), treating it like a conventional AP. The connection process follows standard 802.11 association but with mesh-specific enhancements for addressing and forwarding:

Discovery:

The client scans for available BSSs using beacon frames or probe requests/responses.

The MAP advertises its BSS via beacons, including the Mesh ID (similar to an SSID for the mesh cloud) and standard BSS parameters (e.g., channel, security settings).9965e8

Non-mesh clients ignore the Mesh ID and see only the AP's BSSID.

Authentication:

Uses standard 802.11i mechanisms (e.g., WPA2/3 with SAE for secure networks) or open authentication.

For mesh-integrated security, 802.11s supports Simultaneous Authentication of Equals (SAE) for peer links, but client auth remains AP-client focused.

Association:

The client sends an Association Request to the MAP's BSS, which responds with an Association Response.

The MAP assigns an Association ID (AID) to the client, integrating it into the BSS as in any 802.11 network.

Addressing and Forwarding (Proxy Mechanism):

Once associated, the client's frames are handled via a mesh proxy on the MAP. This proxies ARP/ND for the client, mapping its MAC address to a mesh-wide address (using 6-address scheme: source/destination MACs plus mesh forwarding info).

Traffic from the client is forwarded over mesh paths (using HWMP routing) to portals for external access, or to other MAPs for local delivery.  This ensures seamless multi-hop without client awareness. Synchronization (e.g., timestamps in beacons) ensures timing alignment between mesh nodes and clients.

Power Save and Handoff:

Clients use standard 802.11 power save modes; mesh adds support for proxying power save announcements across the MBSS.

Handoffs (e.g., roaming between MAPs) leverage 802.11r/k/v for fast transitions, with mesh routing handling path updates.

Key MAC/PHY Modifications in 802.11s

MAC Enhancements: 

Adds mesh control fields to frames for path selection, congestion control, and 6-address headers. Supports HWMP for proactive/reactive routing.

PHY Compatibility: Builds on existing 802.11 PHYs (e.g., 802.11a/b/g/n/ac/ax), with no major changes required for client connections—focus is on backhaul links between mesh nodes.

Security: 

Mesh links use SAE; 

client links use BSS security. Gateways may require 802.11u for unauthenticated access (e.g., captive portals).

Relation to Other Standards

Wi-Fi EasyMesh: 

A Wi-Fi Alliance certification based on 802.11s but simplified for controller-based multi-AP setups (tree topology vs. 802.11s's peer-to-peer mesh). EasyMesh uses 802.11s for backhaul but adds proprietary elements for interoperability.

Use Cases: 

Extends WLAN coverage for internet access, IoT, or enterprise without wired backhaul.

For the full technical details, refer to the official IEEE 802.11s-2011 document (available via IEEE Xplore). Implementations like open80211s (in Linux kernel) demonstrate practical client-mesh integration.

Regards,

Steve