New custom component : ZiGate (obsolete)

Indeed it is a flash button to update FW

Yes I confirm, it’s a barebone Windows 10 (not a VM, nothing virtualized).

So I’ve tested this and when I run the zigate.permit_join, I have this showing up in the console:

2018-01-26 11:10:39 DEBUG (SyncWorker_38) [zigate] --------------------------------------
2018-01-26 11:10:39 DEBUG (SyncWorker_38) [zigate] REQUEST      : 0049 FFFC1E00
2018-01-26 11:10:39 DEBUG (SyncWorker_38) [zigate]   # standard : 01 00 49 00 04 50 FF FC 1E 00 03
2018-01-26 11:10:39 DEBUG (SyncWorker_38) [zigate]   # encoded  : b'010210490210021450fffc1e021003'
2018-01-26 11:10:39 DEBUG (SyncWorker_38) [zigate] (timestamp : 11:10:39)
2018-01-26 11:10:39 DEBUG (SyncWorker_38) [zigate] --------------------------------------
2018-01-26 11:10:39 DEBUG (MainThread) [zigate] --------------------------------------
2018-01-26 11:10:39 DEBUG (MainThread) [zigate] RESPONSE 8000 : Status
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   * Status              : Failed with event code: 128
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   - Sequence            : b'00'
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   - Response to command : b'0049'
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   # encoded : b'01800210021002154c800210021049021003'
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   # decoded : 0180 00 00 05 4C 80 00 00 49 0003
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   (@timestamp : 11:10:39)

Also, when I click this, I see a blue and red LED blink once. Both are located on the USb part. There is a blue light always on the radio controller part. It looks like I’m running the same issue as @bdr. So as far as I understand, now I need to boot on Windows and see what happens when I run TestGUI. I keep you up-to-date :slight_smile:

@eLRIC I was able to run the TestGUI. If it does not work you might indeed need to install the drivers, they are given on the website too @bdr.

With the TestGUI it seems that I was able to pair it with my Hue DimmerSwitch. So now I’m back on Linux, and I will check what happens now within my Docker. Also, I forgot to close all the stuff before the reboot so I had to remove and plug back the Zigate device in order to remove it from pairing state.

Great! Now it can enter in pairing mode :tada:!

I think it was lacking of configuration, I’ll check if I’m able to pair my Hue devices later today. I’ll tell you if I’m able to do anything with it and if I encounter some additional issues.

To fix the error, the following steps were required:

At the moment it is only possible to boot on Windows to fix this as the TestGUI has no equivalent on Linux. Concerning the drivers, no drivers are required from Linux are they are native as mentioned on Zigate’s website :slight_smile:

I was able to pair my Zigate with my Hue DimmerSwitch, now I wonder how it should be treated in the configuration file as it a switch with 4 buttons. I think that each should be handled differently, is there something that is close enough and that can be used for my DimmerSwitch?

This ZiGate looks amazing, but I just contacted Frederic and he is not able to ship to the US at this time. This is a little bit disappointing. So if anyone would ever want to take on the task to ship a couple of units here in the US, I would defray all costs or if there is anything here state side that you can’t get in Europe, i would be more than happy to make an exchange.

@Dr_c0w On Hass, you seem to have a response from the zigate.

2018-01-26 11:10:39 DEBUG (MainThread) [zigate] RESPONSE 8000 : Status
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   * Status              : Failed with event code: 128
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   - Sequence            : b'00'
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   - Response to command : b'0049'
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   # encoded : b'01800210021002154c800210021049021003'
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   # decoded : 0180 00 00 05 4C 80 00 00 49 0003
2018-01-26 11:10:39 DEBUG (MainThread) [zigate]   (@timestamp : 11:10:39)

On my side, I haven’t this logs. I’ll try with windows drivers too.
But I haven’t periphal warning.

I don’t mind doing it (and I might contact you later if I need something from the US :stuck_out_tongue: ).

The delivery is 10€ from zigate.fr, so it would be 49€ (zigate) + 10€ (delivery EU) + 20€ (delivery with tracking and insurance up to 50€ via DHL) = 79€

You would still need to pay the tax to your custom service. The stated shipping is for a package up to 2kg, so it cover lots of zigate.

A weird thing on the website zigate.fr is that you can only add one zigate to the shopping cart, so going through the website would add 10€ for each zigate! (but I suppose that by contacting Frederic directly he can sort that out).

Great touliloup I’ll send you a PM shortly

I don’t have one myself, but if you send me the logs when you press each button, I might be able to halp figuring out the config (or the need to modify the lib)

EveryThing is working well. THanks everyone :slight_smile:

But I experiencing something strange, sometimes for 2 or 3 hours my temp sensor ( outside ) refuse to send updates.
I don’t know if it’s a zigate bug or sensor bug :confused:

