HA - ZHA problems with BitronHome - Bitronvideo USB stick

Tamas.Toth.ebola · February 5, 2020, 9:21am

Dear Everybody!

I’m a little bit newby in HA usage but had some easy|slow experiments in the last 1 year. My HA runs not in its final environment just on my main computer through Docker just to slowly test everything before I make a decision about the final solution. Usage of Docker and YAML based config files is not a problem for me so after I started to get to know HA currently I have some Tuya based WiFi plugs (with Tasmota FW) also have 2 Qubino - Z-Wave dimmer|switch through one Z-Wave . Me - USB Z-Wave gateway, one telnet based switch for my Pioneer - receiver, and one Emulated Hue component for use of my Logitech - Harmony Hub (+remote) for automations and also to reach my Z-Wave switch through the smart home buttons of the remote. All these work fine together with some scripts, automations, but as I wrote just as experiment yet.

And here was the point where I would have liked to connect in the system my only one Philips Hue lamp (not a bulb, but an integrated ceiling lamp) with it’s Hue - Dimmer. After some research I got that with the current HA, BitronHome -Bitronvideo should be fine: EU USB sticks for the new Zigbee component This is one Silicon Labs - Ember 3587 chipset based USB Zigbee gatway what in theory (if I’m right) not need any special solution for usage just use as ZHA gateway in HA so did it.

The used HA is the currently latest stable 0.104.3. After attached it through Docker as ‘dev > ttyUSB0’ device I could configure as ZHA component and seemed everything work fine but just seemed as when I tried to pair my Zigbee devices HA just spinned and spinned and at the end timed out.

The Docker USB device attachment seems correct (as with my Z-Wave . Me stick also). Also can call ‘add new device’ function in ZHA component but with time-out at the end. I also tried to debug something with ‘bellows’ but this was the point where I had been lost as the log was ‘longer’ what I could understand for first time:)

So the test cases:

I had reset my Hue lamp with the Dimmer and later the Dimmer switch also to allow re-pairing them. Tried to add without success. As the lamp is far enough to be a problem and I can not move… nor the lamp, nor the computer, my next try was the Dimmer switch.
As my Dimmer had been already reset and flashed with amber light I placed it 10cm close to the USB stick but the device adding was not successful again.
As I red that for Philips - Hue Dimmer we need one custom device handler, I tried to add ‘robmarkcole > Hue-sensors-HASS’ for it, but at the end without success. At this point I was a little bit uncertain about the whole thing as I have no Hue Bridge as a real device while the Git - ReadMe mention that I need that. (The whole global goal would be to not use Hue Bridge).

I tried it more times with or without pressing any Dimmer button while the pairing process run but without success. At this point tried to debug something about the stick but I had been lost.

I logged into the Docker container, switch off HA to reach the stick with ‘bellows’, asked for some info, but… this was the end:) I red lot of community posts as in the last year did it also for my other configs always with success this is the first time when sadly not.

Could anybody help me what could be the problem? I will attach my ‘bellows’ logs about my requests in some minutes.

Very lot of thanks if somebody can point me to the right direction.

Tamas.Toth.ebola · February 5, 2020, 9:24am

bellows - info:

