Another component for ZiGate

@Carasak I’ve opened an issue https://github.com/doudz/zigate/issues/96

I just realize that Ikea motion sensor probably works like Ikea remote, so probably you need the last 3.0f firmware

Thanks for info.
I was trying to update to 3.0f PR…now nothing works :wink:
Will let you know the outcome once i managed to get that thing working again.

I just update the zigate lib to 0.27.8 to fix a crash after flashing a new firmware, sorry for trouble

3.0f is finally released. Do you recommend the update doudz ?
What’s the best way to do that for people using your component ?

sure I recommand it, even if not all new features are supported.
Steps are :

  • Stop HA
  • Flash the new firmware (from Windows for now)
  • If you come from 3.0d or 3.0e : Erase EEPROM
  • ReStart HA
  • If you Erase EEPROM, Pair again your devices
  • Enjoy

And because pairing is using ieee adresses it will recognize devices as soon as I pair them is that correct? No need to change zigate.json file or do whatever in .storage directory ?

yes, you don’t have to touch anything

not always working as expected with me sorry
I’ve updated the firmware but now when I pair battery powered devices I have two entries for the same ieee in zigate.json.
And the hass component is not updated.
for example motion sensor 00158d0001a8d55a in https://termbin.com/u41v

What’s wrong with my setup ?

Forget about this, after a lot of retry and some hass restarts it finally works for almost all my devices at the first try.
But xiaomi devices with batteries does have really strange behavior. But it looks like it’s a know issue: https://zigate.fr/2019/02/11/maj-firmware-zigate-version-3-0f/

hard to say what happens, log could help but if everything’s ok now it’s good

Latest version 0.88 displays warning about zigate:

2019-02-21 15:10:09 WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change switch/zigate.py to zigate/switch.py. This will stop working soon.
2019-02-21 15:10:09 WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change sensor/zigate.py to zigate/sensor.py. This will stop working soon.
2019-02-21 15:10:09 WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change binary_sensor/zigate.py to zigate/binary_sensor.py. This will stop working soon.
2019-02-21 15:10:09 WARNING (MainThread) [homeassistant.loader] Integrations need to be in their own folder. Change light/zigate.py to zigate/light.py. This will stop working soon.

you’re already using 0.88, you’re moving fast :slight_smile:

yes because I had a real issue with my harmony hub not connecting anymore with hass and was really confident that ziagate should work as usual.

luckily, it’s just a file name change

git has been updated :slight_smile:

1 Like

I’m moving fast but you’re patching faster .
No more warnings in logs

I prepare a little custom panel to display the graph
image

3 Likes

I made a custom panel to display the network graph. It’s a bit ugly but it’s works

:heart_eyes: is it possible to display friendly names ?