Deleted
There are problems in UI7 that cause requests from the browser to be delayed. I have seen this to be as high as 40 seconds. MCV indicated it has something to do with some camera logic getting into a tight loop. So you have to be patient with your changes. If you change the TAB in the browser before the change is actually saved … it can cancel the pending save request.
So be patient.
Deleted
If you upgraded from UI5 to UI7, or downgraded from UI7 to UI5 for Vera Alerts (and most of my other plugins for that matter) than you are required to UPDATE the software. An Uninstall/Install is the most drastic way to accomplish this.
The reason is that Installation/Upgrades are where I detect the correct UI version of code.
If you restore I UI5 backup on UI7 … you will have to do the upgrade again!
Deleted
What happens if you do too many at once ?
There should not be a limit in Vera Alerts … but maybe I am hitting a Vera Size problem …
Do you have a log file for when you have problems ?
I had around 40 to 50 after I upgraded to ui7. And I have been doing only one at a time because when I did more then 1 it only showed 1 updated at the top, I would restart luup and refresh browser and only the first would change.
I thought only 1 at a time was possible is it not?
Deleted
Deleted
Yep that’s a problem …
Did you try to refresh to see if that clears it up ?
If Not, Using Chrome …
With the mouse in the Vera Alerts Window … Right Mouse Click … Inspect Elements … Open up the Console tab
Now try to execute the Vera Alerts Funtionality … any errors in the Console ?
[quote=“RichardTSchaefer, post:10, topic:186245”]Yep that’s a problem …
Did you try to refresh to see if that clears it up ?
If Not, Using Chrome …
With the mouse in the Vera Alerts Window … Right Mouse Click … Inspect Elements … Open up the Console tab
Now try to execute the Vera Alerts Funtionality … any errors in the Console ?[/quote]
I have that same issue in chrome some times. A refresh or even re-clicking on the “notification configuration” button again will clear that.
As far as the message overrides not sticking. I have found most people don’t wait for a reload long enough (it takes a painful amount of time). Running the current version on the edge I use the following procedure just to get one at a time done.
#1 Add the message click another box so it will show 1 updated at the top.
#2 Click the Reload LUUP (I think with the latest update you don’t even have to click it but you do have to wait for some time) #3 Wait for atleast a min or more until the blue bar comes up across the top that it’s reloading. I wait until that is completely finished then
#4 refresh browser and confirm the changes have stuck.
Here is pictures of the process
What I found before is you click reload and then 10 sec after (before it actually reloaded) you click refresh browser.
Hope this helps.
Yep … that’s a MCV bug … I have looked at their code … you would not believe the number of places I see them put in comments that say we should fix this … as opposed to just fixing it!
Deleted
[quote=“EarlyMorningHours, post:13, topic:186245”]Sorry I’m late to reply. I don’t think I can add much more information that hasn’t been offered up already. The one thing I would add is it seems like with this new firmware that was released last week, after I make a change to one notification the blue bar at the top appears all on it’s own. Sometimes immediately, sometimes after five to ten seconds. But it’s this self-reLUUPing that prevents me from modifying more than one record. I assume from your last post however that this is part of the MCV bug you mention and until it’s resolved at their end, not too much can be done.
This interface is so aggravating that I can barely take it anymore. It easily takes two hours to accomplish what should take no more than five to ten minutes. And I’m losing count of how often I’ve needed to power cycle the Edge - mostly when the Edge won’t even respond to SSH anymore.[/quote]
I think they boot the auto relaod Luup as before people weren’t getting anything to save. Now atleast is auto reloads so it takes, but yes it only takes the first one. Good is tho that I don’t have any freezing or locking up issues like you.
Some of these little message overrides don’t bother me so much as I don’t do them very often. When I switched to ui7 I had a whole list of overrides and yes I wish I could have done the whole page (probley 40 to 50) at one time and been done. That took some time, but now that that’s all done and I might only do one extra here or there. Doing one at a time works fine, so this is not much of an issue anymore.
Sorry I'm late to reply. I don't think I can add much more information that hasn't been offered up already. The one thing I would add is it seems like with this new firmware that was released last week, after I make a change to one notification the blue bar at the top appears all on it's own. Sometimes immediately, sometimes after five to ten seconds. But it's this self-reLUUPing that prevents me from modifying more than one record. I assume from your last post however that this is part of the MCV bug you mention and until it's resolved at their end, not too much can be done.
This is some type of Vera bug … I do not restart LUA automatically … that’s why I added the “Restart LUA” button.
But if Vera is restarting … and you try to do an update while that happens … the request will get lost. I can add a check to see if the request goes through …
But it should never fail … unless your Vera is failing. I actually had an error at one time … but I took it out because a previous MCV bug was causing so many failures and I did not want to deal with everyone getting failure errors that looked like my code was failing.
NOTE! NOTE! NOTE!
You do not have to RELOAD Vera between each update … even with this Vera Bug … you could have made all of the changes …
At the end … wait one more minute … make a trivial change … wait one minute … then Reload Vera.