OC200 seemingly dead after power cycle
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.OC200 seemingly dead after power cycle
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Have had my OC200 running for 6 months without any real issues other than just software quirks. A few days ago the power went out to the house briefly, then when it came back up I could not reach the controller.
Device had power, but was not on the network. Was not connected to the cloud, and did not show up when I scanned the entire subnet.
Went through reset procedures, had to try over and over again to be able to get to the page with the static 192.168.0.100/192.168.0.253 ip address setup. Got it reconfigured, loaded up a configuration backup, everything seemed good. I was doing this at my office desk, so after a few hours I unplugged it, took it back to the server closet I keep it in, and it went back to once again being unresponsive?
Now I'm back at my desk with it trying to go through the factory reset procedure again, but I can never get the recovery page to load. Not sure if the thing is just randomly bricked, or if there is some other way to get it reconfigured that doesn't involve repeatedly using the reset button and trying to connect to a web front-end that never ever seems to load?
Tried power by PoE, power by USB, multiple cables, tried connecting my PC via both ETH1 and ETH2, always set to 192.168.0.100 as my IP address and trying to hit 192.168.0.253.
I'm at a loss here, anyone else have any suggestions for getting this thing back running?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Larz256 Yea The old controller is dead, and its backup doesn't seem to have the same password. I think I'm going to set a password manually so in the future when I have another dead controller situation I don't have this problem.
- Copy Link
- Report Inappropriate Content
Dear @Dillius,
Dillius wrote
@Larz256 Yea The old controller is dead, and its backup doesn't seem to have the same password. I think I'm going to set a password manually so in the future when I have another dead controller situation I don't have this problem.
The backup file will contain the device account, after you restore the backup file, you may write down the Device Account under Settings -> Site, then try to adopt the devices and check if it works.
- Copy Link
- Report Inappropriate Content
To clarify @Fae's point if anyone else finds this thread, I DID NOT know about the device password configuration information before I reset my devices; so in theory it would have been correct when restored but the Restored Controller instance would not have "automatically adopted" the devices but I could have used that name and password myself to manually adopt the devices to avoid the time and effort of resetting each of the devices manually.
I will definitely be keeping that in mind if I have to do this again.
- Copy Link
- Report Inappropriate Content
@Dillius Ah fair enough.
@Fae That bring up an interesting point; Once registered, does the controller reach out to devices (push) or do the devices poll into the controller (pull) for configuration?
If it is pull (or even push if the device IPs have changed), it makes sense that the connection is broken even with the right device password on the controller.
I think either deploying the new controller on the same IP as the old controller, or advertising the new controller's IP through DHCP Option 138 would make it automatically adopt again.
- Copy Link
- Report Inappropriate Content
Dear @Larz256,
Larz256 wrote
@Fae That bring up an interesting point; Once registered, does the controller reach out to devices (push) or do the devices poll into the controller (pull) for configuration?
If it is pull (or even push if the device IPs have changed), it makes sense that the connection is broken even with the right device password on the controller.
Because the devices were managed by Controller A (the OC200) before, they only remember and look for where Controller A is by the IP address, Controller B (the software controller) won't use its device account to automatically adopt them when devices are marked as managed by others. We need to reset the device or manually provide the device account to unbind devices from the previous controller A and adopt it in the current controller B.
If we use the migration feature to migrate the controller, the devices will discover controller B and be adopted automatically.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 3265
Replies: 15
Voters 0
No one has voted for it yet.