Update the app, then the firmware, then the default modes, then the custom mode.
There are some malfunctions with the app, which we’re working to fix. Part of the malfunction is already fixed and the new version is going to be available in a few minutes with some things fixed.
The online features remain dysfunctional for the time being, we hope to have them straightened out by the end of the week.
Remember this is an opt-in alpha release channel. We’re bound to see many fast updates and instability. Do opt out if you need everything working perfectly all the time.
@ SytRep Yes, we are apparently facing exactly the same pb.
I did in this order: update the app, then the firmware, then the default modes, then the custom mode (empty in my case).
As for you, the firmware update makes the app crash instantly. I have sent the crash report.
@iajrz Great, I can probably test the new release today if not too late for French time.
Hi @iajrz,
Unfortunately the same problem as with the previous app version:the app is consistently crashing when trying to update the firmware …
I sent a crash report.
Yes, same problem for me as well.
By the way, how to know the current version of the firmware in the MM (e.g. boot while pressing a button)? With the crash, I actually don’t know if the previous firmware is kept, corrupted or partially replaced.
Currently all top 3 screens show: EEPROM INVALID.
The unit is no more usable for now, but that’s ok for me, that’s part of the beta testing interest
Thank you for sending the report, we’re working on it. It seems to only show up in some Android devices - it’s because of the way we’re trying to download the firmware, which isn’t tasteful for some devices.
It’s under development, at a pace slower than the Android app. We hope to submit it to the Apple Store during June, although it may not have all the capacities this version of the app has.
Once approved we’ll accelerate its development to catch up with the Android release.
OTOH, @Imagine, you already updated the firmware, that’s why you have EEPROM INVALID. Now you need to update the default modes (button is next to the firmware update in the menu).
That is good news, I have apple gear, phone and iPad so I am not interested in buying an Android device. Has any consideration been given to writing a Mac/PC application using the Bluetooth interface. C# .net has libraries that support Bluetooth.
Yes, still crashing for me as well. I have sent the report. @iajrz One apparent change is that the “Update default modes” now says “Update the firmware first” instead of going through with the update.
Sorry for the time it’s taken us to get back to you. We couldn’t isolate the issue, so we spent some time improving the error reporting capabilities of the app. We’ll release a version of the app today with the sole purpose of getter better feedback on what’s happening on your devices.
We’ve not been able to reproduce the issue in any of ours, so we need you to go through it again sorry.
Hopefully this will allow us to have even faster turnaround time.
sorry.