iOS9 and Homekit

Discussions about Z-Way software and Z-Wave technology in general
pofs
Posts: 688
Joined: 25 Mar 2011 19:03

Re: iOS9 and Homekit

Post by pofs » 27 Sep 2015 14:20

AlphaX2 wrote: In the logs it seem's fine: http://pastebin.com/c6e9ymfG :roll:
It only seems fine. In some beta iOS SDK there was an incorrect uuid for Battery service, so it became invalid in module's constants too. Instead of battery, it treats it like carbon monoxide sensor, and it obviously lacks a few mandatory characteristics, like CO level.

You might want to update to the latest GitHub version of HomeKitGate, where this error is corrected.

AlphaX2
Posts: 110
Joined: 25 Jul 2015 15:03

Re: iOS9 and Homekit

Post by AlphaX2 » 27 Sep 2015 15:30

Thank you very much for the hint! :)

Thanks.

vga
Posts: 59
Joined: 18 Dec 2014 11:28

Re: iOS9 and Homekit

Post by vga » 03 Oct 2015 17:21

Hi,
I have a similar problem:

iPhone: iOS: 9.0.2
Razberry: z-way-server: v2.1.2-rc3-internal-7-gd1fc157

Trying to pair razberry with iPhone. See razberry as an accessory on iPhone App (eve, or HomeKitDemo), can identify the razberry and get the HomeKit PIN in the z-way-log. When entering the PIN on iPhone App I get an error on iPhone screen: "Adding failed".
In z-way-server-log there is no output at the paring time.
In iPhone-device-log I get the following:

Code: Select all

Oct  3 16:13:28 iPhone homed[146] <Error>: Mandatory characteristic 0000008F-0000-1000-8000-0026BB765291 not present in service 00000096-0000-1000-8000-0026BB765291
Oct  3 16:13:28 iPhone homed[146] <Error>: ### Service failed _validateMandatoryCharacteristics
Oct  3 16:13:28 iPhone homed[146] <Error>: ### Service failed validateServiceType
Oct  3 16:13:28 iPhone homed[146] <Error>: ### HAPService failed _updateAndValidateCharacteristics
Oct  3 16:13:28 iPhone homed[146] <Error>: ### Unable to parse serialized service.
Oct  3 16:13:28 iPhone homed[146] <Error>: ### Unable to parse serialized service
Oct  3 16:13:28 iPhone homed[146] <Error>: ### Unable to parse serialized accessory
Oct  3 16:13:28 iPhone homed[146] <Error>: [HAP Service Discovery] Failed HAP service discovery on accessory server <HAPAccessoryServerIP: 0x13e578e90>    Device ID: c1:03:ca:f8:b3:ba    Model: RaZberry    Protocol Version: 1.0    Source Version: (null)    Config Number: 17    Category: 1    Status Flags: 0x1 with error: Error Domain=HMErrorDomain Code=66 "(null)"
With iOS8 all worked fine, after update to iOS9 I´ve got this problem.
Any idea to figure out the problem?

Best Regards,
Dave

vga
Posts: 59
Joined: 18 Dec 2014 11:28

Re: iOS9 and Homekit

Post by vga » 04 Oct 2015 17:32

no idea?
I also reset the z-way server to factory-defaults, but still paring failed? :(

Edit:
Sorry, after reading the whole thread again, i noticed that i have to upload the HomeKitGate module folder from github repository, to fix the issue. Now it is working again. ;)

Edit:
After adding and controlling accessories works fine yesterday - today after truning home the HomeKit App didn't reach the accessory anymore. - paring also doesn´t work. anymore :(

vga
Posts: 59
Joined: 18 Dec 2014 11:28

Re: iOS9 and Homekit

Post by vga » 09 Oct 2015 01:13

here is my accessory dump:
https://gist.github.com/anonymous/3c40b49ada8369ec57a0
is there something wrong with that?

(Edit: renew gisthub link, with self formatted dump output, for better reading!)

pofs
Posts: 688
Joined: 25 Mar 2011 19:03

Re: iOS9 and Homekit

Post by pofs » 09 Oct 2015 10:54

Have you updated to ghe latest github version of HomeKitGate module? As I said, the bundled one has errors which were not released yet as a part of rc-build.

vga
Posts: 59
Joined: 18 Dec 2014 11:28

Re: iOS9 and Homekit

Post by vga » 09 Oct 2015 11:01

