which looks pretty much identical to yours, I believe, except the order of a few lines (which shouldnāt hurt anything.)
If you try to run the smartthings plugin instead, does it start without errors? Just trying to determine if the issue is with Homebridge OR the Hubitat pluginā¦
Had HomeKit running for about a week, works pretty great. Had a few questions/thoughts:
Anyone notice duplicate devices? I have two devices for lights (ie. Barn lights)
(Way more important), is there a way to limit the attributes that come from hubitat into ST. For instance, I have 5 doors leading out to my back yard each is a contact sensor but now I have 5 temperature sensors that I donāt need. This limitation existed in ST.
Anyone else have an experience where a restart of the home kit container (or RPI) caused you to lose all the customized names and room assignments within home kit?
Iām not having the same issue, but Iām not using it on a RPi.
I needed more responsive polling so I could use changes in Hubitat virtual switches to trigger Insteon devices and vise-versa, so I am using a 1 second polling time. No issues with either platform for the last 11 days Iāve been running this way.
So Iāve noticed that my hue hub stopped being as responsive and I couldnāt figure out why. I removed all of my custom apps but it wasnāt until I removed homebridge that Iāve seen improvements.
I removed and re-installed the hubitat plugin, things have been all quite and responsive for about 15 hours. I think things to focus on to improve the plug-in:
Somehow storing room, name, device type data within the plugin so the user does not have to re-build home kit in the event the RPI/container restarts;
Somehow being able to stop device attributes from appearing as separate devices. As an example, a contact sensor with a temperature sensor appears as two separate devices. If the user does not want to see one of them the user should be able to have it not appear. This would seemingly require less data to be pushed to home kit and may improve performance.
Overall improvements as the plugin relates to the hubitat infrastructure. I think this has a lot to do with polling and the resources placed on the hubitat. I have amended my config.json removing all references to polling within the plugin and have gotten stabilityā¦ I had polling @ 10 seconds and I think this caused tremendous stress on the hubitat system as automations failed and response time within hubitat plummeted.
May need to be optimized for a RPi. I have a PZero W I was going to try, but that might be a waste of time. The fact Iām running it on an old Mac seems to be enough, but then again, I also only have 21 devices connected to the Hub right now, so the load is light compared to most here.
I used to see those issues using the ST plugin about a year ago but I think the issue was more with me tinkering with homebridge more than anything. Over the last couple months I havenāt seen this happen at all
As to pollingā¦ that is correct. Events get pushed from hubitat and I did not recognize that. Thank you for the porting.
I do, however, note that restarting the container will remove all home kit configurations and scenes. Paul was aware of this also but never got around to addressing it because it is difficult to replicate. Mainly because sometimes restarting the container (or rebooting homebridge) has no effect on the room and scene configuration for home kit and sometimes it does.
Believe me if I could observe a reason or pattern I would illustrate, but I can tell you that @csteele seems to have the same problem with rooms configurations and scenes disappearing within home kit. This is not your fault and would never insinuate it to be. Youāve been a blessing to this community and the ST community for a long time, I was just passing along some stuff to help others that were experiencing similar issues.
To be clear, I donāt think this is a homebridge issue as much as it is a plug-in issue. When I ran ST I ran homebridge and had no issues using the Foscam camera plug in, but the ST plug-in would reset the room configurations leaving the cameras in place.
When I ran the ST plug-in I also ran hombridge on RPI and not docker.
The problem there is that the ST and Hubitat plug-inās donāt really store data any where that Iām seeing.
The files that store the actual device info are homebridgeās persist folder so if that is not being stored on the disk than that would explain why itās resetting after every reboot.
Iāll be honest iām not a docker pro but I have a feeling itās in the way homebridge gets configured in the docker enviroment.
Do you have a link to the exact docker image your using. I would love to try and test this on my Qnap.
If you can share any docker config parameters you may be using that would be awesome.
I want to be careful with the every reboot talk. When first setting up your plugin, I likely rebooted homebridge 30 times (adding/removing/polling/messing with config.json). This did not trigger the elimination of the room config. For some reason on Sunday, I did a reboot and poof gone! So, I say it is random.
You do raise an interesting point. If the room configuration is stored in the persist directory. Can I simply back that up and (in the event of destruction) copy a file(s) back and restore the room configuration?
This docker image self-installs on synology and installs the gui interface in 1 click. If you look through his repositories you will find variations of docker installs.
Because the install of the homebridge docker container was self-installing and self-configuring, I don't know where to go to find the configuration within docker.