(edit : this is an answer to bdr’s question)
Hello,
Should work (I just re-tested it to be sure) …
Just a question : are you long pressing the small side button (not the big front one), as in : https://youtu.be/QkTx2mqsItw?t=1m14s ?
Pairing is before identifying the endpoints, so that should not interfere
In the link I posted, I was specifically thinking about that part :
Personnellement j’utilise la télécommande de Philips Hue :
Voici ma méthode pour remettre à Zéro, appairer et associer une ampoule :
On appuie sur ON + OFF ( 1 + 0) simultanément pendant 5 secondes à 50 cm de l’ampoule (sous tension bien entendu) On ouvre le réseau ZigBee de votre coordinateur (ZiGate par exemple) On éteint puis on remet sous tension l’ampoule qui s’appaire au coordinateur Pendant que le réseau est ouvert, on retourne la télécommande et à l’aide d’un trombone, on appuie sur le bouton setup pendant 5-10 secondes. La télécommande joint à son tour le réseau ZigBee Si on le souhaite, on peut associer la télécommande et l’ampoule en maintenant le bouton ON (1) pendant 5 secondes à 50 cm de l’ampoule (toujours sous tension).
Is it this process that is not working in your case ?
Seing the 1st issues 
it might be useful to explain how to get more logs for investigation :
In you configuration.yaml, activate debug mode on zigate (and preferentially not on the rest to ease analyze)
logger:
default: warning
logs:
custom_components.zigate: debug
custom_components.switch.zigate: debug
custom_components.sensor.zigate: debug
zigate: debug
The logs will be available in your conf folder, home-assistant.log file
Hope it will help …
For your first reply, yes I’ve tested this part. Nothing changed, even when I try the part on resetting the Dimmer Switch, I was unable to pair it with the Zigate.
Thanks for the help concerning the logs, I was ashamed not to be able to provide something as I only the service being called and executed. I’ll try this tomorrow, I’ll post the output in this thread. I also bought some Xiaomi / Aqara devices in order to check if I have any issue with this also and maybe this would help identify the problem as it seems that it’s working properly with you guys. Door and temperature sensor and Light Switch will be on their way soon. Hope the issue will only concern the Philips equipments 
@eLRIC Yes, I’ve tried both.
I retested this morning. I’ve put the zigate in join mode, then I put the device in discover mode (using the liitle button on the edge - the blue led blinked once)
I have enabled all debug logs according to your last comment and here is the content of it :
2018-01-25 07:55:48 DEBUG (MainThread) [custom_components.zigate] ZIGATE : Starting
2018-01-25 07:55:48 DEBUG (MainThread) [custom_components.zigate.zigate2hass] ZIGATE : Transport initialized : SerialTransport(<_UnixSelectorEventLoop running=True closed=False deb
Serial<id=0x7f0513d68828, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=0, xonxoff=False, rtscts=False, dsrdtr=False))
2018-01-25 07:56:22 DEBUG (Thread-6) [zigate] --------------------------------------
2018-01-25 07:56:22 DEBUG (Thread-6) [zigate] REQUEST : 0049 FFFC1E00
2018-01-25 07:56:22 DEBUG (Thread-6) [zigate] # standard : 01 00 49 00 04 50 FF FC 1E 00 03
2018-01-25 07:56:22 DEBUG (Thread-6) [zigate] # encoded : b'010210490210021450fffc1e021003'
2018-01-25 07:56:22 DEBUG (Thread-6) [zigate] (timestamp : 07:56:22)
2018-01-25 07:56:22 DEBUG (Thread-6) [zigate] --------------------------------------
Again, nothing append… 
Strange : you’re missing the return info from zigate. Log sould be like :
2018-01-25 08:48:54 DEBUG (SyncWorker_0) [zigate] --------------------------------------
2018-01-25 08:48:54 DEBUG (SyncWorker_0) [zigate] REQUEST : 0049 FFFC1E00
2018-01-25 08:48:54 DEBUG (SyncWorker_0) [zigate] # standard : 01 00 49 00 04 50 FF FC 1E 00 03
2018-01-25 08:48:54 DEBUG (SyncWorker_0) [zigate] # encoded : b'010210490210021450fffc1e021003'
2018-01-25 08:48:54 DEBUG (SyncWorker_0) [zigate] (timestamp : 08:48:54)
2018-01-25 08:48:54 DEBUG (SyncWorker_0) [zigate] --------------------------------------
2018-01-25 08:48:54 DEBUG (MainThread) [zigate] --------------------------------------
2018-01-25 08:48:54 DEBUG (MainThread) [zigate] RESPONSE 8000 : Status
2018-01-25 08:48:54 DEBUG (MainThread) [zigate] * Status : Success
2018-01-25 08:48:54 DEBUG (MainThread) [zigate] - Sequence : b'0f'
2018-01-25 08:48:54 DEBUG (MainThread) [zigate] - Response to command : b'0049'
2018-01-25 08:48:54 DEBUG (MainThread) [zigate] # encoded : b'0180021002100215c30210021f021049021003'
2018-01-25 08:48:54 DEBUG (MainThread) [zigate] # decoded : 0180 00 00 05 C3 00 0F 00 49 0003
2018-01-25 08:48:54 DEBUG (MainThread) [zigate] (@timestamp : 08:48:54)
Even before pressing the little button …
I’ll try to guess what can prevent ZiGate’s return code from happening. What config are you running : hass.io, dockerized, python venv ?
NB : For the process in itself once solved, you may try to push the little button longer ? something like > 6 secs (the led normally blinks several times)
That will help for sure
Hue is confirmed to work with ZiGate, so we 'll find a way
@eLRIC I’am using a NUC with ESXi, I have a Debian VM with python venv.
The zigate USB stick seems to be OK at the OS layer :
Bus 001 Device 004: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
I’ll try to open it and look if everything is well connected, etc.
And yes, the blue LED probably blinks several times but stop blinking when I release the button.
If I remember right, the Zigate blink when entering in pairing mode. Do you see any reaction from your Zigate when starting the pairing process? (Service zigate.permit_join)
Sorry to ask maybe something too basic, but, are you pressing for more than 3 seconds?, usually most of Xiaomi devices blinks 3 times when starts in pairing mode.
I’m thinking to buy ZiGate as I have been following the development, but, my help will be only as a tester as I have not knowledge of python.
@touliloup @eLRIC I have two led on the zigate :
- a red one, on the USB controller
- a blue one, on the zigbee part
Both stays on, the permit_join call change nothing, they don’t blink.
What is the function of the button on the zigate ?
I tried to disconnect the zigbee component (from the USB controller) and the behaviour is the same. Is the zigbee component faulty ?
@rex2k1 Yes, I have. It seems that it’s the zigate device (connection) fault.
Yes, the Zigate should at least start to blink when you put the Zigate in pairing mode.
You should also see the led on the serial bridge blink when you send command to the Zigate.
If not, I would say it’s not the Zigate fault, but either the serial bridge, or an improper configuration.
@touliloup
The connection between the OS and the USB seems to work. I have disconnection log when I pull the device out of the USB port :
DEBUG (MainThread) [custom_components.zigate.zigate2hass] ZIGATE : Connection Lost !
I have also tried to connect a usb key on this specific USB port and it works well.
Can I put the zigate in pairing mode physically ? If yes, should the led blink too ?
No, I’m not sure, but I don’t think the button purpose is to pair device. I wonder if it’s not a reset or flash button.
Ok, so I’ll try this evening with a windows computer (haven’t one at home) and the TestGUI software : http://zigate.fr/getting-started/ to figure out if it’s zigate fault.
Good idea 
Unfortunately it seems that my Zigate have a problem.
Here is the error I got when I try to open port with TestGUi software :
I have tried differents options, different USB port, nothing works… 
It’s seems more like a driver problem, or a wrong selection of the com port.
Or it could be just the serial adapter that is faulty.
It says that the port doesn’t exist, not that it’s not able to connect or not responding…
Did you also take the wifi module?
As per linux, the device appears correctly, and can select it without any issue (double click).
But when I try to open port, I have got an error
If it’s the serial adapter, should it work with another one ? Like this one : https://www.amazon.fr/Convertisseur-Converter-Module-Built-CP2102/dp/B00AFRXKFU/
ZiGate has a CH340T based USB-TTL module (with a crystal on it)
You can see the required pinout here : http://zigate.fr/wiki/montage-module-radio-zigate/
Can you confirm that the testgui you’re running is on barebone windows ? (no VM involved)