Room servers are elegant once they’re working. They’re headaches when they’re not.

If your room server isn’t storing messages, delivering them properly, or appearing on your mesh network, here’s how to systematically work through the problem.

Verify Basic Connectivity

Is the device powered and online?

Check:

  • Power LED is illuminated
  • Device is drawing current
  • If WiFi is needed for configuration, is it connected?

Can you communicate with the device?

Try:

  • USB serial connection (if available)
  • WiFi connection to admin interface
  • Bluetooth pairing

If you can’t establish any connection to the device, that’s your first problem to solve. No connectivity means you can’t verify configuration or fix issues.

Check Configuration Settings

Most room server issues are configuration problems, not hardware problems.

Verify these settings:

  • Is the device actually set to room server mode? (Not standard node mode)
  • Is the frequency correct for your mesh network?
  • Is the node ID unique and distinctive?
  • Is the transmit power appropriate for your deployment?

Configuration errors are the most common cause of room servers that appear on the network but don’t function correctly.

Message Storage Verification

Is the room server actually receiving and storing messages?

Test by:

  1. Send a message from another node addressed to the room server
  2. Check the room server’s logs to see if it received the message
  3. Verify storage location (typically in device memory)
  4. Check storage capacity (is the device actually full?)

Common issue: Room server isn’t receiving messages because nodes aren’t configured to send to it. Nodes need to know the room server’s node ID and address messages appropriately.

Message Delivery Troubleshooting

Messages stored but not delivered?

Check:

  • Is the intended recipient node properly rejoining the network after being offline?
  • Does the room server recognize that node has come back online?
  • Is there sufficient signal for the delivery?

Room servers sometimes have trouble recognizing when a node has returned to the network, especially if the node was offline for extended periods. Power-cycling the room server usually clears this.

Coverage Issues

Is the room server actually covering your entire operational area?

Test by:

  • Positioning test nodes at various locations
  • Transmitting to the room server from each location
  • Verifying successful delivery

Coverage maps are useful, but actual on-site testing is more reliable. Terrain, buildings, and RF obstacles often create dead zones that theory didn’t predict.

When All Else Fails

Complete reset and reconfiguration:

  1. Factory reset the room server device
  2. Reconfigure from scratch using documented procedures
  3. Test each function individually before declaring success
  4. Document working configuration for future reference

Room server problems are almost always configuration or coverage issues, not hardware failures. Systematic testing through each component usually identifies the issue.


73