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?
With their awesome new X10 switch!
dbe7408f-dc86-4932-bf71-f0528f5384c1-image.png
I'm hopping in my 1980s time machine to go see whether this is exactly what I think it is. 🙂
(Srsly, tho, I love(d) X10 and did everything humanly possible to keep that old equipment perking along with Vera, and almost succeeded.)
LibraP.S. Just got banned for the 9th time from Hubitat Forum, so had a little extra time to throw shade.
P.P.S. The boilerplate 5-star reviews for this brand-new product come from bots with names like Avery, Phoenix and Owen (two from Mateo!). Sheesh.
Let's assume you have done the following:
Downloaded and installed Z-Way following these instructions. No Zway license is required to do the following. The software is now all up and running with your UZB stick (whole other post). Dial up this Zway web page: http://<Zway_server_IP_address>:8083/expert/#/network/controller Under the heading "Firmware" take note of the "SDK version" and the "Serial API Version". Say they equal 6.71.01 & 05.23 respectively like it shows here.Now on to Vera:
Go to the Vera UI --> Z-Wave Settings and taken note of the "Version" shown for Vera's internal Zwave IC. For example purposes, say it equals "6.01". You plug your UZB stick into Vera. In the Z-Wave Settings you set the port to "/dev/ttyACM0" You've rebooted Vera, so that it starts using the UZB stick.OK, so what "Version" will Vera now display and the version of what? The version shown by Vera is the "Z-Wave protocol" version or the "Serial API" version - it's unclear which but I suspect the former. However on most occasions the numbers are the same. It's not the Software Developers Kit (SDK) version number.
Knowing the UZB firmware version you can identify what Vera will show with the following table.
From the example above: Zway stated the version as 5.23. It will show in Vera as version 4.61 - see table. However the Vera internals showed up as 6.01. So using this method to copy the Zwave configuration to the stick will not work, as the stick represents a downgrade and you can only do same to same or upgrades. So in this case you need to update the stick firmware from 5.23 to 5.32 as a minimum. Then the stick will show up in Vera with version of 6.01.
Which is great. So you then use the Zway software to upgrade the stick firmware. And that's the last you hear from it because this happens:
"Sorry to inform you, but there is a known issue in some UZB manufactured by our partners on license base that after upgrade they become bricked."
And you have to do this to unbrick it. So time to try someone else's stick. Sigh.
ZWay UZB version Vera version SDK version 5.39 6.09 6.82.01 6.08 6.82.00 6.07 6.81.06 6.06 6.81.05 6.05 6.81.04 6.04 6.81.03 6.03 6.81.02 5.37 6.02 6.81.01 5.36 6.02??? 6.81.00 ???? 5.33 6.02??? 6.81.00 ???? 5.32 6.01 6.81.00 5.03 6.71.03 5.02 6.71.02 5.27 BL 48059 4.61 6.71.0? 5.26 4.61 6.71.0? 5.23 4.61 6.71.01 4.6 6.71.00 5.2 4.6? 6.7?.00 5.16 4.6? 6.70.00 4.62 6.61.01 4.33 6.61.00 4.54 6.51.10 5.07 4.38 6.51.09 4.34 6.51.08 4.24 6.51.07 4.05 6.51.06 5.06 4.01 6.51.04 3.99 6.51.03 3.95 6.51.02 3.92 6.51.01 3.83 6.51.00 3.79 6.50.01 3.71 6.50.00 3.67 3.35 6.10.00 3.41 6.02.00 3.37 6.01.03 2.78The table is based on page 434 of silabs app INS13954 and the UZB firmware revision information found here. The table may have errors!
The vera can run both its zwave and zigbee network off of external USB radios instead of the onboard ones. This could have advantages in terms of portability, facilitating migrations or recoveries in case the vera craps out. It could also enable testing of newer radio firmwares.
Zwave is pretty straightforward as its serial API is standardized and the protocol is the same regardless of what brand of USB stick you use. I have run my vera off of USB sticks of various brands for years going from Aeotec, Zooz, Homeseer and even the most generic silabs/Sigma Design. You just insert the stick in the usb port, find out which serial port it created (under the /dev/ folder) and use that port (ie. /dev/ttyACM0, /dev/ttyUSB0 etc) in the zwave advance menu.
Zigbee is a little trickier as the protocol and chipset was not quite as standardized as zwave. The vera only works with ember Znet protocol and you will need to find a usb stick with an EM35x chip in it which already has an ember zigbee firmware loaded. One example of such a stick is the Go Control HUSBZB1 (dual zwave-zigbee stick). The port is not readily accessible on the vera UI but can be accessed either through editing of the /etc/cmh/user-data.json or through ALTUI by going into the hidden zigbee radio device through the "table devices " menu and changing modifying the port variable there.
You can also upgrade the onboard zwave and zigbee radio firmwares from the command line SSH...
incalzire.png
Hello everybody.
I would like to automate the underfloor heating. At the moment I have the gateway from vera secure and thermostat with receiver from SRT SECURE with z-wave. I would like to connect to the gateway a receiver with 4 channels from sonoff and 3 temperature and humidity sensors from aliexpress as a thermostat. do you think it is possible?
and one more question... how can I change the name of the wireless network and the password from the gateway?
Thank you very much!
Script to disable all the mios/vera proprietary program and broadcast its zwave and zigbee radio serial ports in your network so it can be picked up by another controller... For example z-way.
GitHub - rafale77/Nuke-Vera: Script to neuter the vera and broadcast its zwave and zigbee serial ports GitHub - rafale77/Nuke-Vera: Script to neuter the vera and broadcast its zwave and zigbee serial portsScript to neuter the vera and broadcast its zwave and zigbee serial ports - rafale77/Nuke-Vera
Good morning all,
I've got a stable Home Assistant running on a RPI 4 with a Aeotec Z-Stick 7 Plus, and of course the Z-wave JS integration. I've manually moved a handful of devices, and I'm overall much happier with the HA z-wave capability than I am with Vera. There are still some things I'm trying to figure out that I have in Vera that I'm not sure how they'll work in HA, but no deal breakers.
I've got all of my automation on MSR and off of luup Reactor, so really the only thing left for me is to migrate my Z-wave network. I saw @rafale77's post about using a Zwave.me UZB1 to Zway, but of course that's not what I'm using.
Is there a similar method that I can use my Aeotec Z-Stick 7 plus to Home Assistant? I have around 70 Z-wave devices (give or take devices that generate multiple instances in Vera), so manual unpairing, including, etc, would be quite a chore.
So ... I am trying to do the following:
Current setup:
Vera Plus (1.7.4955) Zwave only -> HASSIO VM (full control via Vera Integration)
Future Target:
HASSIO VM (leveraging zwave.me UZB1 dongle via USB)
I have done the following so far:
Updated UZB1 dongle (via RPi SmartHome) to latest 5.39 FirmwareI followed the following steps to try and migrate my existing Z-Wave NW (currently on Vera) onto the UZB1 dongle following the steps listed here:
Migrate from Vera to Z-way
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.
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...
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```Vera account suspended for a 1000 years
-
@dest said in Vera account suspended for a 1000 years:
Seeing all these stuff on the other forum, gave me more pressure to really remove my Vera dependency in my current setup!
Yes, absolutely. Finally time to clone that ZWave dongle and plug it in to ZWay, or elsewhere.
-
@therealdb i'm using one Vera for my 3 zigbee thermostat (so I can probably replaced them by zwave) and the other one it's only for the DSC plugin, that I need to debug on openLuup directly to bring it back on openLuup (was there a while ago and stop working, already talk about that with AK)
All my zwave devices are since a while in ZWAY!
All my scenes/code/etc... are in openLuup since a while too!
-
And I do want to say for the record, the post which got me banned over there was about 2 things:
- A response to a link to the review article for the ezlo USB powered dongle which obviously was written by a home automation newb journalist who knew nothing about it, making claims which were obviously untrue as I had one on hand myself. I called that false advertising.
- The fact that the ezlo controllers, the ezlo plus was an obvious cost reduced version of the vera plus with everything that matters downgraded and everything which is unimportant brought up to date for cost reduction. It is basically a toy grade device barely good enough as a toy for my then 8 year old lego projects. I was pretty sad seeing all the people spending time and money on 3D printing for a shell which is likely worth more than the content. I am a hardware enthusiast working in the semiconductor industry and am pretty well versed in the grade of these chips, who makes them and how. That was my honest feedback. So I called out the false advertising and the forum spamming.
There is nothing wrong with the hardware of the vera. It is actually a very cleverly designed piece of hardware based on a wireless router which was not utilized appropriately by its mcv firmware developers. Unlike the ezlo, it uses SLC NAND which is bears >100x write cycle lifetime than the garbage ezlo put out (the partitioning of the vera storage was the main problem). It uses an appliance grade CPU which is much more reliable than the toy grade junk in the ezlo plus you can buy as a full system for $7 on aliexpress. I could tell from the build of material that it was reallly a cost reduced and downgraded from the vera plus from the build of material and would have never even tried to run my home on it even someone paid me to do it. The only reason why I am no longer using the vera plus as a radio for openLuup/home assistant or z-way is that I got tired of how prone to bricking these embedded devices are. They take a lot more work to recover when there is a storage problem (data corruption etc) so I went low cost x86/x86 which often can be more energy efficient but are always more cost effective and more reliable.
-
@rafale77 said in Vera account suspended for a 1000 years:
people spending time and money on 3D printing for a shell which is likely worth more than the conten
ROFLMAOO.... and I'm dead!!!
-
To give you a more graphic analogy of how I see it from a hardware engineer's point of view:
The vera is equivalent to a solid 80's Mercedes with a V8 diesel engine in which mcv has tried to feed some gasoline to make it faster and forgot to install more than 1 seat. It still runs but sputters a little. With a little maintenance and a few fixes, it will run for a long time albeit with only one passenger.
The ezlo plus on the other hand is a brand new 90's Lada on which they put the wings of cessna and they, ezlo, the snake oil salesmen, tell you it will fly you across the ocean powered by the Lada engine. Sorry I didn't believe it for one femto second, would you? Of course the paint job is worth a lot more than the vehicle... and it has 4 seats! yoohoo! You can seat more people but you can't go anywhere with it. And thanks but no thanks, I don't want to test drive it even for free. And no, I won't consider replacing my private jet with it... yeah yeah I know... the door on it can open really fast! awesome! got it! Still it's a "no". -
-
The only consistent rules there from what I can see after not having gone back there for so long are:
Do not piss the CEO off, do not win an argument with him, do not prove him wrong, do not mention that he broke his forum rules. Truth does not matter. All you need to know is that they are awesome.
Do not provide helpful information to make your home automation work better than ezlo can. They are already awesome. That's what they call stealing from their awesomeness.
Do not criticize the product repeatedly and consistently or point out the false advertising/marketing, especially if what is said is true and you are a respected and regular contributor. Again, they are awesome. They call this spamming.Every other rule is fabricated to justify the above and are applied selectively except for one person. The ultimate purpose is obscurantism to brainwash possessions (huh, I meant customers) into believing that their broken systems work and that they are... you guessed it... awesome... and very fast!
-
Before the take over, the Vera forum was really useful. The criticism was thought provoking. Wow what a change.
Other smart home forums allow for plenty of criticism within their discussions. Even SmartThings allows whole sections of Hubitat related talk. I only know of 1 discussion removed there and it eventually was put back by an employee/moderator.
Glad to see this independent forum has started! -
-
Are you kidding me? For what? Saying the thread isn't constructive? Well, shucks, there's just no room for you around here, Captain Obvious.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
-
@toggledbits don't worry, I will be able to sleep tonight
