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!
Ezlo Plus as Network Attached Zigee & Z-Wave Device
-
Hello, all!
For several years now I've had a Vera Edge at home providing all my z-wave needs. I only really use it as a mechanism to get all my devices integrated into home assistant, which is the brains of the operation.
Recently I ordered a few new z-wave devices that have z-wave 700 chips. They work fine with the Vera (albeit with some more advanced features unavailable), but I figure the Vera's days are numbered are there was a really good pre-order deal available on an Ezlo Plus, so I bought one of those too expecting it would be a drop-in replacement for the aging Vera.
It arrived yesterday, and how wrong I was. There isn't any local control at all as best as I can tell, I can't integrate it with Home Assistant, and doing anything at all requires a clunky app and the cloud. Not what I want.
Googling around I found this post on the home assistant community from few years back from someone who killed the running Vera software on their Vera Edge and ran some software to expose the serial Z-Wave chip to the network so Home Assistant could work with it directly. It looks like that idea eventually evolved into a script that automates the process of nuking the Vera.
Despite just barely knowing what I'm doing I'm giving the same approach a shot on the Ezlo Plus. The first barrier was that ser2net wasn't installed and wasn't available in the mios repo, so I've compiled it from source and I just got it running.
So far that's as far as I've gotten, but I'm interested in hearing from the community - especially those of you with more knowledge and experience. I have home assistant running on a server in my basement so the goal of network-attached radios that can be better located in the house is an attractive one, but is there even merit to the approach I'm trying to take? Is there a simpler way to get the Ezlo Plus working with Home Assistant that I'm overlooking? Has anyone else already done this and I'm just reinventing the wheel for no good reason? Should I just chalk the Ezlo up as a poor purchasing decision and get on with my life?
Looking forward to your responses!
-
It would be a lot of workaround and intermediates to go through... You can see that I posted a few things towards the end of that HA thread. The issue is that the zwave700 serial API is very different from the zwave300/500 as far as I know. You will have a hard time getting it to work on another controller. The best recommendation I would have for an HA bridge is to go with hubitat which also supports zwave700. It already has an integration into home assistant.
-
I don't have openLuup. I gave it a try this afternoon, running it in a docker container. I didn't need to set up anything with mqtt, I just used the home assistant Vera integration to connect to openLuup, then used the Vera bridge plugin to connect openLuup to my existing Vera edge, and the Ezlo bridge plugin to connect it to my new Ezlo. There was some odd behaviour with both bridge plugins running at once and the brightness sliders for my dimmer switches don't work quite right, but all my devices show up in Home Assistant with this setup and I'm sure with some tweaking I could get this working. This may be the way to go, so thanks for the recommendation @Elcid!
In the meantime, I've been pursuing my original plan despite what I've got no doubt is excellent advice that you gave me, @rafale77. I started with Zigbee rather than Z-Wave, and it's been a frustrating afternoon. I took a look in
/dev
and the Ezlo folks have helpfully created descriptive symlinks to both the Z-Wave and Zigbee devices so it's obvious which is which right off the bat. I usedlsof
to identify what process was using the device and killed it. It came back to life, but I tracked down the script that was restarting it and killed that too. I found some logs that indicated the zigbee device uses the EZSP protocol and should therefore work with Home Assistant's zigbee integration. All promising stuff. Then I fired upser2net
and... nothing.After a couple of hours trying a bunch of different stuff with no joy I started to suspect that
ser2net
was the problem. It was listening on the port I'd specified just fine, but I couldn't find any evidence that it was connecting to the serial device. I have no idea if I somehow compiled it incorrectly, if I'm using it incorrectly, or if it's not me at all, but nothing I tried worked so instead I compiled and installedsocat
to try instead and...
Working in home assistant!
For anyone wishing to give it a try, the commands I ran on the Ezlo to kill it's build-in zigbee addon and share it over the network were:
ps | grep "/ha-zig" | cut -b1-5 | xargs -t kill socat /dev/ttyS2,raw,echo=1 tcp-listen:3333,reuseaddr,fork
I'll upload the socat
.ipk
that I compiled somewhere and share a link to it when I get a chance. Rebooting the Ezlo brings it back to stock functionality.I haven't tested the stability of all this yet - I haven't even paired any devices - so take it all with a healthy grain of salt, but I'm pleased with my progress so far.
Home Assistant now recommends Z-Wave JS as the way to integrate Z-Wave networks. I've been trying to figure out if they support 700 series chips but I can't tell from the docs. I suspect not, but I'm hoping it will in the not too distant future, and then I'll try and get that working too
-
I have to applaud your resillience! I had read in the socat manual that it could be used that way but just never did it. It makes a lot of sense.
Now since you are very familiar with the vera scenes, devices and automations and that you have already setup openLuup, why not use openLuup as your automation hub? I personally have found it much easier to control and automate than HA and am using HA only as "child device hub" for openLuup for my zigbee and other integration devices. This would enable you to move over all of your vera scenes and plugins... Just an idea (I of course am running my setup this way). I am pretty confident that the zigbee integration to HA through ZHA will have no problem.
Z-Wave JS is in active development and I don't think they support 700 series API at the moment...
-
@rafale77 thanks! I've discovered something else encouraging too. At the top of the Ezlo Z-Wave log is a line that says
Z-Wave stick based on EFR32ZG14 is supported
A quick search reveals the EFR32ZG14 is a silicon labs Z-Wave 700 chip that seems to be pretty ubiquitous, and according to comments on a couple of closed github issues on the Z-Wave JS repo, it seems like it is already supported. That's at least enough motivation for me to want to keep going
I'm definitely going to play around with openLuup some more. I actually don't have any scenes or automations on the Vera, that's all in Home Assistant. HA automations have seen some big improvements recently, but you're right that they're playing catch-up in that regard. I've been considering taking Node-RED for a spin too.
-
Yeah I only hear good things about node red. That's encouraging about zwave-JS. On our side, z-way has added support for it too though I have yet to see the hardware getting sold at the moment. I don't have a huge motivation to migrate to the 700 series on the controller side given how little incremental benefits it offers. I think the long range mode is probably the biggest one and I have no use for it. All the other benefits are really for the devices. Keep us posted on your progress! It may inspire others.
-
I've been tinkering with a ZWave-JS interface for MSR in the background, after having a good start converting my Hass installation to it. It's definitely an improvement on the Hass side, a breath of much-needed fresh air.
-
@toggledbits said in Ezlo Plus as Network Attached Zigee & Z-Wave Device:
I've been tinkering with a ZWave-JS interface
I have been testing a Zooz 700 stick with Zwave-JS. It appears to be working well. I would like to see a interface into MSR. Right now I have devices from Zwave-JS to Hass to MSR.
-
The Zooz stick and the Ezlo share a common Z-Wave chipset. In fact when I added the Ezlo to ZWave-JS it shows up with a product code of ZST10-700, which I believe is the Zooz stick.
So, good news! I have both Z-Wave and Zigbee working in home assistant now, bypassing all the Ezlo software. The home assistant Zigbee integration connects directly to the Ezlo, and for Z-Wave I have ZWave-JS as an intermediary - but that's hass' recommended configuration anyway.
I think I've figured out some initial stability issues I was having as a result of not setting socat up quite right, but don't quote me on that yet, and for some reason the status of the Z-Wave controller shows up as 'Dead' but it doesn't seem to matter? Not sure what that's about. Also if I start hass before the Ezlo is ready then it will never successfully connect - you have to run socat on the Ezlo first, then start Home Assistant. Other than that it seems to work well. Zigbee in particular is more stable and responsive in this configuration than it was on the sonoff zigbee bridge I was previously using in my setup.
Here's how I did all this:
- Using the instructions on the openWrt site, compile socat for the Allwinner H3 SoC (or, if you're feeling trusting, download the binary I already compiled).
- Copy the .ipk to the Ezlo using whatever method you prefer. I used
scp
. Unfortunately you can't download the binary directly to the Ezlo because it doesn't support SSL and I don't have anywhere I can share the file from that doesn't enforce secure connections. - Install it:
opkg install socat_1.7.3.3-1_arm_cortex-a7_neon-vfpv4.ipk
- Kill the running ezlo processes: (One single error at the end about a process that can't be killed because it doesn't exist is expected).
ps | grep "/ha-" | cut -b1-5 | xargs -t kill
- Share the Z-Wave and Zigbee radios over the network using socat:
socat /dev/ttyS1,raw,echo=0 tcp-listen:3333,reuseaddr,keepalive,fork &
socat /dev/ttyS2,raw,echo=0 tcp-listen:3300,reuseaddr,keepalive,fork &
- In Z-Wave JS' ZWave settings under serial port, ignore the choices in the dropdown menu and manually enter
tcp://192.168.0.100:3333
(change the IP to that of your Ezlo) - In Home Assistant's Zigbee integration select a radio type of EZSP and for the serial port enter
socket://192.168.0.100:3300
- ...
- Profit
If you reboot the Ezlo it returns to its stock setup. I think my plan is to write a little script that checks whether the Ezlo processes are running and, if so, kills them and starts socat, then run that script as a cronjob. @rafale77, do you have any advice on a better approach based on your Nuke-Vera work? I don't want to nuke the Ezlo and do anything irreversible necessarily, but I'm also a little concerned that my plan might be leaving the thing functional enough to one day download a firmware update that breaks what I'm doing.
If it's helpful to anyone, I also compiled binaries for ser2net (I never got it to work) and Nano.