4 wallmote quad. They came in quite nicely. Some took extra patience and several wakeups. But no real problems, really.
I have a quad and a duo and both work fine. You do have to trigger on events rather than on/off, so it’s not clear what you’re doing and isn’t working. Here’s an example automation, but you’ll need to adjust the node and scene ID based on what you need for your use case. The Events dev tool can be used to find the parameters you need.
- alias: Wallmote Duo Button 1
initial_state: true
trigger:
- platform: event
event_type: zwave_js_event
event_data:
node_id: 36
label: "Scene 001"
value: "KeyPressed"
action:
- entity_id: group.fr
service: homeassistant.toggle
That’s right. As soon as the device is recognized you can start using the event, and it works quite well. But, in my installation HA stops responding to these events after 10-15 minutes. That’s causing me a lot of trouble.
Anyone? I have restarted everything, even the host NUC. No success.
This is the first I’ve heard of this
At first, I thought it was some node red problem, but it’s the same in HA automation. The events simply stop after a few minutes.
I added mine initially via HA Z-WaveJS ADD NODE / REMOVE NODE but after changing over to Z-Wave JS to MQTT I’ve been using it’s control panel as I found it more informative. You can use either to initiate inclusion/exclusion on the controller…
Check your palette and ensure all the node add-ons are up to date. Had same issue.
do your wink motion sensors detect the device manufacturer and model correctly? Mine don’t seem to.
To be a bit clearer, I was asking about the Z-Wave.me Z-Way software & control panel which got installed along with the RaZberry image. It has a very powerful Z-Wave management capability. Can it co-exist with the Z-Wave-JS-MQTT? If not, I need to figure out how to stop its services.
Ah! I thought that was a typo… No, it cannot co-exist. Only one can item can use the controller at a time. You can leave it installed but it cannot be running while HA is using the controller.
I had to use Z-Way once to upgrade the RaZberry firmware back when I was using HS. I created a separate SD card/image for it and booted the Pi from that to use the software. There should be a way of stopping it though, possibly via systemctl?
I hope they haven’t crippled it!
Thanks again Daniel - That’s a good idea to keep a separate SD-Card just for maintenance. Have you been happy with the RaZ responsiveness with the ser2net bridge?
Yes! About an hour ago (17:37 PST to be exact) my 6 iBlinds window blinds all starting closing within a 3-4 second time frame as compared to 10-15 seconds before. Everything else I’ve tried is lickety-split now compared to ozw 1.6…
trigger:
- platform: state
entity_id: binary_sensor.south_patio_lux_override
to: 'off'
for: '00:05:00'
from: 'on'
condition: []
action:
- service: light.turn_on
data:
entity_id:
- light.living_room_blind
- light.patio_door_blind
brightness_pct: 97
- service: cover.set_cover_position
data:
entity_id:
- cover.kitchen_blind_1
- cover.kitchen_blind_2
- cover.kitchen_blind_3
- cover.bedroom_blind
position: 97
The disappearing zwave_js_events problem is solved, and maybe the solution can help others in similar situations:
I have a Heltun HE-ZW-THERM-FL2 floor thermostat, which is a very nice product, but:
The “only” thing that had changed since the events worked for more than 15 minutes after restarting, was that I had excluded and re-included it into my network (because of strange behaviour).
So, today I removed it again (and reset it, to make sure it was really gone).
Now the zwave_js_events have been flowing nicely into both automation and NR for more than 2 hours.
I guess the Heltun was flooding the zwave network for some unknown reason.
Yes, you can use the following commands to stop and disable:
systemctl stop z-way-server.service
systemctl disable z-way-server.service
If you ever need to revert, use start and enable respectively in the above commands.
1 Like
It works just fine with ser2net. I’ve been using it for ages with several different home automation systems (Homeseer, Indigo, OpenHAB and HomeAssistant).
The responsiveness is not about ser2net being able to handle the traffic, it’s about the client side solution. It’s blazing fast with Homeseer, Indigo and OpenHAB. It’s also fast (most of the times) with HomeAssistant. I don’t know why sometimes I can see a 2, 3 second delay with HA. But let’s give the new ZWaveJS solution some time and I’m sure the developers will find ways to improve. It’s already better than the 2 previous incarnations of zwave integration.
1 Like
is there already a guide on how to delete a failed Node? After a failed inclusion, I am stuck with a ‘dead’ node 42
Ive tried to excluded it again of course, but it wouldn’t work. I did manage to include the same device after wards, and now am stuck with a dead Node.
I can see it in the device_registry, and deleted that, after which I restarted then instance, only to see it get back in the device_registry:
,
{
"config_entries": [
"852redacted128f1f"
],
"connections": [],
"identifiers": [
[
"zwave_js",
"redacted42"
]
],
"manufacturer": null,
"model": null,
"name": "Node 42",
"sw_version": null,
"entry_type": null,
"id": "redacted5",
"via_device_id": null,
"area_id": null,
"name_by_user": null,
"disabled_by": null
}
What to do, since I fear a dead Node is harmful to the Zwave mesh network. Thanks for having a look.
btw, this wasn’t a nice experience, since after the failed include, All devices were And stayed unavailable. A mere restart didnt help (Zwave stick remains powered after all) and had to reboot the host. Of course after that all battery operated devices were still unavailable, and it took me more than a few to get everything back up and running.
Not a very smooth operation just yet…