[SOLVED] Zigbee Error Can't connect to devices

LuigiTheHunter · March 22, 2019, 5:47pm

Part two:

Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.419 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 0017880102487913: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.418 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 000B57FFFED9D2F1: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.417 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE3497EF: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.421 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 84182600000F1683: Coordinator is unknown or not online.
2019-03-22 18:26:22.417 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFED2DB77: Coordinator is unknown or not online.
2019-03-22 18:26:22.423 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 000B57FFFED9D2F1: Coordinator is unknown or not online.
2019-03-22 18:26:22.424 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE3497EF: Coordinator is unknown or not online.
2019-03-22 18:26:22.426 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 0017880102487913: Coordinator is unknown or not online.
2019-03-22 18:26:22.426 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE8A5ECD: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.427 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE88B7DA: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.429 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFED343B8: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.431 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE88B7DA: Coordinator is unknown or not online.
2019-03-22 18:26:22.434 [hingStatusInfoChangedEvent] - 'zigbee:coordinator_cc2531:ba690b37' changed from OFFLINE: Failed to open communications port to OFFLINE (COMMUNICATION_ERROR)
2019-03-22 18:26:22.436 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE8EEDE7: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.436 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE752261: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.437 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE8A5ECD: Coordinator is unknown or not online.
2019-03-22 18:26:22.431 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFED343B8: Coordinator is unknown or not online.
2019-03-22 18:26:22.441 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE752261: Coordinator is unknown or not online.
2019-03-22 18:26:22.442 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFED59076: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.445 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010670E695: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.445 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 84182600000F1683: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.449 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 001788010670E695: Coordinator is unknown or not online.
2019-03-22 18:26:22.449 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:90fd9ffffe752261' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.448 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFED59076: Coordinator is unknown or not online.
2019-03-22 18:26:22.440 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE860071: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.445 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE8EEDE7: Coordinator is unknown or not online.
2019-03-22 18:26:22.455 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A01CE94: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.455 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 84182600000F1683: Coordinator is unknown or not online.
2019-03-22 18:26:22.455 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 0017880102487913: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.457 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE860071: Coordinator is unknown or not online.
2019-03-22 18:26:22.457 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 0017880102487913: Coordinator is unknown or not online.
2019-03-22 18:26:22.460 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:90fd9ffffed343b8' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.460 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA00AD38A7: Coordinator status changed to OFFLINE.
2019-03-22 18:26:22.464 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA00AD38A7: Coordinator is unknown or not online.
2019-03-22 18:26:22.463 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 7CB03EAA0A01CE94: Coordinator is unknown or not online.
2019-03-22 18:26:22.470 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:90fd9ffffe8eede7' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.474 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:90fd9ffffe860071' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.480 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:90fd9ffffed59076' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.485 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:84182600000f1683' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.490 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:001788010670e695' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.492 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:7cb03eaa00ad38a7' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.495 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:7cb03eaa0a01ce94' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)
2019-03-22 18:26:22.501 [hingStatusInfoChangedEvent] - 'zigbee:device:ba690b37:0017880102487913' changed from UNKNOWN to OFFLINE (BRIDGE_OFFLINE)

LuigiTheHunter · March 30, 2019, 10:17pm

No clue?

giskard · March 31, 2019, 11:31pm

Looks like the serial port your thing is configured to is not available.
I actually expected the log message to contain the name of the symbolic link that you said you were using. Are you sure you configured your thing properly?

I use a simple udev rule to ensure that my device is found after every reboot (‘/etc/udev/rules.d/010-zigbee.rules’):

SUBSYSTEM=="tty", ATTRS{idVendor}=="0451", ATTRS{idProduct}=="16a8", SYMLINK+="ttyUSB_ZIGBEE"

You should be able to find out the vendor and product ID of your Zigbee dongle by entering ‘lsusb’ in the shell. In my case, its the following entry:

Bus 001 Device 003: ID 0451:16a8 Texas Instruments, Inc.

The next step is very important: to make the above symlink visible to Openhab’s Java Runtime, you have to add it as a JVM launch argument.
In my distribution of Openhab2 (may vary in yours), you can edit the file ‘/etc/default/openhab2’ and change the value of ‘EXTRA_JAVA_OPTS’ to this:

EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB_ZIGBEE"

If the key already contains values you can instead append the above content between the quotes and separate it with a blank from the other values.

After a reboot, you should see the symbolic link created by the udev rule pointing to ‘/dev/ttyACM<?>’ by entering ‘ls -l /dev/ttyUSB_ZIGBEE’:

lrwxrwxrwx 1 root root 7 Mär 31 00:43 /dev/ttyUSB_ZIGBEE -> ttyACM0

You should now be able to select ‘/dev/ttyUSB_ZIGBEE’ in PaperUI’s thing configuration interface (or alternatively use it as ‘zigbee_port’ in your .thing file).

LuigiTheHunter · April 1, 2019, 7:47am

Thanks for your great answer, I will try this out tomorrow cause I’m at the hospital right now.

Kim_Andersen · April 1, 2019, 5:04pm

This part I cant get to work.
I have tried with symlinks many times, an every time it doesnt work. I can not pick the correct usb port (symlink port) in PaperUI, cause its not listed. But my symlinks do work allright… They´re just not available in paperUI. And I dont understand why. I have struggled with this so many times now

