Atem 40x40 broken after firmware update

I went to update some labels on my 40x40, and saw there was a new firmware update. Stupidly, I decided to run it.

It seemed to freeze at the end - it was stuck on the "finishing" screen, but the device had run the update and restarted, and seemed to be fine

After a while, I had to quit because I was trying to use that computer - but then it lost connection to the hub. Everything in the studio is on static IP's - nothing changed other than the firmware update.

When I look on the back I have the green light by the ethernet, and the orange comes on, and then turns off. No flashing, etc like normal.

I can connect via USB and see it, but USB doesn't let me control it. I tried other open IP's I have in my range. I tried going from subnet 255.255.255.0 to 255.255.0.0 (saw it in another forum) - nothing. Tried update the control software - moved through various iterations. Restarted the computers, the hub, and eventually the entire rack w/ the ethernet router, etc. Tried plugging ethernet directly from hub to control computer. - nothing. Nada. Zilch.

Is there any way to factory reset these things? Or somehow revert back? It works fine, other than I have no remote control, which hurts our workflow.

Thank you!!

type here your network setup :

IP adresses of all devices .. Netmask and Gateway must be the same on all devices ..

If your compouter have IP for example 192.168.1.55 and Atem have 192.168.1.10, then open terminal:
on mac : command+space -> will open window where write : terminal
on win : push START and write : cmd

in terminal try write
ping 192.168.1.10 (<- this is IP adress of ATEM) .. If it will ping , try turn OFF atem , and try again .. May be U have any different device with the same IP adress ..

I'll check, but it shouldn't be the case. Everything has static IPs in the studio. No DHCP. Was connected via ethernet only when running the update, then it power cycles at the end of the update, and couldn't re-establish connection via IP. Nothing in there should have suddenly jumped onto that IP in the 10 seconds it took to reboot.