Another component for ZiGate

jsl1 · March 8, 2019, 1:12pm

Hi @biau
Thanks for your feedback
Can you use “Graph Settings Builder” in the top right menu, scroll to bottom, and change the property “physics/barnesHut/springLength” to a minimal acceptable value and tell me ?

max5962 · March 8, 2019, 2:11pm

Is anyone use zigate with Xiaomi gateways ?
I want to use gateways as wifi speaker / light

Adorem · March 8, 2019, 3:33pm

Hi,

I start to play with the ZiGate and this component. For the moment I success to pair one bulb to the ZiGate and switch it on/off from HA.
Now I will pair a remote.
With this is it possible that the remote directly (only with the ZiGate and not going through HA) change the status on the bulb (on/off) or it shall go through HA (it receive the pressed button and then an automation change the state of the bulb)?

Thanks.

jsl1 · March 9, 2019, 11:33am

Hi @Adorem ,
It’s possible. You need a remote with group and zigbee commissioning support. For example : Phillips hue dimmer Switch, Ikea Tradfri remote, and many others.

mvdkleijn · March 9, 2019, 3:44pm

I’ve switched to this component, running the latest from Github and running the latest release of the Zigate firmware.

It says that the Zigate is connected and found one device, which is “unknown” and needs to be discovered. Running the zigate.discover_device service with the given entity_id isn’t doing anything as far as I can tell and I have no clue what device this is supposed to be.

The UI gives me the following info on the unknown device:

battery voltage -
battery level 100
lqi percent 94
type -
manufacturer -
receiver on when idle false
missing false
generic type discovery
groups {}
addr 3145
id 0
ieee 00158d0002028106
lqi 239
power type 0

The only thing I seem to be able to find in the logs is:

No type (modelIdentifier) for device 3145

and

Command 0x0045 failed Failed (ZigBee event codes) 128 : b''
Command 0x0042 failed Failed (ZigBee event codes) 128 : b''

Anyone have any clue what’s going on?!?

Edit 1 - I’ve tried pairing several of my previously fine working Xiaomi devices, including a temperature sensor as well as a button. Pairing does not occur and in the logs it keeps saying “command 0x0049 failed.”

I’ve tried running raw_command service with command 0015 which correctly ran and output a list of existing connections in the log. It listed the one unknown device.

Still no clue what’s going on… I’ve even tried to move the Zigate USB stick to a different USB slot on my Pi…

Edit 2: I believe I’ve fixed the problem… seems like I forgot to clear the eeprom after updating the firmware. I managed to fix it by sending raw_command 0x0012 followed by 0x0011 for good measure. Seems like my Xiaomi multi click device is now pairing and updating properly.

biau · March 14, 2019, 8:45am

At some point decreasing the value does not affect rendering anymore for me so with 0 I have this:

Adorem · March 14, 2019, 11:20pm

Hi @jsl1,
Thank you! I have add my Phillips hue dimmer Switch to the zigate and success to create and use groups.

Now I do not understand why the status of my bulb is not reported correctly in HA. Like it is explained previously in this thread I have to send zigate.refresh_device to get the status updated. Is this normal?

doudz · March 15, 2019, 5:10am

Try to call discover_device

Adorem · March 15, 2019, 1:20pm

Thank you doudz,

discover_device change nothing.

Here are the steps I tried and the corresponding logs.

Fresh boot of the system

Boot log

