I've been using Vera Plus for nearly 10 years now but it's time to move on. On top of that we've moved from the previous house whereupon I took all the Z-wave door sensors, locks and switches with me and reverted the pool to manual control, grabbing the Autelis which I won't use now since the new pool we built has Pentair IntelliCenter.
I have the Vera Plus connected and have it controlling a couple of Honeywell Z-Wave thermostats and a couple of lights but It seems to just be slower and slower as it ages. I have an intel i3 NUC that is probably 6 years old but figure it's probably powerful enough to control HA going forward. I also dabbled with HomeSeer but it seems to cost a fortune for plugins. I have HS4 and a G3 Z-Wave Plus dongle from them.
How do I get started? I'm thinking I'll just unpair all my devices from the Vera Plus and add them to HA and then set up Reactor to do the logic but is there a way to migrate? Should I use Open LUA instead?
Lots of questions but I'm ready to get started an any help would be appreciated.
I have set up HA in a VM Box Virtual Machine and am progressing along.
I got new Kwikset Connect 620 door locks and got one connected to HA via Z-Wave JS and automated via Keymaster which is quite convoluted but I got it done.
I went to install the second lock and got it connected to HA via Z-Wave JS but am not being successful getting it to work properly in Keymaster.
Screenshot 2024-08-28 084902.png
Screenshot above is the second lock for the laundry room. It shows it is set up but the codes don't seem to be working.
I have not installed the lock yet and have not set the handing either. Maybe this is the issue but IDK.
Anyone have experience setting up locks in HA using Keymaster that can help would be great!
As our family grows and life gets busier, I've been thinking about upgrading to smart door locks. With kids often forgetting keys and elderly parents needing easier access, the idea of fingerprint and facial recognition seems like the perfect solution. I also love the idea of being able to lock and unlock the doors remotely, especially when we're away. Has anyone else implemented smart locks in a similar situation? How has it impacted your daily routine and overall home security?
Hi
Bought a new ZB device, an EV charger.
I was aware that there would one manufacturer specific cluster that wouldn't work out of the box, but several other clusters I hoped would work from start does not. Or at least there isn't any enteties for them.
So I have tried to study how to write a local quirk, but it is a bit overwhelming for mt brain.
Usually I can manage do get stuff moving with intense googling, finding guides or different solutions that I can start from, but here I find nothing that I can wrap my head around.
My latest try was to chat with Gemini AI 😰 (programmers, rest assured that your job will be safe for the foreseeable future 😁 )
I have gathered my device Diagnostic Info.
I have manufacturers ZB documentation.
A device support request is created on zigpy github (no response the last weeks)
For now there is just two entities for my device, on/off switch and energy sensors.
All non manufacture attributes and commands seems to be recognized in ZHA "Manage this Device"
It would be great if I could get some entities out of them.
For example the entity for manage charging power is expected to be presented as a dimmer slider.
But why isn't there any entity created??
The manufacture specific cluster is more of nice-to-have and could maybe be solved another day.
Any help would be much appreciated. 🙏
I just wanted to post how impressed I am with both HA and MSR. I really don't see that Ezlo have a chance in hell.
I noticed that my Virtual HA instance was killing my machine's performance, so decided that my project for the weekend would be a stand alone Raspberry Pi instance. Less than an hour to install, restore and configure both HA and MSR and it all just works. Thanks to everyone that contributes to these fabulous projects. Especially our own @toggledbits for the amazing work that is the new Reactor!
C
Very impressed by Harmony hub on HA. Seems to suck all of my network goodness in 🙂
One thing I'm not clear on is how to send individual commands. Specifically I'd like to send volume commands to my TV via MSR. I've got as far as:
<edit?> There should be a screen capture here, but I'm getting a Parse error 😞
@DesT ....
Suggestions for values to turn the volume down on my TV, or pointers as to where to look?
TIA
C
Domoticz (used for zigbee integration) have been bothering me so much that i've been looking at HomeAssistant to replace it. Now that Z-way is moving in with an integration, its even more tempting..
But i don't like the idea of having it as an OS that I can't use for other things, and running the HASS Core in a docker seems to be somewhat reduced in terms of addons?
I realize that HASSOS is using docker for integrations or addons, but can I still use docker compose to set up my own dockers (i.e z-way, influx, grafana) there as well?
I guess i'm getting old, change is difficult! 😉
I've just started to look at HASS UI, and have seen enough to see that it has an infinite number of ways to show enitites and devices in all forms and shapes.. But for starters i'd like to have something familiar, so how do i go about getting a sidebar for rooms like in openluup?
I know i can put them in the actual left sidebar, but i'd prefer to keep that for configuration pages..
on each room page i'd like to sort the lights, the heaters, the sensors together, and i saw somewhere that HASS will do that for you if you play your cards (pun) right.. can't find it again now..
Any pointers to a beginner?
Relates to Vera integration in Home Assistant
Just for you to be aware.
If you are using plugs (or whatever) in Vera to measure energy for your appliances this is deprecated in 2022.4.0 since the HA integration to Vera is not updated and maintained anymore.
2022.3.8:
Skärmavbild 2022-04-14 kl. 19.54.47.png
2022.4.3:
Skärmavbild 2022-04-14 kl. 20.48.06.png
Time to move away from Vera for z-wave ...
Link to HA thread:
Yes, it can truly be a hard time to keep up with all the changes and sadly that no one maintains Vera no more. The REST sensor can make it live a bit longer at least for now… sensor: - platform: rest name: "ender_kwh" resource: http://IP_OF_VERA:3480...
I've integrated Reactor and Z-Way Expert panel in my HA UI, but as it is iFrame, it will not work if I log in from the outside.
It would be great to access these in case my wife finds an automation flaw while I'm elsewhere, which seems to be the rule of thumb..
If I understand this right, all the dockers(reactor, z-way) host their own web server on the port, so it should be possible to get this throuh the HA "tunnel"(VPN or whatever its called)?
I noticed that my Octoprint camera is integrated differently, and can be seen on external connection as well even if i only give it a local address in setup?
(Not sure it's the right HA bridge but....)
I have a selection of HA bridge devices to enable Alexa integration. They all work perfectly except one that has just (48 hours) started saying that it's un responsive with Alexa. If I go to the HA bridge and test on / test off it works absolutely perfectly.
I've deleted and renamed from the Alexa App but no change. Simply says 'Device Un-responsive'
Any thoughts?
TIA
C
Hello,
I am currently running Home Assistant and Vera at the same time. I have installed a couple of ZEN32 5 button controllers but having issues getting the additional buttons to control my Vera devices. Am using the ZEN32 (Z-wave JS) blueprint which works well for devices on HASS. In developer tools I can use the Light:Toggle service and toggle my kitchen light through Vera. If I create the same action through the ZEN blueprint it doesn't work.
Anyone have any thoughts?
Roger
Hi!
Since a couple of days, I'm not able to use the TTS in MSR (HA). I haven't done anything else but updated HA. Don't know if that's the source of the problem. Have this happened to anyone else, or is it just me?
When I searched in the HA community, there seems to be a croud of people having this issue - but they often refers to Alexa, so they may not have my problems.
I took a snapshot of a MSR instance, where it shows that the TTS is missing. I use to have 4 different TTS engines to choose from - now I have none. Am I alone in this?
a10dde36-e301-4013-9146-02f2b18c20ed-image.png
Opening a thread to discuss updates to my home assistant fork.
GitHub - rafale77/core: :house_with_garden: Open source home automation that puts local control and privacy first GitHub - rafale77/core: :house_with_garden: Open source home automation that puts local control and privacy first:house_with_garden: Open source home automation that puts local control and privacy first - rafale77/core
I am trying to keep it on par with the official one but have made quite a few tweaks focused on video handling and processing. Home Assistant being developed on python is a great base for integration of machine learning and deep learning models into smarthomes because it is one of the most common languages used in the field.
As of today, I updated the readme file and the version to match the latest official release.
Most of my spoken commands to Alexa go something like this:
"Alexa, time for bed"at which point she executes a pre-planned Routine (triggered by that spoken phrase). The routine may turn On a virtual switch (named, say, "VS: Time for Bed" on my Vera Plus, but known to the Alexa Smart Home skill as "Time for Bed" just to keep my sanity).
The VS is a child device of Switchboard plug-in (by @toggledbits ) and acts as a binary (On/Off) light switch. Typically, I'll instruct Reactor to turn the switch back off -- or, more commonly, have it set to turn itself back off after NN seconds in the Switchboard UI. In other words, it's just a brief Trigger for a Reactor routine or Vera scene.
Now, here's my question: In order to avoid creating dozens of virtual switches -- one for each Routine / Scene -- has anyone tried using a DIMMER instead?
Seems to me that a dimming device, since it can be set to 100 different "brightness levels", could trigger 100 different responses in Reactor. But I'm hesitant to try this arrangement until I know others have had success, and that the faux "dimming" process won't inadvertently trigger intermediate values (e.g. "ramping") along the way.
Eager to hear if this alternative workflow makes sense and is practical, insofar as "Binary" and "Dimmer" seem to be the only switch types that Vera allows Alexa to "see" on Discovery.
Thanks! - Libra
Interfacing Alexa with Reactor via Routines and Dimmer VS
-
-
@elcid "Test Dimmer" is a child device of Switchboard plug-in on my VeraPlus. MSR runs in a Docker container on my Synology NAS, connected to the same local network.
I'm accessing and executing the Alexa Routine using an Android phone (also connected to the same WiFi).
Clearly the type and timing of propagated data in this arrangement is not deterministic enough to be used as a Trigger in MSR. Spent two solid days proving that to myself, lol!
Surely with Node-Red and other more modern, streamlined data channels in place, it would not be a problem, I'm sure. Just wanted to test what I have in my arsenal, which is always 1-2 generations old.
-
@librasun said in Interfacing Alexa with Reactor via Routines and Dimmer VS:
Test Dimmer" is a child device of Switchboard plug-in on my VeraPlus. MSR runs in a Docker container on my Synology NAS, connected to the same local network.
That did not answer my question, how is alexa communicating with the vera virtual device?
-
@elcid Hmm, I gotta think about that.... All I can say is that after creating the virtual switch "Test Dimmer" I went into GetVera configuration > Alexa > checked the new device, then FINISH. Then I ran Alexa app's "Discovery" mode (it found the new device), whereupon it became available inside my Routines.
So as to "how" it communicates, I suppose it's happening through the Alexa <> Vera connection at an API level. That's my best guess.
-
So it's using the laggy Ezlo Alexa plugin. Can you not use HA bridge on your NAS?
[edit] I moved most of the plugins off vera and no aleax plugin , result is alexa is faster and veraplus reloads 1 or 2 times a week, and i am still on firmware 7.31, waiting for offical release of 7.32 as don't want to fall into the no support as you loaded beta firmware trap. -
Ha, your suggestion led me to Google "HA Bridge" and I read up on it over at Github. Fascinating concept, although a bit beyond my technical level (i.e. "slightly scary") and I dare say it solves problems I'm not quite sure (yet) that I have.
As for Vera firmware, yep, on the advice of others, I took the plunge upgrading to 7.32 (beta) and have no regrets. In fact, at the same time I also uninstalled several plug-ins (Site Sensor, Reactor, and GCal3) and have experienced exactly ZERO Luup engine restarts since!
I'll keep your advice in mind for the future, as I learn more about my system's weaknesses. Right now, it does everything I need and more. The experimentation I do here is mostly connected with beta testing MSR, which has kept me occupied for over a month now.
-
-
@librasun said in Interfacing Alexa with Reactor via Routines and Dimmer VS:
Does it also spare you having to go through those godforsaken steps I mentioned earlier (Vera > Logout > Name > Alexa Setup > enable/rename devices > Finish > Alexa app > Discovery)? Cuz that would be wonderful, lol. Have added it to my Reading List.
Probably not, because, as I read it, Vera is the problem......
Openluup is nothing like that bad.
C
-
@catmanv2 said in Interfacing Alexa with Reactor via Routines and Dimmer VS:
Does it also spare you having to go through those godforsaken steps I mentioned earlier (Vera > Logout > Name > Alexa Setup > enable/rename devices > Finish > Alexa app > Discovery)? Cuz that would be wonderful, lol. Have added it to my Reading List.
Probably not, because, as I read it, Vera is the problem......
Is it not as easy as creating the links to the devices in the HA bridge, then asking alexa to discover devices?
-
-
@therealdb said in Interfacing Alexa with Reactor via Routines and Dimmer VS:
Ha-bridge is really plug&play. There’s also a docker image available.
On the promise of that, I have spent the past hour trying to get HA-Bridge up and running on my Synology NAS (using the "latest" downloaded image, and launching it from the Docker GUI), but no joy just yet.
Oh, it runs alright. And I've got all the ports, environment variables, volumes, etc. set up according to all the online FAQs I've read... but, alas, I cannot get anything to come up when I access <my_nas_ip>:8080 (the recommended port, mapped to 8080 in the container).
Looks like I might have to roll up my sleeves, spend a few days reading and understanding Linux and SSH commands, downloading the needed JAR file, and trying alternative install methods through PuTTY.
C'mon Docker, things were supposed to "just work"! Anyone else got HA-Bridge working through the Synology NAS > Docker > GUI > Advanced Settings approach??
UPDATE: I immediately switched over to another Image file, from linuxserver/habridge (which had not appeared in the GUI before when I searched for 'ha-bridge' with the hyphen), and now I've got a working Container! Will experiment more tomorrow.
-
Nice @librasun, looking forward to hearing how you make out.
-
@mikereadington said in Interfacing Alexa with Reactor via Routines and Dimmer VS:
Nice @librasun, looking forward to hearing how you make out.
Haha, baby steps. I managed to configure HA-Bridge to see my Vera Plus, at which point it listed all known Devices (nice). But when I went to "Build" one of those devices -- my "Test Dimmer" which I spoke about earlier -- two things immediately went oddly:
(a) HA-Bridge referred to it as "Virtual Dimmer 21" (its name upon creation in Switchboard, but long ago since renamed to "Test Dimmer" in Vera and honored by MSR GUI)
(b) After I clicked "Add Bridge Device", upon clicking "TEST ON", I got a "Request Error" message (error 404), but the log isn't helpful in determining what exactly is going wrong.
Like I always say, one step forward, two steps back.
UPDATE: Happily, just by giving things time to settle (while I wrote this post), something must have improved. Now when I click "TEST ON" or "TEST OFF" I get a success message:
Request Executed: success [{"success":{"/lights/100/state/on":true}}]Yay!?
P.S. I ran Alexa > Discovery, but she "Could not find any new devices" (my naive hope was that she would discover the "Test Dimmer Switch" newly added to my Bridge Devices). Does this mean I need to map Port 80 of my NAS to HA's internal 8080 port, or something along those lines? I read lots of discussions about this, but the various "solutions" were inconclusive.
-
Seems the current hiccup -- AND THERE ALWAYS IS ONE IN HOME AUTOMATION, RIGHT? -- is that many HA-Bridge users report their Alexa no longer "Discovering" devices. And that's my current issue. Reading the Interwebs feverishly in hopes of a solution.
Guess what I'm also saying is, "Try not to be the first kid on the block to try something new or different." Thank god we have Google.
-
-
@therealdb said in Interfacing Alexa with Reactor via Routines and Dimmer VS:
Yes, you have to map port 80.
In an ironic twist, Docker for Synology NAS will not permit me to change HA-Bridge to listen on port :80, because it "conflicts with other things" in essence. Namely, if you go to <nas_ip>:80, the NAS pushes you up to its secure port :5000.
Not even sure whether this can be worked around, so I'll hang tight for now. Sounds like RaspberryPi users have it easier in this instance.
-
