I modified your code a bit to create a find and replace kind of script:
devs = luup.devices;
for id,obj in pairs(devs) do
luup.log("VERAPLUS http://veraplus_ip:3480/data_request?id=finddevice&devid=" .. tostring(obj['id']) .. " change DEVICEID http://veraplus_ip:3480/data_request?id=device&action=rename&device=DEVICEID&name=" .. tostring(obj['description']) .. "&room=" .. tostring(luup.rooms[obj['room_num']]))
end
Based on your example, you will run this script on your OLD vera3 and it generates 2 URL’s.
The first URL is to find the DEVICEID on the new VERA PLUS based on the ALTID, this is the first number.
The second URL changes name and room of the device (if you have created the rooms of course on the new vera plus), change DEVICEID with the number you get from the first URL.
Every couple of days my Vera Plus would loose connectivity to ALL devices.
The only way to recover was to backup (with a previously good Z-Wave config, not a NEW Z-Wave backup) and then restore (with restore Z-Wave checkbox enabled).
This allowed me to restore my current Vera Device State with a previously good Z-Wave network state. Took about 5 minutes … but what a pain.
During this whole time I still had 3 devices that could not respond to z-wave commands …
One was battery powered, all of my other battery powered devices reconfigured by reinserting the batteries.
This one (Philio -03) had to be unpaired/paired to recover, and it was in a room I rarely use, so it took me a while to get to it.
Two where HA-01 wall plugs. I bought 30 of these on sale, and have replace 7 over the last 2 years … you get what you pay for!)
I finally went to Lowes and picked up a couple of GE Z-wave wall plugs and replaced the remaining bad z-wave nodes.
I use these in places I will NEVER need instant status.
Now that all of my Z-Wave devices work, I have not had any more problems. So something with bad z-wave nodes in the mesh is causing UI7 or the new Z-Wave chips to become unstable.
Now that everything is working … I must say Z-Wave commands are MUCH-MUCH faster.
Actually everything is much Faster.
I measure things in STEPS before automation detects and responds.
In the past I would often need 2-4 steps.
With Vera Plus I am now down to 1-2 steps … Almost twice the speed for a SENSE → LOGIC → COMMAND → NEW DEVICE STATE
=========================================================================================================================
For those that use PLEG and/or PLTS
During my upgrade (i copied from UI5 and pasted in UI7) i entered all my 100s of triggers, schedules, properties, conditions, actions by hand.
I often did a reload to test things.
I NEVER had a problem saving data. Everything just worked as I expected.
I did find a problem with “CONTROL” style actions, If you add a SWITCH, and it shows initially OFF, and that’s what you wanted, you still have to turn in ON/OFF in the action editor in order to record the action properly. It’s event driven, so it records when you actually interact with the device.
So this may appear like the data is not being saved.
But enough people are having problems saving data, not just with PLEG so I do believe there is a VERA problem. I dd see this ONCE on my Vera Edge, but was not prepared to debug it at the time, and I have never seen it again. So I do believe there is some VERA bugs that people are hitting. I do have a new strategy that I will be releasing to save data shortly after the next UI7 release. MCV fixed some bugs that will be available in the next UI7 release that will allow me to use a new (preferred) strategy for saving data.
Thanks for the update Richard. I look forward to trying out the new version of PLEG as well as hope Vera squashes some of its own with the Plus.
I have noticed that once I got everything setup on my Plus and all my devices were happy everything seems faster and more stable. On my edge or lite I would get a random restart every now and then, at least once every 2 days. The plus on the other hand has not randomly restarted yet. At this point I’ve only made it 5 days between a manual restart for needing to update scenes/schedules.
[quote=“RichardTSchaefer, post:22, topic:191114”]Every couple of days my Vera Plus would loose connectivity to ALL devices.
The only way to recover was to backup (with a previously good Z-Wave config, not a NEW Z-Wave backup) and then restore (with restore Z-Wave checkbox enabled).
This allowed me to restore my current Vera Device State with a previously good Z-Wave network state. Took about 5 minutes … but what a pain.[/quote]
Thanks for confirming what others have said about z-wave problems. While I already replaced my ‘questionable’ z-wave devices (Intermatic outlets), I think I want to give MCV a little more time to clean up the firmware with respect to the Plus before I purchase…
After several evenings i still can’t get the vera notice my fibaro door sensor with the voodoo magic (thanks for sharing your approach!) RichardTSchaefer described.
Does anyone have some tips or additional voodoo magic to get it fixed?
Both my Fibaro door sensors refused to work after the migration. I ended up deleting them from Vera, perform the procedure for a factory reset, and then include them again. To include, I did not follow the procedure as shown by Vera (clicking the tamper button 3 times), instead I held the tamper button (as it would normally be after installing it), then clicked the top button 3 times.
You may need to upgrade the GC-100 plugin … It is working for me on UI7.
But I made some changes long ago … and released them back to Vera to integrate.
I just wanted to share my experience. Vera 3 UI5 → Vera Plus UI7. I did the initial step of shifting z-wave controllers which worked. When I tried the MCV method of backing up and restoring the other setting, thy Vera Plus became unresponsive. I had to do a hard reset, then figure out how to set the V3 back to primary. This happened twice before I gave up.
Then I proceeded with RTS’s method of only migrating the z-wave. I had to name all devices, put them in rooms, etc. Then I had to recreate all the PLEG scenes. It took me a LOT longer than 8 hours, but I wasn’t as methodical. The end result was I converted more of my old scenes to PLEG and learned how to work in UI7. I also refamiliarized myself with some old functions and made some simplifications / improvements in the process. In the end, it took a week to get everything migrated then about a week of troubleshooting.
I had been using the V3 as my home routed (I’m probably one of two people that actually do that), so I will leave it in that place and might take the suggesting someone had about having it power cycle the VPlus if it becomes unresponsive.
So far I have seen some improvement but it still gets bogged down if large number of things happen at once.
I don’t like UI7, especially how it doesn’t always save setting and, at RTS pointed out if you want to turn off a light in PLEG you have to set it to turn off then click it back to off or it won’t save.
All of my apps and devices loaded OK. My 2Gig thermostat always required that I set up timed polling or it wouldn’t update and that is still the case albiet perhaps better.
Oh, and like many others I don’t like the UI7 thermostat UI.
