Can I remotely reboot EPIC without manage?

It’s far away and I get this when I try to load groov manage:


The control engine is up and running. Shell access is not configured.

Anything I can do?

Can you get to Node-RED?
Can you remote into a PC thats on the same network (in case its a WAN issue vs a LAN)?

The node-red link gives the same error. I’m on the customers VPN, so I am essentially local.

Is there an OptoMMP command that will reboot the whole enchilada?

I was just going there. I think there is, its in the forums… Just doing a search now… So Im thinking you can just add it to a strategy and fire it off one time.

EDIT: Found it: Reset controller from software?

I gave it a try and I got error code -56 - Invalid Address

The OptoMMP manual shows it as not being supported too:


I may have to wait until someone is on site to power cycle it.

Uh, yeah, I do remember that now…
I am not in front of a unit, but Im thinking if there is something in the API… I don’t think there is, but we are grasping for reboot straws after all…

If your nginx server is down or corrupted, this will probably not work. But maybe useful for other situations. Although maybe not so obvious, everything in the groov MANAGE menu options are really just REST GET or POST calls. So with a bit of fiddling, any menu option can be turned into a post or get command. You obviously need to know the hostname or IP, and then use a administrator user account already configured on the device, but the following is basically what you are looking for.

post https:///manage/api/v1/system/restart

Here is some scriptcode that you can import into Postman and then modify for your own specific controller to see the concept.

	"info": {
		"_postman_id": "ce05aa90-006a-44ee-a912-52eb193a821c",
		"name": "groovEPIC",
		"schema": ""
	"item": [
			"name": "Restart EPIC",
			"request": {
				"method": "POST",
				"header": [
						"key": "apiKey",
						"value": "sVEJ2bQq77nNqnNReZLGSBdwnWFjHZnv",
						"type": "default"
				"url": {
					"raw": "",
					"protocol": "https",
					"host": [
					"path": [
			"response": []

Correct. Terry and I have been using these unofficial API calls for odd jobs for a good long while.
It does not need saying, so that’s why I am here to say it…

These unsupported/undocumented API calls should never be relied on in production or continuous use.
Opto reserves the right to remove or change them without notice.

But until then, have fun!