Script to disable all the mios/vera proprietary program and broadcast its zwave and zigbee radio serial ports in your network so it can be picked up by another controller... For example z-way. rafale77/Nuke-Vera Script to neuter the vera and broadcast its zwave and zigbee serial ports - rafale77/Nuke-Vera

I have a VeraPlus and would like to purchase a second z-wave controler. Is it possible to build a second z-wave network next to an existing z-wave network? Slowly I want to move devices form Vera to the new z-wave network. Is it more advisable to install the second z-wave controller as a slave controler?

My VeraPlus is in Christmas Light mode after attempting the latest update. So as I attempt to get things back with Vera Support I need to start looking into an alternate solution. I've installed OpenLuup in an Ubuntu VM I have running on an old PC. Right now I can still ssh into the VeraPlus. Will I be able to migrate the Z-Wave NW to a UZB dongle in this state? Or can I use @rafale77 's Nuke Vera Script to just use the VeraPlus as my zwave antenna? With either of these options have I lost the ability to migrate my configuration without Vera support restoring my VeraPlus first? Thanks

So ... I am trying to do the following: Current setup: Vera Plus (1.7.4955) Zwave only -> HASSIO VM (full control via Vera Integration) Future Target: HASSIO VM (leveraging zwave.me UZB1 dongle via USB) I have done the following so far: Updated UZB1 dongle (via RPi SmartHome) to latest 5.39 Firmware I followed the following steps to try and migrate my existing Z-Wave NW (currently on Vera) onto the UZB1 dongle following the steps listed here: Migrate from Vera to Z-way Problem: Steps 1-3: went fine (although the dumps are labeled as dongle.6.1.dump.x) Step 4: went fine and the UZB1 was recognized as it should be (per dmesg) Step 5: updating the port to /dev/ttyACM0 went fine, although I didn't see any indication of luup reload (or a save button for that matter when updating the port mapping) Step 6: I did the touch for dongle.restore, but wasn't sure where to trigger a luup reload (I assumed it was Z-Wave Settings > Advanced > Reload Engine). I believe I got an error message when trying to do that step Step 7: verify dongle.restore.go I don't recall being in the directions when I was going the test, but I rebooted Post Reboot: None of my previous z-wave devices were listed. I also checked dmesg via ssh and noticed the following items: [ 4.328000] Unsupported Device! [ 4.328000] Vendor=658 ProdID=200 [ 4.328000] Manufacturer= Product= I saw that item a couple times which almost seems like Vera is blocking the UZB1 or at least complaining about it. I ended up switching the Z-Wave back to the embedded controller, and restoring configuration from backup. Any suggestions what I did wrong??

Never posted this on the vera forum but... Did you know about this? The vera has a very powerful zwaveserial API program in the firmware. Take a look at what it can do: It is what the UI calls to interface with the zwave dongle.

So, after more than 10 years and 4 Vera's, my vera forum account is suspended. I think the monkey of the company, called melih is not man enough te have any critic. In the topic about the "great to come app" I responded to the topic (not off topic!) that a subscription can also be seen (financially) as buying a box, run it for 2 years and come to market with a better one (in better wordings). That means that if you as a company hast a box of 50USD cost, sell it at 250USD would give him a monthly subscription of 200/24=8.33 USD... Users that would last 5 years would pay a monthly of 3.33USD. But... the monkey on the rock has bolded his fists and said: ban him! He just can't take any criticism. To be honest! I am not even sad! It was a very rough journey with Vera. The journey stopped when Ezlo and the monkey took over the name. After that it quickly went downhill... Goodluck all! (except the monkey). Edit: The topic: Aug 16 MiOS Application - early Beta enrollment are you serious? would I become a cost? that is, customers who periodically replace the control unit and are happy with the service praise the Vera system and therefore also free advertising but, the new “company” decides to charge less to bind the customer with a subscription … But the genius... The post: The point you are missing is: If the hardware would “cost” around 50USD, and you sold it for 250USD, an average life span of 5 years would mean 200/(5×12)=3.33USD per month. Thats how Vera used to do it. Then release a faster/better “beast” every 2 years gives you 200/(2×12)=8.33USD per month. That’s how vera used to do it. And that’s how I did it for around 8 years and 4 veras with them untill you bought the company. This is just a matter of how you look at it and explain it. I dont frikking care how you do the maths, I only liked a working product and a close user community (like it was). Now all I see on this forum is a lot of “we are going to” and “we are working on”, “keep them coming guys”. But the reason for ever considering to buy a new vera every 2 years is gone… No clear migration path, no clear compatibility path and no clear integration path… That’s why I started to look for alternatives…

I have 50ish devices in connected to Home Assistant via. VeraPlus hub. I recently picked up an Aeotec Gen5 USB stick which I have successfully integrated into Home Assistant using OpenZWave. Can I add the Aeotec Stick as a Secondary Controller to Vera, turn off vera (making Aeotec primary) and then run natively that way on HA? I know the entity ID's in HA will change, but a lot easier to fix vs. unpair/repair all the devices from Vera. Will this work?

To answer @sdtoddl who emailed me asking how to manually force neighbor node setting on the vera, I don’t think it is possible with the UI. The solution is actually to trigger a neighbor node update on the given device and all the devices located between that said device and the controller. The vera deals with this by running multiple repeated (nightly) network heals which is not very efficient and causes it to frequently have unexpected network breakdowns and surprises good (some devices with problems get fixed) and bad (some devices which used to work stop working). It also takes down the entire network when it does it. One can however manually trigger neighbor node updates on the vera through the device’s advanced menu. To go to the next level, this data, the network node list is actually not recorded in the host controller firmware but in the non volatile memory of the zwave chip both on the controller and on the devices. It is therefore independent of the platform you use and can’t be set by the host. One can only ask the zwave chip on the device to run a survey and then inform the controller’s zwave chip of what it has found.

How to overcome the vera's storage limitations: Execrably poor partitioning and usage of the onboard flash causing hardware reliability failure through data corruption and storage availability for plugin limitations: Add your own external USB SATA drive and extroot. rafale77/vera-extroot Scripts to extroot the vera edge-plus-secure. Contribute to rafale77/vera-extroot development by creating an account on GitHub.

Amazing. One of my (un)trusty old VeraLite machines running UI5 has just achieved an uptime of one month... the maximum that that firmware can ever achieve! The graph below shows the uptime for the last two years, and although sometimes being up for a few weeks, it's never achieved a whole month! I put this down to reduced ZWave traffic and zero plugins, although the configuration hasn't changed for a long while.

I am used to errors, but never seen this before on altui on vera. keep getting this now all the time, any clue?

Using Home Assistant as the heart of my domotica (this was vera for 10 years up untill just a few months ago!) I currently have vera integrated as zwave hub only. Having almost all logic moved to hass leaving vera solely as zwave hub. As I am searching for a solution for a more stable zwave network and all options are open (but messing with zwave network ids etc is still too hard for me) I am also looking to another option. Multiple veras in hass. This way I can have isolated vera edges with smaller zwave networks and still do all logic in hass. One thing... currently only 1 vera is allowed in hass. It is a feature request already and I would like to ask to help me vote this request up: Jul 26, 2018 Multiple Vera Hubs I have multiple locations with Vera hubs at each for Z-Wave/Zigbee controls. However, you cannot add two or more Vera hubs to your configuration.yaml. Please add this as an option.

I found a device on my vera which accidentally had automatically configure set to on. After I turned it off the vera’s memory went from 50% to 20%!!

Since I have disabled nightly heal long time ago and since I have replaced some devices since and I am watching the webinar of z-way I wonder if it is wise and or advisable to do a manual heal of my zwave routibg in vera... what's the best way of doing so?

So if my vera will as it will want to restart after removing each zwave device and I have say 35 devices what are the chances it survives 35 restarts? How do I explain to my wife that our HA system is unstable? Yes, I know backup first.

Is there a way to remove a vera app and keep the devices it created?

As the tiltle describes :-). Is this possible in android via a browser? Mine doesn't allow me.

The vera can run both its zwave and zigbee network off of external USB radios instead of the onboard ones. This could have advantages in terms of portability, facilitating migrations or recoveries in case the vera craps out. It could also enable testing of newer radio firmwares. Zwave is pretty straightforward as its serial API is standardized and the protocol is the same regardless of what brand of USB stick you use. I have run my vera off of USB sticks of various brands for years going from Aeotec, Zooz, Homeseer and even the most generic silabs/Sigma Design. You just insert the stick in the usb port, find out which serial port it created (under the /dev/ folder) and use that port (ie. /dev/ttyACM0, /dev/ttyUSB0 etc) in the zwave advance menu. Zigbee is a little trickier as the protocol and chipset was not quite as standardized as zwave. The vera only works with ember Znet protocol and you will need to find a usb stick with an EM35x chip in it which already has an ember zigbee firmware loaded. One example of such a stick is the Go Control HUSBZB1 (dual zwave-zigbee stick). The port is not readily accessible on the vera UI but can be accessed either through editing of the /etc/cmh/user-data.json or through ALTUI by going into the hidden zigbee radio device through the "table devices " menu and changing modifying the port variable there. You can also upgrade the onboard zwave and zigbee radio firmwares from the command line SSH...

I know how to uptrip but it is so annoying that lots of motion sensor keep tripped... ("urn:micasaverde-com:serviceId:SecuritySensor1", "Tripped", 0, 986) Any tips or suggestion to avoid this sensor behaviour?

I first learned of Lua and Luup (Lua+UPnP extensions) in 2009, but was never quite clear on who created reach language or who "owns" them now. Are these proprietary? Open source? IEEE spec? Fully documented? Extensible? Heck, I didn't even realize there was an SDK out there until this year! Suddenly desirous of learning more... Thanks. Libra