No snark intended.
My quotes meant (to me) that I didn't know exactly what to call it that would communicate. Communicate as in: transfer knowledge or improve understanding.
I'm happy to use snark with people I've communicated with enough times that they'd (probably) understand my humor... I never intentionally use snark on people I've never conversed with before.
I agree that the documentation for EVERYTHING (HomeKit/Homebridge related) is splattered all over the internet, with various vintages of advice too.
This Homebridge-Hubitat-MakerAPI and it's related homebridge-hubitat-hubconnect plugins are new.. 'paint's not dry' new.
It works many, many times better than the previous method(s) but my point is, it's unique. Any other documentation for other plug-ins will be wrong, in a big or little way.
Yes, there is an expectation that people get Homebridge working before adding plugins. Or at least the documentation I read years ago took me down that path. Everytime I spin up a new instance, it seems I have to go that way.. I have to see the "no plugin's installed" error messages to know I've got everything right. Then when I install the plugin, the errors make me focus on just the plugin area of config.json
In other words, this part is strictly for Homebridge, zero plugins:
{
"bridge": {
"name": "Homebridge",
"username": "CC:22:3D:E3:CF:30",
"port": 51827,
"pin": "216-30-116"
},
"platforms": [
]
}
Every appliance will need a plugin and you can have multiple appliances (with a platform <-- singular) within the platforms <-- plural section. Example of two dissimilar appliances:
{
"bridge": {
"name": "Homebridge",
"username": "CC:CC:CC:CC:CE:3C",
"port": 51826,
"pin": "012-45-369"
},
"description": "My HomeBridge: Hubitat and TCC",
"platforms": [
{
"platform": "tcc",
"name" : "Thermostat",
"username" : "csteeleemail",
"password" : "passwd",
"devices" : [
{"deviceID": "123456","name": "Main Floor"}
]
},
{
"platform": "Hubitat",
"name": "Hubitat",
"app_url": "http://192.168.7.66/apps/api/874/",
"access_token": "91d31b-token-311f9"
}
]
}