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 portsScript 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
-
I just found this thread after making my way over to this site to get started with MSR (running on Raspberry Pi 4 Docker) for my VeraPlus. I've been following the 7.32 discussion on the Ezlo site and it definitely sounds like 7.32 isn't coming out of beta anytime soon. I purchased two leak/flood sensors that are supported in 7.32 but not in 7.31, so I'm motivated to get onto 7.32 to get those monitored before I have (another) leak.
Is the beta reasonably stable and free of glaring bugs?
If so, can anyone save me some internet searching and point me to a valid download link?Edit: I figured out the download links from the Ezlo Community site: Do I want the Open Beta 4 downloads or one of the older ones?I realize that nothing is completely stable on Vera, so I'm just looking to see if there are any major issues with 7.32 that I need to consider before trying the beta.
I use Google Home for voice command of the Vera and use the Vera app for geofencing to trigger home/away actions, so the cloud connection is doing some useful things for me at this point. Do I need to decouple to make 7.32 stable? Or are there people using it successfully without going through the decoupling process?
Thanks for any help.
-
@alan_f said in Vera firmware 7.32 beta:
Do I want the Open Beta 4 downloads or one of the older ones?
You want beta 4. It's also linked in this thread in an earlier post by @tunnus
@alan_f said in Vera firmware 7.32 beta:
I use Google Home for voice command of the Vera and use the Vera app for geofencing to trigger home/away actions, so the cloud connection is doing some useful things for me at this point. Do I need to decouple to make 7.32 stable?
You don't need to decouple, and if you're using the native geofencing, you cannot decouple, as decoupling would break that. Even without decoupling, 7.32 is more stable for most users; I suspect those for which it is not are also users of older and less well-maintained/written plugins. Without decoupling, you'll have instability during Internet outages, although there are things you can do without a full decouple to improve on that as well.
@catmanv2 said in Vera firmware 7.32 beta:
FWIWI I'd make the jump to $somethingelse
I think @CatmanV2 's point here is that Vera is walking dead, so by sticking with it, you are only putting off the inevitable. If you start picking up HA or Hubitat now, MSR will let you make the transition more gradually using your old Vera cooperatively with the new hub(s). When your Vera dies, you may not find a replacement, but at least, you'll either have shelved it already, or be so far along the curve with a newer solution that taking the last steps will be less harrowing.
-
@toggledbits said in Vera firmware 7.32 beta:
@catmanv2 said in Vera firmware 7.32 beta:
FWIWI I'd make the jump to $somethingelse
I think @CatmanV2 's point here is that Vera is walking dead, so by sticking with it, you are only putting off the inevitable. If you start picking up HA or Hubitat now, MSR will let you make the transition more gradually using your old Vera cooperatively with the new hub(s). When your Vera dies, you may not find a replacement, but at least, you'll either have shelved it already, or be so far along the curve with a newer solution that taking the last steps will be less harrowing.
Exactly that.
C
-
@gwp1 said in Vera firmware 7.32 beta:
Is this not for the VeraSecure? It gave me a "wrong platform" error.
There are different links for each hardware platform. Here are the three together in one post:
Vera Edge: https://dl.mios.com/rl/732/mt7620a_Luup_ui7-1.7.5385-en-mios.squashfs
Vera Plus: https://dl.mios.com/rl/732/mt7621_Luup_ui7-1.7.5386-en-mios.squashfs
Vera Secure: https://dl.mios.com/rl/732/mt7621s_Luup_ui7-1.7.5387-en-mios.squashfs -
Based on the comments from the more experienced users here I ordered a Hubitat this morning and Amazon had it to my door about 3 hours later. After a few z-wave network resets to try to resolve one switch that just won't configure, I have about 90% of everything migrated over to Hubitat. Vera still has a few SiteSensors (I need to read up on the threads about replicating site sensors on MSR) and some Yeelight bulbs that are on a separate VLAN from the Hubitat. I haven't found a way to connect them manually yet and the Hubitat can't discover them across the VLANs.
I'm still trying to figure out a way to use Google Home to flip a virtual switch in Hubitat to then trigger a http call from MSR. There are a few things I was doing with Vera scenes to achieve a similar effect, but MSR doesn't seem to be able to see Hubitat virtual devices.
I'll probably keep the VeraPlus going for a while with the Yeelights and the SiteSensors while I figure the rest of this out.
Thanks for the advice.
-
@alan_f said in Vera firmware 7.32 beta:
but MSR doesn't seem to be able to see Hubitat virtual devices.
I use them extensively for testing. Make sure that when you add devices, you go back to Maker API and make sure those devices are on the list to be published. New devices aren't added to the permitted/published list automatically, so Reactor won't see them until you fix that.
-
I picked up a Hubs last year and began migrating over from my VeraSecure. I saw the handwriting on the, well, forums and thought the time was right esp given the creation of MSR. Tbh, Reactor was the only thing really keeping me on my Vera. My system is now compromised of Hubs controlling devices (with a random rule or two) and then MSR for 99% of the rule logic and Home Assistant for creating nice dashboards (and two MQQT rules for presence.)
FFWD to today and yesterday marked the apparent end of the role my VeraSecure plays in automating my home. One last device to migrate got moved yesterday morning and, like @Alan_F, the remaining life was the two SiteSensors that pull weather data from the Ambient API and the OpenWxMap API to control my HVAC and lighting (I don't use sunrise/sunset, I use solar radiation and it covers me during those times when it's suddenly dark as night in the house due to a storm.)
I'm currently in testing mode of using variable versions of the API calls and so far so good. Just waiting to see if my failover rulesets work should the Ambient API have issues.
I did put the 7.32 beta on the VeraSecure this weekend - not really sure why given how close to EOL it clearly is - but it seemed to actually speed up clicking thru the web UI, so there's that.
@Alan_F - for those virtual devices, as @toggledbits noted, don't forget as a part of your creation process to add it to Maker API - and also to the Alexa and Google apps in the same way if you desire their ability to access them. I still forget to do so from time-to-time.
-
I just ordered my Hubitat, after months of thinking, still trying to bring Vera to life, I got tired of it! I got tired of devices stopping working without any explanation, newer devices with S2 security are super difficult to connect, Zigbee then does not even exist for Vera.
I hope to find a manual for all my devices to remember how to do a factory reset, and add in the new hub.
Well as I'm out of the USA it takes a week to arrive in Panama, so my adventure begins next weekend, and this is dedicated to reading all your tips here. If there are any posts here in this community that you recommend reading, please comment me.
-
@wmarcolin If you're going to get really aggressive with the transfer of devices, just put the Vera in exclusion mode and start hitting them, from the furthest edges of your mesh working your way in toward the hub. The exclude will suffice as a factory reset in most cases. If that's too much effort, just do it for the device you can't find docs for.
-
@toggledbits thanks for the information, I think I will make a change in two weeks for about 130 devices. Adding a device in Hubitat, is automatically recognized in MSR, correct? Or do I have to do some specific procedure?
I can operate with Vera and Hubitat simultaneously, so I will change the MSR rules progressively as well, will operate with both hubs until the conversion is complete.
I see that in the MSR config/reactor.yaml file it is also very simple, just copy a URL.
Ok let's see, the adventure starts in a week
-
Not to go too off-topic here, but are you guys telling me that I could (in theory) buy a Hubitat and pair all of my Philips Hue bulbs directly with that controller instead of having to keep the Hue bridge in my lineup? I'm always looking for garbage to get rid of!
-
When you add the device to Hubs, @wmarcolin, you'll add it into Maker API app. Bounce MSR using
Restart Reactor
underTools
in MSR. When it reconnects it will see the new devices from Hubs as long as you have that integration configured inreactor.yaml
. -
@wmarcolin , @gwp1 describes the correct procedure. The key is that Hubitat's Maker API doesn't automatically publish new devices, so when you add devices, you have to remember to go into Maker API and tell it to publish them, so that Reactor can then see them. As I get more familiar with Hubitat's developer environment, I may look into doing a custom API for Reactor to avoid that, but at the moment, I regard it as a minor annoyance one quickly adapts to.
-
@toggledbits and @gwp1 THANKS!!!!