2019-03-15 13:47:06 WARNING (MainThread) [homeassistant.loader] You are using a custom component for custom_updater which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-03-15 13:47:06 WARNING (MainThread) [homeassistant.loader] You are using a custom component for zigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-03-15 13:47:06 WARNING (MainThread) [homeassistant.components.mqtt] Data in your config entry is going to override your configuration.yaml: {'broker': 'core-mosquitto', 'discovery': True, 'password': 'xxx', 'port': 1883, 'protocol': '3.1.1', 'username': 'xxx'}
2019-03-15 13:47:23 DEBUG (SyncWorker_10) [zigate] Try loading persistent file
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Load success
2019-03-15 13:47:24 INFO (SyncWorker_10) [zigate] Searching ZiGate port
2019-03-15 13:47:24 INFO (SyncWorker_10) [zigate] ZiGate found at /dev/ttyUSB0
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] REQUEST : 0x0010 
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Msg to send b'0010000010'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Encoded Msg to send b'01021010021002101003'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for status message for command 0x0010
2019-03-15 13:47:24 DEBUG (ZiGate-Listen) [zigate] Raw packet received, b'\x01\x80\x02\x10\x02\x10\x02\x15\x95\x02\x10\x02\x10\x02\x10\x10\x02\x10\x03\x01\x80\x10\x02\x10\x02\x15\x9a\x02\x10\x02\x13\x02\x13\x02\x1f\x02\x10\x03'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8000: b'00000010'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:16, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8010: b'0003030f'
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8010 - Version list : major:3, installer:30f, lqi:0, version:3.0f
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] STATUS code to command 0x0010:RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:16, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for message 0x8010
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Stop waiting, got message 0x8010
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] REQUEST : 0x0021 b'\x03\x18\xc8\x00'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Msg to send b'00210004f60318c800'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Encoded Msg to send b'0102102102100214f6021318c8021003'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for status message for command 0x0021
2019-03-15 13:47:24 DEBUG (ZiGate-Listen) [zigate] Raw packet received, b'\x01\x80\x02\x10\x02\x10\x02\x15\xa4\x02\x10\x02\x10\x02\x10!\x02\x10\x03'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8000: b'00000021'
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:33, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] STATUS code to command 0x0021:RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:33, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] REQUEST : 0x0023 b'\x00'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Msg to send b'002300012200'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Encoded Msg to send b'010210230210021122021003'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for status message for command 0x0023
2019-03-15 13:47:24 DEBUG (ZiGate-Listen) [zigate] Raw packet received, b'\x01\x80\x02\x10\x02\x10\x02\x15\xa6\x02\x10\x02\x10\x02\x10#\x02\x10\x03'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8000: b'00000023'
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:35, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] STATUS code to command 0x0023:RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:35, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Check network state
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] REQUEST : 0x0009 
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Msg to send b'0009000009'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Encoded Msg to send b'010210021902100210021903'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for status message for command 0x0009
2019-03-15 13:47:24 DEBUG (ZiGate-Listen) [zigate] Raw packet received, b'\x01\x80\x02\x10\x02\x10\x02\x15\x8c\x02\x10\x02\x10\x02\x10\x02\x19\x02\x10\x03\x01\x80\x02\x19\x02\x10\x167\x02\x10\x02\x10\x02\x10\x15\x8d\x02\x10\x02\x11\xedD\xa8\xb5\x8f\xb1\x02\x1a\xc7\xa4\x19h$\x8c\x02\x1b\x02\x10\x03'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8000: b'00000009'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:9, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8009: b'000000158d0001ed44a8b58fb10ac7a41968248c0b'
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8009 - Network state response : addr:0000, ieee:00158d0001ed44a8, panid:46479, extended_panid:12757228402095170700, channel:11, lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] STATUS code to command 0x0009:RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:9, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for message 0x8009
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Stop waiting, got message 0x8009
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Set Zigate Time (firmware >= 3.0f)
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] REQUEST : 0x0016 b'$\x1eil'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Msg to send b'001600042d241e696c'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Encoded Msg to send b'01021016021002142d241e696c03'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for status message for command 0x0016
2019-03-15 13:47:24 DEBUG (ZiGate-Listen) [zigate] Raw packet received, b'\x01\x80\x02\x10\x02\x10\x02\x15\x93\x02\x10\x02\x10\x02\x10\x16\x02\x10\x03'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8000: b'00000016'
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:22, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] STATUS code to command 0x0016:RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:22, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] REQUEST : 0x0015 
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Msg to send b'0015000015'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Encoded Msg to send b'01021015021002101503'
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for status message for command 0x0015
2019-03-15 13:47:24 DEBUG (ZiGate-Listen) [zigate] Raw packet received, b'\x01\x80\x02\x10\x02\x10\x02\x15\x90\x02\x10\x02\x10\x02\x10\x15\x02\x10\x03\x01\x80\x15\x02\x10\x02\x1e\xd8\x02\x10\xa15\x02\x10\x17\x88\x02\x11\x02\x13Y\x02\x1c\x85\x02\x11\x9b\x02\x10\x03'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8000: b'00000015'
2019-03-15 13:47:24 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:21, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8015: b'00a1350017880103590c85019b'
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8015 - Device list : devices:[OrderedDict([('id', 0), ('addr', 'a135'), ('ieee', '0017880103590c85'), ('power_type', 1), ('lqi', 155)])], lqi:0
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] STATUS code to command 0x0015:RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:21, error:b'', lqi:0
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Known devices in zigate : {'a135'}
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Waiting for message 0x8015
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Previous devices missing : {'68a3', '8542'}
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Stop waiting, got message 0x8015
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_DEVICE_UPDATED
2019-03-15 13:47:24 DEBUG (Thread-6) [zigate] Check Need discovery Philips LCT015 (a135) 0017880103590c85
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Auto saving /config/zigate.json
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [custom_components.zigate] Update device Philips LCT015 (a135) 0017880103590c85
2019-03-15 13:47:24 DEBUG (Thread-6) [zigate] Check Need discovery Philips RWL021 (8542) 0017880102d5b98c
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] Saving persistent file
2019-03-15 13:47:24 DEBUG (SyncWorker_10) [zigate] File already existing, make a backup before
2019-03-15 13:47:24 DEBUG (Thread-6) [zigate] Check Need discovery Philips LCT012 (68a3) 00178801021dc3e7
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [custom_components.zigate] Device not found Philips LCT015 (a135) 0017880103590c85, adding it
2019-03-15 13:47:24 DEBUG (ZiGate-Decode data) [custom_components.zigate] Add device Philips LCT015 (a135) 0017880103590c85
2019-03-15 13:47:25 DEBUG (SyncWorker_10) [zigate] REQUEST : 0x0018 b'\x01'
2019-03-15 13:47:25 DEBUG (SyncWorker_10) [zigate] Msg to send b'001800011801'
2019-03-15 13:47:25 DEBUG (SyncWorker_10) [zigate] Encoded Msg to send b'010210180210021118021103'
2019-03-15 13:47:25 DEBUG (SyncWorker_10) [zigate] Waiting for status message for command 0x0018
2019-03-15 13:47:25 DEBUG (ZiGate-Listen) [zigate] Raw packet received, b'\x01\x80\x02\x10\x02\x10\x02\x15\x9d\x02\x10\x02\x10\x02\x10\x18\x02\x10\x03'
2019-03-15 13:47:25 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 13:47:25 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8000: b'00000018'
2019-03-15 13:47:25 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:24, error:b'', lqi:0
2019-03-15 13:47:25 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:25 DEBUG (SyncWorker_10) [zigate] STATUS code to command 0x0018:RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:24, error:b'', lqi:0
2019-03-15 13:47:25 DEBUG (SyncWorker_10) [custom_components.zigate] Add device Philips LCT015 (a135) 0017880103590c85
2019-03-15 13:47:25 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/helpers/entity_platform.py", line 344, in _async_add_entity
    raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: zigate.0017880103590c85. Platform zigate does not generate unique IDs
