Reef Angel Forum

Thanks so much @rimai

Teamviewed and things seem much better now, will keep you posted

ahmedess wrote:ok done the update now its version 2.32 do you think I should reset the module or should i test it without resetting cause it seems that the wifi settings were not affected by the update process so it seems there is no reason to reset it

How long did it take to update? I've been "Downloading latest firmware image" for about 45 min. I restarted it, but still taking its time.

It takes just a few seconds, but I think the manufacturer's server is down.
I contacted them, but they have not responded yet.

Besides the firmware update, my WiFi is working again! The main thing I wanted to check were the WiFi settings, but with a broken comp is a little hard. Turns out my router had changed to port 1006. I haven't been messing with the settings, can someone hack into my router using the RA connection?

Sent from my Xoom using Tapatalk 2

no. not possible.

My wifi is still a problem. I have the latest firmware, used the wifi app to set it up, work for a while and the doesn't

http://forum.reefangel.com/viewtopic.php?f=7&t=1272
I released new libraries yesterday.
Can you download the new installer and see if that solves it?

My wifi has lost its settings again

First it lost power even though it was connected, then when I unplugged it and replugged it, it started flashing blue again

Hi.

My wifi also looses it settings

Hey Jean,
Does it loose settings or just loose connection?
Does it give you blue bliking led?

Hi Roberto.

It looses connection first, and the after a while (week or so) the dreaded blue blinking led

JNieuwenhuizen wrote:Hi Roberto.

It looses connection first, and the after a while (week or so) the dreaded blue blinking led

same with me, I still need to reflow the board though

My wifi module stops responding too: I need to un-plug and plug to restart, it stops every day. V 2.32, GW configured.

I have the same issue with my WiFi. I deleted my other thread. I hadn't spotted this one

I'm not sure if this will help but I get this error popping up when validating the WiFi settings.

"<h1>Bad Request (Invalid Verb)</h1>GET /r99 HTTP/1.1"

update: Resetting the wifi back to factory defaults 2 or 3 times and reloading has got me back to the URL working (http://<ip address>/wifi as well as the Client Suite. Now I get the "parsing" error through the Android app.

ishtak wrote:update: Resetting the wifi back to factory defaults 2 or 3 times and reloading has got me back to the URL working (http://<ip address>/wifi as well as the Client Suite. Now I get the "parsing" error through the Android app.

If you are getting a "parsing" error with the app, there can be a couple things going wrong. The most likely issue is a bug in the app which is fixed and almost ready to be updated (hopefully today or tomorrow). The current version of the android app is 0.6.0 and the new version will most likely be 0.6.1. Make sure you update to the latest when it is released and that should fix your problem. If it doesn't, start a new thread and we can figure it out.

Awesome news! Thanks Curt ... I'm having with drawl symptoms not being able to check my tank on my phone every 5 minutes

ishtak wrote:Awesome news! Thanks Curt ... I'm having with drawl symptoms not being able to check my tank on my phone every 5 minutes

Sometime in the future, you won't have to manually check your tank on your phone....your phone will do it automatically for you. That simply means that I'm going to be adding an "auto update" feature to the app and widget(s) to display on the home screen.

If you look here: https://github.com/curtbinder/AndroidSt ... state=open
You will find all the improvements and features I've got in the works for the app. If you would like a feature that's not listed there, feel free to suggest it.

JNieuwenhuizen wrote:Hi Roberto.

It looses connection first, and the after a while (week or so) the dreaded blue blinking led

This happened to me for the first time two days ago. I plugged the module into my laptop and reconfigured it. Everything seems ok now, except the portal will not update for some reason. The last entry on the portal is Monday night, presumably when the blue LEDs started blinking.

Here is what the manufacturer responded:

Hello Roberto,

We have observer this bug and addressed it in ver 2.35 of firmware.

Please upgrade the module to ver 2.35 using:

set ftp address 208.109.14.133
save
ftp update wifly-235.img

Can you try this solution and see if this solves the issue?

rimai wrote:Here is what the manufacturer responded:

Hello Roberto,

We have observer this bug and addressed it in ver 2.35 of firmware.

Please upgrade the module to ver 2.35 using:

set ftp address 208.109.14.133
save
ftp update wifly-235.img

Can you try this solution and see if this solves the issue?

Just to record if the issue comes up again, I now applied the update. I will post here if the blue lights start again.

Just got the courage to try a firmware update and now my WiFi WORKS!

Roberto/Curt,

Is there a manual for commands to the wifi module? My unit still freezes up randomly so I was thinking oerhaps there is a way to code the unit to autiamically reboot itself once a day at say 3am or something? I'm also wanting to know how to code the unit to use a static ip address rather than DHCP. I've noticed every now and then it swops over to a different ip on my network.

Justin

Roberto gave me this link http://forum.reefangel.com/viewtopic.php?p=10947#p10947 to do exactly that. Unfortunately didnt work work for me, but try it anyway. might work for you

Thanks Toolboy. I'll try that when I get home tonight and give feedback I'll also setup a ping monitor to see if the timeouts are working correctly.

I'm still working with the manufacturer to check why this issue is still being persistent.
They asked me for the "get e" dump. If anyone can provide it to me, I'd appreciate.
Also, someone mentioned that the unit performs accordingly if you disable outbound communication and only allow inbound and I'd like to see if this also works for anyone else.
He simply changed the remote host to 0.0.0.0, which simply tells the unit to not send any data to reefangel.com.
The Portal will stop receiving data and you will not have historical web chart and relay activity, but you will still be able to connect using smart phone or portal to check parameters and control relays, just as you were doing before.
Is there a way you can test this option too??
The more information we can give the manufacturer, the better.

Roberto,

I pm'd you my "get e" dump. I'll test changing my unit to static from DHCP. See if that makes any difference.

Justin

An update.

My WIFI has been perfect since I changed the ip config to static rather than DHCP. I'll swop it back over to DHCP today and see if it starts it's nonsense again.

I was unable to connect to the wifi module again today so as i usually do decided to unplug it and replug it back to the controller to make it work but when i connected it again it starting blinking blue and lost its settings, first time to happen.

I was running version 2.32 and i just updated to version 2.35 now and reconnected it to the controller. I will test this update and will let you know if it times out again.

About setting the host to 0.0.0.0, I did try that and I think the module worked better but i m not 100% sure that was the reason. I currently am using the portal so I changed the host to reefangel.com maybe thats why the module is timing out again.

The thing is that the module could work fine after I change something in the settings for a week or two and then it starts timing out again all of a sudden. Could it be wifi interference?

I will test the firmware update I just did to see if it fixes the problem if not then i will change the host to 0.0.0.0 and confirm if that fixed it or not.

I just discovered something new hope it helps figuring out why the connection times out with the wifi module. When I try to connect to the controller using my LAN IP address the connection times out but at the same moment when i try to connect to the controller using my WAN IP address it connects. I just cant figure out why this is happening.