I had home bridge plug-in for hubitat on a Pi and that seemed to work but then I moved it to a Docker on my Synology once I realized it was available there and have this issue (note that I reinstalled everything on HE when I did that).
My virtual switches show up in Homekit after I add them with the HE app.
For my August lock I have a virtual lock in HE and an automation in Homekit that changes the lock's state when Homekit sees the door locked/unlocked.
First question: Is that the right way to map a lock in HE to a Homekit lock?
Second thing is I'm getting this 'Connection refused' whenever the lock state changes in Homekit:
(app 164=homebridge device 67 is my virtual lock)
[app:164]2019-02-08 02:30:08.311 pm warnConnection refused (Connection refused)
[app:164]2019-02-08 02:30:08.285 pm debugSending DEVICE Event (Front Door Locked | LOCK: locked) to Homebridge at (192.168.7.127:8005)
[app:164]2019-02-08 02:30:08.212 pm infoCommand Successful for Device Front Door Locked | Command lock()
[dev:67]2019-02-08 02:30:08.208 pm infoFront Door Locked was locked
[app:164]2019-02-08 02:30:08.175 pm infoProcess Command | DeviceId: 67 | Command: (lock)
So the HE home bridge got the message and change the virtual lock but then failed to communicate that back to Homekit. HE is on *.127, I don't know why it's trying to send the message there. On the phone the virtual switch sits with the spinning communication icon for a long time.
I don't see anywhere to tell the HE plugin where the Homebridge server is running.
I have searched the forums but with no luck.