Just wanted to chime in to tweak the noise to signal ratio. Several versions ago, I followed the guide that @petro created when I saw that Open Zwave was being deprecated. Took about an hour, but my 50+ devices are now working just fine. No speed issues to speak of. I have several automations that depend on motion to trigger. Aeotec stick on a Raspberry Pi 4.
I recently added a couple secure devices and that process went smoothly as well.
In addition, I got some new functionality (at least I think itās new) - I have some switches that let me double or triple tap on/off and Iām able to trigger automations from that via Zwave-JS events.
I have no idea at all with what you are referring to with that statement.
I never use the UI editor to create any automationsā¦everā¦and so I donāt have access to any device based automations so all of my automations are āstate basedā and none of them have stopped working.
There was no change. state based automations still work just fine.
Unless there was some breaking change in the latest HA? But I seriously doubt it.
I saw literally zero difference between the old zwave and zwavejs. Itās neither better nor worse.
All of my motion devices are the exact same devices. My Z Wave stick is the exact same stick. The only thing that changed was updating to JS Z Wave. Before my motion based automations would trigger 4-6 feet into the room. Now I get to the middle of the room and have to wait before the light turns on.
The only thing that changed was updating to JS Z Wave, nothing else in the equation changed.
Unless you think I became a meta-human and turned into the Flash, and am now somehow walking into the room much faster than before.
The JS update completely changed how and where data from my motion detectors are brought into the system. Iām glad your system didnāt break, but acting like Iām imagining this, or that it didnāt completely break my automations, shows you really donāt understand things as well as you think you do.
Ok, still, that doesnāt give any information on what the problem could be. Zwave is a mesh network of devices. All devices behave differently. Things have been updated too. The original OpenZwave 1.4 (which is what you came from) is an old package dating back to 2016. As you can imagine, a lot has changed in 6 years.
Itās just a way of reporting. You can actually change the reporting type on most devices. From basic to notification. But that depends on the device. Basic reporting will give you a binary sensor.
Thatās a device trigger. You can change it to a entity_id based trigger.
Remember when I said to be nice? Calling people smart asses is not the way to handle this. Just ask your questions. Why do you act this way? No one here is āout to get youā. Just act like a reasonable adult. Is that so much to ask?
I have the same amount of Z Wave devices before and after the update. No one moved in and is walking around triggering extra motion detectors. I went into each sensor and adjusted the refresh time to 1s shorter than the default 3s
The old zwave platform did not translate everything properly. Zwave JS does. This is what heās running into.
See how his trigger says 255 for the state? That means old zwave was too dumb to understand that this was a binary device, so it made a sensor that just had 2 states 0 and 255.
No one is saying you arenāt having these issues. However the issues can be over come and itās clear you donāt know how to do that. For some odd reason, you think do know how to fix this yourself. Itās okay to not know things. Thatās life. Can we move on from this childish attitude and actually solve the problems at hand? Please go to your device and screenshot it so we can see how to get you the correct trigger instead of a device trigger.
