@GuybrushMR80 When i’m developing, i’m starting a dev homekit bridge, which i remove and add without any problems. So this works without any problems. Apart from deleting the hap-database folder in pimatic and resetting the homekit settings, i don’t know what else to do.
-
[pimatic-hap] Support for pimatic homekit bridge
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
Sorry for my late answer. Today i had time to check the debug messages when i try to add my pimatic in Home on iOS.
20:20:05.474 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] HAP Request: POST /pair-setup
20:20:05.512 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Pair step 1/5
20:20:19.358 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] HAP Request: POST /pair-setup
20:20:19.378 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Pair step 2/5
20:20:19.873 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] HAP Request: POST /pair-setup
20:20:19.890 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Pair step 3/5
20:20:19.980 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Pair step 4/5
20:20:19.997 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Pair step 5/5
20:20:20.036 [pimatic-hap] debug: [Pimatic HomeKit Bridge] Paired with client D2627D0C-B0D8-4177-9466-19EB8885E6EC
20:20:20.174 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] HAP Request: POST /pair-verify
20:20:20.206 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Pair verify step 1/2
20:20:20.314 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] HAP Request: POST /pair-verify
20:20:20.333 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Pair verify step 2/2
20:20:20.356 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Client D2627D0C-B0D8-4177-9466-19EB8885E6EC verification complete
20:20:20.425 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] HAP Request: GET /accessories
20:20:22.593 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] HAP Request: POST /pairings
20:20:22.615 [pimatic-hap] debug: [fa:fe:db:e4:36:2c] Removing pairing info for client
20:20:22.623 [pimatic-hap] debug: [Pimatic HomeKit Bridge] Unpairing with client D2627D0C-B0D8-4177-9466-19EB8885E6ECI hope this helps finding the problem.
Regards daice
-
@daice it seems that after pairing you are immediately unpaired again. Unfortunately it doesn’t tell me why. I think it could help if you delete the hap-database folder in your pimatic installation and then restart pimatic. Then please try to pair with the HomeKit bridge again. My guess is, that in the database a different client is already registered and that’s why you are immediately unpaired.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
I have deleted the database and resarted pimatic, deleted database + complete plugin and tried to reset my phone/icloud.
It is not working for me… -
@daice that’s all I can say. There’s not really more you can do. Anyone experienced the same problems?
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
@daice Have you renamed the Pimatic Bridge? After I have upgraded to pimatic v0.9 I needed to rename it to make it work again. Best regards, Frank
-
Thanks for the hint but it doesn’t work for me. I also tried to change the pin, without success.
-
@daice All you can do is to delete the hap-database folder, reset your homekit settings on your apple device and restart pimatic. Sorry if that doesn’t work for you.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
Just to let you all know, i’ve just released version 0.8.1 of pimatic-hap. I definitely hope this fixes some of the infinite loops issues some of you guys have. Please test and report if there are any issues.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
latest version works fine, no problem with turning on after startup anymore and have not yet seen an infinite loop
btw you don’t have to apologize if you don’t accept my pull request your reasoning was 100% right
Note:
I was removing the whole plugin to get rid of my patched version of the plugin and then started pimatic again so that it would install the plugin fresh from npm.
After this the plug in would not start.
From the error message I could see that it was a problem with the mdns dependancies. Looks like the pimatic setup routines might have a problem with gyp builds?
To fix it I removed the node-modules folder and did a freshsudo npm install --unsafe-perm
from the console.
Maybe @sweetpi should have a look at it. -
I’ve updated pimatic-hap via web interface and got the following errors:
12:37:25.688 [pimatic] info: Installing: “pimatic-hap@0.8.2” from npm-registry.
12:37:42.878 [pimatic, ppm] info: > curve25519@1.1.0 install /home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/node_modules/curve25519
12:37:42.883 [pimatic, ppm] info: > node-gyp rebuild
12:37:58.362 [pimatic, ppm] info: make: Entering directory '/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/node_modules/curve25519/build’
12:37:58.366 [pimatic, ppm] info: CXX(target) Release/obj.target/curve/node_curve.o
12:39:31.211 [pimatic-pio-remote] info: Received: LM0102
12:39:31.211 [pimatic-pio-remote] info:>
12:39:36.589 [pimatic, ppm] info: SOLINK_MODULE(target) Release/obj.target/curve.node
12:39:36.981 [pimatic, ppm] info: COPY Release/curve.node
12:39:37.014 [pimatic, ppm] info: make: Leaving directory '/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/node_modules/curve25519/build’
12:39:37.118 [pimatic] error: Error installing plugin pimatic-hap: Error running "./node_modules/pimatic/ppm.js install pimatic-hap@0.8.2 --unsafe-perm"
12:39:37.123 [pimatic] debug: Error: Error running "./node_modules/pimatic/ppm.js install pimatic-hap@0.8.2 --unsafe-perm"
12:39:37.123 [pimatic] debug:> at ChildProcess.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic/lib/plugins.coffee:366:24)
12:39:37.123 [pimatic] debug:> at emitTwo (events.js:87:13)
12:39:37.123 [pimatic] debug:> at ChildProcess.emit (events.js:172:7)
12:39:37.123 [pimatic] debug:> at maybeClose (internal/child_process.js:827:16)
12:39:37.123 [pimatic] debug:> at Socket.<anonymous> (internal/child_process.js:319:11)
12:39:37.123 [pimatic] debug:> at emitOne (events.js:77:13)
12:39:37.123 [pimatic] debug:> at Socket.emit (events.js:169:7)
12:39:37.123 [pimatic] debug:> at Socket.emit (/home/osmc/pimatic-app/node_modules/pimatic/startup.coffee:63:24)
12:39:37.123 [pimatic] debug:> at Pipe._onclose (net.js:477:12)After restarting Pimatic:
…
12:40:30.285 [pimatic] info: Loading plugin: “pimatic-hap” (0.8.2)
coffee-cache: compiling coffee-script file “hap.coffee”…Done
coffee-cache: compiling coffee-script file “accessories/button.coffee”…Done
12:40:31.045 [pimatic] error: Cannot find module '…/build/Release/dns_sd_bindings’
12:40:31.089 [pimatic] debug: Error: Cannot find module '…/build/Release/dns_sd_bindings’
12:40:31.089 [pimatic] debug:> at Function.Module._resolveFilename (module.js:325:15)
12:40:31.089 [pimatic] debug:> at Function.Module._load (module.js:276:25)
12:40:31.089 [pimatic] debug:> at Module.require (module.js:353:17)
12:40:31.089 [pimatic] debug:> at require (internal/module.js:12:17)
12:40:31.089 [pimatic] debug:> at Object.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/node_modules/mdns/lib/dns_sd.js:32:22)
12:40:31.089 [pimatic] debug:> at Module._compile (module.js:409:26)
12:40:31.089 [pimatic] debug:> at Object.Module._extensions…js (module.js:416:10)
12:40:31.089 [pimatic] debug:> at Module.load (/home/osmc/pimatic-app/node_modules/pimatic-mobile-frontend/node_modules/nap/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
12:40:31.089 [pimatic] debug:> at Function.Module._load (module.js:300:12)
12:40:31.089 [pimatic] debug:> at Module.require (module.js:353:17)
12:40:31.089 [pimatic] debug:> at require (internal/module.js:12:17)
12:40:31.089 [pimatic] debug:> at Object.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/node_modules/mdns/lib/mdns.js:1:15)
12:40:31.089 [pimatic] debug:> at Module._compile (module.js:409:26)
12:40:31.089 [pimatic] debug:> at Object.Module._extensions…js (module.js:416:10)
12:40:31.089 [pimatic] debug:> at Module.load (/home/osmc/pimatic-app/node_modules/pimatic-mobile-frontend/node_modules/nap/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
12:40:31.089 [pimatic] debug:> at Function.Module._load (module.js:300:12)
12:40:31.089 [pimatic] debug:> at Module.require (module.js:353:17)
12:40:31.089 [pimatic] debug:> at require (internal/module.js:12:17)
12:40:31.089 [pimatic] debug:> at Object.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/Advertiser.js:1:12)
12:40:31.089 [pimatic] debug:> at Module._compile (module.js:409:26)
12:40:31.089 [pimatic] debug:> at Object.Module._extensions…js (module.js:416:10)
12:40:31.089 [pimatic] debug:> at Module.load (/home/osmc/pimatic-app/node_modules/pimatic-mobile-frontend/node_modules/nap/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
12:40:31.089 [pimatic] debug:> at Function.Module._load (module.js:300:12)
12:40:31.089 [pimatic] debug:> at Module.require (module.js:353:17)
12:40:31.089 [pimatic] debug:> at require (internal/module.js:12:17)
12:40:31.089 [pimatic] debug:> at Object.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/lib/Accessory.js:10:18)
12:40:31.089 [pimatic] debug:> at Module._compile (module.js:409:26)
12:40:31.089 [pimatic] debug:> at Object.Module._extensions…js (module.js:416:10)
12:40:31.089 [pimatic] debug:> at Module.load (/home/osmc/pimatic-app/node_modules/pimatic-mobile-frontend/node_modules/nap/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
12:40:31.089 [pimatic] debug:> at Function.Module._load (module.js:300:12)
12:40:31.089 [pimatic] debug:> at Module.require (module.js:353:17)
12:40:31.089 [pimatic] debug:> at require (internal/module.js:12:17)
12:40:31.089 [pimatic] debug:> at Object.<anonymous> (/home/osmc/pimatic-app/node_modules/pimatic-hap/node_modules/hap-nodejs/index.js:1:17)
12:40:31.089 [pimatic] debug:> at Module._compile (module.js:409:26)
12:40:31.089 [pimatic] debug:> at Object.Module._extensions…js (module.js:416:10)
12:40:31.089 [pimatic] debug:> at Module.load (/home/osmc/pimatic-app/node_modules/pimatic-mobile-frontend/node_modules/nap/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
12:40:31.089 [pimatic] debug:> at Function.Module._load (module.js:300:12)
12:40:31.089 [pimatic] debug:> at Module.require (module.js:353:17)
12:40:31.089 [pimatic] debug:> at require (internal/module.js:12:17)
12:40:31.089 [pimatic] debug:> at module.exports (/home/osmc/pimatic-app/node_modules/pimatic-hap/accessories/button.coffee:3:9)
12:40:31.089 [pimatic] debug:> at /home/osmc/pimatic-app/node_modules/pimatic-hap/hap.coffee:7:21
12:40:31.089 [pimatic] debug:> at PluginManager.loadPlugin (/home/osmc/pimatic-app/node_modules/pimatic/lib/plugins.coffee:83:16)
12:40:31.089 [pimatic] debug:> at /home/osmc/pimatic-app/node_modules/pimatic/lib/plugins.coffee:477:25
12:40:31.089 [pimatic] debug:> at tryCatcher (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
12:40:31.089 [pimatic] debug:> at Promise._settlePromiseFromHandler (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:503:31)
12:40:31.089 [pimatic] debug:> at Promise._settlePromise (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:560:18)
12:40:31.089 [pimatic] debug:> at Promise._settlePromiseCtx (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:597:10)
12:40:31.089 [pimatic] debug:> at Async._drainQueue (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:12)
12:40:31.089 [pimatic] debug:> at Async._drainQueues (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:136:10)
12:40:31.089 [pimatic] debug:> at Immediate.Async.drainQueues [as _onImmediate] (/home/osmc/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:16:14)
12:40:31.089 [pimatic] debug:> at processImmediate [as _immediateCallback] (timers.js:383:17)
… -
@GooglyEyz Did the update run fine? It seems that something didn’t work. Just remove the pimatic-hap folder from node_modules and restart pimatic. It should install the latest version again. If there are any errors while installing please report.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
seems to be the same Issue I had see note in post
@thex said in [pimatic-hap] Support for pimatic homekit bridge:
latest version works fine, no problem with turning on after startup anymore and have not yet seen an infinite loop
btw you don’t have to apologize if you don’t accept my pull request your reasoning was 100% right
Note:
I was removing the whole plugin to get rid of my patched version of the plugin and then started pimatic again so that it would install the plugin fresh from npm.
After this the plug in would not start.
From the error message I could see that it was a problem with the mdns dependancies. Looks like the pimatic setup routines might have a problem with gyp builds?
To fix it I removed the node-modules folder and did a freshsudo npm install --unsafe-perm
from the console.
Maybe @sweetpi should have a look at it. -
No, update had some errors, as you can see in the 1st part of the logs above. But reinstallation after removing the folder and restarting Pimatic worked fine. Thanks.
-
Now that my original post (https://forum.pimatic.org/topic/1003/pimatic-plugin-as-apple-homekit-bridge) reached the 70k view mark i released version 0.9.0 and catched up with pimatic in version numbers .
This time there are some nice features:- #42 and #51 Added GenericAccessory, which adds Services based on attributes
- Remove device from HomeKit if removed from pimatic
- Updated to hap-nodejs 0.4.13
With the update of hap-nodejs, pimatic-hap will be able to add support for the new iOS 10 HomeKit features, like door bell and camera. But before you get crazy, I’m not sure if the camera support will ever make it into pimatic-hap.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
Sounds GREAT, will test as soon as I’m at home.
Love the approach for generic sensors. Maybe this could be configurable?
-
@thex We’ll see, but I don’t want to make the plugin to complicated. Currently i like the simple usage: Install and it works.
pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
Sure I’m totally with you
some config options with default values like
Temerature Property Keywords: temperature,Temperature,temp,heating
Humidity Property Keywords: hum,Humidity,humi,RaumfeuchteAnd I think this could maybe easily be extended to other property types supported by homekit (Airquallity etc)
-
@thex i would say that one can change the attribute to “temperature” if this should work. There is no need for a complicated config.
About other attributes like air quality: every new attribute needs a change of the plugin.pimatic-hap - pimatic HomeKit bridge
pimatic-echo - Amazon echo integration
pimatic-dash-button - Amazon dash button support
pimatic-alarm - pimatic alarm system
Like my work? Then consider a donation
Follow me: https://twitter.com/michaelkotten -
Works like a charm! Now netatmo temperature and humidity work out off the box.