After the veralert service was shut down and Richard confirmed that it will not be available again, I searched for a new notification service to use in my vere secure. I signed up for the PushOver service.
I want to take a snapshot from a camera with camera snapshot address “192.168.4.37/img/snapshot.cgi?size=4&quality=1” and video address “192.168.4.37/img/video.mjpeg” according to a trigger.
Actually, someone (Tlex) did a work about this years ago on the vera forum, but I couldn't understand that script. I also wrote to him to be more descriptive, but I didn't get an answer. Can you help me with this?
I have an older Vera Plus controller that has been collecting dust for a little while. I know the hardware is no longer supported but I would prefer it to go to a good home vs the eWaste center. No charge, just pay for shipping and it's yours. If you are interested, let me know.
With their awesome new X10 switch!
dbe7408f-dc86-4932-bf71-f0528f5384c1-image.png
I'm hopping in my 1980s time machine to go see whether this is exactly what I think it is. 🙂
(Srsly, tho, I love(d) X10 and did everything humanly possible to keep that old equipment perking along with Vera, and almost succeeded.)
LibraP.S. Just got banned for the 9th time from Hubitat Forum, so had a little extra time to throw shade.
P.P.S. The boilerplate 5-star reviews for this brand-new product come from bots with names like Avery, Phoenix and Owen (two from Mateo!). Sheesh.
Let's assume you have done the following:
Downloaded and installed Z-Way following these instructions. No Zway license is required to do the following. The software is now all up and running with your UZB stick (whole other post). Dial up this Zway web page: http://<Zway_server_IP_address>:8083/expert/#/network/controller Under the heading "Firmware" take note of the "SDK version" and the "Serial API Version". Say they equal 6.71.01 & 05.23 respectively like it shows here.Now on to Vera:
Go to the Vera UI --> Z-Wave Settings and taken note of the "Version" shown for Vera's internal Zwave IC. For example purposes, say it equals "6.01". You plug your UZB stick into Vera. In the Z-Wave Settings you set the port to "/dev/ttyACM0" You've rebooted Vera, so that it starts using the UZB stick.OK, so what "Version" will Vera now display and the version of what? The version shown by Vera is the "Z-Wave protocol" version or the "Serial API" version - it's unclear which but I suspect the former. However on most occasions the numbers are the same. It's not the Software Developers Kit (SDK) version number.
Knowing the UZB firmware version you can identify what Vera will show with the following table.
From the example above: Zway stated the version as 5.23. It will show in Vera as version 4.61 - see table. However the Vera internals showed up as 6.01. So using this method to copy the Zwave configuration to the stick will not work, as the stick represents a downgrade and you can only do same to same or upgrades. So in this case you need to update the stick firmware from 5.23 to 5.32 as a minimum. Then the stick will show up in Vera with version of 6.01.
Which is great. So you then use the Zway software to upgrade the stick firmware. And that's the last you hear from it because this happens:
"Sorry to inform you, but there is a known issue in some UZB manufactured by our partners on license base that after upgrade they become bricked."
And you have to do this to unbrick it. So time to try someone else's stick. Sigh.
ZWay UZB version Vera version SDK version 5.39 6.09 6.82.01 6.08 6.82.00 6.07 6.81.06 6.06 6.81.05 6.05 6.81.04 6.04 6.81.03 6.03 6.81.02 5.37 6.02 6.81.01 5.36 6.02??? 6.81.00 ???? 5.33 6.02??? 6.81.00 ???? 5.32 6.01 6.81.00 5.03 6.71.03 5.02 6.71.02 5.27 BL 48059 4.61 6.71.0? 5.26 4.61 6.71.0? 5.23 4.61 6.71.01 4.6 6.71.00 5.2 4.6? 6.7?.00 5.16 4.6? 6.70.00 4.62 6.61.01 4.33 6.61.00 4.54 6.51.10 5.07 4.38 6.51.09 4.34 6.51.08 4.24 6.51.07 4.05 6.51.06 5.06 4.01 6.51.04 3.99 6.51.03 3.95 6.51.02 3.92 6.51.01 3.83 6.51.00 3.79 6.50.01 3.71 6.50.00 3.67 3.35 6.10.00 3.41 6.02.00 3.37 6.01.03 2.78The table is based on page 434 of silabs app INS13954 and the UZB firmware revision information found here. The table may have errors!
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...
incalzire.png
Hello everybody.
I would like to automate the underfloor heating. At the moment I have the gateway from vera secure and thermostat with receiver from SRT SECURE with z-wave. I would like to connect to the gateway a receiver with 4 channels from sonoff and 3 temperature and humidity sensors from aliexpress as a thermostat. do you think it is possible?
and one more question... how can I change the name of the wireless network and the password from the gateway?
Thank you very much!
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.
GitHub - rafale77/Nuke-Vera: Script to neuter the vera and broadcast its zwave and zigbee serial ports
GitHub - rafale77/Nuke-Vera: Script to neuter the vera and broadcast its zwave and zigbee serial ports
Script to neuter the vera and broadcast its zwave and zigbee serial ports - rafale77/Nuke-Vera
Good morning all,
I've got a stable Home Assistant running on a RPI 4 with a Aeotec Z-Stick 7 Plus, and of course the Z-wave JS integration. I've manually moved a handful of devices, and I'm overall much happier with the HA z-wave capability than I am with Vera. There are still some things I'm trying to figure out that I have in Vera that I'm not sure how they'll work in HA, but no deal breakers.
I've got all of my automation on MSR and off of luup Reactor, so really the only thing left for me is to migrate my Z-wave network. I saw @rafale77's post about using a Zwave.me UZB1 to Zway, but of course that's not what I'm using.
Is there a similar method that I can use my Aeotec Z-Stick 7 plus to Home Assistant? I have around 70 Z-wave devices (give or take devices that generate multiple instances in Vera), so manual unpairing, including, etc, would be quite a chore.
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 FirmwareI 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:
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??
Having trouble getting a Vera 3 to recognise a Z-Wave.Me UZB stick.
WinSCP indicates it's mounted at /dev/ttyACM0, so the Vera Z-Wave settings were adjusted to match. On a Luup engine reload Vera UI states: "ZWave : Failed To Start". Ditto for a complete Vera reboot.
Has anyone successfully used a UZB stick with a Vera 3?
Hello Everyone,
I am using iPhone locator on Vera, and yesterday it stopped working. Looking at the logs, I can see the connection is refused, but nothing on my end changed. iPhone locator is really important in my particular setup, so I guess I have two questions.
Is it broken, or is it me?
I don't see anyone else saying there is an issue, but I am not sure how many people are still using it (or Vera for location) at this point. I installed it on a blank Vera test controller, same issue. It might be something with the iCloud account, but it works everywhere else.
Is there something similar on another platform?
Mainly what I would like is the ability to force a poll of iCloud location on demand. I have a bunch of triggers setup, including magnetic sensors in my driveway to sense vehicles and determine if the motion is egress or ingress. These triggers in conjunction with MSR have been a great way to double check phone location, and I would hate to lose this functionality. It looks like HA might have something with "iCloud3". Is anyone using it?
Thanks,
Mike
@akbooer said in
The only thing left on Vera is now electricity meter readers, and I simply can't find any suitable WiFi replacement.
My hem stopped reporting this august and I’ve replaced it with a Shelly EM. I’m using another one on my solar and they’re amazing fast to report and quite precise. They’re WiFi, and mqtt based. Recommended!
Long story short: I need to tweak some parameters for Fibaro Plugs, to remove frequent notifications about watts (I just need a very good approximation, in order to detect the cycle of washer/dryer), but the parameters depend on the firmware version, and I have:
271,1554,21554
and the other one has:
271,4102,0
Any help is apprreciated.
Hi all! I am almost relieved from Vera 🙏. Around 65 decices to go. Of which some are on very hard places (under floor etc.). Is there any way to easily get the vera devices on the zwave network without repairing them per piece?
I think I knowthe answer, but I am asking 😉
Anyone installed the new beta f/w on their Vera unit and liking it?
Read https://community.ezlo.com/t/7-32-vera-firmware-beta-release/217060
Have Aeotec Smart Switch 6 in use with Vera Plus (fw 7.31 - 1.7.5186, decoupled) and now as I'm trying to change its configuration, it seems impossible.
Screenshot 2021-09-07 at 11.21.28.png
"Save changes" just initiates luup reload, but parameters stay the same. "Configure node right now" does not help either, Vera informs that command sent, but nothing happens. Hard refresh of the browser done.
Device itself is working, e.g. it reports current wattage.
"Automatically configure" is set to "No", if set to "Yes", configuration change is initiated but fails with the message "Failed at: Setting special association"
EDIT: in the end this was solved by unplugging the switch and then plugging it back, some internal state corrupted...
Hi there,
I know this was floating around on the other forum but just hoping someone can post the steps as I’m finally biting the bullet and moving to a USB stick and Zwave JS in home assistant.
Thanks!
So, I recently added Pi-Hole (pi-hole.net) to my networked clients for its open-sourced Ad and Tracker Blocking. Essentially, it’s a DNS Blacklisting solution and it can display the Domains being accessed.
To my dismay I’m seeing the VERA+ attempting calls to facebook.com on a regular basis between 20 – 70 minutes each.
The Active apps on VERA are Sercomm IP Camera, Amazon Alexa Helper, Garage Door, Foscam HD, Reator, SiteSensor and Ezlo Cameras. I just recently removed AltUI before disconnecting from the cloud services.
Any ideas on how I could track down the culprit caller?
Thanks for your consideration.
I've got a Nokia/Withings bathroom scale on which I weigh myself daily. I used to use IFTTT to push every weighing result into a Google Spreadsheet in the cloud, but now that I use MSR, I'm more interested in integrating this data into that workflow.
Has anyone figured out a way to move data from a WiFi-connected scale into the Vera environment? I don't mind trying something indirect, as for instance I've already linked the weights over to my Google Fit app.
Open to suggestions!
Vera firmware 7.32 beta
-
@librasun said in Vera firmware 7.32 beta:
A puzzlement. And I could of course be wrong.
Anyone else experience such shenanigans?this is frequent if you have a lot of actions attached to a mode. I've transitioned to a staged function, where things get called in sequence (ie: in small groups of 5 decices) and it improved a lot.
-
@therealdb said in Vera firmware 7.32 beta:
this is frequent if you have a lot of actions attached to a mode.
I recalled you saying that, so I had checked to see WHAT actions were taking place in connection with the changing Mode, and basically nothing. In fact, I only let MSR change House Mode 15 seconds after any other reactions are done.
And none of Vera's built-in "House Modes" settings (from the Dashboard) make changes to any devices.
Hmm... I'll have to keep my thinking cap on some more.
-
-
@catmanv2 said in Vera firmware 7.32 beta:
What happens if you change modes manually?
C
Never a problem, but I will certainly investigate. For instance, I have MSR Rules in place which (after a brief pause) cause my ecobee thermostat to match its mode to the new House Mode, and vice versa. Very thoroughly tested, but never 100% above suspicion.
-
You might also try using 3.9 stable branch Reactor. It's got some different job control features specifically for 7.32. I've run that combination on my house Vera for months now and have few reloads.
-
@toggledbits if I have reactor installed from the marketplace can I grab the files from GitHub and upload those to update? I did this once I remember and everything got thrown out of whack
-
That works fine. Just follow the procedure:
- Go to the stable branch for the project on Github: https://github.com/toggledbits/Reactor/tree/stable
- Click the green "Code" button and choose "Download ZIP". Save the ZIP file to your local HD.
- Unzip the file.
- Open the Vera UI and go to Apps > Develop apps > Luup files
- Select all of the unzipped files (not the folder, the files as a group) and drag them to the "Upload" button in the UI.
The system will reload when the upload completes. You'll want to hard-refresh your browser as usual.
-
Following up since I made the above changes last week, and am happy to report NOT A SINGLE LUUP ENGINE RESTART YET!
Having minimal plug-ins installed and periodically rebooting Vera by power cycling seems to be a wise regimen to follow. I'm past thinking the "random restart" problem was induced by House Mode changes and/or too many commands issued at once, etc. -
Yeah, I think I know where their locking bug is that causes deadlocks.
-
Beta discussion (or more of a silence) doesn't look very promising... and as a banned user cannot participate if I wanted to.
They don't seem to publish a production release, so I guess I have to bite the bullet and go for the latest beta, but the link given (Vera Plus) in the first post does not work, so anyone know from where to download?
EDIT: Found beta 4, which seems to be the latest one. I guess this is as solid as Vera can ever be?
Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8
-
@tunnus said in Vera firmware 7.32 beta:
. I guess this is as solid as Vera can ever be?
I think we have to assume that's the case. Clearly, they are overrun with their other efforts. They are now over three years since acquisition, on their way to four, and as we all have experienced, the last 20% of any project can take 80% of the time and effort. Worse, by my product math, if they have 80% of the project 80% complete, they've done 64% of the work necessary (0.8 x 0.8), so I predict mid-2023. I think they're spread so thin trying to get everything done that they claim they will have that there's no bandwidth for Vera firmware on their radar, but if it's going to take that long for the new firmware to be feature complete and stable enough (regardless of how they describe the release... alpha, beta, candidate, etc... customers will decide what it is, as they are doing right now)., they may be forced into the position of doing another release of Vera firmware to try to preserve that customer base. If they don't hold the Vera customer base and get a significant migration of customers, the purchase of Vera was an unnecessary waste.
Everything I have left on Vera now runs on 7.32, and it's pretty stable. Still deadlocks, still reloads, still Vera. If you go to 7.32 and you're using the Reactor plugin for Vera, I recommend updating Reactor to 3.9, which is on Github, not in the App Marketplace. Updates for my other plugins are (and always have been) on Github as well. Decoupling does appear to make it more stable.
-
@toggledbits I 100% agree. My system is stable, and I've since removed 90% of my scenes to further improve it. I'm in the middle of choosing to completely migrate to Home Assistant (and start from scratch with the logic, a tough exercise, but probably a better investment), to MSR (but I want to write code :D), or to my own home-grown solution (which already runs 20% of my logic, TTS, weather, MQTT and many more things). We'll see.
I will not update my plug-ins and I will remove them from the app store anyway. It's sad, but I think eZlo will not build a viable solution for us enthusiasts and probably just focus on very simplicists users. Otherwise, I'm not explaining why, after 2+ years of development, the features offered by their hubs are very, very, very basic.
-
As I already commented in the other forum, it is clear that there is no more effort to fix FW problems, we are relegated to survive with what we have, and that is that.
For more than a year I have been frequenting these user forums, and I have tried to do everything that I understood to be good to reduce the tasks of the Vera hub, I no longer use, for example, Reactor and migrated everything to MSR, an excellent measure. I don't have any scene anymore, everything is in MSR.
Another very important topic that helped me a lot in the system performance, was @rafale77 explanation (https://community.ezlo.com/t/zwave-network-on-vera-explained/210661/3), I executed everything he recommended, increased the battery life, and helped in the performance.
However, despite having done all this, I still have a system that I find unstable. Without the slightest explanation, I get device failure messages that are waiting for a wakeup, and then I have to manually press buttons to get it working again. The device with S2 protection, a huge headache to include and work. Reading some posts above, when I change from Home to Night mode, it is crazy, everything gets an indication that is waiting to run, and of course, the system almost dies.
Before I take what I believe is the most radical step, buying a Hubitat Elevation to solve problems with S2, to have true support for ZigBee devices, I want to make three consultations with you who are super experts:
-
The procedure of decoupling the Vera from the mother ship (https://github.com/toggledbits/Vera-Decouple), I have read and re-read the instruction, besides the comments above, seems to me a great measure. The only thing that is not clear to me is, will the Vera APP on the phone, which allows us to control devices remotely, still work? Will I be able to continue turning things on and off through the APP, or will it stop working?
-
It seems clear to me that the mode shift made by the Vera hub is a problem. I can easily create actions in MSR to perform the actions, although I find it not very productive. Does setting the My Preset Modes panel to DEFAULT mean that the Vera hub won't do anything else when the mode is activated? It will not take any further action? Now when commanding everything from the MSR, I would have to put a time delay between commands, so as not to overload the hub, is that it? In summary, is it recommended to change everything to MSR or is there something to be done first?
-
Any thread that I'm missing recommendations for settings, cleaning, or changing the hub that might be helping too? Something to clean up space? Disable useless function?
The change from Vera to Hubitat is inevitable, however, what will I do to add new devices. Touching the installed base will mean having to reinstall more than 100 devices, search for a manual on the internet to do a factory reset, review a lot of MSR actions to go from one hub to another.
I'm using the latest version 1.7.5386 (7.32) for Vera, the the last MSR 21297.
Thanks.
-
-
@therealdb said in Vera firmware 7.32 beta:
Otherwise, I'm not explaining why, after 2+ years of development, the features offered by their hubs are very, very, very basic.
My feeling is they already missed the boat. I would give them a life expectancy of <2 years, depending on how much Melih is prepared to bankroll it.
They have failed to deliver an improved Vera and (as far as I can tell) are failing to produce anything in the way of a usable Ezlo.
C
-
Ezlo should've stuck with the old Vera FW and worked to give it more features and fix it since its already been used for years. They shot themselves in the foot by taking too long to get a proper working hub out, the home control market has already matured with some really heavy hitters from HA to Hubitat.
I was very close to switching to HA but that requires running a Rpi of sorts to run MSR which will need a pretty big overhaul of logic since it will need to work with all the new devices in HA and I will need to rebuild my Home Remote application. My VP on 7.32 runs pretty stable until a device randomly goes offline then sh*t hits the fan, I run minimal plugins to keep things stable. Had the Z wave network on Vera been better I would've stayed since I basically only have Z wave related issues.
-
@wmarcolin said in Vera firmware 7.32 beta:
it is clear that there is no more effort to fix FW problems, we are relegated to survive with what we have, and that is that.
Ah! … so that would essentially be end of life, then?
-
I have been mostly silent on this forum for some time now with the exception of the occasional notifications for questions addressed to me because I just moved to a new house and my system had been rock solid for over a year... mostly since I got rid of the vera.
I now have to re-build everything from scratch in my new house while I had literally zero reliability issues with my previous setup in spite of its complexity (200+ devices integrated running 3 different software platform interconnected between z-way for zwave, Homeassistant for AI/cameras and the rare cloud integrations or integrations not existing on openLuup/vera and openLuup for scenes/automation/control interface.)
I considered long and hard to sell my old home with the automation but at the end I decided to move as much as I could over mostly because I noticed an increasing trend of the industry to go towards wifi for ease of setup but which cannot scale to large installations and have to encroach into wifi bandwidth. It is getting a bit harder to buy zwave and even zigbee devices. I also didn't want to spend the time to go through the learning curve of hubitat which would have yielded no benefit to my setup.
Dumping the vera was the single biggest improvement to my system and please, no ezlo... They are cost reduced and downgraded controllers to the vera in every important practical aspect.My new setup will be much lighter. Probably will not get to 175 zwave nodes, more likely <100 without the window coverings, fewer lights, fewer sensors. Heck I think I will dump the Phillips hue altogether too. I can't recommend enough migrating away from vera and go to openLuup or MSR in combination with Home Assistant for zigbee and integrations and z-way for z-wave while keeping devices as local as possible by avoiding all the wifi stuff which tend to be cloud dependent (with all their reliability and security disadvantages) and less efficient both in power and RF bandwidth. Still a new adventure...
