Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
rafale77R

rafale77

@rafale77
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Wiring Samotech SM308-S into light fitting
F
Hi Smart Home Community. I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights. To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent. I am however not exactly sure how to wire it in. The manual is available here Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc. I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded. Thanks
Hardware
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
Z-Wave Future....
DesTD
https://forum.z-wave.me/viewtopic.php?f=3417&t=36140 That's not a good thing I think Time to switch again?
Z-Wave.me
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Disaster recovery and virtualisation
CatmanV2C
Following on from my last thread, some progress has been made over the weekend. With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system. Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic. Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work. Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic. Once that hurdle is sorted I'm torn between: Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.) Decisions, decisions. C
General Discussion
Remote access of Zwave stick from Z-wave server
CatmanV2C
Topic thumbnail image
Software
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
About
Posts
1.1k
Topics
84
Shares
0
Groups
1
Followers
3
Following
1

Posts

Recent Best Controversial

  • Vera account suspended for a 1000 years
    rafale77R rafale77

    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.

    Vera

  • Forum Mission Statement
    rafale77R rafale77

    Who 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.

    Announcements

  • Not so quiet around here :)
    rafale77R rafale77

    @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.

    General Discussion

  • openLuup Icons
    rafale77R rafale77

    This 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.zip

    This is a sample of the icons on ALTUI:

    Screen Shot 2021-03-01 at 16.06.18.png

    openLuup

  • zwaveserial
    rafale77R rafale77

    Never posted this on the vera forum but...
    Did you know about this?

    The vera has a very powerful zwaveserial API program in the firmware. Take a look at what it can do:

    Screen Shot 2020-04-24 at 10.29.50.png

    It is what the UI calls to interface with the zwave dongle.

    Vera

  • Not so quiet around here :)
    rafale77R rafale77

    @cw-kid

    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:

    1. Because it's broken
    2. Most of the fixes are trivial
    3. They significantly improve the vera
    4. 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:

    1. Functional equivalency, including all the integrations the plugins supported
    2. 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.

    General Discussion

  • Object Recognition
    rafale77R rafale77

    And... 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!

    IPCam

  • System integration roadmap
    rafale77R rafale77

    From what I recall he likes Scotch better...

    Multi-System Reactor

  • Nuke Vera Script
    rafale77R rafale77

    Script to disable all the mios/vera proprietary program and broadcast its zwave and zigbee radio serial ports in your network so it can be picked up by another controller... For example z-way.

    GitHub - rafale77/Nuke-Vera: Script to neuter the vera and broadcast its zwave and zigbee serial ports

    GitHub - rafale77/Nuke-Vera: Script to neuter the vera and broadcast its zwave and zigbee serial ports

    Script to neuter the vera and broadcast its zwave and zigbee serial ports - rafale77/Nuke-Vera

    Vera

  • Import vera most important topics
    rafale77R rafale77

    Thinking 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.😀

    General Discussion

  • z-way-server 3.1.0 release
    rafale77R rafale77

    @akbooer

    🙂 lol, 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...

    Z-Wave.me

  • Vera account suspended for a 1000 years
    rafale77R rafale77

    Yeah 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.

    Vera

  • Other Forum feedback
    rafale77R rafale77

    Yeah it's not just the website that is fast... the response to feedback is too...

    Comments & Feedback

  • Vera account suspended for a 1000 years
    rafale77R rafale77

    @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

  • Vera account suspended for a 1000 years
    rafale77R rafale77

    And I do want to say for the record, the post which got me banned over there was about 2 things:

    1. 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.
    2. 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

  • Vera account suspended for a 1000 years
    rafale77R rafale77

    Warm 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

  • Vera firmware 7.32 beta
    rafale77R rafale77

    I 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...

    Vera

  • Network Key Location
    rafale77R rafale77

    Useful 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)

    Z-Wave.me

  • Facial recognition triggering automation
    rafale77R rafale77

    I 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.

    IPCam

  • openLuup Hangs
    rafale77R rafale77

    Sorry 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...

    openLuup
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved