The security key should not be a problem. Hopefully, you aren’t pulling the stick out to pair devices. If you have been, just use the Zwave management panel to add devices. Rebooting may return the device to /dev/ttyACM0 but you know how to fix that.
Yup security key setup went OK
rebooted fine, no change to where it thinks the zstick is plugged in for now…
so far so good…
seeing if I can add a device via the panel…
There is an iOS app and on an Android device, you can add a desktop shortcut that looks like an app. Makes it easy to walk around to the device and start the pairing from the mobile app.
doing that…
Keep us updated.
Nope. Lock refusing to pair.
Not a shock. Thing’s been a pain in the ass since day 1. (Schlage Connect)
Zwave still up & going. I’ll keep plugging away at it…
I always reset a new Z-wave device if there are facilities with the device if possible. Then I exclude the device from HA using the Z-wave panel facilities as though you were excluding the device. Then go through the include process using the Z-wave panel. Battery powered devices don’t usually stay awake very long. Follow the directions. I usually have a terminal open and use tail -f OZW_Log.txt to see what is happening as I pair devices.
I figured.
I had it previously setup with another controller (Almond+). It stopped working and I have unpaired, factory reset, etc. Never got it to repair successfully ever again. Its a little far from the controller, too. I may get a switch or a repeater to put in somewhere between the two.
Z-wave really benefits from more well-spaced devices. Just one or a very few especially battery powered devices is tough. Battery powered devices do not contribute to the mesh. Rather than a repeater, do get a real device. The least expensive Z-wave plus device I have found is a lightbulb. Maybe not the most useful if they get turned off but they can work in the right location. In the meantime can you move the Pi closer to the lock.
I may give that a try actually, but for now I’m packing it in.
It’s minus 16 out and all this door opening and closing is losing me a ton of heat (Also to know 100% that my lock is unpaired from the old controller, I may have to move my Almond+ down to the lock…and that is going to be a much bigger PITA. The Pi is also a bit tricky to move…it’s mounted in a DIY “rack”…with the power cables all tacked down…and the network cables all tacked down…and the USB cables are all tacked own. Undoing it all is a bit of a cable management job as there’s a bunch of other stuff mounted in the rack.)
I’m poking around with the GUI layouts & groups for now.
Thanks for the help.
I will reply to this thread once I get there.
Good luck!
I did just install hass.io. There isn’t much you can do from ssh. You are pretty much shielded from the OS.
At one point before I nuked everything and reset to an earlier snapshot, I had installed the terminal add-on and found it equally useless.
hass.io is pretty much locked down. You get convenience I suppose but lose a great deal of control, troubleshooting capabilities, and the opportunity to learn Linux and open source software.
I get that.
I had a pretty vanilla HomeAssistant install running on a standard desktop with Ubuntu (along with Squeezebox server). I just couldn’t deal with the fan noise. I like the ease of deployment with Hass.io & Rpis, but I can see where there are troubleshooting issues. Coupled with the documentation seeming to weave back & forth across different install types for various platforms, it’s not ideal.
I’m also noticing that Phillips Hue is unstable as shit…and not a peep from the error logs. On my old install I had it locked down in config rather than letting the discovery component find it all the time. I may try to hard code it in the config file and see if that solves it.
You can use a Pi for a more standard install. There is hasbian which is an SD image with homeassistant installed. It sets everything up and has some auto install/setup tools. If I were to use a Pi again, I would just use raspbian and a simple pip3 install homeassistant and forget about the virtual environment. I think the venv causes more misunderstandings and problems than it helps. I may go back to a Pi one day.
If I get fed up enough…I’m going back to standard PC server. I’m just going to bury somewhere I can’t hear it ($$cabling$$). Before I moved it I was starting to get the hang of SSH & VNC remote control.
I can move the pi out to the fringes as a client (squeezeplayer, IP cam, whatever…) where it won’t eventually choke on everything I’m going to try to pack onto it as a server…
I use an Intel NUC that is silent most of the time. I run VMware ESXi and have a bunch of virtual machines for lots of different projects. It is simple to spin up a fresh machine to test something on and blow it away when it isn’t useful anymore.