Robotronic wrote:That said, I would argue that there is certainly a need to change the PIN. I don't want to use the same PIN that literally every other installation of Homebridge appears to be using, that's a security nightmare.
I considered that and when you think about the ability to even access Homebridge means they would have to compromise your network too then I think the damage is done. All of that being said, I'll add it to the list to add it back into the software in a very hidden way. Why? One of the reasons I took it out is the purpose of integrating Homebridge was so that people who didn't really know what they were doing with Homebridge didn't have to worry about it. The more options you give to people then the more chances there are that they post up here because they changed something and didn't understand the ramifications and then I've created more support headaches
.
Robotronic wrote:Question now is: Will that file be overwritten if changes are made to the plugin config within Indigo?
Yes, the config.json file will get overwritten when you make changes. You can manually change something in the config (like the PIN) if you want but you risk it getting overwritten and then you would have to create your HomeKit accessories again because they would never again connect until you removed and re-added the HBB server. Yet another reason I try to minimize what people can do to muck with the works.
Robotronic wrote:Also, how do we go about keeping the version of Homebridge built into the plugin updated?
For now just watch the forums, I'll post when I update. I haven't yet incorporated version checking into the plugin because I'm trying to figure out how to do that using GitHub instead of my old method of reading forum posts.