Hi @gundark2,
your issue sounds quite similiar to some odd behaviour I’ve seen with Zigbee vs. Bluetooth binding. If I start both bindings in the right order (in my case: first Zigbee, let it open it’s serial port and then the Bluetooth binding to open it’s serial port(s)) both are working otherwise the Zigbee is failing here.
See full post:
So - If I start just one of two bindings using serial ports at the time (or both in the right order as described above), all is fine. So we can exclude the common serial port permission issues - right?
Could you check the same on your side? So, just start zigbee, verify it’s working and then stop zigbee and start just zwave to check if your udev rules and permissions are correct.
@vkolotov suspected the nrjavaserial port discovery probably causing the issue:
@chris: could you provide a version of the binding which requires excplicite serial port setting (as in pre 2.3 versions of the binding) without depending on the serial port discovery just to rule out this possible cause?
Or does it make no sense at all?