It happened to me with a sensor but it went back to normal without me noticing what really changed …
Anyway, just few infos :

  • apparently, sensor will send data when it detects a change (i.e. not on a time basis)
  • you can check the battery in the “states” page : you should see a line like “battery: 2.965” for your sensor (some sensors have been provided with weaker batteries than others)
  • signal strength measurement should arrive soon, it may help to understand if the sensor is too far from a ZiGate perspective

Lastly: if you speak about a xiaomi sensor, I’m not sure they are suited to be outside (depending on the protection you provide)

Well, now I’m facing another issue. The DimmerSwitch does not send any info to the Zigate. Within TestGUI, I see nothing that comes from the Switch. I re-paired it with my Hue Bridge and the Switch still works well.

Is it possible that my Zigate has still an element that is still misconfigured? As it seems that thanks to the TestGUI it has been able to pair with a Zigbee device…

If anybody has any idea, I’m ready to give it a test :sweat_smile:.

EDIT: More precision on the situation.
I’ve been able to pair my device within TestGUI and within this component in HA. When I press the buttons, nothing happens. After a while, and many pressures, the DimmerSwitch blinks multiple times and I see a request on the update of the available routes on the logs, juste like if I was pairing it again.

The normal behavior of the switch is a green light showing up when the button is pressed. This might be to tell that the action has been received by the remote controller (Hue Bridge in this case).

This issue does not seem to depend on my hardware or software but from the Zigate itself.

I remember reading somewhere that certain lights needs to be adressed on a certain zigbee channel (i.e.18) but I cannot remember if it was for the Hue or Ikea ones (and I did not find back the article)

What I understood is that you cannot have the Hue bridge and the ZiGate acting as Zigbee router at the same time

If you struggle, you can still open an issue on the ZiGate github (fairesoimeme)ad Akila has tested the Hue and might be knowledgeable about your problem

Thanks a lot! I’ll definitely check it and see if I can find an answer in here :smile:. If I find anything useful, I’ll post the link :+1: (in case it might help anybody in the future).

@Dr_c0w are you running HA in a docker container?

I ask because I am and I’m seeing the same error you reported earlier when calling the zigate.permit_join service:

2018-01-29 12:06:46 DEBUG (SyncWorker_9) [zigate] --------------------------------------
2018-01-29 12:06:46 DEBUG (SyncWorker_9) [zigate] REQUEST : 0049 FFFC1E00
2018-01-29 12:06:46 DEBUG (SyncWorker_9) [zigate] # standard : 01 00 49 00 04 50 FF FC 1E 00 03
2018-01-29 12:06:46 DEBUG (SyncWorker_9) [zigate] # encoded : b’010210490210021450fffc1e021003’
2018-01-29 12:06:46 DEBUG (SyncWorker_9) [zigate] (timestamp : 12:06:46)
2018-01-29 12:06:46 DEBUG (SyncWorker_9) [zigate] --------------------------------------
2018-01-29 12:06:46 DEBUG (MainThread) [zigate] --------------------------------------
2018-01-29 12:06:46 DEBUG (MainThread) [zigate] RESPONSE 8000 : Status
2018-01-29 12:06:46 DEBUG (MainThread) [zigate] * Status : Failed with event code: 128
2018-01-29 12:06:46 DEBUG (MainThread) [zigate] - Sequence : b’00’
2018-01-29 12:06:46 DEBUG (MainThread) [zigate] - Response to command : b’0049’
2018-01-29 12:06:46 DEBUG (MainThread) [zigate] # encoded : b’01800210021002154c800210021049021003’
2018-01-29 12:06:46 DEBUG (MainThread) [zigate] # decoded : 0180 00 00 05 4C 80 00 00 49 0003
2018-01-29 12:06:46 DEBUG (MainThread) [zigate] (@timestamp : 12:06:46)

Hello,
How to add a door sensor ( sensor_magnet) ?

I add :
switch:

  • platform: zigate
    name: ‘Cabanon’
    address: 855501
    default_state: ‘event’

But appear lin home-assistant ike a normal switch so not like a door - sensor :frowning:
Any idea ?

thanks.

This is what I use with xiaomi door sensors

- platform: zigate
  name: 'Cabanon'
  address: 855501
  default_state: 'state'
  inverted: 'yes'

It will appear like a switch and will turn on when the door is opened
What behaviour would you want from a sensor approach ? (it is certainly feasible, but not my use case)

Yes I was running HA in a Docker container when I encountered this error. In order to fix it, I had to boot on Windows and follow the steps on the site of Zigate with TestGUI.

After I followed the steps with TestGUI, I was able to start pairing my devices with my Zigate :wink: