droid app for apex?

Oh, and the Aquanotes app for iOS isn't that much better, it just simply has a cleaner looking UI, but functions are very basic as well. FYI
 
I have my Apex set up where it's accessible through my home wireless IP address, but when trying to use the Android app I just get "Error: HTTP connection failed." I'm using dyndns.com as my host and having issues with that as well, so don't know if they are connected or not.

That's the same problem I was having, just like Henery has said log into the your controller from an outside computer (your phone while using 3G) (http:// your unique name.dyndns.info:your port number) the bold lettering is going to be what you set up through the dyndns.com website and your port number is what you set up in your router for "port forwarding".

once you have that then you know that everything is working right and you should be able to use the app.

My problem was that I didn't have the latest firmware loaded on my controller which made it impossible to use the app.
 
It is a great app. Now that I use it on a daily basis and got familiar with it I'm looking forward to some updates that he discribed in the post above.
 
Just wanted to throw in a little info on this. I installed this app, and it worked great from the get go. Most of the complications are from people the user side (us). Not putting in the right info, not changing the password, etc.

That said, i updated my firmware to the latest the other day, and the app stopped working. It would force close after any outlet change, etc. The fix was very easy for me. I just went into the app, and "cleared data". Pointed the app back to my APEX, and all was well again.

Hopefully this will help someone else that ran into this same issue.
 
Henry, thanks for the free app. I am purchasing an Apex pretty soon and am glad to have this app for my Samsung Vibrant.
 
Why am I getting "Error: XML Parser failed." ??

The widget is updating and everything, but I can not controll anything.

Joe
 
Ok...let me level with you. I do NOT have an Apex....but I do have an ACIII. This widget will display my temp, pH and ORP values....Thank you so much! It is GREAT to have this live on my phone!

any chance we could get an outlet status widget for the ACIII?
 
Why am I getting "Error: XML Parser failed." ??

The widget is updating and everything, but I can not controll anything.

Joe

I'm having the exact same problem.
 
Last edited:
It was just a screen real estate question during the design process. I created three sizes of widgets; 1x1 with no parameters just a quick-launch to full screen, 2x1 that can fit something like four parameters and a 2x2 that can fit something like 10 parameters. I am really working from old memory on this.

Someone could easily modify it to add outlets on the widget!

Who is that someone is the key info :)

Somewhere around here I had a suggested new feature list. Outlet status on the widget and taller widgets would have to be prioritized by that magic person taking this on.

ACiii and Apex are indistinguishable for 99% of this functionality.
 
Ok...let me level with you. I do NOT have an Apex....but I do have an ACIII. This widget will display my temp, pH and ORP values....Thank you so much! It is GREAT to have this live on my phone!

any chance we could get an outlet status widget for the ACIII?

I have an ACIII and I can view all my outputs.

EDIT* I didn't notice a page 3......
 
I'm having the exact same problem.

xml parse errors mean that the app is not recognising the response from the controller. IM me to debug the problem.

sorry for the haphazard responses. trying to work from my android phone whie on business travel and getting mixed up with multiple threads and pages.
 
I sent all of the source code to a CompSci student who was going to work the bugs and add features as part of a class project. Haven't heard from him in a couple of days though.

Current Bug List:
  • Certain characters in outlet names cause problems: Encode the URI segments used for database access so that if the user has an outlet name with a slash, dash, asterisk, etc it does not cause errors. The problems come from two areas; 1) any character that could mess us the URI string. Format is something like content://segment/segment/segment and there could be chars that impact URI matching or 2) any characters that mess up the final SQL string that does the insert/updates.
  • Profiles Status on Outlets Not supported: Code currently only expects AON, AOFF, ON or OFF for outlet status. Now that people are using LEDs more and ramp profiles there are more instances of PF1 that cause problems.
  • Force-Close if Refresh during Update: Disable 'update' during a current update. This causes a force-close.
  • Update Widget Data: When user manually updates data via the full app, it does not push the new data to the widget.
  • Rotating the screen causes a refresh. Annoying but not a critical failure.
In my opinion the first two bugs are very significant especially the second.

And a couple of important enhancements:

  • Do a daily update that pulls history data at the full 5-minute resolution rather than rely on the x interval polling. Also during this daily job do some database cleanup/purging according to the preferences setting.

Then the wish list items:
  • User settable background image
  • Manual parameters such as alk/ca/etc
  • Notes
  • Export xml data via email
  • Inhabitants database with pics.

Here are the screen-shots of the app:
widget.jpg


app_1.jpg


app_2.jpg


prefs.jpg


Apex_graphs_ph.jpg
 
Spidey has the source code now, you should provide him the same encouragement you all gave me. I got by a years worth of hard coding on all of your support. Once he gets familiar with the code I'm sure great things will come.

Keep motivated Spidey :-)

I look forward to new updates like everyone else!
 
I am starting to identify to source of the bugs. I have found some.

If the community could help me out by letting me know of any more errors or bugs that you have found. And how you got them.

Also let me know what you would like to see as additions.
 
Back
Top