New custom component : ZiGate (obsolete)

Hey @touliloup,
Did you manage to get Tradfri Dimmer working with ZiGate? :slight_smile:

No, it simply doesn’t appear to be possible. A limitation/function of the ZigBee protocol (the dimmer only address a lamp or a group of lamp directly).

Hi guys,

I come here for a little help.
I juste get my ZiGate and have issues to get it to work.

I updated it with the last firmware and tested it on windows 10. Everything was ok.
So, Home Assistant:

I created the “custom_components” folder within my config directory
then pasted the hole stuff (senso/switch/zigate/LICENSE/README)
Next, I modify my config.yaml by adding

# Enable ZiGate
zigate:

Am I correct?
Because I got an error:
Invalid config for [zigate]: string value is None for dictionary value @ data['zigate']['host']. Got None. (See ?, line ?). Please check the docs at https://home-assistant.io/components/zigate/

PS: I’m running the latest HA 0.67.1 and pasted the lates relase of homeassistant_zigate 0.1.3.post1

[EDIT: I downgraded to HA 0.66 and I no longer get errors]
So no problem for now ^^

Just in case, I just released 0.13.post2 with latest commits from Alex Barcelo : it runs fine with 0.67.1

1 Like

Does anyone tested zigate with docker?

I use it in Docker.
Just added --device=/dev/ttyUSB0 to my docker run command.

1 Like

I use it with HassIO. (Also docker) I did not need to change anything in my setup.

Might be different of course if using wifi or USB module

Using the usb connection, not wifi. (Between zigate and hassio that is)

Hi people,

I come back for a noob question.
Despite all my efforts an researches, I can’t make my zigate to work.

Everything seems to be set up correctly since I have no errors in the logs.

I tried to pair a temp/humid sensor (the round one)
I launch the zigate.permit_join thing and pair the sensor.

A message appears on the front panel saying it’s ok, and gives me an adress that I paste on my configuation.yaml

# Add sensor (previously registered with the ZiGate)
  - platform: zigate
    name: 'Température Chambre_2'
    address: "e1ba"
    default_state: temperature
    default_unit: ‘°C’

But it’s not working. I got an empty sensor

The same appears with my Xiaomi Aqara light switche. I got an adress but… The switch lits up nothing

switch:
  - platform: zigate
    name: 'Interrupteur Chambre_1'
    address: "94f5"
    autotoggle_delay: 2
    default_state: 'state'
    type: 'toggle'

Each time I try to pair again, I get a new adress. Is it normal?

When I look in the log, it seems ok:

2018-04-23 20:37:19 DEBUG (MainThread) [zigate] --------------------------------------
2018-04-23 20:37:19 DEBUG (MainThread) [zigate] RESPONSE 8102 : Attribute Report / Response
2018-04-23 20:37:19 DEBUG (MainThread) [custom_components.zigate.zigate2hass] ZIGATE SIGNAL :
2018-04-23 20:37:19 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Signal   : zgt_signal_update_e1ba01
2018-04-23 20:37:19 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Property : last seen
2018-04-23 20:37:19 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Data     : 2018-04-23 20:37:19
2018-04-23 20:37:19 DEBUG (MainThread) [custom_components.zigate.zigate2hass] ZIGATE SIGNAL :
2018-04-23 20:37:19 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Signal   : zgt_signal_update_e1ba01
2018-04-23 20:37:19 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Property : temperature
2018-04-23 20:37:19 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Data     : 25.93
2018-04-23 20:37:19 INFO (MainThread) [zigate]   * Measurement: Temperature
2018-04-23 20:37:19 INFO (MainThread) [zigate]   * Value: 25.93 °C
2018-04-23 20:37:19 INFO (MainThread) [zigate]   FROM ADDRESS      : b'e1ba'
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   - Source EndPoint : b'01'
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   - Cluster ID      : b'0402'
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   - Attribute ID    : b'0000'
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   - Attribute type  : b'29'
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   - Attribute size  : 2
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   - Attribute data  : b'0a21'
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   # encoded : b'018102120210021f72021ae1ba0211021402120210021002102902100212021a21a803'
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   # decoded : 0181 02 00 0F 72 0A E1 BA 01 04 02 00 00 00 29 00 02 0A 21 A803
2018-04-23 20:37:19 DEBUG (MainThread) [zigate]   (@timestamp : 20:37:19)
2018-04-23 20:37:19 DEBUG (MainThread) [zigate] --------------------------------------

