Zinda
Community Member
I'm posting this since there is clearly an issue here and I want to make sure other Neptune Apex users are aware of current workarounds and fixes.
I had to power cycle my Neptune Apex brain last night because it could not connect to my WIFI. When it came back on, I was shocked to discover that it had readdressed many of the modules on the tank, decided (randomly?) what kind of device they were, and put them into auto mode! Thus, my powerhead was now recognized a light (with a default on/off schedule, etc). This could have been disasterous depending on what got assigned to what. There was no clear way to fix the problem, so I went through and copied the old code and settings to the new module addresses. A real pain. It was just lucky I noticed.
Clearly this is not entirely unusual behavior. As these posts show, others have had the same issue:
- https://www.reef2reef.com/threads/apex-modules-change-address-after-power-interuptions.1001137/
- https://www.reef2reef.com/threads/my-apex-tried-to-crash-my-tank.1028540/
- https://www.reef2reef.com/threads/apes-modules-missing-after-turning-some-power-off.1043521/
It appears that Neptune is finally addressing this issue. Product support let me know that there is a new "Module Replacement" task that you can use to assign the old device to its original address (assuming you haven't deleted it). Still a pain, but better. Now you don't have to copy all your stuff around and hope you set the settings right. Doesn't work for all modules and addresses but fixes some things.
Clearly the device shouldn't be doing this in the first place. The best data I have on this at the moment is the best practice that many have noted on this forum: Use a battery backup with the brain so it never power cycles. Clearly this won't work in all cases (like my case above), but it can help prevent spurious nightmares.
I'm still waiting for Neptune product support to let me know how to avoid this in the first place. I'll post when I find out. Love to hear if others already know how to avoid the problem.
I had to power cycle my Neptune Apex brain last night because it could not connect to my WIFI. When it came back on, I was shocked to discover that it had readdressed many of the modules on the tank, decided (randomly?) what kind of device they were, and put them into auto mode! Thus, my powerhead was now recognized a light (with a default on/off schedule, etc). This could have been disasterous depending on what got assigned to what. There was no clear way to fix the problem, so I went through and copied the old code and settings to the new module addresses. A real pain. It was just lucky I noticed.
Clearly this is not entirely unusual behavior. As these posts show, others have had the same issue:
- https://www.reef2reef.com/threads/apex-modules-change-address-after-power-interuptions.1001137/
- https://www.reef2reef.com/threads/my-apex-tried-to-crash-my-tank.1028540/
- https://www.reef2reef.com/threads/apes-modules-missing-after-turning-some-power-off.1043521/
It appears that Neptune is finally addressing this issue. Product support let me know that there is a new "Module Replacement" task that you can use to assign the old device to its original address (assuming you haven't deleted it). Still a pain, but better. Now you don't have to copy all your stuff around and hope you set the settings right. Doesn't work for all modules and addresses but fixes some things.
Clearly the device shouldn't be doing this in the first place. The best data I have on this at the moment is the best practice that many have noted on this forum: Use a battery backup with the brain so it never power cycles. Clearly this won't work in all cases (like my case above), but it can help prevent spurious nightmares.
I'm still waiting for Neptune product support to let me know how to avoid this in the first place. I'll post when I find out. Love to hear if others already know how to avoid the problem.