Version: v2.1.2-rc3-internal-7-gd1fc157
And from: https://github.com/Z-Wave-Me/home-autom ... er/modules
i´ve took the HomeKitGate folder and replaced it on my razberry system

vga
Posts: 59
Joined: 18 Dec 2014 11:28

Re: iOS9 and Homekit

Post by vga » 09 Oct 2015 13:20

Now I realize:
I took the "master" branch, should i take "develop" branch instead?

Edit: I took the develop branch HomeKitGate folder, but also: "paring failed"
Does this z-way-log helps debugging?:

Code: Select all

[2015-10-09 21:50:16.865] [I] [core] Notification: info (module): HomeKit PIN: 300-18-125
[2015-10-09 21:50:26.765] [D] [zway] RECEIVED: ( 01 0C 00 04 00 04 06 56 01 84 07 CC 39 D4 )
[2015-10-09 21:50:26.766] [D] [zway] SENT ACK
[2015-10-09 21:50:26.768] [D] [zway] SETDATA devices.4.data.lastReceived = 0 (0x00000000)
[2015-10-09 21:50:26.769] [I] [zway] Node 4:0 CC Wakeup: Wakeup notification
[2015-10-09 21:50:26.770] [D] [zway] SETDATA devices.4.instances.0.commandClasses.132.data.lastWakeup = 1444420226 (0x56181a82)
[2015-10-09 21:50:26.772] [D] [zway] SETDATA devices.4.data.isAwake = True
[2015-10-09 21:50:26.773] [D] [zway] SETDATA devices.4.data.lastSend = 8932 (0x000022e4)
[2015-10-09 21:50:26.775] [D] [zway] SETDATA devices.4.data.lastNonceGet = 7932 (0x00001efc)
[2015-10-09 21:50:26.782] [D] [zway] Running wakeup handler for node 4
[2015-10-09 21:50:26.784] [D] [zway] SETDATA devices.4.instances.0.commandClasses.132.data.lastSleep = 1444420226 (0x56181a82)
[2015-10-09 21:50:26.785] [I] [zway] Node 4:0 CC Wakeup: Send node to sleep
[2015-10-09 21:50:26.786] [I] [zway] Adding job: Wakeup Sleep
[2015-10-09 21:50:26.839] [D] [zway] SENDING (cb 0x01): ( 01 09 00 13 04 02 84 08 05 01 6B )
[2015-10-09 21:50:26.842] [D] [zway] RECEIVED ACK
[2015-10-09 21:50:26.845] [D] [zway] RECEIVED: ( 01 04 01 13 01 E8 )
[2015-10-09 21:50:26.846] [D] [zway] SENT ACK
[2015-10-09 21:50:26.847] [D] [zway] Delivered to Z-Wave stack
[2015-10-09 21:50:26.858] [D] [zway] RECEIVED: ( 01 05 00 13 01 00 E8 )
[2015-10-09 21:50:26.859] [D] [zway] SENT ACK
[2015-10-09 21:50:26.861] [I] [zway] Job 0x13 (Wakeup Sleep): Delivered
[2015-10-09 21:50:26.862] [D] [zway] SETDATA devices.4.data.lastPacketInfo.delivered = True
[2015-10-09 21:50:26.863] [D] [zway] SETDATA devices.4.data.lastPacketInfo.packetLength = 5 (0x00000005)
[2015-10-09 21:50:26.865] [D] [zway] SETDATA devices.4.data.lastPacketInfo.deliveryTime = 13 (0x0000000d)
[2015-10-09 21:50:26.868] [D] [zway] SETDATA devices.4.data.lastPacketInfo = **********
[2015-10-09 21:50:26.873] [D] [zway] SendData Response with callback 0x01 received: received by recipient
[2015-10-09 21:50:26.874] [D] [zway] SETDATA devices.4.data.lastSend = 8940 (0x000022ec)
[2015-10-09 21:50:26.876] [D] [zway] Job 0x13 (Wakeup Sleep): success
[2015-10-09 21:50:26.877] [D] [zway] SETDATA devices.4.data.isAwake = False
[2015-10-09 21:50:26.881] [D] [zway] Sending the queue for node 4 into sleep
[2015-10-09 21:50:26.883] [I] [zway] Removing job: Wakeup Sleep
[2015-10-09 21:50:47.212] [D] [zway] Job 0x13: deleted from queue
I do not know how to continue. Slowly it becomes frustrating :(

bdo
Posts: 3
Joined: 13 Oct 2015 18:40

Re: iOS9 and Homekit

Post by bdo » 13 Oct 2015 20:37

The OpenWeather app doesn't work for me either, but after removing it, I got an additional error with my Danfoss Living Connect Thermostat. It seems, the bridge can't handle the battery device of the thermostat. Here's the config entry in automation/storage:
"ZWayVDev_zway_3-0-128":{"deviceType":"battery","metrics":{"probeTitle":"Battery","scaleTitle":"%","level":95,"icon":"battery","title":"Battery 3-0 Danfoss"}
and here's the corresponding log entry when the server tries to add the battery device:

Code: Select all

[2015-10-13 19:28:04.058] [I] [core] Creating device thermostat ZWayVDev_zway_3-0-67-1
[2015-10-13 19:28:04.079] [I] [core] HK: added ZWayVDev_zway_3-0-67-1
[2015-10-13 19:28:04.143] [I] [core] Creating device battery ZWayVDev_zway_3-0-128
[2015-10-13 19:28:04.167] [I] [core] HK: added ZWayVDev_zway_3-0-128
[2015-10-13 19:28:04.195] [I] [core] Notification: error (core): Cannot create vDev based on: 3-0-128: Error: Invlid type UUID
[2015-10-13 19:28:04.274] [I] [core] Error: Invlid type UUID
    at new HKCharacteristic (zway/homekit:270:15)
    at HKService.addCharacteristic (zway/homekit:244:26)
    at onDeviceAddedCore (automation/modules/HomeKitGate/index.js:437:13)
    at onDeviceAdded (automation/modules/HomeKitGate/index.js:457:3)
    at EventEmitter.emit (automation/lib/eventemitter2.js:339:30)
    at _.extend.create (automation/classes/DevicesCollection.js:51:18)
    at ZWave.parseAddCommandClass (automation/modules/ZWave/index.js:1725:39)
    at ZDataHolder.<anonymous> (automation/modules/ZWave/index.js:1191:12)
    at ZWave.dataBind (automation/modules/ZWave/index.js:1006:10)
    at ZWaveCommandClass.<anonymous> (automation/modules/ZWave/index.js:1120:9)
Any ideas what to do? I tried with revision afb23611479f8d538a253ebfc8fc551af05f8696.

Edit:
Commenting the corresponding code for device type battery makes the module work, even though that might not be the best solution ;). Is it due to Apple restrictions regarding certified hardware/bridges that only the power switches are visible in Eve?

vga
Posts: 59
Joined: 18 Dec 2014 11:28

Re: iOS9 and Homekit

Post by vga » 14 Oct 2015 00:59

thanks for that info.
i removed my danfoss Living Conect thermostat, but still couldn´t pair.

Also, I got this z-way-log output:

Code: Select all

[2015-10-13 23:37:26.856] [D] [zway] SETDATA devices.4.data.lastReceived = 0 (0x00000000)
[2015-10-13 23:37:26.857] [E] [zway] Packet CC::MULTI_CHANNEL_CMD_ENCAP_V2 is too short: required at least 5 bytes, got 3
[2015-10-13 23:37:26.858] [E] [zway] Error returned from _zway_cc_call_handler(zway, command, controller->id, 0, data[4], &data[5]): Wrong packet from Z-Wave network or Discovery got bad data (stick communication failed) (-9)
[2015-10-13 23:26:13.668] [D] [zway] SETDATA devices.4.data.lastReceived = 0 (0x00000000)
[2015-10-13 23:26:13.670] [D] [zway] SETDATA devices.4.instances.0.commandClasses.48.data.1.level = True
[2015-10-13 23:26:13.671] [D] [zway] SETDATA devices.4.instances.0.commandClasses.48.data.1 = Empty
[2015-10-13 23:26:13.686] [D] [zway] RECEIVED: ( 01 09 00 04 00 04 03 60 0D 01 99 )
[2015-10-13 23:26:13.687] [D] [zway] SENT ACK
So I excluded device 4 "Fibaro Multi Sensor" too.
Now HomeKit paring works!

Is it because of the multilevel/meter characteristics of these devices, or what else?
Is there a way to fix/workaround this problem by myself, without exclude/commenting code, maybe modifying some characteristics?

Hope there will be a fix in next z-way server release.

Post Reply