2019-03-15 13:47:25 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 13:47:25 DEBUG (SyncWorker_10) [custom_components.zigate] Add device Philips RWL021 (8542) 0017880102d5b98c
2019-03-15 13:47:25 DEBUG (SyncWorker_10) [custom_components.zigate] Add device Philips LCT012 (68a3) 00178801021dc3e7
2019-03-15 13:47:25 DEBUG (SyncWorker_7) [custom_components.zigate.sensor] Creating sensor for device Philips RWL021 (8542) 0017880102d5b98c {'endpoint': 2, 'cluster': 64512, 'attribute': 1, 'data': '', 'expire': 2, 'name': 'button_on', 'type': <class 'str'>, 'value': ''}
2019-03-15 13:47:25 DEBUG (SyncWorker_14) [custom_components.zigate.light] Creating light for device Philips LCT015 (a135) 0017880103590c85 11
2019-03-15 13:47:25 DEBUG (SyncWorker_7) [custom_components.zigate.sensor] Creating sensor for device Philips RWL021 (8542) 0017880102d5b98c {'endpoint': 2, 'cluster': 64512, 'attribute': 4, 'data': '', 'expire': 2, 'name': 'button_down', 'type': <class 'str'>, 'value': ''}
2019-03-15 13:47:25 DEBUG (SyncWorker_14) [custom_components.zigate.light] Creating light for device Philips LCT012 (68a3) 00178801021dc3e7 11
2019-03-15 13:47:25 DEBUG (SyncWorker_7) [custom_components.zigate.sensor] Creating sensor for device Philips RWL021 (8542) 0017880102d5b98c {'endpoint': 2, 'cluster': 64512, 'attribute': 2, 'data': '', 'expire': 2, 'name': 'button_up', 'type': <class 'str'>, 'value': ''}
2019-03-15 13:47:25 DEBUG (SyncWorker_7) [custom_components.zigate.sensor] Creating sensor for device Philips RWL021 (8542) 0017880102d5b98c {'endpoint': 2, 'cluster': 64512, 'attribute': 3, 'data': '', 'expire': 2, 'name': 'button_off', 'type': <class 'str'>, 'value': ''}

The light is off and the button in HA report off.
I clic on the light button in HA. It goes ON and then back OFF after few seconds. The light is ON.

Log