bash-5.0# bellows -v DEBUG -d /dev/ttyUSB0 info
debug: Using selector: EpollSelector
debug: Using selector: EpollSelector
debug: Connected. Resetting.
debug: Resetting EZSP
debug: Resetting ASH
debug: Sending: b'1ac038bc7e'
debug: RSTACK Version: 2 Reason: RESET_SOFTWARE frame: b'c1020b0a527e'
debug: Send command version: (4,)
debug: Sending: b'004221a850ed2c7e'
debug: Data frame: b'0142a1a8502815eabd9d7e'
debug: Sending: b'8160597e'
debug: Application frame 0 (version) received: b'04020058'
debug: Send command version: (4,)
debug: Sending: b'7d314321a85035937e'
debug: Data frame: b'1243a1a8502815eaf03d7e'
debug: Sending: b'82503a7e'
debug: Application frame 0 (version) received: b'04020058'
debug: Switched to EZSP protocol version 4
EZSP Stack Type: 2, Stack Version: 22528
debug: Configuring...
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_STACK_PROFILE: 12>, 2)
debug: Sending: b'224021fb5828158cc87e'
debug: Data frame: b'2340a1fb54c6107e'
debug: Sending: b'83401b7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_SECURITY_LEVEL: 13>, 5)
debug: Sending: b'334121fb592f15e8d57e'
debug: Data frame: b'3441a1fb54d32a7e'
debug: Sending: b'8430fc7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_SUPPORTED_NETWORKS: 45>, 1)
debug: Sending: b'444621fb792b15f7b37e'
debug: Data frame: b'4546a1fb5435d07e'
debug: Sending: b'8520dd7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_PACKET_BUFFER_COUNT: 1>, 255)
debug: Sending: b'554721fb55d515fe607e'
debug: Data frame: b'5647a1fb54a9ec7e'
debug: Sending: b'8610be7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command networkInit: ()
debug: Sending: b'664421bf58057e'
debug: Data frame: b'6744a5bf5489477e'
debug: Sending: b'87009f7e'
debug: Data frame: b'7744b1b1c4b2087e'
debug: Application frame 23 (networkInit) received: b'00'
debug: Sending: b'8070787e'
debug: Send command getEui64: ()
debug: Application frame 25 (stackStatusHandler) received: b'90'
debug: Sending: b'7045218e75797e'
debug: Data frame: b'0045a18ed63a2ebf59fb4725a0697e'
debug: Sending: b'8160597e'
debug: Application frame 38 (getEui64) received: b'82103b0d006f0d00'
[00:0d:6f:00:0d:3b:10:82]
debug: Send command getNodeId: ()
debug: Sending: b'014a218f7d5da87e'
debug: Data frame: b'114aa18f542aca087e'
debug: Sending: b'82503a7e'
debug: Application frame 39 (getNodeId) received: b'0000'
[0x0000]
debug: Send command networkState: ()
debug: Sending: b'124b21b00d5f7e'
debug: Data frame: b'224ba1b056832a7e'
debug: Sending: b'83401b7e'
debug: Application frame 24 (networkState) received: b'02'
[<EmberNetworkStatus.JOINED_NETWORK: 2>]
debug: Send command getNetworkParameters: ()
debug: Sending: b'2348218038017e'
debug: Data frame: b'3348a180542bc7faad03efb37908e75b944127abedce677302c1623f7e'
debug: Sending: b'8430fc7e'
debug: Application frame 40 (getNetworkParameters) received: b'0001d248f497a596d35d7512080f0000000000f8ff07'
[<EmberStatus.SUCCESS: 0>, <EmberNodeType.COORDINATOR: 1>, <EmberNetworkParameters extendedPanId=[210, 72, 244, 151, 165, 150, 211, 93] panId=4725 radioTxPower=8 radioChannel=15 joinMethod=EmberJoinMethod.USE_MAC_ASSOCIATION nwkManagerId=0x0000 nwkUpdateId=0 channels=134215680>]
debug: Send command getCurrentSecurityState: ()
debug: Sending: b'344921c11d5e7e'
debug: Data frame: b'4449a1c1545e153049af4725c55892d69d7e'
debug: Sending: b'8520dd7e'
debug: Application frame 105 (getCurrentSecurityState) received: b'00740082103b0d006f0d00'
[<EmberStatus.SUCCESS: 0>, <EmberCurrentSecurityState bitmask=116 trustCenterLongAddress=00:0d:6f:00:0d:3b:10:82>]
debug: Closed serial connection
bash-5.0#

Tamas.Toth.ebola · February 5, 2020, 9:25am

bellows - scan:

bash-5.0# bellows -v DEBUG -d /dev/ttyUSB0 scan
debug: Using selector: EpollSelector
debug: Using selector: EpollSelector
debug: Connected. Resetting.
debug: Resetting EZSP
debug: Resetting ASH
debug: Sending: b'1ac038bc7e'
debug: RSTACK Version: 2 Reason: RESET_SOFTWARE frame: b'c1020b0a527e'
debug: Send command version: (4,)
debug: Sending: b'004221a850ed2c7e'
debug: Data frame: b'0142a1a8502815eabd9d7e'
debug: Sending: b'8160597e'
debug: Application frame 0 (version) received: b'04020058'
debug: Send command version: (4,)
debug: Sending: b'7d314321a85035937e'
debug: Data frame: b'1243a1a8502815eaf03d7e'
debug: Sending: b'82503a7e'
debug: Application frame 0 (version) received: b'04020058'
debug: Switched to EZSP protocol version 4
EZSP Stack Type: 2, Stack Version: 22528
debug: Configuring...
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_STACK_PROFILE: 12>, 2)
debug: Sending: b'224021fb5828158cc87e'
debug: Data frame: b'2340a1fb54c6107e'
debug: Sending: b'83401b7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_SECURITY_LEVEL: 13>, 5)
debug: Sending: b'334121fb592f15e8d57e'
debug: Data frame: b'3441a1fb54d32a7e'
debug: Sending: b'8430fc7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_SUPPORTED_NETWORKS: 45>, 1)
debug: Sending: b'444621fb792b15f7b37e'
debug: Data frame: b'4546a1fb5435d07e'
debug: Sending: b'8520dd7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_PACKET_BUFFER_COUNT: 1>, 255)
debug: Sending: b'554721fb55d515fe607e'
debug: Data frame: b'5647a1fb54a9ec7e'
debug: Sending: b'8610be7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
Scanning channels 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
debug: Send command startScan: (<EzspNetworkScanType.ACTIVE_SCAN: 1>, 134215680, 2)
debug: Sending: b'664421b2552aed4d5e96e55b7e'
debug: Data frame: b'6744a1b25423db7e'
debug: Sending: b'87009f7e'
debug: Application frame 26 (startScan) received: b'00'
debug: Data frame: b'7744b5b45f1cb9347e'
debug: Sending: b'8070787e'
debug: Data frame: b'0744b5b4581c653f7e'
debug: Application frame 28 (scanCompleteHandler) received: b'0b36'
debug: Sending: b'8160597e'
Traceback (most recent call last):
  File "/usr/local/bin/bellows", line 8, in <module>
