Set Reaction > Script Action

[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

[toggledbits]

Expect LOTS of device mappings to be off, or very generic. Not all devices follow the Z-Wave spec recommendations, particularly legacy Z-Wave devices, and even some first-generation Plus devices. I imagine this is why the Gen 2 specs are a good bit tighter. Regardless, every oddity and exception has to be handled as what it is, which is why I collect data from the interface. I literally sit and spend hours picking through your devices. On every new release, check those devices that previously didn't seem right. If, after a release or two, things still look or behave oddly, do let me know (specific data, please; if you say "X doesn't work" and nothing else, I will ignore it).

[eonnet]

@vezinpi in addon settings add 3000 port to the host.
And than you can access the zwavejs2mqtt addon via ws://ip:3000

[vezinpi]

@eonnet are you using the supervised version with HAAS os ?

[eonnet]

@vezinpi yes hassos

[vezinpi]

Many thanks

[toggledbits]

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

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

Reactor has its own set of values for its capabilities. These are mapped (or not) into the ZWave standard values supported by the command class, and/or what the device actually supports. Reactor's list is not limited by what the device does, although choosing values the device doesn't support usually won't do anything (or cause a default to be chosen, device-dependent); this has always been true for all devices on all controllers in Reactor.

EDIT: I see where you are getting the numbers, and that's actually a bug (an ancient one, at that) in the Reaction editor, nothing to do with ZWaveController specifically. That is now fixed both for general release 22053 and zwavejs build 22053.

[toggledbits]

Build 22053:

• Fixes in sync with general release build 22053 -- see BREAKING CHANGE notice there
• More small device tweaks
• The default for capturing the zwave-js logs is now false in config (i.e. it won't capture zwavejs log entries by default now).

[toggledbits]

Build 22054:

• Continued device improvements (lots of work on Aeotec devices among others)