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 or not vera?
-
I bought the Pi!
I'm right there now
#wget https://github.com/akbooer/openLuup/raw/master/Utilities/openLuup_install.luaFor some reason he writes to me that:
openLuup_install.lus: permission denied.What do I have to do now?
-
It was key !!
"saved"
Thanks.
I'm going on my way ... -
one more problem ...
the installation stalled here.pi@raspberrypi:/etc/cmh-ludl $ sudo lua5.1 openLuup_install.lua openLuup_install 2019.02.15 @akbooer getting openLuup version tar file from GitHub branch master... un-zipping download files... mv: 'openLuup-master/openLuup/'-t can't remove here: './openLuup': The directory is not empty getting dkjson.lua... creating required files and folders initialising... downloading and installing AltUI... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 29170 100 29170 0 0 90309 0 --:--:-- --:--:-- --:--:-- 90309 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 6570 100 6570 0 0 32364 0 --:--:-- --:--:-- --:--:-- 32364 lua5.1: openLuup/init.lua:291: openLuup - is another copy already running? Unable to start HTTP server on port 3480 stack traceback: [C]: in function 'error' openLuup/init.lua:291: in main chunk [C]: ? openLuup downloaded, installed, and running... visit http://192.168.0.159:3480 to start using the system pi@raspberrypi:/etc/cmh-ludl $ lua5.1: openLuup/init.lua:291: openLuup - is another copy already running? Unable to start HTTP server on port 3480 stack traceback: [C]: in function 'error' openLuup/init.lua:291: in main chunk [C]: ? "If I try to open it in a browser the message is:
"This XML file does not appear to have any style information associated with it. The document tree is shown below."What should I do?
-
@krisztianszabo said in Vera or not vera?:
openLuup - is another copy already running?
It means exactly what it says.
Try accessing it with AltUI URL. If it’s an old copy running, you can abort it with the exit command, as described in the documentation...
http://openLuupIP:3480/data_request?id=exit -
with openluup ip, the browser prints the following (in black on a red background):
"Waiting Initial Data"
... but nothing has happened for a long time ... -
Look for errors in the log file.
You should be able to access the native openLuup UI with
http://openLuupURL:3480/openLuup/...in order to access the logs.
The most common issue here is that your computer locale setting specifies a language which AltUI does not implement. The error log should clarify this. A workaround is to copy the English language file to one with your country extension OR set your language to one which is implemented.
-
Language really was the problem. Thanks.
I got past that, but here's another one ....
The two files were born in the right places (etc / cmh-ludl and systemd / system) with good content.
When I type that:pi@raspberrypi:/etc/cmh-ludl $ sudo systemctl enable openLuup
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified. -
@Akbooer
I copied this from the startup_log.
Something was not filled properly?
Could the above error message be the cause?2020-11-05 15:35:49.788 openLuup.init:: Cjson not installed - using openLuup.json.Lua.decode() instead
2020-11-05 15:35:49.789 luup.create_device:: [1] D_ZWaveNetwork.xml / / ()
2020-11-05 15:35:49.789 openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
2020-11-05 15:35:49.804 luup.create_device:: [2] D_openLuup.xml / I_openLuup.xml / D_openLuup.json (openLuup)
2020-11-05 15:35:49.804 openLuup.init:: loading configuration user_data.json
2020-11-05 15:35:49.804 openLuup.userdata:: loading user_data json...
2020-11-05 15:35:49.812 luup.variable_set:: 2.openLuup.HouseMode was: EMPTY now: 1 #hooks:0
2020-11-05 15:35:49.812 openLuup.userdata:: loading rooms...
2020-11-05 15:35:49.812 openLuup.userdata:: ...room loading completed
2020-11-05 15:35:49.812 openLuup.userdata:: loading devices...
2020-11-05 15:35:49.813 luup.create_device:: [1] D_ZWaveNetwork.xml / / ()
2020-11-05 15:35:49.813 openLuup.chdev:: ERROR: unable to read XML file I_ZWave.xml
2020-11-05 15:35:49.908 openLuup.scheduler.sandbox:: device 3 defined 'string.starts' (a function value)
2020-11-05 15:35:49.908 openLuup.scheduler.sandbox:: device 3 defined 'string.altui_split' (a function value)
2020-11-05 15:35:49.908 openLuup.scheduler.sandbox:: device 3 defined 'string.template' (a function value)
2020-11-05 15:35:49.908 openLuup.scheduler.sandbox:: device 3 defined 'string.trim' (a function value)
2020-11-05 15:35:49.909 luup.create_device:: [3] D_ALTUI.xml / I_ALTUI.xml / D_ALTUI_UI7.json (urn:schemas-upnp-org:device:altui:1)
2020-11-05 15:35:49.917 luup.create_device:: [4] D_AltAppStore.xml / I_AltAppStore.xml / D_AltAppStore.json (urn:schemas-upnp-org:device:AltAppStore:1)
2020-11-05 15:35:49.917 openLuup.userdata:: loading scenes...
2020-11-05 15:35:49.917 openLuup.userdata:: number of scenes = 0
2020-11-05 15:35:49.917 openLuup.userdata:: ...scene loading completed
2020-11-05 15:35:49.917 openLuup.userdata:: loading installed plugin info...
2020-11-05 15:35:49.917 openLuup.userdata:: [openLuup] openLuup (20.5.22)
2020-11-05 15:35:49.917 openLuup.userdata:: [AltAppStore] Alternate App Store (20.3.30)
2020-11-05 15:35:49.917 openLuup.userdata:: [VeraBridge] VeraBridge (not.installed)
2020-11-05 15:35:49.917 openLuup.userdata:: [8246] Alternate UI (GitHub.master)
2020-11-05 15:35:49.917 openLuup.userdata:: [Z-Way] Z-Way (not.installed)
2020-11-05 15:35:49.918 openLuup.userdata:: [Arduino] MySensors (not.installed)
2020-11-05 15:35:49.918 openLuup.userdata:: ...user_data loading completed
2020-11-05 15:35:49.918 openLuup.init:: running openLuup_STARTUP
2020-11-05 15:35:49.918 luup_log:0: startup code completed
2020-11-05 15:35:49.918 openLuup.init:: init phase completed
2020-11-05 15:35:49.918 :: openLuup LOG ROTATION :: (runtime 0.0 days) -
The main problem is one post up. I'm still standing on "openLuup Start on Bootup Lua", unfortunately.
(I was just guessing why it didn't work) -
Hello @akbooer,
I’ve been working on the system a lot in recent days.
(altui starts with "pi", I have the tools with all the icons and also the rooms, language file copied. I'm still in the process of installing the vera plugins and moving the reactor scenes (sensors).1, What I noticed:
- startup lua error:
2020-11-09 09: 24: 00.644 openLuup.init :: Cjson not installed - using openLuup.json.Lua.decode () instead
2, I have read the openluup manual you wrote several times unfortunately, yet one or two things are not clear.
Settings for the user_data.json file:
-
the actual location of the backup and log directory on the pi must be specified. Right?
-
"ditto Lines and Versions - number of lines before log rotation, number of versions saved"
i don't know what to change here .... -
"openLuup.UserData.Checkpoint - number of minutes between each user_data.json save."
here the number 60 should be changed to 6?
3, Altui for some reason identifies my wife's name in the system. he writes that
"unregistered version for" my wife's login name "Why do I log in with this? -
@krisztianszabo said in Vera or not vera?:
2020-11-09 09: 24: 00.644 openLuup.init :: Cjson not installed - using openLuup.json.Lua.decode () instead
It's not an error, it's just an information message. It's an extension to the system that you don't need.
@krisztianszabo said in Vera or not vera?:
Settings for the user_data.json file
Nothing needs changing here – all the defaults are just fine. What problem are you trying to solve?
@krisztianszabo said in Vera or not vera?:
Altui for some reason identifies my wife's name in the system.
Do you have VeraBridge up and running and linked to your Vera yet? openLuup receives its username information from Vera via the bridge. There is a well-known problem with AltUI/Vera in the case that there are multiple registered users, since it's not clear which one will be picked by Altui to check the licence. This is not an openLuup issue unless you are trying to run without an attached Vera. In which case I can provice a licence key, if you are actually licensed with AltUI, and you send me a screen snapshot of your AltUI footer, showing the licence information.
-
Thank you for your response @akbooer.
"Nothing needs changing here – all the defaults are just fine. What problem are you trying to solve?"
I'm following the openluup briefing.
I found there: "Appendix: Configuring key openLuup parameters at Startup"From this I thought something had to be changed in user_data.json.
Don't I have to be change someting there?
Or don't have to?
I'm starting to lose a little bit of the yarn between a lot of information ... sorry. -
"Do you have VeraBridge up and running and linked to your Vera yet? openLuup receives its username information from Vera via the bridge. There is a well-known problem with AltUI/Vera in the case that there are multiple registered users, since it's not clear which one will be picked by Altui to check the licence. This is not an openLuup issue unless you are trying to run without an attached Vera. In which case I can provice a licence key, if you are actually licensed with AltUI, and you send me a screen snapshot of your AltUI footer, showing the licence information."
VeraBridge, installed, bridge, running, connection good, devices taken over.
I'm trying to run with Vera for now and I don't have an Altui license. Then it's so good. Right?
-
@krisztianszabo said in Vera or not vera?:
I found there: "Appendix: Configuring key openLuup parameters at Startup"
This is entirely optional, and just describes a way to change things if you want to... but you don't, so nothing to do here!
I'm sorry the manual is perhaps not as clear as it could be. It has rather grown over time as features got added, so the organisation of it is not ideal. I did try to put everything necessary in the early chapters and additional documentation in the Appendices.
@krisztianszabo said in Vera or not vera?:
VeraBridge, installed, bridge, running, connection good, devices taken over.
That's great.
@krisztianszabo said in Vera or not vera?:
I'm trying to run with Vera for now and I don't have an Altui license. Then it's so good. Right?
OK, that explains it. If you want to get rid of the message, then you need to contact @amg0 about a licence. You should ask for it in the login name that it is trying to use, in this case, your wife's. Then openLuup will pick up this information too, and if you keep Vera attached all will be well. If, someday, you remove Vera, having transferred all your ZWave devices to ZWay, say, then you will need a licence key from me to enable you to keep your AltUI licence running, but openLuup, itself, requires no licence.
