-
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?
-
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...
-
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!
-
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.
-
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 - GitHub - rafale77/Nuke-Vera: Script to neuter the vera and broadcast its zwave and zigbee serial ports
-
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!
-
Recently I have been getting constant reloads on my Vera Plus running the latest 7.32 beta build. It usually starts after a 3-4 day Luup uptime and the reloads start at around 5am local time and keep going every 30 mins until I physically restart my Vera Plus (unplugging and plugging it back in). Right before a reload I see on the status bar above the modes on the homepage "cannot write user data" then after a few minutes a reload occurs. Looking into the logs I have seen mention of 03 06/21/21 8:53:18.102 JobHandler_LuaUPnP::Reload: low memory Critical 1 m_bCriticalOnly 0 dirty data 1 running 1 <0x76aa7520> almost every single time a reload happens. I have attached logs from 2 instances this morning where a reload happened. I have noticed that the OpenSprinkler plugin has been very chatty even though I have set debugging to 0, is that what is filling up temp log system?
01 06/21/21 8:45:58.123 IOPort::Connect connect -1 192.168.8.43:23 <0x6a148520> 02 06/21/21 8:45:59.031 UserData::CommitToDatabase data size 1244271 1244271 <0x7662b520> 01 06/21/21 8:45:59.333 UserData::WriteUserData saved--before move File Size: 234865 save size 234865 <0x7662b520> 02 06/21/21 8:45:59.333 UserData::TempLogFileSystemFailure start 0 <0x7662b520> 02 06/21/21 8:45:59.334 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x7662b520> 02 06/21/21 8:45:59.334 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x7662b520> 01 06/21/21 8:45:59.341 UserData::WriteUserData failed File Size: 234865 save size 234902 <0x7662b520> 02 06/21/21 8:45:59.342 UserData::TempLogFileSystemFailure start 1 <0x7662b520> 02 06/21/21 8:45:59.344 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x7662b520> 01 06/21/21 8:45:59.632 UserData::WriteUserData failed result:1 size2:234865 vs 234865 <0x7662b520> 02 06/21/21 8:45:59.632 UserData::TempLogFileSystemFailure start 1 <0x7662b520> 02 06/21/21 8:45:59.634 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x7662b520> 02 06/21/21 8:45:59.635 UserData::TempLogFileSystemFailure start 0 <0x7662b520> 02 06/21/21 8:45:59.635 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x7662b520> 02 06/21/21 8:45:59.636 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x7662b520> 06 06/21/21 8:45:59.636 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusID was: 1 now: 2 #hooks: 0 upnp: 0 skip: 0 v:0x1099d38/NONE duplicate:0 <0x7662b520> 06 06/21/21 8:45:59.637 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusText was: OK now: Resetting ZWave Network #hooks: 0 upnp: 0 skip: 0 v:0x1a02d48/NONE duplicate:0 <0x7662b520> 06 06/21/21 8:45:59.637 Device_Variable::m_szValue_set device: 2 service: urn:micasaverde-com:serviceId:ZigbeeNetwork1 variable: NetStatusID was: 0 now: 3 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7662b520> 06 06/21/21 8:45:59.638 Device_Variable::m_szValue_set device: 2 service: urn:micasaverde-com:serviceId:ZigbeeNetwork1 variable: NetStatusText was: OK now: GET_LANG(resetting_zigbee_network,Resetting Zigbee Network) #hooks: 0 upnp: 0 skip: 0 v:0x12b9e60/NONE duplicate:0 <0x7662b520> 01 06/21/21 8:45:59.648 RAServerSync::SendAlert notification lost quit 1 device 50002761 servers:vera-us-oem-event12.mios.com/vera-us-oem-event11.mios.com for time 23822220 type 7 code user_data <0x7642b520> 02 06/21/21 8:46:01.381 UserData::CommitToDatabase data size 1244349 1244349 <0x770dc320> 01 06/21/21 8:46:01.675 UserData::WriteUserData saved--before move File Size: 234875 save size 234875 <0x770dc320> 02 06/21/21 8:46:01.675 UserData::TempLogFileSystemFailure start 0 <0x770dc320> 02 06/21/21 8:46:01.676 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x770dc320> 02 06/21/21 8:46:01.676 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x770dc320> 01 06/21/21 8:46:01.680 UserData::WriteUserData failed File Size: 234875 save size 234865 <0x770dc320> 02 06/21/21 8:46:01.680 UserData::TempLogFileSystemFailure start 1 <0x770dc320> 02 06/21/21 8:46:01.682 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x770dc320> 01 06/21/21 8:46:01.940 UserData::WriteUserData failed result:1 size2:234875 vs 234875 <0x770dc320> 02 06/21/21 8:46:01.941 UserData::TempLogFileSystemFailure start 1 <0x770dc320> 02 06/21/21 8:46:01.943 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x770dc320> 02 06/21/21 8:46:01.944 UserData::TempLogFileSystemFailure start 0 <0x770dc320> 02 06/21/21 8:46:01.945 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x770dc320> 02 06/21/21 8:46:01.945 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x770dc320> 50 06/21/21 8:46:03.102 luup_log:1304: VeraOpenSprinkler[1.50]: [updateFromController] error: false - nil - nil <0x72581520> 01 06/21/21 8:46:05.210 Main WatchDogRoutine: blocked - terminating 1 <0x695de520> 02 06/21/21 8:46:05.211 Dumping 40 locks <0x695de520> 02 06/21/21 8:46:05.211 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.211 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.211 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.211 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.212 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.212 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.212 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.212 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.212 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.212 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.213 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.213 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.213 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.213 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.213 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.213 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.214 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.214 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.214 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.214 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.214 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.214 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.215 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.215 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.215 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.215 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.215 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.215 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.216 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.216 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.216 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.216 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.216 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.216 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.217 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.217 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.217 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.217 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.217 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.217 OL: (0xbbc560) (>100746) Variable JobHandler_LuaUPnP.cpp l:9817 time: 4:00:00p (1624290365 s) thread: 0x6f948520 Rel: Y Got: Y <0x695de520> 02 06/21/21 8:46:05.217 finished check for exceptions <0x695de520> 02 06/21/21 8:46:05.218 OL: (0xbbc560) (>100751) Variable JobHandler_LuaUPnP.cpp l:9817 time: 4:00:00p (1624290365 s) thread: 0x6d948520 Rel: Y Got: Y <0x695de520> 2021-06-21 08:46:05 - LuaUPnP Terminated with Exit Code: 137 03 06/21/21 8:53:18.102 JobHandler_LuaUPnP::Reload: low memory Critical 1 m_bCriticalOnly 0 dirty data 1 running 1 <0x76aa7520> 01 06/21/21 8:53:18.103 luup_log:901: Tesla Car_error: Monitor awake state, failed #400 HTTP/1.1 400 BAD REQUEST !! <0x72ffd520> 02 06/21/21 8:53:18.482 UserData::CommitToDatabase data size 1244185 1244185 <0x76aa7520> 01 06/21/21 8:53:18.781 UserData::WriteUserData saved--before move File Size: 234865 save size 234865 <0x76aa7520> 02 06/21/21 8:53:18.781 UserData::TempLogFileSystemFailure start 0 <0x76aa7520> 02 06/21/21 8:53:18.781 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x76aa7520> 02 06/21/21 8:53:18.782 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x76aa7520> 01 06/21/21 8:53:18.787 UserData::WriteUserData failed File Size: 234865 save size 234875 <0x76aa7520> 02 06/21/21 8:53:18.787 UserData::TempLogFileSystemFailure start 1 <0x76aa7520> 02 06/21/21 8:53:18.789 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x76aa7520> 01 06/21/21 8:53:18.813 IOPort::Connect connect -1 192.168.8.43:23 <0x6a7c4520> 01 06/21/21 8:53:19.020 UserData::WriteUserData failed result:1 size2:234865 vs 234865 <0x76aa7520> 02 06/21/21 8:53:19.020 UserData::TempLogFileSystemFailure start 1 <0x76aa7520> 02 06/21/21 8:53:19.023 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x76aa7520> 02 06/21/21 8:53:19.027 UserData::TempLogFileSystemFailure start 0 <0x76aa7520> 02 06/21/21 8:53:19.028 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x76aa7520> 02 06/21/21 8:53:19.028 UserData::TempLogFileSystemFailure 0 res:0 (null) <0x76aa7520> 06 06/21/21 8:53:19.029 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusID was: 1 now: 2 #hooks: 0 upnp: 0 skip: 0 v:0x14bad80/NONE duplicate:0 <0x76aa7520> 06 06/21/21 8:53:19.029 Device_Variable::m_szValue_set device: 1 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: NetStatusText was: OK now: Resetting ZWave Network #hooks: 0 upnp: 0 skip: 0 v:0x1e23b10/NONE duplicate:0 <0x76aa7520> 06 06/21/21 8:53:19.033 Device_Variable::m_szValue_set device: 2 service: urn:micasaverde-com:serviceId:ZigbeeNetwork1 variable: NetStatusID was: 0 now: 3 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76aa7520> 01 06/21/21 8:53:19.040 RAServerSync::SendAlert notification lost quit 1 device 50002761 servers:vera-us-oem-event12.mios.com/vera-us-oem-event11.mios.com for time 20546340 type 7 code user_data <0x76ca7520> 06 06/21/21 8:53:19.044 Device_Variable::m_szValue_set device: 2 service: urn:micasaverde-com:serviceId:ZigbeeNetwork1 variable: NetStatusText was: OK now: GET_LANG(resetting_zigbee_network,Resetting Zigbee Network) #hooks: 0 upnp: 0 skip: 0 v:0x16dadc0/NONE duplicate:0 <0x76aa7520> 02 06/21/21 8:53:20.807 UserData::CommitToDatabase data size 1244263 1244263 <0x77759320> 01 06/21/21 8:53:21.081 UserData::WriteUserData saved--before move File Size: 234875 save size 234875 <0x77759320> 02 06/21/21 8:53:21.081 UserData::TempLogFileSystemFailure start 0 <0x77759320> 02 06/21/21 8:53:21.116 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x77759320> 02 06/21/21 8:53:21.117 UserData::TempLogFileSystemFailure 699 res:1 -rw-r--r-- 1 root root 504 Jun 26 2017 /etc/cmh/user_data.json.luup.lzo -rw-r--r-- 1 root root 234865 Jun 21 08:53 /etc/cmh/user_data.json.lzo -rw-r--r-- 1 root root 234996 Jun 21 08:11 /etc/cmh/user_data.json.lzo.1 -rw-r--r-- 1 root root 234930 Jun 21 08:02 /etc/cmh/user_data.json.lzo.2 -rw-r--r-- 1 root root 234968 Jun 21 07:47 /etc/cmh/user_data.json.lzo.3 -rw-r--r-- 1 root root 234658 Jun 21 07:11 /etc/cmh/user_data.json.lzo.4 -rw-r--r-- 1 root root 234909 Jun 21 06:50 /etc/cmh/user_data.json.lzo.5 -rw-r--r-- 1 root root 234875 Jun 21 08:53 /etc/cmh/user_data.json.lzo.new <0x77759320> 02 06/21/21 8:53:21.228 UserData::TempLogFileSystemFailure start 0 <0x77759320> 02 06/21/21 8:53:21.259 UserData::TempLogFileSystemFailure (not failure, only WriteUserData) 0 <0x77759320> 02 06/21/21 8:53:21.259 UserData::TempLogFileSystemFailure 610 res:1 -rw-r--r-- 1 root root 504 Jun 26 2017 /etc/cmh/user_data.json.luup.lzo -rw-r--r-- 1 root root 234875 Jun 21 08:53 /etc/cmh/user_data.json.lzo -rw-r--r-- 1 root root 234865 Jun 21 08:53 /etc/cmh/user_data.json.lzo.1 -rw-r--r-- 1 root root 234996 Jun 21 08:11 /etc/cmh/user_data.json.lzo.2 -rw-r--r-- 1 root root 234930 Jun 21 08:02 /etc/cmh/user_data.json.lzo.3 -rw-r--r-- 1 root root 234968 Jun 21 07:47 /etc/cmh/user_data.json.lzo.4 -rw-r--r-- 1 root root 234658 Jun 21 07:11 /etc/cmh/user_data.json.lzo.5 <0x77759320> 06 06/21/21 8:53:21.465 Device_Variable::m_szValue_set device: 2 service: urn:micasaverde-com:serviceId:ZigbeeDevice1 variable: PendingRemoveDevices was: 0024460000144655-01d8,0024460000146120-a155,00244600001467ad-a538 now: 0024460000144655-01d8,0024460000146120-a155,00244600001467ad-a538 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x77759320> 06 06/21/21 8:53:21.469 Device_Variable::m_szValue_set device: 2 service: urn:micasaverde-com:serviceId:ZigbeeDevice1 variable: UnknownDevices was: now: #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x77759320> 03 06/21/21 8:53:22.100 LuaUPNP: ending <0x77759320> 2021-06-21 08:53:22 - LuaUPnP Terminated with Exit Code: 0``` -
Hi,
Some devices, I don't know why, stay in a tripped state after the trigger has already closed.
Let me try to explain better.
A door sensor is tripped when it opens the door, for some reason it does not go back to an Untripped state when it closes. Or a motion sensor likewise, arms with a movement, and then does not disarm even though there is no more presence to justify being armed.
Is it possible by some command to make the device reevaluate its state? If the door was closed, and it is still indicating open, reevaluate and put the correct state of closed door?
Thanks.
-
I have 6 stations in the Open Sprinkler web page/app, however after installing the Vera plugin, only 2 stations appear as Vera devices. I have uninstalled and re-installed, but same result.
I have 3 programs in Open Sprinkler and all of them show up in Vera.
Not sure what I need to do for the other stations to show up as devices in Vera.
Note: I installed the plugin using the Vera apps listing by simply clicking the 'Install' button.
Any help you can provide would be much appreciated @therealdb
Thanks,
Chris -
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!
-
First I want to say thank you to this group. You have given me ideas and help along the HA path for a long time.
I'm an old Vera user and planning to decouple from MIOS cloud now or after 7.32 but I'm stuck at how to push messages out.
I'm using Reactor and Scenes for Vera native messaging. What's a good solution going forward?Also want to mention that after reading the Decoupling document I have built a NTP GPS server on a Pi3B and enjoyed learning more about Linux along the way. I have it stabilized after learning 100 different ways.
Thanks
-
Hello Everyone -
Can someone point me in the proper direction of doing a Vera (Secure) backup?
Specifically, I'm worried about a controller failure and unable to source a new one where I could just use the included backup facilities.
I'm considering staying on Vera a little longer to see what happens with Ezlo (especially around easy migrations).
I know I can manually run backups from the UI but wondering if there's a more "standard" method that would allow me to move to another platform if required. This would require me to pull my (important definition, I feel. This shouldn't be a secret) encryption key off of the Vera as part of the backup - so any pointers there would be helpful as well.
Neighbour node setting
-
To answer @sdtoddl who emailed me asking how to manually force neighbor node setting on the vera, I don’t think it is possible with the UI.
The solution is actually to trigger a neighbor node update on the given device and all the devices located between that said device and the controller.
The vera deals with this by running multiple repeated (nightly) network heals which is not very efficient and causes it to frequently have unexpected network breakdowns and surprises good (some devices with problems get fixed) and bad (some devices which used to work stop working). It also takes down the entire network when it does it. One can however manually trigger neighbor node updates on the vera through the device’s advanced menu.To go to the next level, this data, the network node list is actually not recorded in the host controller firmware but in the non volatile memory of the zwave chip both on the controller and on the devices. It is therefore independent of the platform you use and can’t be set by the host. One can only ask the zwave chip on the device to run a survey and then inform the controller’s zwave chip of what it has found.
-
Thank you for responding. It is frustrating that Vera either gives you an error when you select something on the UI that is no longer supported and/or they even allow you to do it when it isn’t supported.
On the device that is currently unreachable, the error on the UI is, “Can’t Detect Device.” Am I suppose to trigger the node update on the device I can’t reach on that specific device or under Settings -> Zwave settings -> Advanced -> Update Neighbor Nodes?
On all the devices, under Advanced -> Neighbors, there is an edit button on the UI. What does this do if anything if I edit the Neighbors on the device I can’t reach or on a device really close to the device the controller can reach? My plan was to manually tell a device that the controller can’t reach who isn’t neighbors were or a device the controller can reach put in the device that is currently unreachable.
-
@sdtoddl said in Neighbour node setting:
On the device that is currently unreachable, the error on the UI is, “Can’t Detect Device.” Am I suppose to trigger the node update on the device I can’t reach on that specific device or under Settings -> Zwave settings -> Advanced -> Update Neighbor Nodes?
Yes in short but do it from the controller towards your thermostat, one device at a time, leaving a good 10 minutes between devices.
On all the devices, under Advanced -> Neighbors, there is an edit button on the UI. What does this do if anything if I edit the Neighbors on the device I can’t reach or on a device really close to the device the controller can reach? My plan was to manually tell a device that the controller can’t reach who isn’t neighbors were or a device the controller can reach put in the device that is currently unreachable.
This does nothing. The vera UI is a host controller, it can only ask the zwave chips on the network to update nodes, it cannot impose a neighbor on a node as far as I know.
-
This what bothers me about Vera. There is no clear directions or even an FAQ on how to fix things. They shouldn’t allow you to edit neighbors if it does nothing. How hard would it be for them to remove the edit function on that one line of the UI! It could be such a great product if they would simply make a few changes.
-
The device I am adding is a CT100 battery operated thermostat. I moved my controller close to it when I paired it. I wonder if I should have did the update network neighbors on the close switched before I moved my controller back to its normal place in the house. As soon as I moved the controller, the thermostat was no longer reachable.
-
Does update neighbors even work anymore with the individual devices? I select the individual device (light switch). The Device Options -> Update Neighbors. It says that it is updating them but I am not seeing anything on top of the UI.
In Settings -> Logs -> I have Show Polling and Show Individual Jobs checked. -
Well honestly, it is such a simple zwave level command that I would be surprised if the update neighbor node does not work. It should be the same command being used for network heals.
The command takes time, that’s why I said you need to wait a good 10min before moving to the next step. The process is also handled by the zwave chip and not by the vera firmware. It is possible that the vera gets bogged down and reloads in the meantime, potentially interrupting the process but it normally shouldn’t. Just be patient with it. Since it is a battery powered device, do you know by any chance if it is a FLiRS type? I assume that it should be since it should be always ready to receive a command from the controller.
If it isn’t then you will need to wakeup the device while the neighbor node update is underway... but I doubt it is the case.Now the real brute force solution to all of these problems is to get rid of the vera and migrate to a less obscur and buggy platform... In the meantime, I can’t recommend at least moving all your scenes and plugins to openluup.
-
I am not sure. It is the Radio Thermostat CT100. It isn’t Zwave Plus.
https://2gig.com/wp-content/uploads/2015/12/CT100-Operation-Guide.pdfLike you said, since it is always ready to accept commands to change the temperature, I suspect it is.
I liked the user interface and that is why I chose it. Plus, this location doesn’t have a C wire so I had to do battery. It definitely works better if you have a C wire and can then pair it without batteries.
I tried doing what you said and it didn’t work. What bugs me is I even did the update neighbors on the device that is unreachable gave me a “success.” Clearly, it wasn’t a success because the device is not even reachable so it couldn’t even try.
Any other suggestions? Should I try doing a update network neighbors in the Zwave settings on the controller for the whole system?
I spoke to a tech support person on Friday and told me there is no way to update the network neighbors and the system does it automatically at 1 or 2 am.
I question if that was really accurate. Again, if it was, the they should remove update network neighbor options from the UI on all the devices and in the Zwave setting for the controller.
So frustrating because these things are difficult to change. They need to rename the product Almost. -
The tech support is talking about the idiotic nightly heal happening at 2am if you don’t stop it and almost never finished on my network because it was so large. It is a great function for a 10 node network with no battery operated device but will start stuttering for anything more, requiring multiple retries and therefore many days to complete, crashing the system a few times on the way.
The update neighbor node on the vera zwave menu should trigger exactly the same action. You can try that. If they broke the individual device neighbor node update, then I don’t know. Things like that is why I moved to z-way... I can update neighbor nodes on any node I want at any time I want... and watch the progress and outcome while it is doing it. -
Thank you again for all your help.
This shouldn’t be rocket science. This system only has approximately 11 devices. Although, more than half of them are batteries. 2 locks, 3 smoke detectors, 2 thermostats, 4 light switches. I made sure the light switches were evenly spaced so I would get a good mesh network of devices that always had power. I just did the system wide network neighbor update. Keeping my fingers crossed. I guess if this doesn’t work, I am going to swap out this thermostat. I didn’t like that this thermostat didn’t show its neighbor even when I paired it. The other thermostat shows it. None of the smoke detectors (Zwave Plus) show the network neighbors. I noticed the locks that are also Zwave plus don’t show neighbors. - I am not sure if that is a Vera issue or a Zwave issue. Clearly some battery devices show the neighbors so you would think they all would. I wish Zwave was more strict on making manufacturers implement al the zwave features. It has gotten better since Zwave plus but still not perfect. Friends that have Lutron products love it. They say it works 100% of the time. -
I can tell you that anything zwave besides vera and SmartThings (due to cloud) work 100% of the time too. You are right, this is not rocket science and as I have expressed in other posts here and elsewhere, I finally graduated from this phase and replacing the vera was the key. I am now able to focus on growing and developing new things as opposed to constantly troubleshooting my network or the luup engine...
The display of the neighbor nodes is just that... a display. My experience with it is that it is fairly inaccurate on the UI so I would not even bother looking at it unlike any other controller.
-
I did the whole network neighbor update and it didn’t work. I am going to try replacing that thermostat tomorrow. It could just be defective I didn’t like that it didn’t show the neighbors when I first paired it. I would have expected it to that since the other thermostats shows its neighbors. . What I don’t know if it it the other thermostat showed them right away. One of the big problems with Vera is they just aren’t very transparent on what the controller is doing and/or what works and doesn't work. I wish they had a system were you could see all the reported bugs so you don’t waste hours trying to debug something that will never work. I wasted a lot of time with my new Schlage Zwave Plus lock. Vera had to give me a beta release to fix it. - I am going to look at your reviews of the different hubs. I want to look at Hubitat and open source Home Assistant. - Vera is especially bad with older non-Zwave + devices. Are these other hubs OK with that? I don’t want to have to replace all my switches and I have an expensive water cutoff. The Vera gives strange errors for the water cutoff. Plus, they have the notifications wrong. When I turn the water off, it tells me I turns it on. Thanks again.
-
Short answer: No other controllers have these problems. It's not to say that they won't have any problems but none as unreliable and as poorly implemented as the vera. openZwave used to have issues with some specific device types because the other was reverse engineering the protocol without documentation but even that library, which is used by domoticz, openhab, home-assistant amongst others is now more complete and reliable than the vera. The other three major zwave libraries are the SmartThing/Hubitat, Homeseer and the zwave.me one. They all use the same zwave serial API and zwave chips, with various level of implementation (the zwave chip may have more or less embedded memory, have a usb to serial interface, etc...). The zwave commands should all be the same.
I too have very ancient devices. Half of my network is on legacy zwave... I actually don't think your issues are a device support issue so much as a zwave network handling from vera. -
OK. Thanks. I am going to look at the other hubs. Hubitat, I doesn’t appear to support Schlage locks. I remember when I looked at Homeseer about 10 years ago, it was a windows based product. This may have changed. The HomeSeer products sure look nice now. It is probably between that and the Zwaveme. The Zwaveme doesn’t look as polished of a web page but...
I like that Homeseer has been around for so long and they say their product works with dozens of zwave devices.The devices I am most concerned about are:
Evolve - LFM-20 (not Zwave Plus)
Fortrezz WV-01 water cutoff (Not Zwave plus)
Schlage locks Zwave plus and older versions
First alert Zwave smoke detectors.and to a lesser extent but it would be nice
Aeotec SmartEnergy Switch (their first generation one that is big. I believe it was Aeon labs DSC06106-ZWUS)I assume they will all work with the GE light switches.
Plus, I want it to have an OS X app -
@sdtoddl said in Neighbour node setting:
OK. Thanks. I am going to look at the other hubs. Hubitat, I doesn’t appear to support Schlage locks.
I don't think that this is possible. One of my neighbors runs Schlage locks with Hubitat but more importantly, there is no such a thing as a device not supported by Hubitat. This is a vera thing. On hubitat, you can load your own driver for every zwave and zigbee device and I am fairly sure someone from their community has developed one. The whole device support concept is vera/EZLO nonsense which openzwave has also suffered from because of the way it came to be. No other platform that I know of has these problems... They support everything which talks zwave albeit potentially with some work required to configure. To be honest, even on the vera, I found non officially supported devices to often work much better than the official ones, in part because I manually configured them and disabled the auto-configuration feature. So they either support zwave or they don't. That is it. Device support issues is a foreign concept to hubitat/ST, zwave.me and to some extent homeseer. Homeseer is pushing to Homeseer4 which from what I read is a bit of a mess so I would not recommend it. It remains a windows/VB based platform.
-
Have a look at:
qt-openzwave/README.md at master · OpenZWave/qt-openzwave
QT5 Wrapper for OpenZWave. Contribute to OpenZWave/qt-openzwave development by creating an account on GitHub.
For me so far so good. Openzwave in home assitant (or mqtt). This is my current aim as a succesor for vera...
-
Thanks for that advice on the Hubitat. I had just looked at their list of supported devices and thought it was interesting that they didn’t have Schlage on there. They are sold out right now so it doesn’t look like I am going to buy one of those.