Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jc2k
    @Jc2k
    i guess another factor is the tado isn't some unknown brand either - it's Apple certified enough to be on their store:
    Joachim Lusiardi
    @jlusiardi
    agreed, it wasn't a specific issue with that PR more a general "how can we be sure"
    Jc2k
    @Jc2k
    yeah, its definitely a worry
    best i have right now is that going forward part of the PR is capturing logs from a real iOS device and homekit_python and the PR has to move things in the direction of byte-for-byte perfection to be merged.
    Jc2k
    @Jc2k
    we probably need a regression test harness too
    e.g. for previous PR i'd add one test that said pairing headers must equal exactly the ones we currently send otherwise we risk breaking device X
    seperate test for paired comms
    Joachim Lusiardi
    @jlusiardi
    at least some documentation why we did what?
    Jc2k
    @Jc2k
    yes
    ideally links to tickets
    Joachim Lusiardi
    @jlusiardi
    mh yes
    i'll be afk for the evening
    Jc2k
    @Jc2k
    that might even reference HA tickets - so we can try and track down an owner with one if we need them to test it
    ok
    not sure what my plans are yet - want to have a look at my Eve Energy for #125
    Joachim Lusiardi
    @jlusiardi
    What is also not the best way: we only know which devices we had to work on to support them. Not which one worked out of the box 😕
    Jc2k
    @Jc2k
    @jlusiardi are there any tickets you want to address before we do another release? (it would be good to be able to roll out the tado fixes in HA soon, and to get the pairing flow change added to HA too)
    Joachim Lusiardi
    @jlusiardi
    hi @Jc2k, i will have a look!
    what do you think about the last comment on jlusiardi/homekit_python#129
    Joachim Lusiardi
    @jlusiardi
    I think i can make a 0.14 tomorrow
    enough features are there
    ;)
    Jc2k
    @Jc2k
    \o/
    having a think about #129
    not sure what we can do, short of acquiring a Smartbar
    pcap would help potentially, i guess the failure is happening before the messages are encrypted
    Jc2k
    @Jc2k
    it dropping the connection after our M3 makes me think it could still be a difference between how an iPhone pairing looks vs how ours looks, rather than it being a different pairing system for software authentication vs MFi hardware auth.
    i know there is still at least one deviation from how apples implementation looks on the wire. looks like apple sends the bonjour service name rather than ip in Host header - but would be surprised if that tripped us up at the M3 and not the M1
    Joachim Lusiardi
    @jlusiardi
    It also looks strange to me how this message was communicated. The GitHub account does not seem official or „old“
    It also would imply there is some difference how devices are paired.
    Joachim Lusiardi
    @jlusiardi
    @Jc2k release done, 0.14.0 is on pypi!
    🎉 and stuff
    Jc2k
    @Jc2k
    :fireworks: yay, thank you
    Joachim Lusiardi
    @jlusiardi
    you're welcome ;)
    Joachim Lusiardi
    @jlusiardi
    @/all I started to list supported devices in https://github.com/jlusiardi/homekit_python/tree/add_device_reports/doc/tested_devices can you contribute yours please?
    Anton Panasenko
    @dieu

    Hey folks, maybe a silly question, but could I pair/connect to device which already connected to homekit?

    from the doc I got a sense that prepare_add_remote_pairing is what I'm looking for, is right?

    @jlusiardi ^^^
    Jc2k
    @Jc2k
    If your device is already connected to an iOS device then you can't (easily) use it with homekit_python.
    the "add remote pairing" process lets you create multiple keypairs that can share access to a device, but you still need to have a working keypair in th first place.
    Jc2k
    @Jc2k
    Technically, however, I recently became aware of this process: https://pvieito.com/2019/12/extract-homekit-pairing-keys
    It's a manual process and involves having a macOS machine with x-code (which needs to be signed in to your icloud account) and needs you to disable various security mechanisms in macOS. The code as it comes has bugs, so you need to pull together fixes from open PR's in that repo and its upstreams.
    It's very much not supported, here be dragons, if you break it you get to keep the pieces.
    Joachim Lusiardi
    @jlusiardi
    We had a similar question in jlusiardi/homekit_python#205... but @Jc2k seems to have news...
    Jc2k
    @Jc2k
    I stumbled onto it yesterday/day before, was meaning to update that issue with it! :) but its quite a high entry threshold and might stop working (theres nothing about this in the HAP spec (of course), so its very much open for further security hardening etc and could disappear in any future macOS release)
    Joachim Lusiardi
    @jlusiardi
    yeah definitely not easy to use but pretty cool never the less. I guess the key sharing via iCloud is not much a Homekit thing at all. There is a good reason (security) you cannot read them easily ;)
    Jc2k
    @Jc2k
    indeed!
    it means i can use my Hive thermostat now though (they don't give you a pairing code so no way to use it with homekit_python's normal pairing process)
    don't know whether the Hive app is entering the code for me behind the scenes or whether there is another undocumented pairing flag for apps to use
    Joachim Lusiardi
    @jlusiardi
    so you can only use the Hive thermostats with the app?
    Jc2k
    @Jc2k
    you can use them from the official homekit app, but only after you have paired them with the official app.