2019-03-15 14:01:05 DEBUG (SyncWorker_19) [zigate] REQUEST : 0x0092 b'\x02\xa15\x01\x0b\x01'
2019-03-15 14:01:05 DEBUG (SyncWorker_19) [zigate] Msg to send b'009200060902a135010b01'
2019-03-15 14:01:05 DEBUG (SyncWorker_19) [zigate] Encoded Msg to send b'010210920210021602190212a1350211021b021103'
2019-03-15 14:01:05 DEBUG (SyncWorker_19) [zigate] Waiting for status message for command 0x0092
2019-03-15 14:01:05 DEBUG (ZiGate-Listen) [zigate] Raw packet received, b'\x01\x80\x02\x10\x02\x10\x02\x15\x17\x02\x10\x02\x10\x02\x10\x92\x02\x10\x03'
2019-03-15 14:01:05 DEBUG (ZiGate-Event Loop) [zigate] Dispatch ZIGATE_PACKET_RECEIVED
2019-03-15 14:01:05 DEBUG (ZiGate-Decode data) [zigate] Received response 0x8000: b'00000092'
2019-03-15 14:01:05 DEBUG (ZiGate-Decode data) [zigate] RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:146, error:b'', lqi:0
2019-03-15 14:01:05 DEBUG (ZiGate-Decode data) [zigate] Dispatch ZIGATE_RESPONSE_RECEIVED
2019-03-15 14:01:05 DEBUG (SyncWorker_19) [zigate] STATUS code to command 0x0092:RESPONSE 0x8000 - Status response : status:0, sequence:0, packet_type:146, error:b'', lqi:0

Call service zigate.refresh_device. The button now in HA report the correct ON status.

Log

See attached file: refresh_device.txt.yaml (86.2 KB)

At this step I also see this new logs on the top part of the dev-info page:

Command 0x0100 failed Failed (ZigBee event codes) 21 : b''
14:03 deps/lib/python3.7/site-packages/zigate/core.py (ERROR) - message first occured at 14:03 and shows up 10 times
RESPONSE 0x8702 - APS Data Confirm Fail : status:212, source_endpoint:1, dst_endpoint:1, dst_address_mode:2, dst_address:8542, sequence:116, lqi:255
14:03 deps/lib/python3.7/site-packages/zigate/core.py (ERROR)

biau · March 15, 2019, 9:44pm

What’s the distance between the zigate and the bulb ?

edit: it seem’s you only have one device and lqi is always 162 so it’s really good and does not look like a range issue.

Adorem · March 16, 2019, 2:45pm

Yes I’m currently testing this solution and the ZiGate and my bulb are really close.

Carasak · March 16, 2019, 8:08pm

I have the same behavior from time to time independent of range to Zigate. It is also not device specific. Have had this with Innr, Osram and tradfri bulbs. Only Philipps Hue ones have been always reliable.

max5962 · March 17, 2019, 4:20pm

I Just upgrade your lib and now i Have :.

 2019-03-17 17:16:53 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.140344113490184] Error handling message: {'type': 'call_service', 'domain': 'zigate', 'service': 'build_network_map', 'service_data': {}, 'id': 15}
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/websocket_api/decorators.py", line 17, in _handle_async_response
    await func(hass, connection, msg)
  File "/usr/src/app/homeassistant/components/websocket_api/commands.py", line 148, in handle_call_service
    connection.context(msg))
  File "/usr/src/app/homeassistant/core.py", line 1130, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/app/homeassistant/core.py", line 1154, in _execute_service
    await self._hass.async_add_executor_job(handler.func, service_call)
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/zigate/__init__.py", line 406, in build_network_map
    myzigate.build_network_map(hass.config.config_dir)
AttributeError: 'ZiGate' object has no attribute 'build_network_map'

doudz · March 18, 2019, 8:08am

build_network_map as been removed since the map is available on the custom panel.

Adorem · March 18, 2019, 8:33am

In my case this problem always appear and like biau already notice it’s not due to a range issue.
I try and success to pair another device (legrand neatmo light switch) and in this case his status is correctly reported even when I change his status not from HA (with the wall button for example).

Could it be because these bulbs were previously paired with my hue system (I have unpair and remove from the hue app)?

Can someone please provide me some debugs logs when you switch on/off hue bulb?

What else can I try and check?

doudz · March 18, 2019, 8:53am

APS Data Confirm Fail means the message sent from zigate is not received by the bulb, so it’s a problem between zigate and bulb
maybe if your bulb is offline for a long period it unpair itself from zigate ? (supposition)

Adorem · March 18, 2019, 9:19am

Thank you for this info it will help me to debug and track the issue.

Could it be because I have not reset correctly the ZiGate when I have update to 3.0f?

I also want to test on a new installed HA system but if you think it’s a problem between zigate and bulb then for the moment this test is not useful.

I don’t think so because this appear all the time and because all the devices are very close to each others and it receive the on/off command because the state of the bulb change immediately when I send them from HA.

Carasak · March 18, 2019, 9:52am

adding symptom description:
I can dimm the bulbs no problem. But when set to e.g. 50% light they still show as off (or on) depending what state they got stuck in. So commands are reaching the bulbs.

doudz · March 18, 2019, 7:50pm

What you describe is a state reporting problem, it should be fixed by calling discover_device.
Since many people have problem with Ikea bulb, I bought one, first tests are working.

doudz · March 18, 2019, 7:53pm

Beside, I’m happy to announce the support of zigate to zigpy and so on zha component.
It’s still in early stage but it works !