forum

Thanks 10neWulf! I was afraid that it is caused by Apple's policy. Just wasn't sure as the latest version of the Gateway is still pretty new. Do you know if HomeBridge can run on the same Raspberry than Z-Way? Might be an alternative. I've been running Homebridge for the last year+. I started out r...

Many of us have switched to Homebridge for our Homekit functions. It has a ton of support for many different platforms and is more robust and configurable than the built in homekit functionality ever was. To be honest, though, I never actually found where the "official" z-way version went ...

FYI, if you're using Homebridge, do not update to v2.2.2 yet.

It is a known issue that it is not yet compatible.

Homebridge is not that hard to setup but I found it better to setup on a second raspberry pi rather than sharing with my Z-Way install. It worked on my rpi2 with both installed but the whole thing crashed after a few days. It's been runniing fine for a couple of weeks with Z-Way on the rpi2 and Home...

Would you be kind enough to offer a little assistance? Regards Simon Sadly, I do not currently have time to offer anything meaningful in the way of assistance. Here's what I can share, though: 1. The process is straightforward if you have some Linux experience. I wouldn't go so far as to call it ea...

I originally had Homebridge setup on the same rPi2 as my Z-way server. Moving it off to it's own rPi1 dramatically improved the performance of the Homekit integration.

@vh342,

Do you have any links to instructions on mounting var/log to a ramdisk and logrotate?

I don't have enough understanding of what's going on yet, but I am repeatedly getting corrupt filesystems on my Z-Way install. Prior to the 2.2 RCs, I had been running the same install of Raspbian on an rPi1 for over a year. Since 2.1.2-RC17, I've had to rebuild and re-install my rPi about 5 times. ...

The problem is now gone. I did install Homebridge and the system got rebooted several times during the process. Perhaps something installed or the reboots fixed it.

Tested successfully with 2.2.0-rc4 but the install took a lot longer than expected with all of the various packages that needed to be install on the rPi 2!