MOBIUS APP TIMEOUT CONNECTION.????

[exnisstech]

I'm back up and running

Lucky you

 

[xCROv]

It's a shame almost all of these companies want to force you into a cloud only solution. Hydros has a similar issue and if their servers were to go down, all their devices would turn into bricks. Not sure if they plan on fixing the issue since it's been brought up a few times and they never acknowledge it as a problem.

 

[redseaenroute]

Not trying to derail from the underlying issue here... But this just solidifies my decision to buy the remote control ONLY version of my reefbreeder lights. The thought of them being inop during cloud based issues was enough for me to stay local control only. I'm leaning this way for all equipment now. If it has single point of control via app/cloud.... I'm out

 

[SpyC]

It's a shame almost all of these companies want to force you into a cloud only solution. Hydros has a similar issue and if their servers were to go down, all their devices would turn into bricks. Not sure if they plan on fixing the issue since it's been brought up a few times and they never acknowledge it as a problem.

The programming also isn't stored locally? I was under the impression it was

 

[brettdyer80]

Ecotech response

I had the exact same response from my second email..! That's almost a hush up and get on with comment from Ecotech..! Ok I'm a realist and appreciate technology goes wild at times, but this is crap considering the amount we fork out for their products.. I'm seriously debating a return to RedSea lighting. Lol

 

[Hreef]

I can log in but Lighting is not loading, The other devices are but not Lighting.

 

[Cristy17]

#COMPENSATION

Right! Good luck!

 

[Cristy17]

Still having this same issue here. I have also occasionally noticed my two lights being out of sync from each other.

That happened to me, just unplug the one that is not syncing and it should reset and join the other light.

 

[exnisstech]

Deleted.

 

[David Gaskins]

Shoot id take twice a week. This past week for me has been better, but prior weeks, when i get home from work ill have to update the time, sometimes numerous times a day and every day at that. There app is garbage.

Of course, when i contact support i get no response.

Same here. I have a pair and I have to reset the time at least once a week. If time is off, one of my Versa pumps set up to dose 6ml of ARF won't dose at all until I reset time. Crap shoot of a device design. And don't get me started on the lack of integration (after adding Mobius) to Apex. I'd prefer this to be a device completely free of BT control. I understand the issue with Amazon Cloud Services was culprit, but this isn't streaming Netflix Dorthy, we've got livestock to worry about!

 

[xCROv]

The programming also isn't stored locally? I was under the impression it was

You can't use the app at all locally if you don't have internet. It's the same issue that Mobius just experienced. CoralVue just locked a post about it on their facebook group so I guess no one is allowed to talk about it lol.

 

[Sisterlimonpot]

The programming also isn't stored locally? I was under the impression it was

I started distancing myself from clarifying information that should be published for all to view by ecotech.

But I do want to clarify, that each device attached to mobius does store the data that you program into it. Whether it's a lighting schedule, dosing times and amounts, pump speed and modes, etc., those are stored on their respective devices.

Which means that even though some people experienced a connection issue based on a server problem. The mobuis connected devices will continue to run their normal schedule.

The reason why having cloud service go down is such a big concern is because some people rely on that connectivity to make changes or even simply to check the box after refilling a dosing container. Even certain circumstances where you set the flow of a pump the day before and realize today that it's too much flow.

Not to mention all the issues mobius is plagued with requiring people to routinely connect just to correct the drifting clock.

 

[SpyC]

You can't use the app at all locally if you don't have internet. It's the same issue that Mobius just experienced. CoralVue just locked a post about it on their facebook group so I guess no one is allowed to talk about it lol.

But the programming for the hydros is still on the units though, right? Saying the device is a brick means it is no longer functioning at all.

 

[BeanAnimal]

But the programming for the hydros is still on the units though, right? Saying the device is a brick means it is no longer functioning at all.

I would assume so, yes. If not, then they have no business being in the controller business.

 

[BeanAnimal]

HYDROS:

