** Sadly, a tree fell on our old garage and took out our old opener not long after I recorded these notes, so they aren’t as refined as I’d like them to be; however, they might serve others getting stuck setting up their Garadget. **<\/p>\n
To install homebridge, I followed these instructions: From Terminal.app, I ran:<\/p>\n After installing homebridge, begin installing plugins for your accessories. For instance, to install a plugin for an open source garage door opener, Garadget, read the plugin instructions<\/a>, then open Terminal and paste in:<\/p>\n Paste in the text below and save it (you can skip the “Platforms” section, as that is for other devices I’m using on the network):<\/p>\n \"description\": \"Garadget as an accessory.\", \"platforms\": [ \"token\" : \"c.mLRXPhJxsllnEk2XGVkh4yE4iceogLwK19iyRihYLJaZOWWl6vadUBw0pYzNH5Nqyu5ANCjmnay4PzGXmCX7xiQifgJro7rymQgTKdsxQ4Z7GwJEUya0jpU2y3C8YBSLntYuy4kZIPsNaQDb\",<\/p>\n \"clientId\": \"0fb9563b-16b3-4452-8721-268df1104d5a\", \"username\" : \"brad@schwie.com\", }<\/code><\/p>\n The Garadget plug-in requires a bit more tinkering of obtaining a Device ID and Access Token using Chrome, as described here<\/a>.<\/p>\n An example config.json file is here<\/a> if you don’t want to copy and paste what I laid out above.<\/p>\n In my case, the Garadget device ID was: Paste the Device ID and Access Token into your ~.\/homebridge\/config.json file.<\/p>\n I can’t remember why, but I also needed to tweak my homebridge settings in ~.\/config.json file by changing the port number from 51826 to 59393.<\/p>\n TROUBLESHOOTING: While running homebridge, I tried opening the garage door from the homekit hub device, my daughter’s iPad, using the Home app. But the garadget button in Home app said “No Response”, which was what I was seeing from other devices. When I looked at the output of homebridge from the macOS Sierra server, I noticed the following output, which indicated the token was no longer working:<\/p>\n [6\/21\/2017, 4:20:12 PM] [Garage Door] Set state to closed At least two things can mess up your access_token:<\/p>\n 1. Using the web app (accessing the garadget from a web browser – https:\/\/www.garadget.com\/my\/) seems to request a new token from the Garadget, which then causes the old token to be purged.<\/p>\n 2. Every 90 days the garadget token seems to expire.<\/p>\n I’m not sure which of these cases bit me, but I’ll update this later when I know.<\/p>\n To fix this issue, open the config.json app (mine was at ~\/.homebridge), I grabbed my updated token following these instructions (https:\/\/community.garadget.com\/t\/using-garadget-in-ifttts-recipes\/440), and then I inserted the updated token in the config.json app. Bam. Everything is working again.<\/p>\n *********************************** To find outdated homebridge plugins: To update homebridge: To update home bridge plugins: homebridge runs out of launchDaemons on the Mac mini. To restart it, unload it: and then re-load it: ** Sadly, a tree fell on our old garage and took out our old opener not long after I recorded these notes, so they aren’t as refined as I’d like them to be; however, they might serve others getting stuck … Continue reading
\nhttps:\/\/community.garadget.com\/t\/homekit-integration-with-homebridge-garadget-plugin\/664<\/a>
\nand
\nhttps:\/\/github.com\/nfarina\/homebridge\/wiki\/Install-Homebridge-on-OSX<\/a><\/p>\nsudo npm install -g --unsafe-perm homebridge<\/code>
\n(unsafe-perm was needed on macOS Sierra, not sure about other systems)<\/p>\nsudo npm install -g homebridge-garadget
\ncd ~\/.homebridge
\npico config.json<\/code><\/p>\n{
\n \"bridge\": {
\n \"name\": \"Homebridge\",
\n \"username\": \"CC:22:3D:E3:CE:39\",
\n \"port\": 51826,
\n \"pin\": \"031-45-154\"
\n },<\/p>\n
\n \"accessories\": [{
\n \"accessory\": \"Garadget\",
\n \"name\": \"Garage Door\",
\n \"cloudURL\": \"https:\/\/api.particle.io\/v1\/devices\/\",
\n \"deviceID\": \"500031001851353432393433\",
\n \"access_token\": \"7ab6b8b49072b6caf7490b8beb0a75086b1f4401\"
\n }
\n ],<\/p>\n
\n {
\n \"platform\": \"BelkinWeMo\",
\n \"name\": \"WeMo Platform\",
\n \"expected_accessories\" : \"1\",
\n \"timeout\" : \"25\",
\n \"no_motion_timer\": \"60\",
\n \"homekit_safe\" : \"1\"
\n },
\n\t {
\n \"platform\": \"Nest\",<\/p>\n
\n \"clientSecret\": \"8o4x71vmef6BDieuLTNwLyZx4\",
\n \"code\": \"RLZC9XJX\",<\/p>\n
\n \"password\" : \"schw0143\"
\n }
\n ]<\/p>\n
\nhttps:\/\/api.particle.io\/v1\/devices\/500031001851353432393433\/setState<\/a>
\nwith access_token:
\n7ab6b8b49072b6caf7490b8beb0a75086b1f4401<\/p>\n
\nThe garadget access_token reset 90 days after I started using homebridge. It took me a while to figure this out – just couldn’t dedicate time to it – but finally got it working again:<\/p>\n
\n[6\/21\/2017, 4:20:12 PM] [Garage Door] Error ‘null’ setting door state. Response: {“error”:”invalid_token”,”error_description”:”The access token provided is invalid.”}
\n[6\/21\/2017, 4:20:14 PM] [Garage Door] state = 1
\n[6\/21\/2017, 4:20:14 PM] [Garage Door] Set state to closed
\n[6\/21\/2017, 4:20:14 PM] [Garage Door] Error ‘null’ setting door state. Response: {“error”:”invalid_token”,”error_description”:”The access token provided is invalid.”}<\/p>\n
\nTo update npm:
\nsudo npm install -g npm<\/p>\n
\nsudo npm outdated -g<\/p>\n
\nsudo npm install -g -unsafe-perm homebridge@latest -g<\/p>\n
\nsudo npm install -g -unsafe-perm homebridge-pluginname@latest -g
\nsudo npm install -g -unsafe-perm homebridge-nest@latest -g
\nsudo npm install -g -unsafe-perm homebridge-platform-wemo@latest -g
\nsudo npm install -g -unsafe-perm homebridge-lifx-lan@latest -g
\nsudo npm install -g -unsafe-perm git+https:\/\/github.com\/luisiam\/homebridge-liftmaster2.git -g
\nsudo npm install -g -unsafe-perm homebridge-samsung-tizen<\/p>\n
\nsudo launchctl unload \/Library\/LaunchDaemons\/com.homebridge.server.plist<\/p>\n
\nsudo launchctl load \/Library\/LaunchDaemons\/com.homebridge.server.plist<\/p>\n","protected":false},"excerpt":{"rendered":"