Who are my Home Assistant + ZWave-JS users?
-
Using HA with zwavejs2mqtt.
-
Count me in!
-
I do not use it, as we have talked about before, but if necessary I will install it and can be one more to help with tests.
-
Hi,
I would be happy to assist. I am also using zwavejs2mqtt without the mqtt part activated.
-
Sign me up
-
Running a HA with zwaveJS2 and an old Vera Lite with some not-yet-migrated devices. Reason for not migrating is that I love Reactor. On HA I was not able to get MSR to run yet.
-
@kellyjelly32 said in Who are my Home Assistant + ZWave-JS users?:
On HA I was not able to get MSR to run yet.
It's a pretty easy setup. If you've had trouble getting it done, I recommend opening a new thread for that discussion.
Ref: Docs: Configuration for Home Assistant
-
@toggledbits Any info on what and when this is coming?
-
Had some issues with Aqara motion sensors falling off my Hubitat after a few hours. (Yes, the manufacturer is not supported on HE.) But this led me down a path to stand up HA in my docker. Which then led me down another path of getting the zwavejs2mqtt docker running and integrated. So I may be down for this.
Am I assuming that MSR will become my JS provider and I could possibly shutdown the zwavejs2mqtt docker?
-
@rogero I got bogged down trying to get newer scene controllers to work, and I think I've got it now. Really nice, actually (using a Zooz ZEN32 for testing). Heck, I even got an ancient Everwave SC-7 working great, and it just wasn't reliable on Vera at all. The effort being put into Z-Wave JS really shows.
@3rdstng said in Who are my Home Assistant + ZWave-JS users?:
Am I assuming that MSR will become my JS provider and I could possibly shutdown the zwavejs2mqtt docker?
You'll either need to keep zwavejs2mqtt or install and run the zwave-js-server. I'm not doing a direct interface (i.e. library direct to serial port) just yet, but that's coming. The management tools of zwavejs2mqtt are pretty nice, so that's a good incentive to keep it.
-
Excellent, I have a few of those installed and the Blueprints I found for them are not super dependable.
-
@toggledbits Next you will be saying your Leviton scene controllers are working perfectly.
-
@rogero I've had those going good for a while on Vera, using a plugin I wrote but never published (a few people got it, though... were you one of them?). I don't expect much trouble from them on Z-WaveJS. Also testing Hank 4-button and Remotec ZRC-90.
-
Yes, I was one of the people you shared it with. It did work very well. Replaced them with the ZEN32's but at my age I cannot remember what 4 pushes of the bottom left button does, etc. Need to tape a legend to the wall. Look forward to having them running in MSR.
-
Haven't forgotten you all... I've been working furiously at putting this together, including a new build system (because I'll be doing this release on a separate track, not in latest). I'm trying to get something out this weekend for a first look.
Do any/all/none of you all use Discord?
-
I do not.
-
I don't, but I could if that's the way you want to communicate.
-
@vezinpi said in Who are my Home Assistant + ZWave-JS users?:
I don't, but I could if that's the way you want to communicate.
Same
-
Just trying to gauge what people use. Doesn't seem like a path with enough support in this community, and that's fine; it's not my favorite, either.
-
toggledbitswrote on Feb 16, 2022, 8:46 PM last edited by toggledbits Feb 16, 2022, 3:49 PM
OK, I just PM'd the 9 of you that stepped up. If you replied on this post but didn't get a PM from me, let me know.
Some things to know about the test...
First and most important to Docker users, it runs on a different image from the mainstream latest, so you'll need to create a new container.
For all participants, the test code is bi-directionally compatible with the mainstream latest release path, so you'll be able to move back and forth between them if you need to. I think you'll be fine staying on the zwavejs track, and it will keep pace with other development throughout. Always make a backup of your config, of course, just in case, but you should be able to use the same config freely with any current version (the non-Zwave versions will complain about the controller not being available, though, and then move along).
I have a meager variety of devices to test with (lots of devices but limited in breadth of type and manufacturer), so I expect a lot of exceptions and oddities with the various devices out there. Don't panic. We know from all of our other Z-Wave platforms that manufacturers have leeway to do things within the spec, and they take it, and that complicates onboarding devices. Everyone goes through this. We won't be an exception.
I have to say, I'm really excited about this. ZWave-JS is really nice. First and foremost, it seems completely unbothered by device errors and mesh problems; it doesn't crash, delay, or do other things that other (ahem) platforms can't seem to get right. That alone makes it worth the effort. It's got a lot of support and the developers are really active. I have high hopes.
Discussion here is fine. Seems like the easiest way to go. Remember to be as complete as possible in your descriptions of issues, including device details, logs, etc. This version will create its own
zwavejs.log, so that's a good place to start (and removes the noise of all the other subsystems).There is data collection. The form you are asked to complete in the PM declares this as well, and you are asked to agree to it. It sends me a copy of your Z-WaveJS device inventory on startup, which will help (a lot) with device support. It does not send logs; that we'll have to do as needed. Happy to answer any questions on this, of course.
13/51