Reef Angel Forum

THANK YOU!!!!!!!!!!!!!

I reprogrammed the controller, why does it think I am still running an expansion relay?

You have to remove all references to the second relay box. Commenting out isn't good enough

I see that the additional Water Level sensors have been added to the Portal and to the Andriod app.
On the Portal it displays my 1 WL sensor correctly, but on the Android App it comes up as Water Level 4 and it's not picking up the label from the Portal when I told it to.

It looks like the android app is taking the last wl ...try renaming wl4...

Just curious of thats what its doing...

That's what I thought too, but the data of 34% is the correct amount for the single WL.

There is a "crossed wire" somewhere.

When I changed the label for Water Level 4 in the Portal it shows up in the app correctly, but with data from the single WL sensor.

Yea i dont think the android app is supporting it right

Yeah, something's not right. I'm sure it's a simple programming error that Curt will figure out.

Sent from my HTC One VX using Tapatalk

I will have to look at it. I think I know the answer and it has to do with what was said about the water levels. the data will match only the first one and the labels will take the last water level tag. I know i have not accounted for the multiple water level sensor in the app. I guess now I will.

Sent from my Nexus 7

Thanks Curt.

I know you'll figure it out.

Sent from my HTC One VX using Tapatalk

i looked at the xml code processing and its doing exactly what i thought it was. im going to try to get that fixed up for the names for the water levels. i wont have the multi channel water level added in yet though....sorry.

and, i have a fix for the data retrieval and hopefully a fix once and for all to that blasted SAX parser error. its preliminarily been tested and shown to work well by myself and another. still doing some further testing before releasing but it is looking very promising. this will be nice because i get sick of the error and tracking it down has been a pain.


Sent from my iPad mini

Steve,

Where are you finding these additional water level sensors? I just installed my multi channel expansion and do not see anywhere to select additional water levels?

The Andriod app is not showing all 5 channels of WL sensors.
It is showing the 1 channel that I have, but it is labeled as Water Level 4.



The Web Portal does show all 5 channels of the WL sensor.

Hmmm, my app is trying to read it as if I still have just the single channel expansion (which I have removed to use on a different tank) so it keeps thinking my water level is 0. Which is annoying because I have an alert programmed to tell me when my water level is low.

I just found out about the portal tonight so I'm a complete newb with using that and don't see any of those statuses on it. Although from I might need to add the appropriate code to my reef angel for that. Which I have possibly talked myself into the solution...

Nope. Still don't see the water levels in portal.

If I read Binders post correctly from the previous page, he hasn't added support for the multi channel WL sensor to the Android App yet.

As far as the portalvi think it just showed up one day. I don't remember doing anything for it.

I don't even have the multi channel sensor niw, so why would I look to turn it on.

Sent from my HTC One VX using Tapatalk

you are correct. the multi channel water level is not supported yet. currently, the last label for the water level devices gets used as the label for the water level display. i have to fix the code to make it function properly. i have not had time to do that yet.

Ah. Thought maybe you had a secret I couldn't figure out. Thanks for the responses though.
Curt, fantastic app all around don't think I could live without it. Hopefully you'll get that working in the near future.

Hey Curt,

What are the chances of a widget? It would be awesome if we could have a widget that displays the Controller Data labels that we have selected to view within the App. Not necessarily relay/dimming information.

ReEfnWrX wrote:Hey Curt,

What are the chances of a widget? It would be awesome if we could have a widget that displays the Controller Data labels that we have selected to view within the App. Not necessarily relay/dimming information.

I had considered that and have enabled functionality for a widget to be created. I didn't have much success with the drawing and displaying of it when I looked at things a year or so ago. I had a hard time with the way things were laid out on the screen. I know I originally wanted to do something like the web banners but never got much farther into it. I can try to take a look at it more. Thanks for the request

I had a day off today and decided I would spend some time getting some features added to the app. I've got a release candidate that I plan on releasing either tomorrow or Sunday.
For those that want to give it a try, here's the link to it:
http://curtbinder.info/apps/AndroidStatus-0.9.4.RC1.apk
And for fun, I created a QR Code for quick access from your phone. Like always, it will install over the top of your existing version and will be upgraded by the play store when the official version is released.

Highlights of this release:

• improved XML downloading
• added 4 channel water level displaying
• allow portal to be chosen from first run screen
• removed Commands option from overflow menu, changed to Date/Time
• added calibration buttons to command page (ph, phe, salinity, orp, water level)
• get software version is added to the Commands Page
• added humidity expansion

I have not fully tested everything since I don't have a humidity expansion or a 4 channel water level expansion. The only thing that might not work as expected is the automatic updating of the modules based on what the controller reports. I just say that because I haven't tested it. However, it most likely should work just fine because of how it is coded.
All of your data should be preserved (ie, your history, errors, notifications, etc). They were preserved on my phone when I just installed it.

