[SOLVED] Telegesis ETRX3: Status "OFFLINE" Failed to initialize ZigBee transport layer

Hi Chris,

I saw you solved the Telegesis fails to connect with Openhab 2.4.
I use Openhab 3.2.0 and have the same issue. Hope you can help. It is unclear in my case which commands I should enter in putty to solve this.

  • Telegesis ETRX3 Dongle : status ONLINE

  • Port : /dev/ttyUSB0 : which shows up in putty amongst all other tty*
    However when adding the coordinator with that port I receive the errors.

Raspberry Pi

Some info from log event

2022-01-10 14:47:11.562 [INFO ] [penhab.event.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_telegesis:5e4396f9b1 changed to UNKNOWN.

2022-01-10 14:47:11.568 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:5e4396f9b1’ changed from UNINITIALIZED to INITIALIZING

2022-01-10 14:47:11.604 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:5e4396f9b1’ changed from INITIALIZING to UNKNOWN

2022-01-10 14:48:32.692 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:5e4396f9b1’ changed from UNKNOWN to OFFLINE: Failed to initialize ZigBee transport layer

I think @chris would at least need a debug log (see ZigBee - Bindings | openHAB).

Yes, I would need to see the debug log. The 3.x binding is using the same libraries, and the same binding for the ETRX, so it may not be the same issue as was previously fixed.

Hi Chris,

Thanks for taking the time and swift response. I followed the instructions for the openhab consol and I
cannot see a log subfolder in the userdata folder.

I gave the command ```
log:set debug org.openhab.binding.zigbee
in the openhab console.

I am a beginner but did my best to follow the instructions.

Log files are written to either userdata/log (manual setup) or /var/log/openhab (package based setup) and can be accessed using standard OS tools for text files.

The default installation of openHAB generates two log files:

  • events.log
  • openhab.log

You shouldn’t need to mess around with the config files - just type the various commands listed in the docs directly into the console. This will enable logging, and you can then display the log with the zigbee log view. The log will be the openhab.log file.

I exactly entered the commands below

openhab-cli console
password habopen

log:set debug org.openhab.binding.zigbee
log:set debug com.zsmartsystems.zigbee
log:set info com.zsmartsystems.zigbee.dongle.ember.internal.ash

then opening the online log viewer
Looking for on my raspberry inside the openHAB-userdata folder…according to documentation …
Log files are written to either **userdata/log** (manual setup) or /var/log/openhab (package based setup) and can be accessed using standard OS tools for text files. The default installation of openHAB generates two log files:

However there is no log directory or any logfile inside the openhab
My raspberry is still online with openhab and showing an error on the thing page.

Fronttail is reporting :slight_smile:
2022-01-11 21:21:24.807 [ERROR] [ngle.telegesis.ZigBeeDongleTelegesis] - Unable to open Telegesis serial port

2022-01-11 21:21:24.808 [DEBUG] [tsystems.zigbee.ZigBeeNetworkManager] - Network state is updated to OFFLINE

2022-01-11 21:21:24.809 [DEBUG] [bee.handler.ZigBeeCoordinatorHandler] - null: networkStateUpdated called with state=OFFLINE

2022-01-11 21:21:24.885 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis queue: 1

2022-01-11 21:21:24.886 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis: TelegesisDisplayNetworkInformationCommand [device=null, channel=null, power=null, panId=null, epanId=null]

2022-01-11 21:21:24.904 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis Data:AT+N?

2022-01-11 21:21:24.919 [DEBUG] [gesis.internal.TelegesisFrameHandler] - RX Telegesis Data:+N=COO,11,08,06A9,F3A84D3E69090045

2022-01-11 21:21:24.921 [DEBUG] [gesis.internal.TelegesisFrameHandler] - RX Telegesis Data:OK

2022-01-11 21:21:24.922 [DEBUG] [gesis.internal.TelegesisFrameHandler] - RX Telegesis: TelegesisDisplayNetworkInformationCommand [device=COO, channel=11, power=8, panId=1705, epanId=F3A84D3E69090045, status=SUCCESS]

==> /var/log/openhab/events.log <==

2022-01-11 21:21:24.812 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:5504f370ba’ changed from UNKNOWN to OFFLINE: Failed to open communications port

2022-01-11 21:21:24.814 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:5504f370ba’ changed from OFFLINE: Failed to open communications port to OFFLINE (COMMUNICATION_ERROR)

Ok, that looks fine. I’m not sure why you previously mentioned changing the config files then.

I’m not sure how your system is configured, but I expect somewhere there is a logfile. The folders end up in different places depending on how you have installed the system and this is described in the installation docs.

You don’t have two copies of the binding running do you? It seems strnte that there is a statement that the serial port can’t be opened, but at the same time there is communications being logged showing the serial port is working.

… or two (or more) Telegesis Coordinators fighting for the same serial port?

@Walter1
How to check whether more than one instance of the ZigBee Binding is running:

openhab> bundle:list | grep -i zigbee
238 x Active x  80 x 1.4.2                 x com.zsmartsystems.zigbee
239 x Active x  80 x 1.4.2                 x com.zsmartsystems.zigbee.console
240 x Active x  80 x 1.4.2                 x com.zsmartsystems.zigbee.console.ember
241 x Active x  80 x 1.4.2                 x com.zsmartsystems.zigbee.console.telegesis
242 x Active x  80 x 1.4.2                 x com.zsmartsystems.zigbee.dongle.cc2531
243 x Active x  80 x 1.4.2                 x com.zsmartsystems.zigbee.dongle.ember
244 x Active x  80 x 1.4.2                 x com.zsmartsystems.zigbee.dongle.telegesis
245 x Active x  80 x 1.4.2                 x com.zsmartsystems.zigbee.dongle.xbee
270 x Active x  80 x 3.3.0.202112300337    x openHAB Add-ons :: Bundles :: ZigBee Binding
271 x Active x  80 x 3.3.0.202112300339    x openHAB Add-ons :: Bundles :: ZigBee CC2531 Bridge
272 x Active x  80 x 3.3.0.202112300339    x openHAB Add-ons :: Bundles :: ZigBee Console
273 x Active x  80 x 3.3.0.202112300340    x openHAB Add-ons :: Bundles :: ZigBee Console Ember
274 x Active x  80 x 3.3.0.202112300340    x openHAB Add-ons :: Bundles :: ZigBee Console Telegesis
275 x Active x  80 x 3.3.0.202112300339    x openHAB Add-ons :: Bundles :: ZigBee Ember Bridge
276 x Active x  80 x 3.3.0.202112300337    x openHAB Add-ons :: Bundles :: ZigBee Serial Driver
277 x Active x  80 x 3.3.0.202112300339    x openHAB Add-ons :: Bundles :: ZigBee Telegesis Bridge
278 x Active x  80 x 3.3.0.202112300340    x openHAB Add-ons :: Bundles :: ZigBee XBee Bridge

This is the outcome. What does this tell me ?

openhab> bundle:list | grep -i zigbee
264 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee
265 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.console
266 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.console.ember
267 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.console.telegesis
268 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.dongle.cc2531
269 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.dongle.ember
270 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.dongle.telegesis
271 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.dongle.xbee
274 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Binding
275 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee CC2531 Bridge
276 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Console
277 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Console Ember
278 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Console Telegesis
279 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Ember Bridge
280 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Serial Driver
281 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Telegesis Bridge
282 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee XBee Bridge

This answers @chris ´ question

You have only one copy of the binding running, so there must be another cause for the failure.

I have managed to find the logs on the pi
I have different log files called openhab

audit.log events.log events.log.1.gz events.log.2.gz events.log.3.gz events.log.4.gz openhab.log openhab.log.1.gz openhab.log.2.gz openhab.log.3.gz openhab.log.4.gz openhab.log.5.gz openhab.log.6.gz openhab.log.7.gz Readme.txt

I will show the first below
looks like all logs show same as below

vim openhab.log

2022-01-12 11:07:53.023 [DEBUG] [gesis.internal.TelegesisFrameHandler] - RX Telegesis Data:+N=COO,11,08,DCA4,39AB73C4F34CAD13
2022-01-12 11:07:53.024 [DEBUG] [gesis.internal.TelegesisFrameHandler] - RX Telegesis Data:OK
2022-01-12 11:07:53.026 [DEBUG] [gesis.internal.TelegesisFrameHandler] - RX Telegesis: TelegesisDisplayNetworkInformationCommand [device=COO, channel=11, power=8, panId=56484, epanId=39AB73C4F34CAD13, status=SUCCESS]
2022-01-12 11:07:54.008 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis queue: 1
2022-01-12 11:07:54.009 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis: TelegesisDisplayNetworkInformationCommand [device=null, channel=null, power=null, panId=null, epanId=null]
2022-01-12 11:07:54.027 [DEBUG] [gesis.internal.TelegesisFrameHandler] - TX Telegesis Data:AT+N?^M

I have flashed the installation via Etcher on 2 brand new Sandisk micco SD cards. However when validating the flash it said : failed. Tried it 2 times / new download of openhabian but still same failure on validating the flash. I installed 2 different raspberry with each a new SD.
Might be a corruption of a file perhaps ?
Shall I re-install openhabian via the command line ?

I did a fresh install this time without the Telegesis dongle in the USB port.

After installing the Zigbee binding put the dongle in and adding :slight_smile:

Looks like a firmware issue

022-01-14 22:03:39.515 [INFO ] [openhab.event.InboxRemovedEvent ] - Discovery Result with UID ‘zigbee:coordinator_telegesis:04000BE2’ has been removed.

2022-01-14 22:03:39.588 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:04000BE2’ changed from UNINITIALIZED to INITIALIZING

2022-01-14 22:03:39.685 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:04000BE2’ changed from INITIALIZING to UNKNOWN

2022-01-14 22:03:43.562 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:04000BE2’ changed from UNKNOWN to ONLINE

2022-01-14 22:03:43.569 [INFO ] [penhab.event.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_telegesis:04000BE2 changed to UNKNOWN.

2022-01-14 22:04:10.487 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:087301d757’ changed from UNINITIALIZED to INITIALIZING

2022-01-14 22:04:10.524 [INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing ‘zigbee:coordinator_telegesis:087301d757’ changed from INITIALIZING to UNKNOWN

2022-01-14 22:04:10.527 [INFO ] [penhab.event.FirmwareStatusInfoEvent] - Firmware status of thing zigbee:coordinator_telegesis:087301d757 changed to UNKNOWN.

I’m sorry - no further ideas from my side.

According to ZigBee - Bindings | openHAB the Telegesis stick doesn’t support ZigBee 3.0 - OTOH the docs state that its firmware can be upgraded. IIUC, upgrading the firmware transmutes the Telegesis stick to an Ember EZSP NCP coordinator. But do so at your own risk …

BTW, which fimware version are you using?

openhab> zigbee firmware version
Dongle firmware version is currently 6.7.8.0

I’m not really sure what you mean? What firmware? The INFO level logging is really pretty difficult to conclude anything (at least I personally find it difficult).

As I mentioned above, there seems to be something strange going on and the only thing I can think of is there is some sort of duplication. On one hand you have an error saying the serial port can’t be opened, and on the other hand there is data being received - which is not possible if the port is not open.

These two sets of messages are only 100ms apart, and I can’t explain why it says the port can’t be opened and then sets the device offline, but is receiving data.

Please can you provide a debug log showing what is going on.

There is only one version of the Telegesis firmware supported and I think if it was wrong, there is a an error about firmware versions being incompatible. I don’t see anything here that states the firmware is wrong (and again at INFO level logging, it’s pretty difficult to draw any conclusion at all).

However as stated by @Ap15e I would really not recommend the Telegesis dongle as the firmware is now very old, and doesn’t support newer devices that require the Zigbee 3.0 security.

when typing that command the response is

Error: Multiple ZigBee bridges found; please select one using the setBridgeUid command

FYI I have ordered a conbee 2 zigbee gateway which should easlily be configured via the deCONZ binding. Hope this works. keep you posted

At least two ZigBee coordinators are installed on your system. If there is only one ZigBee stick in your system, there should be exactly one ZigBee coordinator. Remove all coordinators but one (Things → [coordinator] → Delete Thing) and check the port of the remaining one.

1 Like

I needed to force closure of the coordinator.
The dongle stick itself is still online.

openhab> zigbee firmware version

Dongle firmware version is currently R309C

openhab> bundle:list | grep -i zigbee
238 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee
239 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.console
240 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.console.ember
241 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.console.telegesis
242 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.dongle.cc2531
243 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.dongle.ember
244 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.dongle.telegesis
245 x Active x 80 x 1.4.2 x com.zsmartsystems.zigbee.dongle.xbee
248 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Binding
249 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee CC2531 Bridge
250 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Console
251 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Console Ember
252 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Console Telegesis
253 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Ember Bridge
254 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Serial Driver
255 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee Telegesis Bridge
256 x Active x 80 x 3.2.0 x openHAB Add-ons :: Bundles :: ZigBee XBee Bridge

checking the port

openhabian@openhabian:~ $ dmesg |grep tty
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 console=ttyS0,115200 console=tty1 root=PARTUUID=5d8ca972-02 rootfstype=ext4 fsck.repair=yes rootwait
[ 0.001139] printk: console [tty1] enabled
[ 3.069752] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2
[ 5.588550] systemd[1]: Created slice system-getty.slice.
[ 101.123180] systemd[1]: Started Getty on tty1.
[ 695.797514] usb 1-1.1.2: cp210x converter now attached to ttyUSB0

openhab.log

2022-01-14 22:08:21.626 [ERROR] [nding.zigbee.serial.ZigBeeSerialPort] - Serial Error: Port [/dev/ttyUSB0] does not exist.
2022-01-14 22:08:21.630 [ERROR] [ngle.telegesis.ZigBeeDongleTelegesis] - Unable to open Telegesis serial port
2022-01-14 22:08:22.640 [INFO ] [bee.handler.ZigBeeCoordinatorHandler] - ZigBee dongle inactivity timer. Reinitializing ZigBee
2022-01-14 22:08:23.659 [ERROR] [nding.zigbee.serial.ZigBeeSerialPort] - Serial Error: Port [/dev/ttyUSB0] does not exist.
2022-01-14 22:08:23.660 [ERROR] [ngle.telegesis.ZigBeeDongleTelegesis] - Unable to open Telegesis serial port

Hope this info helps