This is how I am using in automation. Parameter 3 is for chimes in zse19 and value is the chime you want to play. I believe it comes with 0-34 and you can load your own which will be starting from 35
My minimote have stopped working with HA. In zwavejs2mqtt is can see the button presses in the log but when i goto the main view I see two statue for minimotes
- Protocolinfo - After restarting zwavejs docker, once I wake the mininmote it goes to Nodeinfo
- Nodeinfo - Minimote after waking up. Other device normally goto complete after protocolinfo except for Minimotes.
Anyone have any idea what might be the issue? Weird part is I can see button presses for each of the buttons and respective scene id in zwavejs2mqtt log
zwavejs2mqtt: 4.0.1
zwave-js: 7.3.0
Hi,
Same situation for me…
I tried to exclude, re-include, re-interview, reset, edit some parameters but unfortunately no result.
When using Zwave JS to MQTT and looking at the notification status, it seems that they are never updating and that they are stuck at the following states:
Then I understand this is the info which is permanently forwarded to HA and this is why the status is never changing.
If I check the binary sensors, their states is updated properly when dor is closed/open or when motion is detected.
It looks like an update or link problem between these two but didn’t find out how to solve it.
It is also unclear for me if this device is supposed to be supported or not…
Regards
HI Guys,
anyone knows how to calibrate may Fibaro Shutter 3?
thank you
- Use Z-Wave JS 2 MQTT to send the configuration using its GUI
OR
- Use Z-Wave JS service zwave_js.set_config_parameter to set value 2 on parameter 150 to force calibration
OR
- Use the switch attached to the device:
Calibration using connected momentary switch
- Make sure:
- the device is supplied,
- the momentary switch is connected to S1 and S2 terminals,
- the device added to the Z-Wave network,
- parameter 151 is set to 1 or 2.
- Press and hold
or 
switch for at least 3 seconds - Press and hold the same switch again for at least 3 seconds.
- Press and hold the same switch again for at least 3 seconds.
- The device will perform the calibration process, completing full cycle – up, down and up again.
- Test whether the positioning works correctly.
1 Like
I’m confused on the HA UI translation of parameters in configuration from ZJS Server.
For example, my Inovelli switch is set up with the following parameter 51:
But HA is showing the following:
where the descriptions are opposite each other (0 = no delay, 1 = delay/scene control).
Seems like HA Integration isn’t following the ZJS description field. Thoughts? @cgarwood not sure if this is a bug or how I should handle?
THANK YOU SO MUCH!
1 Like
The screenshots seem to be showing completely different devices. Which switch do you have? Your first screen shot is of the LZW31-SN. It’s also the JSON of the device file, it’s not what HA will see. HA sees what zwave-js tells it.
Instant On == LZW30-SN or LZW36
Button Delay and Scene Control == LZW31-SN
I only have LZW31-SN devices and LZW36’s, but those are taken from the same node ID.
It seems the switch config might have changed recently, so re-interviewing the node is bringing across the right description into ZJS integration.
Hoping for some help with association using zwavejs2mqtt
I’ve setup an association so when my basement hallway light switch is pressed, the front theatre and back theatre lights also come on. This is working fine.
What I’m noticing is that the entities light.theatre_light_front and light.theatre_light_back do not turn on even though the switch itself is turning on through the association.
Aside from creating an automation to turn the 2 entities on/off when the hallway light turns on (defeating the purpose of association), is there a way to get the entities to turn on when controlled through association?
EDIT: This may be specific to the GE switches. I just tested associating an Inovelli switch and the entity is turning on/off
Yes, replace the GE switches with good switches like Zooz or Inovelli.
Not in a huge hurry, but when will it be possible to remove dead nodes? And no I don’t want to switch to mqttzwave. Like I said not in a hurry, just have 4 dead ones hanging out.
LOL, I actually have 3 undeployed Inovelli dimmers, so that’s probably exactly what I’ll do. It’ll fix my problem and then I’ll bury the GE switches out in the sheds to give me control out there.
1 Like
I kind of have the same problem with my Qubino devices (ZMNHDD).
I press “off” in the UI on a light entity.
The lights will dim to off.
The UI states “off” for the light entity, the directly switches to “on” again.
Then I have to press “off” again in the UI and its its states “off” as it should.
Also notices that this is only for the light entity.
The qubino device also provides a switch entity that works perfect with “on” and “off”.
This was working before I updated either HA or ZJS to lastest version.
I might have been 2 releases behind before so Im not sure which version exactly that this was actually working on.
That’s funny - my GE switches support associations better than my Zooz switches do (the earlier ZEN23s don’t support associations at all - and yes, I confirmed this with zooz support). GE is one of the few that makes toggles, so I’m staying with them…
The GE/Jasco 14291 / ZW4005 switches do not support associations at all. They also blow up randomly if the power goes out or you flip the breaker.
I am moving my Schlage/Allegion BE468, BE469, and BE469ZP locks from HomeSeer to HA zwave_js. One thing that I was missing is the last Access Control notification that says how the lock was locked or unlocked, such as Manual lock operation, Manual unlock operation, Keypad unlock operation and which key was entered on the keypad.
I have worked around this for now by making an automation and python script to watch for zwave_js_notification events and record them in sensors.
If it helps someone else, I have these in home-assistant/collect_zwave_events.py at 8f8faeb42a356f76792ce2864bea52882bd2638d · rodpayne/home-assistant · GitHub and home-assistant/collect_zwave_events.yaml at 8f8faeb42a356f76792ce2864bea52882bd2638d · rodpayne/home-assistant · GitHub. (What I haven’t figured out is how to look up the device name from device_id or node_id to make it easier to find the right sensor, but it works anyway.)
1 Like
Regarding First Alert ZCOMBO
I seemingly have two different generations of these smoke/co detectors, the first generation only shows battery level and battery state, with three disabled entities.
The second generation shows the whole smash with 9 entities, plus 7 hidden entities!
I am guessing this is something to do with the smoke sensors firmware as gen 1 is FW v0.5, and gen 2 is FW v11.0
These should help you: Templating - Home Assistant
You can use the device_attr template function to convert a device ID into an attribute like name
Sounds like there is no fingerprint for the first version in the zwave2js database. Does it show up as an unknown device in the Device Info page?
I had a similar thing with one of my Fibaro Flood sensors. One was fully available and another wasn’t (just three barebone entities and no ability to configure). Turns out they were slighly different revisions and one wasn’t in the zwave2js database.
I ended up updating the config file and making a pull request to the main project (which should be included in an upcoming version).