Hi @Ioana,
Just installed the beta. Problem with scene action getting wiped on setting a geofence trigger is not solved.
Update. It is even worse. I testen with android 9 and 10, two user ids, two controllers, with same results. Creating and editing scenes is completely broke. Both the trigger and action are not stored.
After waiting two days without beta v.369 pushing to my Android device, I went ahead and uninstalled v.360, then installed anew from Google Play Store.
Shocking, I must say, to notice that only 7 of the 38 reviews for VeraMobile posted during 2020 gave it more than 1 star. I meanā¦ yikes!
Having finally obtained v.369, I logged into my Edge controller to look for an āAmazon Alexaā device under āDevicesā but found none. So I once again went through the āezlo VOIā linking process, which indicated success (as it had the previous 5-6 times I tried that in .360), yet still I have nothing listed under āDevicesā.
This is on a fresh Edge newly updated to the Linux firmware (1.0.16) this morning, with no other devices or modifications. Running Android 9 in Lineage OS nightly (3/22 latest) on a rooted OnePlus One device.
ā¦is VERY difficult to use, because itās (a) NOT alphabetical, (b) NOT organized by GMT +/- offset, and (c) NOT arranged by continent/country, either.
Just a seemingly random smattering of every possible Time Zone in the known world ā an exceptionally long list, including many Iāve never seen before (and I consider myself a bit of an expert!), ā with the expectation that users will spend 10 minutes scrolling through it.
The geofence data I moved from my Plus to an Edge also got corrupted. I suspect the current production version of the app causes this. With the data corrupted the beta app shows the same issues as the production version. The new style dashboard is not loaded. The devices are not listed by room. Trying to do anything results in a spinning wheel.
IMO this scenario must be addressed. Alternative is that your support team must correct the user_data.json of all people that are experiencing this geofence data corruption.
I now a bit of log file showing proof that the Geofencing in the app corrupts the user_data.json. At this moment some Enter and Exit events even crash the Luup Engine. This happens when the app sends a quoted Enter or Exit value in the action. I guess in some cases the quoted value does make it in the user_data.json and then makes the controller inaccessible via the app.
Thank you again @reneboer for all the help youāre providing. The team is looking at your latest report and weāll provide a build with a fix once we have it - to get the Beta builds starting today we switched to a new tool called Firebase, please enrol here.
We need to switch because of the big delays weāre facing with the app approval from Google, more details in the above like.
Ioana
Still seeing these Enter/Exit data corruptions with the latest Beta. Also found that one time the status got recorded as ā"Enterā" and this also creates issues with the app. The only valid value is with plain single quotes āEnterā.
On initial open of the newly installed Beta v.386, āSelect a Locationā mistakenly reported my Linux Edge as āOfflineā when it has been online constantly, especially since it was used with .383 about two minutes before.
Switching to my Vera Plus (shown correctly as āOnlineā all along) then back to Menu > āMy Controllersā cures the problem. But I still think itās worth reporting.
In .386, hereās another instance of VOI/Alexa taking the wrong intent from a known-good phrase that works as expected when spoken to a physical Echo device in my home:
dim fireplace to 50 percent
Rather than turn ON the Hue light named āFireplaceā and dimming it to 50%, I get this:
Great question! No, I have no skills like that active on Alexa. The closest one is called Twenty Questions but thatās a game not a chat bot.
The skill mentioned in the screenshot above has to do with generating ambient noises, which I do have among My Skills set.
At this point Alexa mismatch your āFireplaceā device/room name with your sleep sound, not VOI. You should try to change your device name or song name. So as you see, VOI is bridge between your alexa account and vera which returns what alexa responses back to you. There are still problems on Alexa side. Even same command with capital letter response differently. For example for letter āiā: āIs kitchen light onā and āis kitchen light onā. In that case, you can try one of these command ādim fireplace to 50 percentā, ādim Fireplace to 50 percentā, ādim fire place to 50 percentā or ādim Fire place to 50 percentā.
Roger that. Never meant to imply VOI had a hand in the misinterpretation, only that the mismatch was happening during a VOI command attempt.
Will continue playing with things and report back. This ordeal has me wondering whether it wouldnāt be advantageous to define preset Routines in Alexa with very distinct trigger phrases ā e.g. [When I sayā¦] āVera Scene Alpha Bravoā ā so that VOI has a fighting chance of getting through without misinterpretation.
I may try that approach. Because the current mechanism(s) seems far too sensitive (adding letter-case and spacing to that kinda blows my mind).
Alexa, Google Assistant like applications are still a baby. So, we are also complaining about with their issues. For example, I couldnāt connect Alexa and with my LG TV. Also, I couldnāt link my Xiaomi account with Google Home. They have so many bugs like that.
Please continue playing with VOI. You are asking great questions that makes us happy.
NEW FEEDBACK: Mismatched lists of āScenesā between app and UI
On my 7.0.31 Vera Plus, I canāt help noticing that the Scenes listed on her UI differ in number from those listed in beta app version .386. These screenshots show the discrepancy:
IN APP
I assume that the app is handling the āHiddenā attribute differently from Vera? And that the Geolocation-related āScenesā in turn are being handled differently from, say, the ones generated by individual Device āNotificationsā.
In the latter case ā as explained in earlier Feedback ā my placing those Notification scenes into Rooms caused them to surface/appear on Vera. However, despite placing the Geolocation-generated scenes into the room āAppsā, they remain hidden on Vera.
Inconsistent?! Not sure now what I ought to be seeing or where.