Valid for all Semieta Server Versions
On occasion, a controller might need to be rebooted. This could be due to a software update, an issue sending/receiving commands or if Events are not pulling through accordingly.
First, you will need to establish whether you can communicate with a controller. This can be achieved in 3 ways:
- Send commands via the Controllers menu and then Manage Controllers > Send Controller Parameters
- Ping the controller's IP address via Command Prompt - See the below article:
Semieta Server - How to 'Ping' a Controller - Navigate to the controller's web interface by searching for the controller's IP address in your preferred web browser - See the below article:
Semieta Server - How to connect to a controllers Web-Interface
Note - If none of the above work, then a manual reboot might be required, please follow the details in the attached article:
Semieta Server - How to manually re-boot a physical controller board
Once the connection to the controller has been established, then please navigate to the web interface, as per the instructions above.
Then navigate to System and then select Reboot:
This will open a System Reboot screen, select Reboot to confirm:
This will begin the reboot process and should take roughly 10 seconds.
Once the controller has rebooted, you will be greeted with the following screen:
Click on the button in the middle, and this will return you to the Controllers log-in page.
If the controller does not reboot, and a manual reboot does not work - please raise a ticket and contact the Semeita Support Team and we can investigate further.