Guys, the best possible answer is to make our home automation setup work the way we want it in reliable and efficient manner, with or without our EOL veras but with each other's help. That's what we are seeking after all. While keeping our minds open, exploring all the novelties and discussing what we can do to continuously innovate improve and optimize. The vera had an awesome forum with tremendous community of developers. I sensed the end of an era and as much of our time and energy we have spent there, it was not all wasted. The best answer is to move on, not only for the sake of answering but also to refocus on what we aim to do: A community to grow, develop, debate, explore smart home technologies.
rafale77
@toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.
I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.
I see these errors on the following browsers:
Safari 16.6.1 on macOS Big Sur Safari 18.1.1 on MacOS Sonoma DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma Firefox 133.0.3 on macOS Big Sur Chrome 131.0.6778 on macOS Big SurHere are the errors
Safari while creating/updating an expression
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29 reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32 @http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40 dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040DuckDuckGo while clicking on status
http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44 asyncFunctionResume@[native code] saveGridLayout@[native code] dispatchEvent@[native code] _triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30 _triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31 makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30 addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24 placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44Firefox while updating a rule
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39 forEach@[native code] @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58Chrome while creating/updating an expression
TypeError: Cannot read properties of undefined (reading 'getEditor') at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86) at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54) at http://192.168.0.13:8111/client/MessageBus.js:98:44 at Array.forEach (<anonymous>) at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54) at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44) at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15) at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18) ``Build 24343 has fully HTTP actions, so cool things could be created (see docs). I've recently changed a couple of cams because better definition and I've found tha Reolink has a couple of cams that have spotlights. While the spotlights are driven by motion (so the cam could record in color), I wanted to drive them directly, so in case of any "security" event, like alarm on, door open, etc, I could use the lights to have a better video and make - you know - light.
So, if you want to use HTTP actions in VirtualController, just go to config, entities under your VirtualEntityController section in reactor.yaml, and add this:
- id: cams_retro_spotlights name: "Retro Cam - Spotlights" template: Binary Switch # update the status at interval http_request: interval: 900 # 15m url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo" method: "POST" force_json: true headers: "Content-Type": "application/json" "Accept": "application/json" body: '[{"cmd": "GetWhiteLed", "action": 0 , "param": { "channel": 0 }}]' capabilities: power_switch: attributes: state: expr: "isnull( response ) ? null : response[0]?.value?.WhiteLed?.state == 1" default: false actions: "on": http_request: url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo" method: "POST" force_json: true headers: "Content-Type": "application/json" "Accept": "application/json" body: '[{"cmd": "SetWhiteLed", "param": { "WhiteLed": {"bright" : 100, "channel": 0, "mode": 1, "state": 1}}}]' target: state expr: "isnull( response ) ? null: response[0]?.value?.rspCode == '200'" "off": http_request: url: "http://192.168.1.31/cgi-bin/api.cgi?user=foo&password=foo" method: "POST" force_json: true headers: "Content-Type": "application/json" "Accept": "application/json" body: '[{"cmd": "SetWhiteLed", "param": { "WhiteLed": {"bright" : 100, "channel": 0, "mode": 1, "state": 0}}}]' target: state expr: "isnull( response ) ? null : response[0]?.value?.rspCode == '200' ? false : null"Reolink has API where you have to post a JSON and the response will give you a JSON (in theory). It's not really JSON, so force_json: true will do the trick for you. I'm lefting this as an example of cool things you could do with the new capabilites added/documented in 24343. HTH.
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi
Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.
I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.
I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?
I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.
But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?
So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.
This is how I installed nodejs as whilst logged in as root
ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png
Thanks in advance.
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.As the title says, here's my OpenAI Controller for Reactor:
OpenAI Controller per Reactor. Contribute to dbochicchio/reactor-openai development by creating an account on GitHub.
It supports both OpenAI and Azure OpenAI endpoints. You'll need keys/endpoints, according to each service.
The controller supports multiple models, and each one could be mapped as an entity.
It's quite easy to use, and responses can be stored in variables, for easy access. Or sent to another action (Text To Speech, another endpoint, etc).
9013ae50-fd68-42a2-87c3-97479132e465-image.png
80a88eec-7c89-464a-8196-690b4b72d044-image.png
Have fun with LLM into your scenes!
I've switched to a virtual entity with both power_switch and string_sensor capabilities to represent the current holiday.
The power switch is used to indicate if it's a public holiday (so, no school/work), while the string sensor is a string with the actual holiday (Easter, Christmas, Halloween, etc - we don't have thanksgiving), mostly to drive lights.
I build it with some static dates (mostly birthdays/anniversaries) and then the dynamics ones are taken from webcal.guru. My lights/scenes are linked to events this way and it's easier to manage it in the long run: just a bunch of group action in the reaction driving the lights. This part is outside Reactor for me (because, legacy), but it's not difficult to completly drive it off a virtual sensor or a custom controller.
I don't know how people are doing this, but I'm lefting a note for the ones looking for a working solution.
In Home Assistant I have an integration that if I add entities to it, I will get the following error in MSR as certain entity values I'm using in expressions are null for a moment. This is more or less cosmetic issue and happens very rarely as I rarely modify that integration on the hass side.
Screenshot 2024-11-28 at 22.20.41.png
And the expression is
Screenshot 2024-11-28 at 22.38.19.png
Could I "wrap" hass-entity shown above somewhat differently to prevent this error from happening? Using build 24302.
Hello
I am trying to set up Multi System Reactor to automate routines across multiple smart home devices & platforms (e.g., Home Assistant, SmartThings, and Hubitat). While I have successfully linked the systems; I am facing issues with:
-Delays in triggering actions on secondary devices.
-Inconsistent execution of complex logic conditions.
-Synchronization of states between devices when one system updates.
Is there a recommended way to optimize performance & confirm seamless state sharing across systems?
I have checked https://smarthome.community/category/22/multi-system-reactor-msbi guide for reference but still need advice.
Any tips on debugging or log analysis to pinpoint where the issue arises would also be appreciated.
Thank you !
Hello AK
Have been writing about the openLuup email server as I was tinkering with it the other day. One minor problem: it looks like the domain part of the email address eg ...@openLuup.local is case sensitive in openLuup.
Looking round the net, it suggests that the local part is case sensitive but the domain part is not meant to be. To keep things so they are more likely to work, it's suggested the email address should be totally case insensitive regardless. Refer to rfc2821 page 13 or search on the word "sensitive". Suffice to say I was using mail@openluup.local rather than mail@openLuup.local, so it didn't work for me.
Next challenge was that the file saved in /etc/cmh-ludl/mail has "Content-Transfer-Encoding: base64" so the body of the email was encoded:
Received: from ((openLuup.smtp) [ip_address_1] by (openLuup.smtp v18.4.12) [ip_address_2]; Tue, 26 Nov 2024 14:21:22 +1000 From: "dali@switchboard" <dali@switchboard> To: "mail@openLuup.local" <mail@openLuup.local> Subject: Warning form R2E. MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: base64 QXV0byBXYXJuaW5nOiBDb2xkIHN0YXJ0IGV2ZW50The above base 64 text translates to "Auto Warning: Cold start event".
Is it your preference to leave the saved files in the raw mode or would you consider translating the base64 text in the openLuup code base?
On a side note, does the reception of an email by openLuup generate some sort of trigger that can be watched. In the case above; the email represents the restoration of power after a power outage. I would like to know about that by the email triggering a "Telegram" notification on my mobile.
I see that the images@openLuup.local images@openLuup.local can be associated with I_openLuupCamera1.xml, which spawns a movement detector child. Anything similar for the other email addresses?
I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
@toggledbits Since I have upgraded ZWaveJSController to 24293 from 24257 I am seeing entries related to registering action set_volume, but action is not defined by the capability 143 every time I restart Reactor.
The Siren seems to be doing what it is supposed to do. The volume levels are fine. Should I worry about it?
Reactor version 24302
ZWaveJSController version 24293
Z-Wave JS UI version 9.27.4
zwave-js version 14.3.4
I have an oven that I need to manage the temperature of, keeping it in the neighborhood of 600° C (1100° F). I have not been able to find a Zigbee-enabled solution to measure temps that high. Does anyone know if such a thing exists? If not, any ideas for how to roll a custom solution that I could integrate into a Sonoff ihost controller? I have no trouble finding high temperature probes, but none of them interface with my automation stack.
Hi All
Hopefully this place looks like a helpful forum as I’m quite new to all this!
I’ve had a few devices all working separately /through their proprietary apps but we’re just finishing off a large house extension and this has added to the list.
I’d ideally like to be able to view/switch a number of different devices on one screen/head end but have no idea where to start.
The devices we have/will have shortly are as follows;
Zigbee Smart Sockets
Zigbee smart switches (for lights)
Heatmiser Neo Underfloor Heating (this runs from a Samsung ASHP but that part is automatic)
Samsung VRF air conditioning (currently using Smart Things App)
Hive (2xLTHW heating circuits in the existing house and Hot Water)
Ring (doorbell!)
Hik Vision PoE CCTV
We have lots of appliances (Neff N70) which we can control remotely but not too fussed about controlling those at the
Moment)
Any help/recommendations would be appreciated!
Thanks
Adrian
After a major hassle got z-way running on my ubuntu 16 VM with a USB pasthough UZB1 stick including license and connected to Vera...
I see:
I also see:
0d6e8c78-c8cd-4307-9474-23e0d6a55094-image.png
But how do I update that?
e09ffa19-a31d-4a03-8983-01228bc5478f-image.png
I have a legacy home automation set-up running on Windows XP. the computer and software have now died.
I have written a very nice Excel VBA program to replace the software and it can run on any modern Windows system.
My only remaining problem is to output the correct signal to a USB port to trigger the wireless switches.
Has anybody done a similar exercise. Please help.
The locksmith is trying to persuade me to purchase the BE-TECH K35 touchscreen lock with both Wi-Fi and Bluetooth, claiming it's better than the Yale Assure Lock 2. What are your thoughts on this? Which one would you recommend?
Here is the link to the Chinese brand BE-TECH: BE-TECH Smart Deadbolt K3S.
The other smart lock I am considering is the Schlage Encode Plus.
Thank you!
Posts
-
Vera account suspended for a 1000 years -
Forum Mission StatementWho are we, what is our purpose? A community of smart home user or fans who felt the need for an independent place to share our experience, discuss novelties and ideas and test/develop better tools for home automation. Many of us come from the old Vera community but feel there is a space for non-partisan space to discuss the technology.
Everybody from any platform is welcome to discuss and share even though many of us are starting from the Vera and its much improved derivate, openLuup. We would only ask to for everyone to remain respectful and courteous to one another. Yes! even technical discussions can become heated as opinions can conflict. We respect everyone’s opinion and decisions and expect the same from others.
This forum is hosted benevolently by long time Vera community member DesT.
-
Not so quiet around here :)@perh said in Not so quiet around here :
I've asked for them to delete my account, but they say "the jury's still out" in the case of the "SHC mutineers".
Did they actually use the term "mutineers" there?
Are they actually serious? Do they still think that we are properties/employees/soldiers they should have any sort of control over? I hope not.They are booting the most loyal customers, ones who are willing to spend their time providing free customer support to others, sharing their fixes and findings to the community. Customers who are also providing them feedback to make their products better... He forced the creation of this forum with censorship then accuses people of all kinds of things and now is surprised that people are leaving?
Trust me only a very small number of those who have left are here. Many more are on many other platforms ranging from Homeseer to Hubitat to Home Assistant. And the cold hard truth is, that everyone has been much better off after leaving, has a much more reliable and capable system and for those who rely on community forums, have a place to discuss and have fun learning again.
-
openLuup IconsThis is a set of openLuup icons to replace the ones which you normally would transfer over from the vera. The only thing for the dimmable lights is that one needs to use a new json file to replace the original light bulb with an vector graphics type which I am also sharing.
icons.zip
D_DimmableLight1.json.zipThis is a sample of the icons on ALTUI:
-
zwaveserial -
Not so quiet around here :)Been trying to refrain myself from replying but here we go...
Instead of repeating what I have said in the past, my view is that ezlo and its leader have a very different view of the market and possibly do not understand what they bought by merging vera.But the basics are:
"But what can you do. Both sides have done things to upset the other."
Sorry but one has to put the context as to who is who back in place here. There is no circumstance under which a business owner should ever treat their customers this way. For anyone running a business, if a customer is upset, you should first asking why. Instead the guy keeps doing what upsets his customers and starts insulting and calling them names. That's unprofessional and unheard of."I think he feels you are all against the Ezlo platform and its future success and you just want your Vera firmware as is, to hack."
Again, instead of feeling this way, he should be asking why? Being the one who tore down the firmware down to the OS level, I think I can speak of it. Certainly "as is" is incorrect. The whys:
- Because it's broken
- Most of the fixes are trivial
- They significantly improve the vera
- They are not fixing it themselves.
Now on the understanding of this home automation market. If you run a market survey, you will see that the vast majority if not all platforms today rely to various degree on community development of external integration, cloud or local, and run on increasingly more powerful hardware. When they bought vera, they inherited a community, a small remnant of hardcore users who have extended the life of the vera to its limits trying to maintain the platform on par with the competition but still somewhat behind. A large number of people have already jumped ship quietly. The most vocal people on the forum are the most loyal supporters of the platform and many stay because of the technical migration barrier to other platforms. I think we were all excited about the prospective of a new hub and an updated platform. I was all in. There are however two bare minimum critical requirements to a new hub:
- Functional equivalency, including all the integrations the plugins supported
- An ease of migration from a vera installation to the new hub.
Sadly what I have observed is a complete disdain of these basic requirements and a development strategy aiming straight down the toilet (excessive focus on mobile app and cloud base processing, disregard of the critical wireless stacks and repeat of past mistakes in conception of the API) while the current product gets increasingly far behind competitive platforms, including open source ones. I kept an open mind, not being an expert on the software side but expressing a lot of concerns. The increasing amount of spamming of the forum with "exciting breakthroughs" and "pure innovations" of things the community has been able to do and better/faster/simpler for years combined with the release of an underwhelming hardware for the new controller, clearly pointing to a focus on minimum cost at the compromise of extendibility and reliability and you can clearly see my disappointment. That was the last straw for me. I predicted last year that the platform would not be ready in a year because of their approach... look at where they are now.
In the meantime, I have moved my zwave network to z-way. Stunningly, the migration is easier than to go from vera to ezlo and it felt like jumping from the stone age to science fiction. Everything became lighning fast... All my secure class problems and latency issues gone. I can no longer find any unsupported devices... etc... And all of my previous integrations are retained and more. So yeah I can see why he is upset but he can only be so at himself. Taking it out on his most loyal customers is... well you're the judge. -
Object RecognitionAnd... it is done! My outdoors IP Cams no longer just detect motion... They detect people, packages, and cars and are now used as openLuup scene triggers!
-
System integration roadmapFrom what I recall he likes Scotch better...
-
Nuke Vera ScriptScript 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.
-
Import vera most important topicsThinking about it, I don't think we should be importing posts without the consent of their authors so... I am rewriting, resharing a compacted version of my posts.
-
z-way-server 3.1.0 releaselol, yes I can imagine. So far I am seeing a few cosmetic improvements on this new version but since I am rarely ever interacting with the z-way UI, it isn't doing much for me. The upgrade went pretty smoothly though it had to be a little manual.
For those who want to do it on debian/ubuntu, the process is to download the file:wget https://storage.z-wave.me/z-way-server/z-way-server-Ubuntu-v3.1.0.tgz
decompress it:
tar -zxf z-way-server-Ubuntu-v3.1.0.tgz
remove the default config file:
rm z-way-server/automation/storage/*.json
and then overwrite the z-way-server installation folder wherever it is. Mine is in the /opt folder which requires root permission.
sudo cp -r z-way-server /opt/
PS: One notable improvement is in the noise meter. Now the below detection limit shows up as -95dBm instead of a nil value which made the graph looked like the noise remained at a high level. I think it was one of my requests...
-
Vera account suspended for a 1000 yearsYeah really don't miss the old forum thanks to @DesT!
Live and let ... be.
Happy as clam with my zwave and zigbee setup honestly... and to not have had to exclude/re-include anything to get there was a major part of it, given the size of my network. -
Other Forum feedbackYeah it's not just the website that is fast... the response to feedback is too...
-
Vera account suspended for a 1000 years@akbooer said in Vera account suspended for a 1000 years:
Clearly deranged. All I ever wanted to do was support openLuup users, and point out that, under the new regime, that was best done here rather than there!
Didn't need to explain AK. The guy shows us something green and tells us that it is orange. It's be going on since I was there. Everybody else can see that it is green...
@dest said in Vera account suspended for a 1000 years:
Some people are having way too much free time
And not enough neurons...
Talk about forum rules.. so many he made up to justify banning people giving feedback and expressing their problems and obviously not applying them to himself. Community users are not possessions or employees... they are customers. He is dictating that everyone be happy with the trash and lies he is feeding people without asking why customers are unhappy. Honest customer feedback is essential to success. In my line of work, we don't let ourselves make a single customer unhappy... not one.
Let him be.
-
Vera account suspended for a 1000 yearsAnd 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.
-
Vera account suspended for a 1000 yearsWarm welcome for your first post! This forum only exists thanks to the generosity of @DesT who provided the domain name, hosting and design! We should also be grateful to the venerable mcv/vera for connecting so many people and pioneering this hobby.
-
Vera firmware 7.32 betaI have been mostly silent on this forum for some time now with the exception of the occasional notifications for questions addressed to me because I just moved to a new house and my system had been rock solid for over a year... mostly since I got rid of the vera.
I now have to re-build everything from scratch in my new house while I had literally zero reliability issues with my previous setup in spite of its complexity (200+ devices integrated running 3 different software platform interconnected between z-way for zwave, Homeassistant for AI/cameras and the rare cloud integrations or integrations not existing on openLuup/vera and openLuup for scenes/automation/control interface.)
I considered long and hard to sell my old home with the automation but at the end I decided to move as much as I could over mostly because I noticed an increasing trend of the industry to go towards wifi for ease of setup but which cannot scale to large installations and have to encroach into wifi bandwidth. It is getting a bit harder to buy zwave and even zigbee devices. I also didn't want to spend the time to go through the learning curve of hubitat which would have yielded no benefit to my setup.
Dumping the vera was the single biggest improvement to my system and please, no ezlo... They are cost reduced and downgraded controllers to the vera in every important practical aspect.My new setup will be much lighter. Probably will not get to 175 zwave nodes, more likely <100 without the window coverings, fewer lights, fewer sensors. Heck I think I will dump the Phillips hue altogether too. I can't recommend enough migrating away from vera and go to openLuup or MSR in combination with Home Assistant for zigbee and integrations and z-way for z-wave while keeping devices as local as possible by avoiding all the wifi stuff which tend to be cloud dependent (with all their reliability and security disadvantages) and less efficient both in power and RF bandwidth. Still a new adventure...
-
Network Key LocationUseful for migration from a vera zwave network to z-way.
Find the vera's S0 network key, close the z-way-server and input the key into the
z-way-server/config/zddx/homeid-DeviceData.xml line 147 at the end of the line networkKey replacing the one z-way created by default when you loaded your uzb on it for the first time.
(replace homeid with your homeid after you already migrated the dongle data from the vera to the uzb and already booted z-way at least once) -
Facial recognition triggering automationI have optimized my facial recognition scheme and discovered a few things:
My wifi doorbell, the RCA HSDB2, was overloaded by having to provide too many concurrent rtsp streams which was causing the streams themselves to be unreliable:
Cloud stream
stream to QNAP NVR
stream to home assistant (regular)
stream to home assistant facial recognition.I decided to use the proxy function of the QNAP NVR to now only pull 2 streams from the doorbell and have the NVR be the source for home assistant. This stabilized the system quite a bit.
The second optimization was to find out that by default home assistant processes images every 10s. It made me think that the processing was slow but it turns out that it was just not being triggered frequently enough. I turned it up to 2s and now I have a working automation to trigger an openLuup scene, triggering opening a doorlock with conditionals on house mode and geofence. Now I am looking to offload this processing from the cpu to an intel NCS2 stick so I might test some other components than Dlib to make things run even faster.
-
openLuup HangsSorry for reviving this @akbooer but I wanted to give a quick update on lua socket.
I realized that the library used by luarocks is very old (3.0 RC1 from 2013) and that the apt debian/ubuntu version is a little newer (March 2015). The library has since gone through 5 years of development and I just installed the latest github version using this command:luarocks install luasocket --server https://luarocks.org/dev
It compiles the library from the current GitHub master. I am not sure it will help but so far it has not hurt. Will test further...