I’m not sure this was introduced in 7.09 or in teh last 2 or 3 releases. I just noticed it trying to modify camera’s and creating a new one.
Vera 3 with UI7.09
Blue Iris plugin v0.6 from the app store
When attempting to modify camera values either for an existing or a newly created one:
Under advanced settings, changes on the Params tab are recognized and processed. (eg the IP address) However, the values on the Variables tab (such as the camera name) don’t seem to stick. As soon as I modify the 2nd camera, the 1st one I modified, reverts the camera names on the variables back to the old value. This also happens when I create new camera devices. As they default to the Index name. I change it and try to add or change another camera and boom, it goes back to index.
I was attempting to move my camera’s from my old BI to my new BI server which means the IP address changed and I also changed the camera naming convention. Which is how I discovered this.
At this time, to be able to use my new, more powerful BI server and be able to repurpose my old one, I changed the naming convention back to the old one. Which is allowing me to at least access my existing cameras on Vera. Unfortunately I am not able to add the 2 new camera’s I was about to install.
This may be the tip for you. The advanced variables page does not get the update and is reading from cache unless you reload your browser. This has been true for quite a while. Try this: make your first change then reload your browser to see if the change has taken. If you do not reload the browser the url will load from the cache that does not contain the current value.
Then go to the second one and do the same thing. This is behavior that I noticed a couple of updates ago and is simply because the parameters for the url do not change between requests. The server sees it as the same request and fills it with a fully rendered page from the cache. Even though the value has changed it is not reflected in the page since the last one loaded with the parameters contained the old value.
You may be surprised that the change to the variable is actually occurring but the page is being read from cache. If I had the VP with the new features ready to go I would send you some Lua to throw in the command dialog and hit run.
@RSTROUSE: You Rock!!! 8) That’s indeed the fix for the issue. Dang! GetVera really needs to fix that.
Oh well, renaming all camera’s back to the new naming convention and I just shut down the old WHS2011/BI box. should save me a few $$ as the new one is a Lenove TS140 with Xeon and low power consumption. The old one was a gome made AMD Phenom II box that used a lot more juice based on the heat it generated. Pity MS dropped WHS2011 as 2012 Essentials is above the budget just for running BI. [My primary server is a *nix box :)] May end up slapping Win7 on it and doing the free upgrade to Win10.
Editing a freshly created camera is a chore as it won’t retain the changes to the settings page properly either. I finally managed to get those to hold after about 5 tries with page refreshes and saves and dancing on one leg chanting mantra’s. After which I was able to set the correct values on the advanced tabs…
Yeah the page caching can bite you. There was a blurb in the release notes a few updates ago where they optimized page loads. Me thinks they forgot to kill the cache on header for a couple of the Ajax and pure js pages. I see a few reported issues on here where folks think their settings don’t take but the variable_set is being called on the cached value and Vera hasn’t gotten around to persisting it yet.
I think you may be surprised with the level of functionality that is plopped into Win10 as a desktop platform. WHS2011 was so neutered that it was hard to call it a server platform. Still it has a ton of fans that will be sad to see it go. Win10 may very well scale better into a home server platform.
I too think the page loading it now too ‘optimized’. When working remote the devices do not reflect the latest status until the matching variables have changed. Or you need to open the device and click back to update to current status.
It also seems they are discouraging using the Advanced Variables tab to configure your devices. It seems they want plugin makers to create setting pages for inputting settings. Especially annoying if you just want to add some LUA to a standard device definition to make it work as you need it to.
I have reported the caching issue to support and was notified it has been escalated to the R&D team for review. I’ve run into another issue. The latest .118 Vera Android app beta will no longer display the camera feeds but instead shows a ghostbuster logo like red circle with diagonal line. I’m not sure if it’s on the app side or on the 7.09 side. I’ll have to wait until I get home to see of AuthomationHD can access the camera’s on my UI7 (Have not set that up for remote access.)
I agree with WHS2011 being neutered (8GB memory limit really?) but at the price it was a great solution for a home server even with the restrictions. A lot of WHS2011 users have migrated to Windows 8.1 and configured that as a ‘server’. I’m hoping Win10 will allow a similar setup in which case I’ll migrate over within the ‘free upgrade’ year.
I have a test box with a reservation sitting waiting for MS to push Win10 so I can evaluate it.
Looks like the issue may be with the Blue Iris plugin under 7.09 then. That would suck as I am dependent on that plugin as Vera does not natively support my IP camera’s
Best Home Automation shopping experience. Shop at Ezlo!