Bitron Video ZigBee USB Funkstick stops working after a while

Tags: #<Tag:0x00007faed9f25a50> #<Tag:0x00007faed9f25910>

Hi, I’m using the Bitron Video ZigBee USB Funkstick and I’m able to make it work and pair several devices that I have but after a while it stops working and no updates are received nor commands sent. It is usually fixed by just unplugging and plugging the dongle, then it works for a while.

In the events.log I see that it works till 4:43, then no more updates:

2019-08-05 04:41:45.394 [vent.ItemStateChangedEvent] - zigbee_device_01382722_286d97000105ca1f_286D97000105CA1F_1_temperature changed from 26.56 °C to 26.57 °C
2019-08-05 04:41:47.067 [vent.ItemStateChangedEvent] - zigbee_device_01382722_286d97000106cc54_286D97000106CC54_1_temperature changed from 26.59 °C to 26.60 °C
2019-08-05 04:42:01.298 [vent.ItemStateChangedEvent] - zigbee_coordinator_ember_01382722_rx_dat changed from 13958 to 13981
2019-08-05 04:42:02.923 [vent.ItemStateChangedEvent] - zigbee_coordinator_ember_01382722_tx_ack changed from 13958 to 13981
2019-08-05 04:42:12.738 [vent.ItemStateChangedEvent] - zigbee_device_01382722_286d970001032626_286D970001032626_1_temperature changed from 22.26 °C to 22.90 °C
2019-08-05 04:42:31.293 [vent.ItemStateChangedEvent] - zigbee_coordinator_ember_01382722_rx_dat changed from 13981 to 14004
2019-08-05 04:42:31.312 [vent.ItemStateChangedEvent] - zigbee_coordinator_ember_01382722_tx_ack changed from 13981 to 14004
2019-08-05 04:43:01.312 [vent.ItemStateChangedEvent] - zigbee_coordinator_ember_01382722_rx_dat changed from 14004 to 14024
2019-08-05 04:43:01.364 [vent.ItemStateChangedEvent] - zigbee_coordinator_ember_01382722_tx_ack changed from 14004 to 14024

In the openhab log I see that from 4:42 it keeps polling without any result:

2019-08-05 04:42:12.717 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001032626: Updating ZigBee channel state zigbee:device:01382722:286d970001032626:286D970001032626_1_temperature to 22.90 °C
2019-08-05 04:42:49.212 [DEBUG] [converter.ZigBeeConverterTemperature] - 286D970001050CFC: ZigBee attribute reports ZclAttribute [cluster=TEMPERATURE_MEASUREMENT, id=0, name=MeasuredValue, dataType=SIGNED_16_BIT_INTEGER, lastValue=2663, lastReportTime=Mon Aug 05 04:42:49 CEST 2019]
2019-08-05 04:42:51.853 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 286D970001050CFC: Channel zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_temperature updated to 26.63 °C
2019-08-05 04:42:51.858 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Updating ZigBee channel state zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_temperature to 26.63 °C
2019-08-05 04:50:27.511 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Polling...
2019-08-05 04:50:27.517 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Polling zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_batterylevel
2019-08-05 04:50:35.522 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Polling zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_batteryalarm
2019-08-05 04:50:43.526 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Polling zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_water
2019-08-05 04:50:51.530 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Polling zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_tamper
2019-08-05 04:51:02.809 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Polling zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_batteryvoltage
2019-08-05 04:51:10.819 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Polling zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_temperature
2019-08-05 04:51:18.828 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001050CFC: Polling zigbee:device:01382722:286d970001050cfc:286D970001050CFC_1_iaslowbattery
2019-08-05 04:55:23.184 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling...
2019-08-05 04:55:23.188 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling zigbee:device:01382722:286d97000105ca1f:286D97000105CA1F_1_intrusion
2019-08-05 04:55:31.193 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling zigbee:device:01382722:286d97000105ca1f:286D97000105CA1F_1_batteryvoltage
2019-08-05 04:55:39.197 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling zigbee:device:01382722:286d97000105ca1f:286D97000105CA1F_1_batteryalarm
2019-08-05 04:55:47.201 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling zigbee:device:01382722:286d97000105ca1f:286D97000105CA1F_1_motion
2019-08-05 04:55:55.206 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling zigbee:device:01382722:286d97000105ca1f:286D97000105CA1F_1_iaslowbattery
2019-08-05 04:56:03.211 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling zigbee:device:01382722:286d97000105ca1f:286D97000105CA1F_1_batterylevel
2019-08-05 04:56:11.216 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling zigbee:device:01382722:286d97000105ca1f:286D97000105CA1F_1_temperature
2019-08-05 04:56:19.221 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D97000105CA1F: Polling zigbee:device:01382722:286d97000105ca1f:286D97000105CA1F_1_tamper
2019-08-05 05:06:00.150 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 286D970001032626: Polling...

