how do I uninstall the plugin?
Same as install except you type uninstall
ok...uninstalled...
Cool. Shouldn’t be the reason you cannot scan the QR code though
Yeah...still no joy on finding the bridge..."accessory not found"
Under the Home icon > Hubs and Bridges
Anything there?
I have 3 Ecobee thermostats, rachio, and hue bridges all showing up, but they are not connected since it is a new "home" in the app.
What about in the previous home?
I had all of those bridges setup in my home before I deleted it. I never pushed those from SmartThings, since I just did a direct integration via HomeKit with those devices.
Should I add them back first?
I keep getting a Syntax error and I'm not sure what I'm doing wrong. I get
"Error: Parse error on line 19:
...ebridge" }, { "platform": "
---------------------^
Expecting 'STRING', got '{' "
Blockquote
{
"bridge": {
"name": "Raspberry",
"username": "E3:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",
"platforms": [{
"platform": "config",
"name": "Config",
"port": 8080,
"sudo": true,
"restart": "sudo -n systemctl restart homebridge",
"temp": "/sys/class/thermal/thermal_zone0/temp",
"log": {
"method": "systemd",
"service": "homebridge"
},
{
"platform": "Hubitat-MakerAPI",
"name": "Hubitat",
"app_url": "http://192.168.10.169/apps/api/YOUR_APPS_ID/",
"access_token": "THIS-SHOULD-BE-YOUR-TOKEN",
"local_ip": "10.0.0.70",
"local_port": 20010,
"polling_seconds": 300,
"temperature_unit": "F",
"mode_switches": true,
"hsm": true,
"debug": false,
"programmable_buttons": [
"97",
"98"
],
"excluded_capabilities": {
"HUBITAT-DEVICE-ID-1": ["Switch", "TemperatureMeasurement"]
},
"excluded_attributes": {
"HUBITAT-DEVICE-ID-1": ["power", "humidity"]
},
"logFile": {
"enabled": true,
"path": "",
"file": "",
"compress": true,
"keep": 5,
"size": "10m"
}
]
}
Not the issue. They wouldn’t cause Homebridge not to scan. I had this issue when moving from ST too, but changing the QR code and deleting those files worked for me.
Sorry but I’m out of ideas at this point. @csteele and a few others here know quite a lot about Homebridge and may be able to offer further advice that will help you resolve the issue.
thanks @SmartHomePrimer. I appreciate the help.
1 Like
Try This,
{
"bridge": {
"name": "Raspberry",
"username": "E3:22:3D:E3:CE:30",
"port": 51826,
"pin": "031-45-154"
},
"description": "This is an example configuration file with one fake accessory and one fake platform. You can use this as a template for creating your own configuration file containing devices you actually own.",
"platforms": [{
"platform": "config",
"name": "Config",
"port": 8080,
"sudo": true,
"restart": "sudo -n systemctl restart homebridge",
"temp": "/sys/class/thermal/thermal_zone0/temp",
"log": {
"method": "systemd",
"service": "homebridge"
}
},
{
"platform": "Hubitat-MakerAPI",
"name": "Hubitat",
"app_url": "http://192.168.10.169/apps/api/YOUR_APPS_ID/",
"access_token": "THIS-SHOULD-BE-YOUR-TOKEN",
"local_ip": "10.0.0.70",
"local_port": 20010,
"polling_seconds": 300,
"temperature_unit": "F",
"mode_switches": true,
"hsm": true,
"debug": false,
"programmable_buttons": [
"97",
"98"
],
"excluded_capabilities": {
"HUBITAT-DEVICE-ID-1": ["Switch", "TemperatureMeasurement"]
},
"excluded_attributes": {
"HUBITAT-DEVICE-ID-1": ["power", "humidity"]
},
"logFile": {
"enabled": true,
"path": "",
"file": "",
"compress": true,
"keep": 5,
"size": "10m"
}
}
]
}
Blockquote
I did find this reddit page that talked about using this discovery dns app on the iPhone to see if you can find the homebridge broadcasting through bonjour and I am not seeing it there. Not sure if that helps, but maybe it is a breadcrumb.
What comes after the QR code?
I just installed it on a rPi and used a completely defective config.json (on purpose) and got these lines after the QR code:
[2019-11-6 05:44:37] [Hubitat hhm:0.4.2] Fetching Hubitat-MakerAPI devices. This can take a while depending on the number of devices are configured! [2019-11-6 05:44:37] [Hubitat hhm:0.4.2] Refreshing All Device Data [2019-11-6 05:44:38] Homebridge is running on port 51826. uncaughtException: Service name is already in use on the network [2019-11-6 05:44:38] Error: Service name is already in use on the network at Registry._onProbeComplete (/usr/lib/node_modules/homebridge/node_modules/bonjour-hap/lib/Registry.js:106:27) at Prober.done (/usr/lib/node_modules/homebridge/node_modules/bonjour-hap/lib/Prober.js:67:10) at Prober.onMDNSresponse (/usr/lib/node_modules/homebridge/node_modules/bonjour-hap/lib/Prober.js:61:102) at emitTwo (events.js:126:13) at EventEmitter.emit (events.js:214:7) at Socket.<anonymous> (/usr/lib/node_modules/homebridge/node_modules/multicast-dns/index.js:49:43) at emitTwo (events.js:126:13) at Socket.emit (events.js:214:7) at UDP.onMessage [as onmessage] (dgram.js:659:8) uncaughtException: Service name is already in use on the network [2019-11-6 05:44:38] Got SIGTERM, shutting down Homebridge... [2019-11-6 05:44:38] [Hubitat hhm:0.4.2] latest version on npmjs is 0.4.2 [2019-11-6 05:44:38] [Hubitat hhm:0.4.2] your version of the plugin is up2date
I've got a duplicate address because it's just the default that Dan.T put in his instructions far at the top...
{ "bridge": { "name": "Homebridge", "username": "CC:25:3C:C3:CE:3C", "port": 51826, "pin": "031-45-111" }, "description": "My HomeBridge: Hubitat", "platforms": [{ "platform": "Hubitat-MakerAPI", "name": "Hubitat", "app_url": "http://192.168.10.169/apps/api/YOUR_APPS_ID/", "access_token": "THIS-SHOULD-BE-YOUR-TOKEN" } }] }
Maybe you will want to have more config AFTER you get it initially working.
I also became a convert to the one Instance-per-plugin-Club. If you decide you want those other plugins, you probably want individual instances.
I installed MakerAPI on a Hub and selected a device.
I fixed up the config.json from what I pasted above:
{
"bridge": {
"name": "Homebridge4",
"username": "CC:25:CD:C3:CE:3C",
"port": 51826,
"pin": "031-45-111"
},
"description": "My HomeBridge: Hubitat and TCC",
"platforms": [{
"platform": "Hubitat-MakerAPI",
"name": "Hubitat-Maker1",
"app_url": "http://192.168.7.65/apps/api/35/",
"access_token": "obscured"
}]
}
And the result is:
$ homebridge [2019-11-6 06:03:00] Loaded config.json with 0 accessories and 1 platforms. [2019-11-6 06:03:00] --- [2019-11-6 06:03:02] Loaded plugin: homebridge-hubitat-makerapi Homebridge Version: 2.4 Plugin Version: 0.4.2 [2019-11-6 06:03:02] Registering platform 'homebridge-hubitat-makerapi.Hubitat-MakerAPI' [2019-11-6 06:03:02] --- [2019-11-6 06:03:02] Loading 1 platforms... [2019-11-6 06:03:02] [Hubitat-Maker1] Initializing Hubitat-MakerAPI platform... Setup Payload: X-HM://0023ISYWDCKAC QR CODE HERE [2019-11-6 06:03:02] [Hubitat-Maker1 hhm:0.4.2] Setting "local_ip" not set in config, tried to determine it and found 192.168.7.35 -> I hope this is correct [2019-11-6 06:03:03] [Hubitat-Maker1 hhm:0.4.2] Configuration of cached accessories not done, wait for a bit... 2 [2019-11-6 06:03:03] Homebridge is running on port 51826. [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] latest version on npmjs is 0.4.2 [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] your version of the plugin is up2date [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] Device Added (Cache) - Name Qubino RGBW Controller Dimmer, ID 2 [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] Device Added (Cache) - Name Qubino RGBW Controller, ID 1 [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] Fetching Hubitat-MakerAPI devices. This can take a while depending on the number of devices are configured! [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] Refreshing All Device Data [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] Received All Device Data [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] Starting receiver [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] Set communcation_broken to false [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] Setting MakerAPI post URL to http://192.168.7.35:20010/event at http://192.168.7.65/apps/api/35/ [2019-11-6 06:03:04] [Hubitat-Maker1 hhm:0.4.2] homebridge-hubitat-makerapi server listening on 20010 [2019-11-6 06:03:05] [Hubitat-Maker1 hhm:0.4.2] MakerAPI postURL successfully activated
I admit, I've built this a lot of times.. and it works each time.
The most critical part related to seeing the Accessory in iOS Home App is the username: and pin;
Those must be unique and changing them (both) is usually what I've had to do to see the Accessory.
2 Likes
This is what is right after the QR code. Below that is the list of devices. I've changed the username and pin both multiple time with no luck.
I just uninstalled homebridge as well...still with the same result.
The devices all load and are refreshing. It just doesn't want to connect??!?!!?
Change your port in the config.json file to 45525. It is what mine is running on, for some reason I cannot remember. I google it, and all I find is this guy is using it in an example config.json file for some instructions I have never seen before. So it wasn't here that I got that from, but somewhere he and I read the same help doc apparently. 
Maybe it's nothing, but I'm running Homebridge on a Macbook Pro with High Sierra, and my phone is running 13.2 
Sorry, I guess I am late to the party. I have seen this behavior before and it can happen that the mDNS traffic is send to the wrong interface. You can try to add the following to your config file:
"mdns": { "interface": "192.168.42.1" },
Just need to change the IP to your IP address and restart Homebridge.
Here is an example on how the config looks with that part: mDNS packets send to wrong interface · Issue #1957 · nfarina/homebridge · GitHub
EDIT: if you just copied the config above, than I am pretty sure it won’t work. The app_url, access_token are still looking like my demo values. Can you PM me you full config? We should be able to get you up and running in no time