And

2018-04-23 20:38:24 DEBUG (MainThread) [zigate] --------------------------------------
2018-04-23 20:38:24 DEBUG (MainThread) [custom_components.zigate.zigate2hass] ZIGATE SIGNAL :
2018-04-23 20:38:24 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Signal   : zgt_signal_update_94f5
2018-04-23 20:38:24 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Property : MAC
2018-04-23 20:38:24 DEBUG (MainThread) [custom_components.zigate.zigate2hass] - Data     : 00158d0001f57030
2018-04-23 20:38:24 DEBUG (MainThread) [zigate] RESPONSE 004d : Device Announce
2018-04-23 20:38:24 DEBUG (MainThread) [zigate]   * From address   : b'94f5'
2018-04-23 20:38:24 DEBUG (MainThread) [zigate]   * MAC address    : b'00158d0001f57030'
2018-04-23 20:38:24 DEBUG (MainThread) [zigate]   * MAC capability : b'\x04\x93'
2018-04-23 20:38:24 DEBUG (MainThread) [zigate]   # encoded : b'0102104d0210021c9b94f50210158d02100211f5703002149303'
2018-04-23 20:38:24 DEBUG (MainThread) [zigate]   # decoded : 0100 4D 00 0C 9B 94 F5 00 15 8D 00 01 F5 70 30 04 9303
2018-04-23 20:38:24 DEBUG (MainThread) [zigate]   (@timestamp : 20:38:24)
2018-04-23 20:38:24 DEBUG (MainThread) [zigate] --------------------------------------

Do you have some ideas that could help?

Thanks a lot.

Add a “01” to each address (so e1ba01 and 94f501) as the endpoint is required in config
That should do … :slight_smile:

Thanks a lot for your help.

Unfortunately, I don’t get anything better :confused:

I’m using it with the latest version of HA and everything is OK :slight_smile:

I think deconz has a solution for it.
IIRC its by having an empty light group defined that the dimmer is paired with.

Hello EveryOne,
I’m developper and i’d like to help.
Its my first python project but i’m not afraid :slight_smile:

I’m having a lot a issues in order to use my local pyzigate library …
In my docker :

  1. Git clone zigate
  2. change setup.py with new versionning : version=‘0.1.3.test1’
  3. Change hass_custom_component zigate version (init.py) : pyzigate==0.1.3.test1
  4. Do change on Zigate lib
  5. cd ZIGATE_FOLDER
  6. python setup.py install
  7. pip install --upgrade .

I’m still not seeing my new logs … any idea ?

Hi,

I’m not a developper at all, but I think I have noticed a typo.

Isn’t it “custom_component”?

1 Like

for it to work that way, you have to publish your pyzigate library to pipy (so that it is automatically downloaded by HASS)

A quick & dirty solution would be to identify where the lib is installed in your docker image and replace it with your version

Even if i do :

  1. remove old file : rm -rf /usr/local/lib/python3.6/site-packages/pyzigate*
  2. pip install …
  3. /usr/local/lib/python3.6/site-packages/pyzigate/interface.py | grep “NEEEW” => new line is here

still no new logs :frowning: in hass

What do you mean no new log?
Did you configure zigate in Home-Assistant? Did you restart Home-Assistant?
What is in Home-Assistant log?

of course, everything is configured since the beginning.

I run python in debug mode,and the library is load in the folder :
/CONFIG_FOLDER/deps/lib/python3.6/site-packages/pyzigate

Now i can debug my developpements.