debug: Data frame: b'1744b5b4591c4c8a7e'
debug: Sending: b'82503a7e'
    sys.exit(main())
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 764, in __call__
debug: Data frame: b'2744b5b45a1c36557e'
debug: Sending: b'83401b7e'
debug: Data frame: b'3744b5b45b1c1fe07e'
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 717, in main
debug: Sending: b'8430fc7e'
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/bellows/cli/util.py", line 38, in inner
    loop.run_until_complete(f(*args, **kwargs))
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 583, in run_until_complete
    return future.result()
  File "/usr/local/lib/python3.7/site-packages/bellows/cli/network.py", line 154, in scan
    v = await s.startScan(scan_type, channel_mask, duration_symbol_exp)
  File "/usr/local/lib/python3.7/site-packages/bellows/ezsp.py", line 117, in _list_command
    raise Exception(v)
Exception: [11, <EmberStatus.MAC_COMMAND_TRANSMIT_FAILURE: 54>]
debug: Data frame: b'4744b5b4441c49317e'
debug: Sending: b'8520dd7e'
debug: Data frame: b'5744b5b4451c60847e'
debug: Sending: b'8610be7e'
debug: Data frame: b'6744b5b4461c1a5b7e'
debug: Sending: b'87009f7e'
debug: Data frame: b'7744b5b4471c33ee7e'
debug: Sending: b'8070787e'
debug: Data frame: b'0744b5b4401cefe57e'
debug: Sending: b'8160597e'
debug: Data frame: b'1744b5b4411cc6507e'
debug: Sending: b'82503a7e'
debug: Data frame: b'2744b5b4421cbc8f7e'
debug: Sending: b'83401b7e'
debug: Data frame: b'3744b5b4431c953a7e'
debug: Sending: b'8430fc7e'
debug: Data frame: b'4744b5b44c1cc0987e'
debug: Sending: b'8520dd7e'
debug: Data frame: b'5744b5b44d1ce92d7e'
debug: Sending: b'8610be7e'
debug: Data frame: b'6744b5b44e1c93f27e'
debug: Sending: b'87009f7e'
debug: Data frame: b'7744b1b4ab2afa557e'
debug: Sending: b'8070787e'
^C

Tamas.Toth.ebola · February 5, 2020, 9:28am

bellows - permit:

