SpencerShepard Posted May 28, 2014 Share Posted May 28, 2014 If you are having any issues, please contact me: sales[at]blueworldaquariums.com-Android app v1.6 timezone issue: Currently the timezone is set automatically during BlinkUp. If the timezone is not set correctly on your device, or possibly because of DST settings, this value can be wrong. You should set it manually to be sure. For now, you can change this under Extras>Sandbox. This menu is beta only and needs to be unlocked. I have been unlocking it for new registrations, but if you don't see it, please try logging out/in, and contact me with your username if it's not there. In the next app version this setting will live in the normal settings menu and be a required part of the BlinkUp process. Fixed in Android app v1.07 -iOS app location bug: Setting your simulated location to a place without weather data will cause the app to crash on login. This should only happen if you try to set a really obscure location. If you set a location, and it doesn't immediately return data, change it back. You can recover by logging in with an Android device and changing the location or contacting me. This is fixed in v1.06 (not yet released). Patched in automatic firmware update.-Server connection hang: Not yet verified, but code on our server may render it unresponsive until rebooting your unit. This would be a coding problem on our end, and not an issue with your unit (the hardware should never require a reboot as the wifi connection and processor will reboot automatically when needed). The controller would continue to run normally, but you would not be able to connect with the app. If you need to reboot your unit to re-establish connection, please email me with your username and the time/date when you needed to do this. This should be fixed now, but it is difficult to test, as the cause of the problem is rare (EI making changes to their servers that cause no downtime, but restarts our server code). The controller should never require a reboot to re-establish connectivity...if this happens I need to know. -Natural sun inaccuracy: The Natural Sun feature produces a bell curve output. Right now the formula needs improvement. The degree of inaccuracy varies depending on start/end times, but they could be off by up to an hour. A new formula has been developed that will make it into the next firmware update (3.5). -iOS blank text fields will cause app-crash on login. Channel names, webcam url, etc must not be left blank, or you will see the issue next login. This will be fixed next firmware update (3.5). If you accidentally do this, please email me with your username and I will correct your settings. Fixed in iOS app v.1.06CHANGELOG:May 30,2014 (Firmware 3.3):-Patched iOS app location bug May 31,2014 (Firmware 3.4):-Fixed server bug causing unresponsiveness after updates-Fixed bug causing inaccuracy with night start time using Natural Sun and Minimum Dimming (was keeping light on longer than expected). Still some minor inaccuracy with certain day lengths...working on improving the formula to work with a larger range of settings. -Reduced QuickTime/FastForward speed by half (will probably make this adjustable in future app versions) August 23, 2014 (Android app 1.07): -Added persistent login checkbox -Set time zone moved to system settings -Set time zone manually on blink up -Improved accuracy and ease of use in settings sliders (hold for more than three seconds and accuracy increases) -Option to blink up on connection error (rather than automatic direction to blink up) November 22, 2014 (iOS app 1.06): New Features: -Instant bug reporting and feedback-Simulated location forecast-User Guide-Increased slider accuracy-Persistent login New Features (**available with firmware version 4.0+): -Light Graph visualization-System Status-Light Preview option while adjusting settingsBug fixes: -Crashing on login due to blank text fields-Display Colors not saving on some devices-Lunar Cycles button not populating -Option to blinkup on failed connection (ie. after WiFi change) Link to comment
This topic is now archived and is closed to further replies.