LOL - that has to be one of the silliest things I have ever read. I wouldn't touch a hydros controller with a 10 foot pole with logic like that. Now it makes sense that every device has a random name that doesn't follow a convention. They must have clowns making decisions.

 

[SpyC]

HYDROS:

LOL - that has to be one of the silliest things I have ever read. I wouldn't touch a hydros controller with a 10 foot pole with logic like that. Now it makes sense that every device has a random name that doesn't follow a convention. They must have clowns making decisions.

That is horrible logic. I wish I had known about that 'logic' before spending $800 to switch from apex to hydros. I'm going to have to test this out a bit. Seems like every popular option that you can easily find parts for has issues.

 

[xCROv]

But the programming for the hydros is still on the units though, right? Saying the device is a brick means it is no longer functioning at all.

The devices will function with whatever they were doing for the current schedule but will eventually start rebooting on a 1-2 minute loop when they fail to get a connection from the server. This was brought to my attention via a support ticket and was honestly shocked that this was the solution. It means that if CoralVue ever has an extended outage period, or goes out of business, within 30 days (certification expiring time that ultimately causes the yellow breathing lights) all these devices are toast and people will be holding a big bag of useless bricks. When it enters this "reboot loop mode" with flashing yellow led's, it will constantly reboot all of your equipment plugged into it as well and restart any schedules. It caused so many issues with my tank that I almost ripped it all out in frustration before eventually finding a solution. While you wait on that though, you can't even put your tank in feed mode and the only way to shut equipment down is to physically unplug things. I honestly feel like none of this equipment has been tested in a "worst case" failure kind of scenario and it's just waiting to drop on everyone. Those kind of scenarios always come as such a shock to people that think "this will never happen to me" which is the vibes I get from CoralVue currently.

The issue has been frustrating reporting to CoralVue because they refused to acknowledge that it is an issue and anyone who brings it up quickly get's their threads locked on their facebook group. I've looked into parameter monitoring for some of the open source platforms and eventually want to move to one of those given that CoralVue has no interest in some of the things the community has brought up like this and an actual API integration.

 

[BeanAnimal]

The devices will function with whatever they were doing for the current schedule but will eventually start rebooting on a 1-2 minute loop when they fail to get a connection from the server. This was brought to my attention via a support ticket and was honestly shocked that this was the solution.

If actually true, this is absolutely insane... just insane.

Can anybody else confirm this is the case? Do all Hydros devices reboot if they can't communicate to the Hydros hosted services?

There is not ANY valid reason for logic like this given the context of what these controllers are responsible for. If it is truly the case [the cyclical reboots, restarting timers, etc.] -- product decisions are being poorly made.

Somebody please tell me there is a misunderstanding here and these devices do not behave like this by design!

The issue has been frustrating reporting to CoralVue because they refused to acknowledge that it is an issue and anyone who brings it up quickly get's their threads locked on their facebook group.

If this is actually confirmed I would run away from this product and these people as fast as I can.

Edit: reworded a bit… how can we confirm if this is happening and by design?

 

[BeanAnimal]

It means that if CoralVue ever has an extended outage period, or goes out of business, within 30 days (certification expiring time that ultimately causes the yellow breathing lights) all these devices are toast

Explain please - is there direct language indicating that the devices will be disabled if they don't check in for 30 days?

The devices will function with whatever they were doing for the current schedule but will eventually start rebooting on a 1-2 minute loop when they fail to get a connection from the server. This was brought to my attention via a support ticket

Can you please indicate the ticket and exactly what was said? Not that I don't trust you, but there are people saying that this is not true and others that are saying it is.

 

[Sisterlimonpot]

The issue has been frustrating reporting to CoralVue because they refused to acknowledge that it is an issue and anyone who brings it up quickly get's their threads locked on their facebook group.

This is what irks me the most. I don't understand why companies can't face things like this publicly and either explain the reasoning or vow to make it right... the constant hiding from it only forces people to shine a light on it and creates advisories.