Skip to content

Hub Display Logic & Multi-site Deployment

❓ Problem Description

In multi-site deployment scenarios, the Hub displays all sensors under the account, but non-local devices will show as "N/A". If you want the Hub to display only local devices and would like to understand why Hubs cannot sync data display via network, here is the technical explanation and solution.

✅ Solutions & Technical Explanation

By default, the Hub displays all devices under the same "Asset/Home". If you place all devices in the default My Home, the above phenomenon will occur.

Solution: Use the "Multi-Asset" Feature for Grouping

Simply create different assets in the App based on physical locations and move devices accordingly:

  1. Open the MOCREO App, tap the asset name in the top-left corner, and select "Home Management".
  2. Tap "Add New Home" to create a new asset (e.g., name it "Office").
  3. In the device list, change the Home assignment of the Hub and Sensors located in the office to "Office".
  4. Result: Now, the office Hub will only display Sensors under the "Office" asset, no longer showing devices from home.

2. Technical Deep Dive: Why Don't Hubs Share Data via Internet?

Regarding the suggestion to "let Hubs share data via the Internet for network-wide data sync display", this is indeed a direction for modern IoT experiences. However, MOCREO currently adopts a "Distributed Architecture" design primarily based on the following industrial-grade stability considerations:

🛡️ Fault Isolation

Each Hub is designed as an independent "combat unit".

  • Independence: If the network at Location A goes down or the Hub fails, the Hub at Location B is completely unaffected.
  • Risk Mitigation: If Hub interconnection is established, once a core node has data anomalies, it could cause data display logic confusion across the entire network. Maintaining "no interconnection" means an extremely high fault tolerance rate.

⏱️ Real-time Data Latency

The core value of the Hub screen is to display local, immediate RF raw data.

  • Latency Risk: If the data path becomes Sensor -> Hub A -> Server -> Hub B, the data displayed on Hub B will inevitably have latency.
  • Misleading Operations: In cold chain or laboratory monitoring, making decisions based on delayed data (e.g., temperature from 5 minutes ago) is very dangerous. We insist that the Hub screen must reflect the current real status.

⚙️ Role Definition

  • Hub (Gateway): Defined as a data producer/forwarder. Its primary task is to report data to the cloud with low power consumption and high stability.
  • App (Client): Defined as a data consumer. The App has powerful processing capabilities, suitable for aggregating and displaying full data.
  • Having the Hub take on the client's "full data display" function would increase firmware complexity and power consumption, thereby reducing its core stability as a gateway.

!!! note Nevertheless, we fully recognize the importance of enhancing multi-site linkage experience in today's favorable network conditions. This suggestion has been submitted to the R&D team as an important reference for future high-end product line feature planning.