Content
| Table of Contents | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
If you followed the mentioned steps and still face the same issue, feel free to contact us under support@roomz.io or book a short meeting Support Meeting - 15min Contact
...
Status red / not connected
Should you notice that the sensor shows connection status red in the portal or isn’t working anymore as it should, you can try the following steps.
Make sure the sensor is turned on Switching on
Check the health (connectivity, battery) of the sensor in the portal
If your sensor is offline, try to reconnect it with your WiFi 5 - Connection to the Wi-Fi
If your sensor shows a low battery, check if its still covered by warranty (mostly 2 years from registration date), if yes Request a RMA with ROOMZ support. If no contact your reseller to order a new battery
Connect the sensor with ROOMZ Tools and check the terminal for more information's ROOMZTools
Status grey / Battery 0V / last seen date 01.01.1970 in portal
...
Open the sensor housing and turn the On/Off switch to “On” Switching on
Check on ROOMZ Portal if the sensor is now connecting (connectivity green)
If not rewrite the network configuration on the device 5 - Connection to the Wi-Fi
Connect to ROOMZTools and open the terminal for troubleshooting
Ghost-Meetings are not released (auto-release)
The sensor receives its "action plan" once a day at midnight. If the meeting was created beforehand, the function works. If the meeting was created during the day, the sensor has no information about it and the function does not work. The meeting will not be cancelled, it will be shorted to the duration set in the Room option set Conclusion: The function only works for meetings created before midnight. If you still have the same error, follow these steps:
...
Battery consumption too high
Contact ROOMZ Support for logsto analyze the situation and get more information