Neptune Apex sometimes changes module addresses after power outage

[Zinda]

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.

 

[ca1ore]

As you note, this has been true for a long time. Happened to me back when I first got the A2 in 2017-ish - head unit does not like to lose power ...... so don't let it! My solution also was to buy the external power supply and an UPS. OK, it's not unreasonable to assume Neptune should have made the Apex less susceptible to wonky behavior after a power loss, but apparently, they have not.

 

[Zinda]

so don't let it! My solution also was to buy the external power supply and an UPS

I do have it hooked up to a UPS but I had to power cycle it to get it to connect to WIFI again.

it's not unreasonable to assume Neptune should have made the Apex less susceptible to wonky behavior after a power loss, but apparently, they have not

And I'd say this much more strongly: it is *unacceptable* that modules can get reassigned after a power failure. Of course giant power spikes might fry machines (but I'd hope they've accounted for a lot of that too), but normal power cycling should *never* reassign modules!

 

[Luisn17]

Hello,

Stuck in the same issue. I woke up and noticed one of the flow pump was off. I could not connect to the apex via my phone so I disconnected one of the usb cables and bam chaos! I hear my RODI and RODI pump turn on, two of my lights turn off among other stuff. I could not figure out what was going on until I see the 6 new modules. Will be calling Neptune later today and see if they can guide me thru the replacement steps. I don’t want to spend hours reprogramming everything. What a total mess.

 

[Luisn17]

Hello,

Stuck in the same issue. I woke up and noticed one of the flow pump was off. I could not connect to the apex via my phone so I disconnected one of the usb cables and bam chaos! I hear my RODI and RODI pump turn on, two of my lights turn off among other stuff. I could not figure out what was going on until I see the 6 new modules. Will be calling Neptune later today and see if they can guide me thru the replacement steps. I don’t want to spend hours reprogramming everything. What a total mess.

In case anyone finds this post, after contacting neptune they did guide me on how to do a module replacement via the task menu. It was fairly simple and straightforward once I identified the old and new modules. I must had some sort of power flicker since they could not find a reason and everything is back to normal. I probably need a power back up of some sort to prevent this from happening again.

 

[Zinda]

Lucky it didn't happen until you were there! Having a battery backup seems to be the only real solution here based on my support call too (along with Module replacement task for the immediate problem). Hopefully the battery doesn't run out while you are not around.