Errors after updating to MQTTController build 25139

[toggledbits]

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.

[toggledbits]

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.

[RogerO]

@toggledbits Will you post a list of the devices you see in the initial survey from the nine participants? I have half my system on Vera and would move over any devices I have that are not on your list.

[kellyjelly32]

Really appreciate the effort. My Vera with all the non-migrated Z-Wave is currently not reachable (holiday home). Can't migrate the devices to HA without being there. End of March I might be there to do it. Still need to find a way to get MSR to run. There is no easy way to run it on the same hardware my HA is running on (I run HA OS on bare metal). Or have I missed a MSR addon for HA?

[sender]

Can you please first answer my question? It's pretty much work what you ask.

Question: I know reactor by name. Do I need it? I have 80 zwavjes devices and a fully loaded homeassistant (+20 integrations)

[RogerO]

I am running MSR in docker. I deleted MSR and installed the zwavejs version pointing to the MSR data directories. Didn't loose a thing.

[vezinpi]

Finally got there... MSR-zwavejs installation (docker) went very well, no issues there. It was a different story with HASS. I am running an unsupported version of Home Assistant Supervised on a raspberry pi (bulleyes). I had to get rid of the zwave2mqtt addon and install it by itself (still with docker). Then I had to re-install the zwavejs integration. Home assistant documentation for zwave has a procedure to migrate the integratio to a new server without losing any devices. That helped alot.

@toggledbits, you should be seeing some data going you way. If not let me know. I will also complete my transition from vera to zwavejs in the following days. So more devices will eventually show up.

[toggledbits]

@sender said in Who are my Home Assistant + ZWave-JS users?:

Can you please first answer my question? It's pretty much work what you ask.
Question: I know reactor by name. Do I need it? I have 80 zwavjes devices and a fully loaded homeassistant (+20 integrations)

If you're not a current Reactor user and familiar with it, this isn't the situation in which to learn. I'll remove you from the test list.

[toggledbits]

I will have my first update to post later today with some fixes and a lot of new device support (thanks to those of you running so far -- lots of data, good stuff!).

[vezinpi]

@toggledbits Since we are at the beginning of this, should we put a header like "ZWAVE-JS" at the begining of the title for every new post related to Zwave-JS just to flag the topic? Or do we keep on going into this thread for all issues, questions, etc...?

How would you like us to proceed?

[toggledbits]

I think that's a great idea. Actually, you can use tags in posts... maybe that's even better?

[toggledbits]

Build 22049 for zwavejs now posted. Some bug fixes, and a lot of device mapping.

[eonnet]

Hello, i'm running zwavejs2mqtt addon on Home Assistant and the addon don't allow to connect to the addon via IP address. Is there a solution for this or i'm out of luck?

I'm running my Reactor on a docker on Unraid, and home assistant os as a VM on the unraid, i can't install docker zwavejs2mqtt because for some unknown reason my zwave stick loses a connection with the docker after couple of days and cant find the solution for that.

cheers

[sender]

@toggledbits why not answer my question? Do I need msr? What's in it (extra) for me?

[toggledbits]

@sender If you're happy with whatever you are using for automations, you may not need Reactor. If you're struggling with Node-Red or find HA's native automations too limiting or clunky, then Reactor may be an alternative you find agreeable.

[toggledbits]

Build 22050:

• Continued improvements in attribute mapping for devices (locks are entirely new in this release).
• Z-Wave device polling see docs

[toggledbits]

Build 22051:

• Fix node/entity-specific interval on polling
• More device updates and action enhancements

[toggledbits]

Build 22052:

• Fix startup synchronization issue causing problems for polling when connection reset/restarts.

[eonnet]

Hello, i managed to connect the HA add on to reactor. The first thing i noticed is that mappings for fan on ZXT-600 and ZXT-120 IR extender for AC are incorrect, on reactor are as follows: 0-off, 1 - auto, 2 - continuous, 3 - periodic, 4 - low, 5 - medium, 6 - high, in zwavejs web console are 0 - Auto low, 1- Low, 3 - High, 5 - Medium

[vezinpi]

@eonnet said in Who are my Home Assistant + ZWave-JS users?:

Hello, i managed to connect the HA add on to reactor.

As I mentionned earlier in this thread, I also had issues with the zwavejs2mqtt HA addon. The only option I found was to remove the addon and install it stand alone but still in Docker.

I am just curious to know your setup and how you manage to make it work still using the HA addon.

Thanks