bash-5.0# bellows -v DEBUG -d /dev/ttyUSB0 permit -D /config/zigbee.db
debug: Using selector: EpollSelector
debug: Using selector: EpollSelector
debug: Loading application state from /config/zigbee.db
debug: Checking quirks for None None (00:0d:6f:00:0d:3b:10:82)
debug: Considering <class 'bellows.zigbee.application.EZSPCoordinator'>
debug: Found custom device replacement for 00:0d:6f:00:0d:3b:10:82: <class 'bellows.zigbee.application.EZSPCoordinator'>
debug: Resetting EZSP
debug: Initialize OTA providers
debug: Resetting ASH
debug: Sending: b'1ac038bc7e'
debug: OTA image directory '/config/zigpy_ota/' does not exist
debug: RSTACK Version: 2 Reason: RESET_SOFTWARE frame: b'c1020b0a527e'
debug: Send command version: (4,)
debug: Sending: b'004221a850ed2c7e'
debug: Data frame: b'0142a1a8502815eabd9d7e'
debug: Sending: b'8160597e'
debug: Application frame 0 (version) received: b'04020058'
debug: Send command version: (4,)
debug: Sending: b'7d314321a85035937e'
debug: Data frame: b'1243a1a8502815eaf03d7e'
debug: Sending: b'82503a7e'
debug: Application frame 0 (version) received: b'04020058'
debug: Switched to EZSP protocol version 4
EZSP Stack Type: 2, Stack Version: 22528
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_STACK_PROFILE: 12>, 2)
debug: Sending: b'224021fb5828158cc87e'
debug: Data frame: b'2340a1fb54c6107e'
debug: Sending: b'83401b7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_SECURITY_LEVEL: 13>, 5)
debug: Sending: b'334121fb592f15e8d57e'
debug: Data frame: b'3441a1fb54d32a7e'
debug: Sending: b'8430fc7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_SUPPORTED_NETWORKS: 45>, 1)
debug: Sending: b'444621fb792b15f7b37e'
debug: Data frame: b'4546a1fb5435d07e'
debug: Sending: b'8520dd7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_APPLICATION_ZDO_FLAGS: 42>, 3)
debug: Sending: b'554721fb7d5e2915defb7e'
debug: Data frame: b'5647a1fb54a9ec7e'
debug: Sending: b'8610be7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_PAN_ID_CONFLICT_REPORT_THRESHOLD: 34>, 2)
debug: Sending: b'664421fb7628150b847e'
debug: Data frame: b'6744a1fb54948f7e'
debug: Sending: b'87009f7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_TRUST_CENTER_ADDRESS_CACHE_SIZE: 25>, 2)
debug: Sending: b'774521fb4d2815f46a7e'
debug: Data frame: b'7045a1fb5481b57e'
debug: Sending: b'8070787e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_ADDRESS_TABLE_SIZE: 5>, 16)
debug: Sending: b'004a21fb513a15ff5f7e'
debug: Data frame: b'014aa1fb54e28c7e'
debug: Sending: b'8160597e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_SOURCE_ROUTE_TABLE_SIZE: 26>, 8)
debug: Sending: b'7d314b21fb4e2215d06d7e'
debug: Data frame: b'124ba1fb547eb07e'
debug: Sending: b'82503a7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_MAX_END_DEVICE_CHILDREN: 17>, 32)
debug: Sending: b'224821fb450a15e03c7e'
debug: Data frame: b'2348a1fb5443d37e'
debug: Sending: b'83401b7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_INDIRECT_TRANSMISSION_TIMEOUT: 18>, 7680)
debug: Sending: b'334921fb462a0b86cf7e'
debug: Data frame: b'3449a1fb5456e97e'
debug: Sending: b'8430fc7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_KEY_TABLE_SIZE: 30>, 1)
debug: Sending: b'444e21fb4a2b1566047e'
debug: Data frame: b'454ea1fb54b0137e'
debug: Sending: b'8520dd7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_TRANSIENT_KEY_TIMEOUT_S: 54>, 180)
debug: Sending: b'554f21fb629e1562217e'
debug: Data frame: b'564fa1fb542c2f7e'
debug: Sending: b'8610be7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_END_DEVICE_POLL_TIMEOUT: 19>, 60)
debug: Sending: b'664c21fb471615d2c97e'
debug: Data frame: b'674ca1fb54114c7e'
debug: Sending: b'87009f7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_END_DEVICE_POLL_TIMEOUT_SHIFT: 27>, 8)
debug: Sending: b'774d21fb4f221578837e'
debug: Data frame: b'704da1fb5404767e'
debug: Sending: b'8070787e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_MULTICAST_TABLE_SIZE: 6>, 16)
debug: Sending: b'005221fb523a15b1c97e'
debug: Data frame: b'0152a1fb547ce87e'
debug: Sending: b'8160597e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command setConfigurationValue: (<EzspConfigId.CONFIG_PACKET_BUFFER_COUNT: 1>, 255)
debug: Sending: b'7d315321fb55d515fe6f7e'
debug: Data frame: b'1253a1fb54e0d47e'
debug: Sending: b'82503a7e'
debug: Application frame 83 (setConfigurationValue) received: b'00'
debug: Send command getConfigurationValue: (<EzspConfigId.CONFIG_APS_UNICAST_MESSAGE_COUNT: 3>,)
debug: Sending: b'225021fa574fee7e'
debug: Data frame: b'2350a1fa54201586817e'
debug: Sending: b'83401b7e'
debug: Application frame 82 (getConfigurationValue) received: b'000a00'
debug: APS_UNICAST_MESSAGE_COUNT is set to 10
debug: Send command addEndpoint: (1, 260, 48879, 0, 0, 1, [], [1280])
debug: Sending: b'335121aa552e145de7944a24aa50e0797e'
debug: Data frame: b'3451a1aa54f5037e'
debug: Sending: b'8430fc7e'
debug: Application frame 2 (addEndpoint) received: b'00'
debug: Ezsp adding endpoint: [<EzspStatus.SUCCESS: 0>]
debug: Send command setConcentrator: (False, <EmberConcentratorType.HIGH_RAM_CONCENTRATOR: 65529>, 600, 1800, 2, 5, 0)
debug: Sending: b'445621b854d3eaea5b9c4d27af5597827e'
debug: Data frame: b'4556a1b85476e87e'
debug: Sending: b'8520dd7e'
debug: Application frame 16 (setConcentrator) received: b'00'
debug: Set concentrator type: [<EmberStatus.SUCCESS: 0>]
debug: Send command networkInit: ()
debug: Sending: b'555721bff5037e'
debug: Data frame: b'5657a5bf54af837e'
debug: Sending: b'8610be7e'
debug: Data frame: b'6657b1b1c49c787e'
debug: Application frame 23 (networkInit) received: b'00'
debug: Sending: b'87009f7e'
debug: Send command getNetworkParameters: ()
debug: Sending: b'67542180aa6e7e'
debug: Application frame 25 (stackStatusHandler) received: b'90'
debug: Data frame: b'7754a180542bc7faad03efb37908e75b944127abedce677302c16e677e'
debug: Sending: b'8070787e'
debug: Application frame 40 (getNetworkParameters) received: b'0001d248f497a596d35d7512080f0000000000f8ff07'
debug: Send command setPolicy: (<EzspPolicyId.TC_KEY_REQUEST_POLICY: 5>, <EzspDecisionId.DENY_TC_KEY_REQUESTS: 80>)
debug: Sending: b'705521fd517a7f437e'
debug: Data frame: b'0055a1fd542d327e'
debug: Sending: b'8160597e'
debug: Application frame 85 (setPolicy) received: b'00'
debug: Send command setPolicy: (<EzspPolicyId.APP_KEY_REQUEST_POLICY: 6>, <EzspDecisionId.ALLOW_APP_KEY_REQUESTS: 97>)
debug: Sending: b'015a21fd524b69a77e'
debug: Data frame: b'115aa1fd5457d77e'
debug: Sending: b'82503a7e'
debug: Application frame 85 (setPolicy) received: b'00'
debug: Send command setPolicy: (<EzspPolicyId.TRUST_CENTER_POLICY: 0>, <EzspDecisionId.ALLOW_PRECONFIGURED_KEY_JOINS: 1>)
debug: Sending: b'125b21fd542bd1927e'
debug: Data frame: b'225ba1fd54c35f7e'
debug: Sending: b'83401b7e'
debug: Application frame 85 (setPolicy) received: b'00'
debug: Send command getNodeId: ()
debug: Sending: b'2358218f8a8d7e'
debug: Data frame: b'3358a18f542a34997e'
debug: Sending: b'8430fc7e'
debug: Application frame 39 (getNodeId) received: b'0000'
debug: Send command getEui64: ()
debug: Sending: b'3459218ee7167e'
debug: Data frame: b'4459a18ed63a2ebf59fb4725d6097e'
debug: Sending: b'8520dd7e'
debug: Application frame 38 (getEui64) received: b'82103b0d006f0d00'
Device 0x0000 (00:0d:6f:00:0d:3b:10:82) joined the network
debug: Skip initialization for existing device 00:0d:6f:00:0d:3b:10:82
debug: EZSP nwk=0x0000, IEEE=00:0d:6f:00:0d:3b:10:82
debug: Send command getMulticastTableEntry: (0,)
debug: Starting EZSP watchdog
debug: Sending: b'455e21cb54957b7e'
debug: Data frame: b'555ea1cb542a15b294e67e'
debug: Sending: b'8610be7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[0] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (1,)
debug: Sending: b'565f21cb5519667e'
debug: Data frame: b'665fa1cb542a15b2a22e7e'
debug: Sending: b'87009f7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[1] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (2,)
debug: Sending: b'675c21cb5614667e'
debug: Data frame: b'775ca1cb542a15b200cb7e'
debug: Sending: b'8070787e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[2] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (3,)
debug: Sending: b'705d21cb577d317d5d7e'
debug: Data frame: b'005da1cb542a15b2cfbe7e'
debug: Sending: b'8160597e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[3] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (4,)
debug: Sending: b'016221cb502e4a7e'
debug: Data frame: b'1162a1cb542a15b266bd7e'
debug: Sending: b'82503a7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[4] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (5,)
debug: Sending: b'126321cb51a2577e'
debug: Data frame: b'2263a1cb542a15b250757e'
debug: Sending: b'83401b7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[5] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (6,)
debug: Sending: b'236021cb52af577e'
debug: Data frame: b'3360a1cb542a15b2f2907e'
debug: Sending: b'8430fc7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[6] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (7,)
debug: Sending: b'346121cb53aa4c7e'
debug: Data frame: b'4461a1cb542a15b23de57e'
debug: Sending: b'8520dd7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[7] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (8,)
debug: Sending: b'456621cb5cbd597e'
debug: Data frame: b'5566a1cb542a15b25ec67e'
debug: Sending: b'8610be7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[8] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (9,)
debug: Sending: b'566721cb5d31447e'
debug: Data frame: b'6667a1cb542a15b2680e7e'
debug: Sending: b'87009f7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[9] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (10,)
debug: Sending: b'676421cb5e3c447e'
debug: Data frame: b'7764a1cb542a15b2caeb7e'
debug: Sending: b'8070787e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[10] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (11,)
debug: Sending: b'706521cb5f395f7e'
debug: Data frame: b'0065a1cb542a15b2059e7e'
debug: Sending: b'8160597e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[11] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (12,)
debug: Sending: b'016a21cb582a817e'
debug: Data frame: b'116aa1cb542a15b2f5107e'
debug: Sending: b'82503a7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[12] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (13,)
debug: Sending: b'126b21cb59a69c7e'
debug: Data frame: b'226ba1cb542a15b2c3d87e'
debug: Sending: b'83401b7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[13] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (14,)
debug: Sending: b'236821cb5aab9c7e'
debug: Data frame: b'3368a1cb542a15b2613d7e'
debug: Sending: b'8430fc7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[14] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command getMulticastTableEntry: (15,)
debug: Sending: b'346921cb5bae877e'
debug: Data frame: b'4469a1cb542a15b2ae487e'
debug: Sending: b'8520dd7e'
debug: Application frame 99 (getMulticastTableEntry) received: b'00000000'
debug: MulticastTableEntry[15] = <EmberMulticastTableEntry multicastId=0x0000 endpoint=0 networkIndex=0>
debug: Send command sendBroadcast: (<BroadcastAddress.ALL_ROUTERS_AND_COORDINATOR: 65532>, <EmberApsFrame profileId=0 clusterId=54 sourceEndpoint=0 destinationEndpoint=0 options=0 groupId=0 sequence=1>, 0, 2, b'\x01\x1e\x00')
debug: Sending: b'456e219ea8d515b26f944a25aa5592499d4e25a8ecd067f5047e'
debug: Data frame: b'556ea19e543a41697e'
debug: Sending: b'8610be7e'
debug: Data frame: b'656eb1ed512a158459944a25aa559259634e27ab1231648ae3c61d547e'
debug: Sending: b'87009f7e'
debug: Application frame 54 (sendBroadcast) received: b'0010'
debug: Application frame 69 (incomingMessageHandler) received: b'050000360000000000000010ff000000ffff03011e00'
debug: Received incomingMessageHandler frame with [<EmberIncomingMessageType.INCOMING_BROADCAST_LOOPBACK: 5>, <EmberApsFrame profileId=0 clusterId=54 sourceEndpoint=0 destinationEndpoint=0 options=0 groupId=0 sequence=16>, 255, 0, 0x0000, 255, 255, b'\x01\x1e\x00']
debug: [0x0000:zdo] ZDO request 0x0036: [30, <Bool.false: 0>]
debug: Data frame: b'756eb19752d6eab259a24a25aa5592499c5e25cded50b77e'
debug: Sending: b'8070787e'
debug: Application frame 63 (messageSentHandler) received: b'06fcff0000360000000000000010026600'
debug: Received messageSentHandler frame with [<EmberOutgoingMessageType.OUTGOING_BROADCAST: 6>, 65532, <EmberApsFrame profileId=0 clusterId=54 sourceEndpoint=0 destinationEndpoint=0 options=0 groupId=0 sequence=16>, 2, <EmberStatus.DELIVERY_FAILED: 102>, b'']
debug: Send command permitJoining: (30,)
debug: Sending: b'506f218a4a25297e'
debug: Data frame: b'066fa18a54353b7e'
debug: Sending: b'8160597e'
debug: Application frame 34 (permitJoining) received: b'00'
Joins are permitted for the next 30s...
debug: Send command nop: ()
debug: Sending: b'616c21ad143c7e'
debug: Data frame: b'176ca1ad6a487e'
debug: Sending: b'82503a7e'
debug: Application frame 5 (nop) received: b''
debug: Send command nop: ()
debug: Sending: b'726d21ada3777e'
debug: Data frame: b'206da1ad20bc7e'
debug: Sending: b'83401b7e'
debug: Application frame 5 (nop) received: b''
debug: Send command nop: ()
debug: Sending: b'037221adf8e47e'
debug: Data frame: b'3172a1ad22fd7e'
debug: Sending: b'8430fc7e'
debug: Application frame 5 (nop) received: b''
Done
debug: Data frame: b'4172b1ee54aaea63789582c855aa6db662b12be15ac86603eac66889f77e2ff92bdcde6fe0933ebfd7c11e377e'
debug: Sending: b'8520dd7e'
debug: Data frame: b'5172b1ee54aaea787895822255aa6db662b12be15ac86603eac66889f77e2ff92bdcde6f0f2ef9ffd7c1f7bf7e'
debug: Sending: b'8610be7e'
debug: Data frame: b'6172b1ee54aaea7b7895822a55aa6db662b12be15ac86603eac66889f77e2ff92bdcde6f4b49ce69d7c12f2d7e'
debug: Sending: b'87009f7e'
debug: Data frame: b'7172b1ee54aaea7b7895823255aa6db662b12be15ac86603eac66889f77e2ff92bdcde6f0d07a461d7c1702c7e'
debug: Sending: b'8070787e'
debug: Data frame: b'0172b1ee54aafa727895821855aa6db662b12be15ac86603eac66889f77e2ff92bdcde6ff70afd2cd7c1c82c7e'
debug: Sending: b'8160597e'
debug: Data frame: b'1172b1ee54aaaf0c7895826155aa6db662b12be15ac86603eac66889f77e2ff92bdcde6f50b63df6d7c184ba7e'
debug: Sending: b'82503a7e'
debug: Data frame: b'2172b1ee54aaea777895827155aa6db662b12be15ac86603eac66889f77e2ff92bdcde6fb1a218dfd7c175667e'
debug: Sending: b'83401b7e'
debug: Data frame: b'3172b1ee54aaea7a7895829055aa6db662b12be15ac86603eac66889f77e2ff92bdcde6fc4b0fd1bd7c144f67e'
debug: Sending: b'8430fc7e'
^C