As I said if I unplug and plug the USB seems to recover, any ideas?

  • Hardware: Raspberry PI3 Model B (ARM)
  • OS: Raspbian GNU/Linux 9.9 (stretch)
  • Java Runtime Environment: Zulu8.38.0.163-CA-linux_aarch32hf / build 1.8.0_212-b163)
  • openHAB version: 2.5.0~M1-1

I know the zwave binding has a daily network heal turned on by default. If Zigbee has that too try turning it off.
Battery zwave devices seem to hang during the daily heal.

Hey, thanks for your suggestions. AFAIK there’s not “network heal” for zigbee, or at least there’s not setting that I can find.

In the preparation discussion for 2.5M1 I saw a reference to Zigbee devices going offline.
@5iver should be able to prvoide more details.

The first question to ask is what version of the binding are you using?

ZigBee doesn’t have a heal - it works very differently to ZWave and battery devices are also quite different.

I don’t see anything in the logs about devices going offline, and this would not impact on what is being seen here since the OFFLINE issue is only related to the OH state and not the network operation.

@Robotto Please also use code fences when posting logs so that they are easier to read (thanks).

1 Like

Thanks @chris. I guess I got jumpy seeing this post from Scott (near the end).

But the ZigBee binding should not be impacted by any other binding (eg ZWave) - it’s totally independant and works totally differently.

The OFFLINE issue was only introduced in the last merge - it won’t always happen on all systems, and is in any case now fixed in the latest snapshot. Hence it’s important to know what version is used since the latest stable is now 9 months old, the latest milestone is now 7 months old and there have been man changes.

1 Like

@chris version is 2.5.0.M1

In the logs I can only see that what it seems to me a packet counter stops reporting activity and then I cannot use any zigbee device.

Hope this helps.

(and sorry about the first logs post, it was too early here :wink: )

Are you on Windows? When doing testing in Windows, I have to disable power management on the USB device or the controllers disappear after a while.

1 Like

@5iver I’m on Openhabian in a RB Pi 3 Model B. I don’t know where to check that or if it is applicable in my system

power mgmt for USB devices is a Windows thing - it causes in many other HW cases some troubles. However you can find it in linux as well, but I never came across it

if it helps I’ve added all the system info I could gather (and fixed the logs format)

It would be good to get a full debug log so I can see if it’s caused by communications issues with the dongle, or if it’s a network issue.

I would also probably suggest upgrading to a more recent binding (ie the snapshot) as the M1 version is now quite old.

I cannot upload the log file because I’m still a new user, but here you have it: https://drive.google.com/open?id=1gMWPThajLsX75RlXqr3nnZh1epUIa-E7

How do I upgrade just a binding?

This script is the easiest way. You need to uninstall the old binding first though.

The script will uninstall it for you, whether it was installed through a UI, the console, or manually.

1 Like

I tried the script but it doesn’t seem to work:

It has taken more than two minutes to uninstall the Zigbee binding, so exiting

I checked the Zigbee version in Paper UI and it’s the same that I had: binding-zigbee - 2.5.0.M1

Shall I uninstall it manually before trying to upgrade? Should I remove all the things as well?

You could or, if you wait a little bit, 2.5M2 may be out.
They are sorting through final build issues now.

EDIT: Kai has given up on M2 build until tomorrow.

There are lots of things that can cause this. Usually, it’s an issue with the REST API (used when checking if the binding is uninstalled and then installed). Restarting OH sometimes helps. If not, try manually removing and then try the script again. The readme in the repo for the script lists all the manual steps needed, so you can do it that way too.

1 Like

I uninstalled it using PaperUI then I could run the script.
I updated the Zigbee binding but now the BV 2010/10 (ZigBee USB dongle)fails to be online, no matter what port I use… I’m about to give up and start over with a fresh new install.