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 Alexa Plugin 7.32
-
@therealdb said in Vera Alexa Plugin 7.32:
@catmanv2 it’s in the Amazon doc I linked in readme. Also, sounds are very specific and you could send them but not in the same command with voice.
Thanks. I did look, I promise. I'll look again!<edit> Got it, eventually! Thanks.
C -
@librasun said in Vera Alexa Plugin 7.32:
@catmanv2 said in Vera Alexa Plugin 7.32:
But can't for the life of me get the sound effects:
Funny, that's one thing I've got working no problem:
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e sound:amzn_sfx_trumpet_bugle_04 -d 'Living Room'"}, 344)Ahh per the Guru's words. Won't work with the speech. Thanks
C
-
I did some more digging, and discovered that:
WHEN I RUN THIS LUA
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","RunCommand",{Command="-e speak:'what is the temperature outside' -d 'Living Room'"}, 344)Alexa speaks the sentence and VeraAlexa shows this LastResponse: "sending cmd:speak:what is the temperature outside to dev:Living_Room"
WHEN I RUN THIS LUA
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1", "Say", {Text="what is the temperature outside", Repeat = 1}, 344)Alexa DOES NOT speak the sentence and VeraAlexa shows this LastResponse: "sending cmd:speak:<s>what is the temperature outside</s><break time="0s" /> to dev:Living_Room "
Instead she utters, "Sorry, I'm having trouble accessing the Simon Says ??? Skill right now." then a bong tone sounds. Weird!Thus, I'll continue using the 1st construct to have Alexa speak sentences.
INSIGHT: I honestly believe the "Simon Says ???" Alexa mentions has to do with an error parsing <SSML> tags!!
-
I tried to run that command verbatim(!) -- changing only my device # -- and get the same spoken "Sorry..." error as always. Really driving me bonkers!! Would love to use SSML in my workflow, but until this gets resolved, no go. Thanks for the suggestion(s), of course. I'm sure it's ME, not ALEXA.
-
Fun times. I took my own advice and completely removed VeraAlexa plug-in from my Vera Plus (making sure there were no hidden devices lurking, then executing a device > remove command via HTTP request in my browser). Rebooted, restarted MSR (so it would forget about deleted Entity), copied ZIP from Github, loaded files onto Vera, restarted Luup engine, created Device (it starts hidden!), restarted Luup engine again, see device in UI (no name), restart Luup yet again, see "Alexa" device, says "Configured=1" (yay!), update its "DefaultEcho" variable, etc., restart MSR in Docker, hard refresh all browsers.
And I'm back. Now HERE is the fun part... SOME of the "Say" commands work now, some ALMOST do, and others still do not.
WORKS // says "Hello from Vera Alexa"
luup.call_action("urn:micasaverde-com:serviceId:Sonos1", "Say", {Text="Hello from Vera Alexa"}, 345)ALMOST WORKS // says "Domain" and stops
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<amazon:domain name="conversational">Hello from Alexa</amazon:domain>', Volume=10, Repeat = 1}, 345)DOES NOT WORK // says "Sorry..." error message
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<voice name="Raveena">Hello from Vera Alexa</voice>', Volume=40,GroupZones="Living Room"}, 345)I must be a bad person.
-
Yep, tried that. Changed GroupZones= to "Sonos Beam" (name of my Alexa-enabled Sonos device also known as "Living Room"), and still... silence.
But thanks for the tip to try!Oh wait! You're saying try piping the command to the SONOS service instead of the 'bochicchio' one... hold on... gonna try.
Answer: NOPE. Still same "Sorry, I'm having trouble accessing ___ skill right now."
-
@librasun said in Vera Alexa Plugin 7.32:
Fun times. I took my own advice and completely removed VeraAlexa plug-in from my Vera Plus (making sure there were no hidden devices lurking, then executing a device > remove command via HTTP request in my browser). Rebooted, restarted MSR (so it would forget about deleted Entity), copied ZIP from Github, loaded files onto Vera, restarted Luup engine, created Device (it starts hidden!), restarted Luup engine again, see device in UI (no name), restart Luup yet again, see "Alexa" device, says "Configured=1" (yay!), update its "DefaultEcho" variable, etc., restart MSR in Docker, hard refresh all browsers.
And I'm back. Now HERE is the fun part... SOME of the "Say" commands work now, some ALMOST do, and others still do not.
WORKS // says "Hello from Vera Alexa"
luup.call_action("urn:micasaverde-com:serviceId:Sonos1", "Say", {Text="Hello from Vera Alexa"}, 345)ALMOST WORKS // says "Domain" and stops
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<amazon:domain name="conversational">Hello from Alexa</amazon:domain>', Volume=10, Repeat = 1}, 345)DOES NOT WORK // says "Sorry..." error message
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<voice name="Raveena">Hello from Vera Alexa</voice>', Volume=40,GroupZones="Living Room"}, 345)I must be a bad person.
I forgot entirely about the default echo. Mine was 3 floors away this morning.I don't have a Sonos so can't test that bit but
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<amazon:domain name="conversational">Hello from Alexa</amazon:domain>', Volume=10, Repeat = 1}, 22)Works
luup.call_action("urn:bochicchio-com:serviceId:VeraAlexa1","Say", {Text='<voice name="Raveena">Hello from Vera Alexa</voice>', Volume=40}, 22)Works.
I am not on Vera though. Openluup with full JQ AFAIK
C
-
Perhaps my never having used OpenLuup, that could be the key differentiator between my setup and yours and @therealdb 's?
I'm on a stock Vera Plus running 7.32 firmware. I'm sending all Lua commands via MSR for testing purposes. -
-
@elcid said in Vera Alexa Plugin 7.32:
@librasun Have you tried to install JQuery on the vera, it's is now available with 7.32
Uh oh, I thought "jq" was a package included with 7.32? I'd scoured @therealdb 's notes and ReadMe, seeing references to "jq" (never once thinking that meant "JQuery").
How does one "install" "jQuery" on Vera??
-
@librasun The plug-in will take care of it. So, just set configured to 0 and it will install it.
I've had a very busy week, but tomorrow I'll have more time to re-try from scratch. Keep in mind that this is using some internal amazon stuff and the chances that they changed something is high. Anyway, it should not create <s>... unless you have announcements enabled. I'll take a deeper look tomorrow. I've tested with 7.32 beta, but not this build, and it worked, but I've not tested all the possibile variants.
-
-
@pabla said in Vera Alexa Plugin 7.32:
Also if anyone in the future has Cookie issues, you must turn of JavaScript in Firefox to get the correct cookie file, I didn't and it wasn't working.
Does this apply to Chrome as well? And if so, do you mean "Disable Javascript" for all sites, forever? Or just while VeraAlexa plug-in is configuring itself?
(Because I did none of that.
-
@librasun I am not sure if it applies to chrome but I assume it would, because when you disable JavaScript and login you get the Captcha login screen (which is what you are trying to bypass).
Yes temporarily disable JavaScript until you have got the cookie file.
-
@pabla I never turn off JS, I use Export Cookies Addon to export to a txt file. I will add i do it on Android Firefox I login to layala.amazon.co.uk. Once logged in i export amazon.co.uk to text file. I then copy the contents to .alexa.cookie