[18:47:23] openhabian@openHABianPi:~$ ls -l /dev/ttyUSBZStick
lrwxrwxrwx 1 root root 7 Mar 31 22:55 /dev/ttyUSBZStick -> ttyACM0
[18:48:13] openhabian@openHABianPi:~$ ls -l /dev/ttyUSBRS485
lrwxrwxrwx 1 root root 7 Mar 31 21:58 /dev/ttyUSBRS485 -> ttyUSB0
[18:48:51] openhabian@openHABianPi:~$ ls -l /dev/ttyUSBMeshConn
lrwxrwxrwx 1 root root 7 Apr  1 18:53 /dev/ttyUSBMeshConn -> ttyUSB1
[18:53:49] openhabian@openHABianPi:~$

/dev/ttyUSBZStick, /dev/ttyUSBRS485, /dev/ttyUSBMeshConn are not available in PaperUI.
Can you tell me what I´m doing wrong, cause its driven me nuts every time I connect a USB stick it mess everything up?
If I pick the , ttyAMC0, ttyUSB0, ttyUSB1 the devices work… But its a bit difficult to know, and I doubt thats the idea using symlinks.

This is my serial rules:

SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="ttyUSBZStick", GROUP="dialout", MODE="0666"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="ttyUSBRS485", GROUP="dialout", MODE="0666"
SUBSYSTEM=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="8856", SYMLINK+="ttyUSBMeshConn", GROUP="dialout", MODE="0666"

And this is my java opts:

EXTRA_JAVA_OPTS="-Dgnu.io.rxtx.SerialPorts=/dev/ttyUSB0:/dev/ttyS0:/dev/ttyS2:/dev/ttyACM0:/dev/ttyAMA0:/dev/ttyUSBZStick:/dev/USBRS485:/dev/USBMeshConn"

LuigiTheHunter · April 7, 2019, 12:42pm

Sorry was at the hospital till recently. I did exactly like you said. And thats how I had it before, but it still does not work. It says the tty USB Stick is online. But all the parameters and everything is empty.

LuigiTheHunter · April 9, 2019, 1:23pm

It does not work, with or without symlink anymore. I think i will try to completely remove and readd it.

LuigiTheHunter · April 23, 2019, 10:09am

Thanks for your answer. Sorry for the late answer…

I’ve done exactly as you said. And like I said since I used a symlink the stick stopped working somehow. Maybe I did something wrong while creating it, I tried the stick on a fresh new Installation and it looked like i got the same issue so (maybe its the stick?). Unfortunately I bought this stick for 40€ because I don’t own the equipment of flashing my own. What can I do now? Do I have a chance or resetting the stick completely?

Thanks

LuigiTheHunter · April 30, 2019, 5:17pm

I tried many things nothing seems to work.

LuigiTheHunter · May 8, 2019, 8:49am

I followed your tutorial again this is what happens after it:

Kim_Andersen · May 8, 2019, 8:57am

Is the stick online? If not, it makes no sense trying to add devices.

LuigiTheHunter · May 8, 2019, 9:00am

Surely it is.

Kim_Andersen · May 8, 2019, 9:11am

Hmm Thats odd.
I dont think it has been fully included. If this is the coordinator it looks very strange.

This is my zigbee coordinator:

LuigiTheHunter · May 8, 2019, 9:27am

I know without the symlink my Coordinator looks like yours too. But I followed the tutorial exactly and I even setup a pie with openhabian.

Is it normal that he says this:
2019-05-08 10:54:58.426 [DEBUG] [ding.zigbee.handler.ZigBeeSerialPort] - Serial port '/dev/ttyUSB_ZICK' closed.

Kim_Andersen · May 8, 2019, 9:35am

No, it´s not normal…
Forget about symlinks. They wont work if you use a newer OH 2.5 build.
Make sure to get the stick to connect properly… I can not say exactly how, but you need to fiddle with it after rebooting your Rpi. When you get the connection right, DONT! reboot or restart… Otherweise you´ll have to fiddle again each time… (I know it´s a pain atm…).

Do you have other USB/Serial devices connected to your Rpi? If not, I suspect you should be using /dev/ttyUSB0. Maybe /dev/AMC0 or whatever available…
If you do have other devices, disconnect whatever you can live without, untill you find the correct USB port to use for your stick…

Its a real pain to be honest… But thats the best advices I can give you atm.

LuigiTheHunter · May 8, 2019, 9:40am

WTF, so symlinks don’t work anymore? And there is no other way? OMG, this is really pain. But thanks for the advice i did not know this before. I will remove the symlink and start fiddling. xD

Kim_Andersen · May 8, 2019, 9:48am

Not if you use a newer openhab 2.5 build… I cant tell you exactly what has gone wrong, but it´s something with the serial driver, and newer changes in OH.
I have to admit though, I have been struggling with symlinks far longer than this “announcement” says… It has gone from bad to disastor since I upgraded from OH 2.4 to OH 2.5M1 build #1575. Atm I try to avoid rebooting, hoping this will get fixed soon.

You dont have to remove the symlinks settings… Just dont use them.

LuigiTheHunter · May 8, 2019, 9:54am

Ok thanks for this info. And thanks for helping me resolving this issue