News about HomeKit and Vera

[rafale77]

I think I found the problem. I will test make a push on git.

[Hackworth]

Yeah, it looks like he reversed the logic of this for...I don't know why? I'm sorry, I should have looked at it closer before merging it in, I don't have a lock so it was not on my mind.

[Hackworth]

Okay. Do a git pull and test, please

[rafale77]

Ok other problem is that it is seen as a switch, not a lock because there is an error in the device definition. I will get this changed too.

[rafale77]

Alright after pulling my hair a bit I found out that the version before your edit had the correct logic if the lock device was recognized by homekit as a lock. As it is, it is broadcasted as a light switch which causes the need to invert the logic.

I have it working correctly as a door as seen by Eve (and I assume homekit) with a modified Lock.js but siri does not see any door lock. I assume this was the reason why this accessory used the trick to be disclosed as a power switch. Not sure what else to do as siri clearly knows to look for a door lock.

[rlmalisz]

How annoying.

DEBUG=* npm run start

So starting from scratch (rm -rf persist) on the server and killing Eve and resetting the HomeKit on my phone with the iPad on Airplane Mode, I get this sequence:

....
Create accessory: Toggle center door
Create accessory: Toggle north door
Create accessory: Toggle south door
Create accessory: W Greenhouse Door Opened
  EventedHTTPServer Server listening on port 51826 +0ms
  EventedHTTPServer [::ffff:192.168.1.28] New connection from client +14s
  EventedHTTPServer [::ffff:192.168.1.28] HTTP server listening on port 54826 +1ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP request: /pair-setup +4ms
  HAPServer [CC:22:3D:E3:CE:F6] HAP Request: POST /pair-setup +0ms
  HAPServer [CC:22:3D:E3:CE:F6] Pair step 1/5 +1ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP Repsonse is finished +16ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP request: /pair-setup +10s
  HAPServer [CC:22:3D:E3:CE:F6] HAP Request: POST /pair-setup +0ms
  HAPServer [CC:22:3D:E3:CE:F6] Pair step 2/5 +1ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP Repsonse is finished +21ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP request: /pair-setup +15ms
  HAPServer [CC:22:3D:E3:CE:F6] HAP Request: POST /pair-setup +0ms
  HAPServer [CC:22:3D:E3:CE:F6] Pair step 3/5 +1ms
  HAPServer [CC:22:3D:E3:CE:F6] Pair step 4/5 +10ms
  HAPServer [CC:22:3D:E3:CE:F6] Pair step 5/5 +2ms
  Accessory [Vera Bridge] Paired with client 21897FE4-D83E-494E-B387-D5C6B362CCF4 +2ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP Repsonse is finished +9ms
  EventedHTTPServer [::ffff:192.168.1.28] Client connection closed +69ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP connection was closed +1ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP server was closed +0ms
  EventedHTTPServer [::ffff:192.168.1.28] New connection from client +1s
  EventedHTTPServer [::ffff:192.168.1.28] HTTP server listening on port 54826 +1ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP request: /pair-verify +2ms
  HAPServer [CC:22:3D:E3:CE:F6] HAP Request: POST /pair-verify +0ms
  HAPServer [CC:22:3D:E3:CE:F6] Pair verify step 1/2 +1ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP Repsonse is finished +4ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP request: /pair-verify +23ms
  HAPServer [CC:22:3D:E3:CE:F6] HAP Request: POST /pair-verify +0ms
  HAPServer [CC:22:3D:E3:CE:F6] Pair verify step 2/2 +1ms
  HAPServer [CC:22:3D:E3:CE:F6] Client 21897FE4-D83E-494E-B387-D5C6B362CCF4 verification complete +2ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP Repsonse is finished +1ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP request: /accessories +42ms
  HAPServer [CC:22:3D:E3:CE:F6] HAP Request: GET /accessories +1ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP Repsonse is finished +11ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP request: /pairings +405ms
  HAPServer [CC:22:3D:E3:CE:F6] HAP Request: POST /pairings +0ms
  HAPServer [CC:22:3D:E3:CE:F6] Removing pairing info for client +1ms
  Accessory [Vera Bridge] Unpairing with client 21897FE4-D83E-494E-B387-D5C6B362CCF4 +0ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP Repsonse is finished +4ms
  EventedHTTPServer [::ffff:192.168.1.28] Client connection closed +112ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP connection was closed +0ms
  EventedHTTPServer [::ffff:192.168.1.28] HTTP server was closed +1ms

