[SOLVED] Do I have to unplug my Z-Stick Gen 5 to include new devices?

[5iver (Scott Rushworth)]

@anonymous.one

The above will spit out all the logs with that time stamp, which could be helpful to you if you wanted to look at the past events but limit the only a date/timestamp.

To add to this, you can set zwave into debug (log:set DEBUG org.openhab.binding.zwave), and grep for the node in a tail of openhab.log. Just remember to set zwave back to WARN when you’re done. This can be used real-time or for historical data (the -n option for tail), and will provide a lot more detailed info for troubleshooting the device.

tail -F -n5000 /var/log/openhab2/openhab.log | grep "NODE 2:"

@162884

Now when I walk in front of the MultiSensor, nothing happens. It’s like the rule never fires off.

You may want to double check the configuration parameters for the device (best done through Habmin). There is a setting which disables motion detection. Do you have any associations setup?

And…

How to use code fences

We all have to type this content over and over and over. Here is a posting we can all point to when the topic comes up. Why use code fences? Because rules, sitemap, logs, and configs are all but unreadable when code fences are not used. When to use code fences? Whenever one is posting any sort of code, config, log, and any text where line wrapping, indentation, and using an equal spaced font makes the text more legible. How to use code fences? Use 3 backticks (```)... Or use <code>... …

@KjetilA

Please note, however, that it is strongly recommended to have the device you are trying to include in very close proximity of the Zwave controller (USB stick), so that you are sure to have a direct link between the two and not going through the mesh, when doing inclusion.

I respectfully disagree… why do you strongly recommend this? For older devices that only support low power inclusion, and to utilize the Security CC, being in close proximity to the controller would be required. For all other cases, it is best to do the opposite, and perform inclusion with the device and controller in their final locations. This is especially true for mains powered devices, so the routes are set properly.