Here I see one OTA image directory '/config/zigpy_ota/' does not exist warning, but don’t think this would be the problem.

Thanks again in advance for everybody!

Tamas.Toth.ebola · February 9, 2020, 5:36pm

Just as history.

After updating to 0.105.1 I deleted my ZHA integration with all related files (zigbee.db, zha(storage, etc.). After restarting HA and tried to add new ZHA integration I got unsuccessful error message but without any log entry.

Secondly I tried to add ZHA manually from configuration.yaml as:

zha:
  usb_path: /dev/ttyUSB0
  database_path: /config/zigbee.db

I got also unsuccessful ZHA integration also but happily with error log:

2020-02-09 18:30:06 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry /dev/ttyUSB0 for zha
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 215, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 103, in async_setup_entry
    await zha_gateway.async_initialize()
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 136, in async_initialize
    await self.application_controller.startup(auto_form=True)
  File "/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py", line 138, in startup
    await self.initialize()
  File "/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py", line 91, in initialize
    await self._cfg(c.CONFIG_KEY_TABLE_SIZE, 8)
  File "/usr/local/lib/python3.7/site-packages/bellows/zigbee/application.py", line 231, in _cfg
    assert v[0] == t.EmberStatus.SUCCESS  # TODO: Better check
AssertionError

Could anybody help me on it?

Tamas.Toth.ebola · February 12, 2020, 10:04am

There are interesting results after upgraded HA to 0.105.3. After the upgrade the configuration.yaml configured ZHA integration appeared again in the GUI and there were no more error in the logs. As I did not know that the result was true or false I disabled the integration in the yaml and tried to add from the GUI as brand new solution. In this case I got success again.

It seemed that the state is again in the desired as was with 0.104.x earlier but with more gladly details. Before there were no any direct details about the gateway device but now that is in the ZHA integration settings without any problem:

Silicon Labs EZSP
EZSP by Silicon Labs
IEEE: 00:0d:6f:00:0d:3b:10:82
Nwk: 0x0000
Device Type: Coordinator
LQI: Unknown
RSSI: Unknown
Last Seen: 2020-02-11T19:58:25
Power Source: Mains
Quirk: bellows.zigbee.application.EZSPCoordinator

The LQI value later changed to 255 but I simply could not followed when.

After tried to add a new Zigbee device from the GUI, I got this:

[0x0000:zdo] ZDO request 0x0036: [60, <Bool.false: 0>]
[0x0000](EZSP): started initialization
[0x0000:ZDO](EZSP): entry loaded from storage: ZhaDeviceEntry(name='Silicon Labs EZSP', ieee='00:0d:6f:00:0d:3b:10:82', last_seen=None)
[0x0000:ZDO](EZSP): channel: 'async_initialize' stage succeeded
[0x0000](EZSP): power source: Mains
[0x0000](EZSP): completed initialization

The spinner spinning and spinning and timeout.

At this point I tried to disable the custom Hue Dimmer sensor, after it I got just this (without the other lines from the earlier) when I tried to add new Zigbee device from the GUI:

[0x0000:zdo] ZDO request 0x0036: [60, <Bool.false: 0>]

For me seems the result is the most complete yet but as I did not do anything at this point I simply could not pair my Hue lamp, nor the Hue - Dimmer.

Could anybody help me on it?

koying · February 13, 2020, 7:38am

~~I’ve no experience adding Hue devices directly to zha, but did you try to reset the lamp (https://www.home-assistant.io/integrations/zha/#philips-hue-dimmer-switch) ?~~

Sorry, saw you tried that. If I read you correctly, you could not bring the lamp and the zigbee stick close together, though. That might be a problem.

Note that dimmer and lamp are separate devices for HA.
You should be able to control the lamp with ZHA, while you’ll need “robmarkcole > Hue-sensors-HASS” to add the dimmer as a sensor.

javicalle · February 13, 2020, 9:26pm

If I’m not wrong the ‘robmarkcole > Hue-sensors-HASS’ only works with an Hue Brigde. It’s not needed to work with ZHA.
I have paired an Aqara button, an Aqara sensor and an Osram Plug, so no experience with Hue pairing proccess.

From what I have read, you have to put the remote in pairing mode (orange led blinking) and then search for devices from HA. This is the same process that I followed with my devices. Some of them detected at first and with others I had to make several attempts.

If the lamp is far away, it can be a problem. Something that can help is having a repeater device along the way. Zigbee devices powered by current are usually repeaters (except light bulbs). A zigbbe plug could do the job. I have used the Ikea repeater

Tamas.Toth.ebola · February 29, 2020, 1:13pm

@koying @javicalle thanks for your suggestions! I move my whole config to our notebook and through it I could reached my Hue lamp from lot more closer (10cm ). From that point I could reach the lamp with successful connection. After it controlling the lamp from HASS was perfect without any problem.

What is totally interesting for me that after connect the lamp to the Bitronvideo gateway I could connect the Hue Dimmer also. I could not use it as I’m not yet know how could I use that sensor (if there is possibility for it in theory) but I successfully connected and saw that from HASS also. The configuration of that will be the next step when I get a repeater or move my whole config into the planned final RPi 4 (with SSD) what final position should be lot more closer to the lamp as the current PC.

Thanks again for your answers! Seems that the Bitronvideo gateway recognized the 2 Hue devices just need to find in the future out how could I use the Dimmer in HASS

finity · June 9, 2020, 2:10am

I just got an Aqara button (WXKG11LM) and (I think…) it’s paired.

It shows up as “lumi.remote.b1acn01” in the zigbee devices list.

However, when I push the button nothing happens, the state remains 'unknown" and there are no zha_event’s" fired.

Any advice on how to get this button working?

javicalle · June 10, 2020, 7:17am

I remember that pairing the button was a more complicated and I had to try it several times until it was paired.
The advice would be to make the pairing process very close to the zigbee coordinator, press the button every second (or two) to keep it active throughout the pairing process and try several times until it is well paired.

In my case, the device zigbee information is:

{
  "node_descriptor": "<NodeDescriptor byte1=2 byte2=64 mac_capability_flags=128 manufacturer_code=4151 maximum_buffer_size=127 maximum_incoming_transfer_size=100 server_mask=0 maximum_outgoing_transfer_size=100 descriptor_capability_field=0>",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0006",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0012"
      ],
      "out_clusters": [
        "0x0000"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.remote.b1acn01",
  "class": "zhaquirks.xiaomi.aqara.sensor_switch_aq3.SwitchAQ3B"
}

nerdosity · June 12, 2020, 1:36pm

For me it worked “almost” perfectly.
Bitronvideo AV2010/10, the 20 EUR one bougth from Amazon.
“almost” since it will not connect to my two Xiaomi temperature sensors. It worked with everything else,

OSRAM lightify lights
IKEA 2 buttons remote, Symfonisk volume controller, E14 cold/warm light, E27 light, power outlet, extender, 30w led dimmer (transformer)
Xiaomi cube, switch, door sensors, motion sensors, water leak sensor, vibration sensor
Heiman smoke sensors

Routing and OTA worked for me.

Hedda · September 15, 2020, 12:46pm

Have anyone here upgraded firmware on Bitron Video AV2010/10 or SMaBiT AV2010/10 USB-sticks?

As I understand it could possibly support newer EmberZNet NCP application firmware (ver. 6.5 or 6.6?).

Preferably want later version of EmberZNet 6.6 / 6.6.x / 6.6.x.x if possible for EZSP v5/v6/v7 support.

I don’t have one myself but think it would be a good idea to collect that information in one location, ex:

github.com/zigpy/bellows

[DOCUMENTATION] Links to how-to upgrade firmware on Bitron Video AV2010/10 and SMaBiT AV2010/10 USB-sticks?

opened 07:00AM - 15 Sep 20 UTC

closed 12:59PM - 10 Jan 22 UTC

Hedda

Does anyone have links to info on how-to upgrade firmware on SMaBiT AV2010/10 an…d Bitron Video (BV) AV2010/10 USB stick? Would be good to add links to step-by-step in bellows README.md file https://github.com/zigpy/bellows/blob/master/README.md Plus links to publicly available firmware images with newer EmberZNet NCP application FW image files for them? From the info that I could find these are based on Ember EM3587 (EM358x series) chip + has a CP2104 USB-to-Serial/UART chip? This AV2010/10 USB-stick is effectively an RS232 to USB bridge connected to a SiLabs ETRX3 Series ZigBee module. https://silabs-prod.adobecqms.net/support/resources.p-wireless_zigbee-and-thread_em358x-wireless-zigbee-socs https://www.silabs.com/documents/public/reference-manuals/TG-PM-0509-ETRX358x.pdf https://www.texim-europe.com/getfile.aspx?id=101076 That probably means users preferably want later version of EmberZNet 6.6 / 6.6.x / 6.6.x.x if possible for EZSP v5/v6/v7 support? https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/ _**"The ZigBee USB radio device can be used to use ZigBee devices that run QIVICON Home Base 1 and Telekom Speedport Smart. The product is not compatible with QIVICON Home Base 2. You can still use the wireless Stick with another OpenHAB-based system."**_ ![](https://img.smabit.eu/Smart%20Home/AV2010-10/transparent/AV2010-10%20(1).png) @martin3000 added the Bitron Video Zigbee Stick to Home Assistant ZHA list https://www.home-assistant.io/integrations/zha/ - **_Bitron Video/Smabit BV AV2010/10 USB-Stick with Silicon Labs Ember 3587_** @walthowd has for example posted great instructions on upgrading HUSBZB-1 https://github.com/walthowd/husbzb-firmware PS: Submitted a PR to update bellows README.md with a general recommendation to upgrade EmberZNet firmware in https://github.com/zigpy/bellows/pull/346 PPS: I am only asking this on behalf of the community as I do not actually own any Bitron Video/Smabit USB dongles myself.

also see

and