At this point, I have the "adding failed" message on my phone.  It looks from the above like all went well, but I guess not.

The server is running Ubuntu 14.04.  "node -v" gives "v5.2.0".  I made sure the firewall was disabled, had no effect.

FWIW, I have uninstalled Eve and reinstalled, in case it was hanging on to some bad state.  Made no difference.

--Richard

[rafale77]

Hackworth, I figured it out. I have a fully working lock accessory I am pulling on your repo. Please merge!

[JuniorJedi]

Hmmmm...everything was fine until some time early this morning when Vera stopped responding to Siri.

Now when I nam run start I see the accessories created and then this:

Create accessory: Welcome Home Light
/home/pi/VeraHomeKitBridge/lib/HAP-NodeJS/node_modules/mdns/lib/advertisement.js:56
  dns_sd.DNSServiceRegister(self.serviceRef, flags, ifaceIdx, name,
         ^
Error: dns service error: name conflict
    at Error (native)
    at new Advertisement (/home/pi/VeraHomeKitBridge/lib/HAP-NodeJS/node_modules/mdns/lib/advertisement.js:56:10)
    at Object.create [as createAdvertisement] (/home/pi/VeraHomeKitBridge/lib/HAP-NodeJS/node_modules/mdns/lib/advertisement.js:64:10)
    at Advertiser.startAdvertising (/home/pi/VeraHomeKitBridge/lib/HAP-NodeJS/lib/Advertiser.js:43:30)
    at Bridge.Accessory._onListening (/home/pi/VeraHomeKitBridge/lib/HAP-NodeJS/lib/Accessory.js:352:20)
    at HAPServer.emit (events.js:104:17)
    at HAPServer._onListening (/home/pi/VeraHomeKitBridge/lib/HAP-NodeJS/lib/HAPServer.js:159:
    at EventedHTTPServer.emit (events.js:104:17)
    at EventedHTTPServer.<anonymous> (/home/pi/VeraHomeKitBridge/lib/HAP-NodeJS/lib/util/eventedhttp.js:62:10)
    at Server.emit (events.js:104:17)

npm ERR! Linux 3.18.11+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
npm ERR! node v0.12.1
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR! VeraHomeKitBridge@1.0.0 start: `node app.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the VeraHomeKitBridge@1.0.0 start script 'node app.js'.
npm ERR! This is most likely a problem with the VeraHomeKitBridge package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node app.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls VeraHomeKitBridge
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/VeraHomeKitBridge/npm-debug.log


What does it mean? There couldn't possibly be a machine name conflict on my LAN.


Any ideas anyone?

[rafale77]

Are you sure you are not running multiple instances of the bridge with the same name? Did you make sure your first instance was killed before trying a new one?

[JuniorJedi]

Are you sure you are not running multiple instances of the bridge with the same name? Did you make sure your first instance was killed before trying a new one?

Two questions so two answers:

No

No

All sorted - thank you @anhman 

[Kalapa]

@Hackworth - Great Job.
Just installed VeraHomeKitBridge on Linux Mint system and working great via MyTouchHome app.

[Kalapa]

Hmmm .. when I tried the same on "ubuntu container" (Intel Synology)  i get the following error.. it was working fine my Linux Mint box.

npm run start failed with followng msg

Error : dns service error : unknown

Any hints?


 

[Hackworth]

@rlmalisz - I don't know what's going on, it's something particular to your setup.

@Kalapa - Do an npm rebuild in both VeraHomeKitBridge and VeraHomeKitBridge/lib/HAP-NodeJS

[rlmalisz]

Understood.  Could you be so good as to post the "DEBUG=* npm start run" chatter for a non-problem launch and connect?  I can try to drill down on this on my own.  But it would be good to see what success looks like.

--Richard

[Hackworth]

@rlmalisz Absolutely, once I'm home. In the meantime, I've been poking around for other people with the issue and they're suggesting one of your devices is causing it to die. I've got two ideas, one you could look at your http://IPADDRESS:51826/accessories file (after running it through a json formatter service) and see if anything looks wrong, for instance a value is outside a min or max value. The second is you could git checkout 15d263 which is the commit right before I converted this to bridge mode, then go add *every* device individually and note which fails to add.

Also, do you have window coverings or garage doors?