The look of the app is still the same as it has been. I have not completed the new layout/look yet. I put that on the back burner to try to get more functionality added. As always, feedback is welcome.
If you don't install this version, just wait for the update in a couple days.

Awesome!!
I'm testing it.
When is that the app updates the active modules? Every refresh or startup?
The reason I ask is because I'm trying to make the main screen change it based on the controller, but it seems that the visibility has priority over the EM bits.

rimai wrote:Awesome!!
I'm testing it.
When is that the app updates the active modules? Every refresh or startup?
The reason I ask is because I'm trying to make the main screen change it based on the controller, but it seems that the visibility has priority over the EM bits.

On every refresh, the app checks the current EM bits against the old EM bits. If they differ, it will update the modules only if you have "auto update modules" enabled.

If you change the visibility manually, the modules will not get reset until the EM bits change.

Hmm...thinking about this now, I may want/have to rethink this process a little. The only time you would notice things changing is if you switched to a different controller and then back to the original one or if you added on a new module or took a module off of your controller and updated.

It's not working then.
I had auto-update on and it didn't update the screen.
Then, I went and manually set visibility and they showed up and updated just fine. So the values display the correct value and everything works, except for the auto update.
As a test, I went ahead and uncheck ORP on the visibility. The screen changed and got the ORP out of the main screen, but when I refreshed, it did not bring it back up. This is all with the auto-update on.

rimai wrote:It's not working then.
I had auto-update on and it didn't update the screen.
Then, I went and manually set visibility and they showed up and updated just fine. So the values display the correct value and everything works, except for the auto update.
As a test, I went ahead and uncheck ORP on the visibility. The screen changed and got the ORP out of the main screen, but when I refreshed, it did not bring it back up. This is all with the auto-update on.

Ok. It may be working though. If your controller has not had any modules or code update and you had been communicating with it from the phone previously, the values would have been saved so no changes would be necessary. After my last comment, I started thinking more about the process and I think this is how I need to handle the the auto update functionality.

At each refresh, compare what modules are visible or not, update the visible modules based on what the controller says but only if "auto update modules" is selected.

currently, the only time the auto update modules changes anything is if the EM bits get changed. this would only happen if the controller was reprogrammed. this will also override any of the visibility settings because the EM bit check is done after the other visibility displaying is handled. in this update, i only added in the EM1 bits. the EM bits logic has not been changed.
so i think i will have to add in another level of updating and improve it more.

Ahh. Makes sense now.
I just added a new issue to the github tracking
It would be nice to have dimming override implemented

I just installed it and you have fixed the issue with the Water Level Sensors that I reported. Thanks, I don' see anything else going on. I looks good.

What does "allow portal to be chosen from first run screen" mean?

Also the Get Version button on the Commands page returns 1.1.0.

Sacohen wrote:I just installed it and you have fixed the issue with the Water Level Sensors that I reported. Thanks, I don' see anything else going on. I looks good.

Great.

What does "allow portal to be chosen from first run screen" mean?

When you first install the app, it won't let you proceed and use it unless you configure it. Originally, you had to input your controller address in order to start the app. There was never a way for you to choose the portal initially. You had to set your host, then goto the settings and change to Portal to get the app to pull the data from the portal. So now, if you only wanted to pull the data from the portal, you have that option from the first run screen / initial app setup.

Also the Get Version button on the Commands page returns 1.1.0.

yeah, when you click on the Get Version button, it just changes the text of the button to be the version of the controller software. i didn't know where to put the Version of the controller, so i figured i would experiment with putting it there and changing the button text.

rimai wrote:Ahh. Makes sense now.
I just added a new issue to the github tracking
It would be nice to have dimming override implemented

The dimming override functionality is slightly more complicated than what i originally thought, however it will be added. i wanted to try to get some of the "easy" things taken care of first.

What does "allow portal to be chosen from first run screen" mean?

When you first install the app, it won't let you proceed and use it unless you configure it. Originally, you had to input your controller address in order to start the app. There was never a way for you to choose the portal initially. You had to set your host, then goto the settings and change to Portal to get the app to pull the data from the portal. So now, if you only wanted to pull the data from the portal, you have that option from the first run screen / initial app setup.

OK. So That's really for new installs. Wouldn't effect me.

Also the Get Version button on the Commands page returns 1.1.0.

yeah, when you click on the Get Version button, it just changes the text of the button to be the version of the controller software. i didn't know where to put the Version of the controller, so i figured i would experiment with putting it there and changing the button text.[/quote]

I like the button changing to text, but I thought it was going to be a quick way to get to the version of the app.

Sacohen wrote:I like the button changing to text, but I thought it was going to be a quick way to get to the version of the app.

Ahh...I follow you. Should I change the text/wording of the button to be something for the "Controller Version" or "Get RA Version"?