-
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
-
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??
-
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.
-
Does anyone have a quick way to delete multiple devices without having to do a reload between each delete? I have about 20 child devices to get rid of and it will take forever to delete them all one by one with a reload in between.
-
This is just a note for anyone who wants to delete the duplicate child devices the Vera likes to create. In my pervious experience when I would delete a child device (duplicate or not) the parent device would get deleted too.
What I now have discovered is that if you go into AltUI and clear the value set in the attribute for the child device called id_parent you can simply delete the child device without the parent device getting deleted.
I am unsure if the new FW recently added the ability to delete child devices like this, but now I went from 30+ child devices down to the expected 4. Hope this helps someone out!
-
Hello @therealdb , I have updated to the new vera FW and cant seem to get your plugin working. I keep seeing "install jq package" on the device itself and when I reset everything and got a new cookie file I see this in the device's Latest Response variable: ERROR: missing argument for -d /storage/alexa/alexa_remote_control_plain.sh [-d .
I have used the code to reset the cookies, added a new cookie file, added the OTP, updated the plugin (did this first actually) and still cant get it working.
Testing some TTS commands I see this response in my logs:
"Say", {Text="Hello from Vera Alexa", Volume=50, GroupZones="Bar Echo", Repeat = 3}, 632)) <0x6bc41520> 08 03/14/21 10:57:57.179 JobHandler_LuaUPnP::HandleActionRequest device: 632 service: urn:bochicchio-com:serviceId:VeraAlexa1 action: Say <0x6bc41520> 08 03/14/21 10:57:57.179 JobHandler_LuaUPnP::HandleActionRequest argument Repeat=3 <0x6bc41520> 08 03/14/21 10:57:57.179 JobHandler_LuaUPnP::HandleActionRequest argument Text=Hello from Vera Alexa <0x6bc41520> 08 03/14/21 10:57:57.180 JobHandler_LuaUPnP::HandleActionRequest argument GroupZones=Bar Echo <0x6bc41520> 08 03/14/21 10:57:57.180 JobHandler_LuaUPnP::HandleActionRequest argument Volume=50 <0x6bc41520> 50 03/14/21 10:57:57.180 luup_log:632: VeraAlexa[0.9.0@632]:addToQueue: added to queue for 632 <0x6bc41520> 01 03/14/21 10:57:57.181 LuaInterface::CallFunction_Job device 632 function SVeraAlexa1_VeraAlexa1_Say_run failed /etc/cmh-ludl/L_VeraAlexa1.lua:89: bad argument #3 to 'format' (string expected, got nil) <0x6bc41520> 50 03/14/21 10:57:57.181 luup_log:0: ALTUI: Evaluation of lua code returned: nil <0x6bc41520> ``` -
I use the ROKU plug-in from Vera's app repository. It seems to constantly add Log entries every 5 seconds or so, to the point where my LuaPnP log is just littered with page-long reports about the status of my Roku TV. My Log is 75% "Roku" status!
The only pertinent setting I see under Advanced > Variables is "PollingEnabled" (default: true) which when set to false does indeed stop the logging altogether. But I fear this also completely stops the plug-in from checking TV status which otherwise would update variables that happen to trigger some of my MSR routines. (More testing needed here...)
But do you guys know of any way -- up to and including editing the D_, I_ or L_ files of the plug-in itself! -- to simply stop or slow a running plug-in from writing to the Log??
Also, is there any harm (other than mild annoyance when I have to review the Log for unrelated things) in allowing Vera to write so vigorously to the Log all day long??
THANKS!
-
I regret my decision to click "Configure Node Right Now" on an otherwise working device (a Fibaro RGBW LED dimmer control) while it was "Off". Doing so seems to have caused all of its "children" devices (RGB(R), RGB(G), etc.) to disappear from my Vera UI, and I have no idea how to get them back.
Meanwhile, the parent device keeps reporting "Device Failed to Configure" (in red)** and cannot be controlled by Vera any longer. Nor do the attached LEDs go "On" in response to other Scenes.
How do I undo this innocent mistake? Restarting the Luup engine and hard-refreshing my browser/UI has not helped.
THANKS!
P.S. What does that button DO!??!
EDIT: Now the affected device reports (in light blue) "Please wait! Getting the manufacturer...", then "Setting special association", etc. Then 8 unnamed devices magically appeared in the affected room...
I am hoping these are good signs? -
Seems as though during my testing of the Vera Mobile app, I set up a couple of Scenes (now deleted) which never worked anyway.
But MSR's "Entities" tab still shows the presence of two waypoints (with Vera ID's like vera>geo_1625761_1) which I have no clue how to delete.
I've searched high and low in the app (Settings, Users, etc.), and can't think of anywhere in the Vera Plus UI to look for these - not even sure what to call 'em - to Delete them.
Any clues?
-
I just peeked into my Vera Plus > User and Account Info > Other Users and much to my astonishment (and horror?) found a little surprise waiting for me, an account called "LinuxTest".
Seems it magically has the highest possible authority ("Account Administrator") within my Vera Plus, along with a contact email of linuxtest@mailinator.com
Does this appear on anyone else's 7.32 (beta firmware) Vera unit?
(In case it matters... no, I've never requested or authorized Customer Support on this unit, at least not in the past 10 years.)
Hmm. - Libra
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!
-
Do you have openLuup running, If so you could link via mqtt, as there is an Ezlo bridge for openLuup.
-
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
/devand 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 usedlsofto 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 upser2netand... nothing.After a couple of hours trying a bunch of different stuff with no joy I started to suspect that
ser2netwas 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 installedsocatto 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,forkI'll upload the socat
.ipkthat 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 supportedA 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.
